Days Since Calculator – How Many Days Since a Date?

The count, drawn out

The same count as a journey from the day it happened to the next round number — every figure follows the calculator above.

How it works, in 3 steps

The counting behind it

Deep dives

Four fixed spans that teach the whole counter

Type these two dates yourself and the page returns exactly these figures. None of them depends on the day you open the page, so they are safe to check against any other counter.

The first row is the page’s own worked example, and it is the one that catches lazy counters. 28 February 2024 to 1 March 2024 is 2 days, not 1, because 2024 is a leap year and 29 February sits between them. The same two calendar dates in 2025 give 1 day. Any counter that multiplies months or assumes February always has 28 days gets this quietly wrong; real date arithmetic, which this page does by converting each date to a pure day number and subtracting, does not. The weekday evidence confirms it: 28 February 2024 was a Wednesday and 1 March 2024 a Friday, with the leap Thursday in between — two steps forward, two days.

The second row is the trap in the other direction. 31 January 2026 to 28 February 2026 is 28 days — four weeks exactly, and the page calls it “1 month” in calendar terms — even though February 2026 has only 28 days and January has 31. A counter that assumed every month is 30 days would call it 30 days and be wrong by two; a counter that assumed a month is four weeks would be right here by luck and wrong elsewhere. The third and fourth rows complete the lesson: a common year is 365 days (52 weeks and 1 day, which is why 1 January 2027 falls on a Friday, one weekday later than the Thursday of 1 January 2026), while a leap year is 366 days (52 weeks and 2 days, so 1 January 2025 fell on a Wednesday, two weekdays after the Monday of 1 January 2024). The extra day is always exactly one, never a rounding error, and it always lands in February.

Business days: weekdays only, holidays included

The business-day figure on this page counts Monday to Friday and nothing else — and the page says so itself, in a note under the result: public holidays are not subtracted, because they differ by country, state and employer. That honesty matters more than it looks. The 365-day span of 2026 contains 261 business days and 104 weekend days, which adds up exactly (261 + 104 = 365), and the leap-year span contains 262 and 104 (262 + 104 = 366). But a real deadline measured in “working days” in a country with, say, 10 public holidays on weekdays would be about 10 days shorter than the page’s figure. The page’s number is therefore the right starting point and the wrong finishing point for a legal or contractual deadline: use it to get the shape of the span, then subtract your jurisdiction’s holidays yourself, and check which counting rule the authority uses — difference counting, as here, or inclusive counting that treats the starting day as day 1.

The inclusive-versus-exclusive distinction is worth a paragraph of its own because it is where late filings are born. This page counts the difference: between 1 January and 2 January there is one day of difference, but the span touches two calendar dates. Hotels, car hire and age all use the difference — one night, one day, one year older on the birthday itself. Some form deadlines and a few legal and medical counts use the inclusive style, counting the starting day as day 1 (“within 30 days of this notice, counting the day of the notice”). Both numbers exist honestly; they answer different questions. If an official deadline matters to you, the one-day gap between the two rules is exactly where trouble lives, so confirm the rule before trusting any counter, including this one.

Milestones: the dates worth marking

Every span on this page also reports the next 100, 500 or 1,000-day milestone, and those dates are fixed once the starting date is fixed — they do not drift with the day you open the page. Count from 1 January 2026 and day 100 was 11 April 2026, day 500 falls on 16 May 2027, and day 1,000 lands on 27 September 2028. Count from 28 February 2024 instead and day 100 falls on 7 June 2024, while day 1,000 lands on 24 November 2026. Count from 1 January 2024 and day 100 was 10 April 2024, day 500 was 15 May 2025, and day 1,000 lands on 27 September 2026 — note how the leap-year start pulls its 1,000-day milestone a full year earlier than the 2026 start’s, because the leap day sits inside the count. Milestones are the page’s most human feature: a raw count of 296 days means little, but “day 500 falls on 16 May 2027” is a date you can put in a calendar, a dinner you can plan, an anniversary you can actually mark.

There is a quieter use for milestones, too: they are a check on the counter itself. If another tool tells you day 500 from 1 January 2026 is any date other than 16 May 2027, one of the two tools is counting inclusively, or mishandling a leap day, or both — and the table in the first section tells you which kind of error to look for. A one-day disagreement points at the fencepost rule; a one-day disagreement that appears only across February points at the leap year; a disagreement of weeks points at a tool that multiplied months instead of counting days. The milestones turn an abstract argument about counting rules into a single date you can compare.

Why the counter ignores clocks entirely

A calendar day is not always 24 hours. On the spring daylight-saving Sunday the day is 23 hours long; on the autumn one it is 25. A tool that measures elapsed hours and divides by 24 can call a weekend across the spring change “1.96 days” and round it the wrong way, or shave a day off a long span that crosses several changes. A tool on a server in another time zone can be a whole date ahead of you. So this page never looks at a clock: each date is converted to a pure day number — a count of calendar days from a fixed day zero — using integer arithmetic on the year, month and day alone, and the answer is the difference of two day numbers. Twenty-three-hour days, twenty-five-hour days and your time zone cannot touch it, and picking the same date twice gives a clean zero rather than a rounding artefact. That design choice is also why the page works from the year 100 onwards: day numbers do not care how old the date is, while clocks and time-zone databases very much do.

Counting backwards, and the century rule

The counter subtracts day numbers, so it counts backwards exactly as well as forwards — and the leap rule it implements has one famous exception, in the year 2100.

Count backwards from 1 January 2026 by 100 days and you land on 23 September 2025: the page returns exactly 100 days for that pair, with the same four-way breakdown it gives for forward spans. Backwards counting is the same subtraction with the dates swapped, and it is the right tool for questions like “when did the 100 days before the launch start?” or “what date was 90 days before the deadline?” — questions where the answer is a date, not a count. The milestone feature works backwards in spirit too: knowing that day 100 from 28 February 2024 was 7 June 2024 tells you that 7 June 2024 was the 100th day of that count, and the same date can be the end of one span and the milestone of another. Dates are points; spans are the distances between them; and a counter that treats them that way never has to special-case direction.

The century rule is the Gregorian calendar’s fine print, and it is worth knowing because it decides whether a February has 29 days once a century. The rule most people learn — every fourth year is a leap year — has two corrections: years divisible by 100 are not leap years, unless they are also divisible by 400. So 2000 was a leap year (divisible by 400), and the page confirms it: 28 February 2000 to 1 March 2000 is 2 days, with 29 February 2000 in between. But 2100 will not be a leap year (divisible by 100, not by 400), and the page confirms that too: 28 February 2100 to 1 March 2100 is 1 day, with no leap day between them. The same rule is why 1900 was not a leap year either, and why the calendar stays aligned with the seasons over centuries instead of drifting a day every 128 years as the Julian calendar did. If you ever count a span that crosses a century February, check the divisibility — or just type the dates here and let the day numbers do it, which is the same advice as everywhere else on this page: when the rule has exceptions, let the arithmetic carry them.

One more pattern falls out of the same arithmetic for free: any span of exactly 28 days returns to the same weekday. The probed pair proves it — 31 January 2026 was a Saturday and 28 February 2026 was a Saturday, 28 days and four weeks apart, with 20 business days and 8 weekend days in between. The same holds for 7 days, 14 days, 21 days and every other multiple of seven: the weekday repeats because the week divides the span exactly, with nothing left over. That is why rotas repeat weekly without adjustment, why “four weeks from Saturday” is always a Saturday, and why a span that is not a multiple of seven must shift the weekday — by one day for 365 days, by two for 366, exactly as the year rows in the first section show. Weekday arithmetic is day arithmetic modulo seven, and once you see it that way, the calendar stops looking like a list of exceptions and starts looking like the clockwork it is.

A final backwards-counting caution: month arithmetic is not day arithmetic, and the page’s calendar-terms figure (“9 months and 23 days”, “1 month”) is a description of the span, not a second count. Nine months and 23 days from 1 January 2026 is 24 October 2026 only because the months in between have the lengths they have; the same “9 months and 23 days” from a different start lands on a different total-day count whenever February or a 31-day month falls differently inside the span. That is why the total days figure is the authority and the calendar terms are the translation: if two tools agree on the total days but differ on the months, they are describing the same span in different words, and if they differ on the total days, one of them is wrong.

Counting in weeks, months, and years: why a month is not 30 days

Days are exact. Weeks are exact. Months and years are calendar units, and they only make sense from an anchor date.

Weeks divide cleanly, because every week is 7 days: 100 days is 14 weeks and 2 days, and any day count converts to weeks and days by dividing by 7 and keeping the remainder, with no judgement involved. Months do not divide cleanly, because months are 28, 29, 30, or 31 days, and a count of 60 days is two months from the 1st of January to the 1st of March in a leap year, one month and 29 days from the 15th of January to the 15th of March, and two months and a day from the 31st of January, depending on where the count starts. Any statement of months between two dates must name the anchor, the start date from which the months are counted, or it is not a statement at all, only an approximation wearing the clothes of one. The calculator above counts days exactly, and the months and years it reports are counted on the calendar from the dates given, which is the only honest way to report them.

Leap days are ordinary days in the count and extraordinary only in the calendar. The 29th of February counts as one day, like any other, and a period that spans it is one day longer than the same period in a common year, which is why the 1st of January to the 1st of March is 60 days in 2024 and 59 days in 2025, and why a day count that ignores the leap day is wrong by exactly one. Years behave like months: a year from the 1st of March 2024 to the 1st of March 2025 is 365 days, because the leap day falls before the period starts, while a year from the 1st of January 2024 to the 1st of January 2025 is 366, because the leap day falls inside it. Count days exactly, convert to weeks by dividing by 7, and convert to months and years only on the calendar, from the anchor date, and the three answers will agree with each other and with the calendar. The companion guide works the Excel formulas for the same counts, so a spreadsheet and this page can be checked against each other, day for day.

Days since questions, answered

Related calculators