Milestone dates
Last updated: October 28, 2026
A milestone on this site is a round elapsed count: 100 days, 365 days, 1,000 days. It is the moment the counter would show that many days and zero hours, which is local midnight a whole number of 24-hour blocks after the start date. It is not a notification, and it is not the anniversary of the month and day unless the arithmetic happens to land there. This guide shows how to find the calendar date, using January 1, 2026 as the sample so the steps match the homepage.
What “reaching” a number means
The day figure increments when another 86,400 seconds have elapsed, not when a wall calendar looks round. At 300 days and 23 hours you have not reached day 301. You reach it when the hours and minutes roll through to the next whole day. In a zone that is not in the middle of a daylight-saving shift, that rollover is local midnight. The time-zone guide explains the hour of lag or lead when a civil day was 23 or 25 hours long. For the dates below, the milestone is named as the civil date of that midnight, which is the right reading on ordinary days.
The counter will not email you, badge the tab, or save a list of upcoming milestones. You find the date yourself, with a calendar or with the addition below, and you come back if you want to see the live hours. Local storage remembers the start date you calculated. It does not remember a target.
100 days from the sample
January 1, 2026 plus 100 days is April 11, 2026. The day-of-year check: January 1 is day 1, and day 101 of a non-leap year is April 11 (January 31 + February 28 + March 31 = 90, so April 1 is day 91, and April 11 is day 101). Elapsed days are the difference in those indexes, 101 − 1 = 100. At local midnight at the start of April 11, 2026, a count from January 1 shows 100 days, 0 hours, 0 minutes.
During April 10 the count is still 99 days plus some hours. People who celebrate “100 days” on the 99th evening are early by the rule this site uses. The calendar-day guide is the longer version of that zero point. If your own tradition calls the start date day 1, your celebration is one day earlier than the midnight this page uses, for every milestone, not just this one.
365 days, and why it is not always the anniversary
January 1, 2026 plus 365 days is January 1, 2027. That span contains no February 29, so the round number and the calendar anniversary are the same morning. January 1, 2024 plus 365 days is December 31, 2024, not January 1, 2025. The anniversary is the next midnight after that, day 366, because 2024 is a leap year. If you stop at 365 out of habit, you stop a day before the anniversary whenever a leap day sits inside the year. The leap-year guide keeps the rule for which years those are. Use 365 when you mean 365 days. Use the same month and day when you mean the anniversary. The anniversary guide shows a seven-year case where the day total is 2,557, not 7 × 365.
1,000 days is not three years
January 1, 2026 plus 1,000 days is September 27, 2028. You can see the shape of it without a calculator if you subtract whole years and watch February. From January 1, 2026 to January 1, 2028 is 730 days (365 + 365; neither 2026 nor 2027 is a leap year). The remaining 270 days run from January 1, 2028 into 2028, which is a leap year, so February 29, 2028 is inside those 270 days. January (31) + February (29) + March (31) + April (30) + May (31) + June (30) + July (31) + August (31) = 244 days to get to September 1, 2028. 270 − 244 = 26, so September 1 plus 26 days is September 27. At midnight on September 27, 2028 the counter shows 1,000 days.
Three calendar years from January 1, 2026 is January 1, 2029. That morning is past day 1,000. Two calendar years is January 1, 2028, which is day 730, well before it. “About 2.7 years” is a fair gloss if you say it is a gloss. It is a bad substitute for September 27 if you are trying to be in a particular place on the day the counter rolls. The page will not print “2.7 years.” It will print days, hours, and minutes.
Shorter marks people actually watch
Seven days from any start is the same weekday, one week later, because a week does not change length and daylight saving, when it falls inside the week, only shoves the hour figure. Thirty days from January 1, 2026 is January 31, not February 1. Ninety days from October 28, 2026, the day this guide was checked, is January 26, 2027. Those are elapsed days, not “one month” or “three months.” A habit counter that quotes 30, 60, and 90 is using this kind of number. The habit guide says plainly that the numbers are not a clinical threshold. This page only locates them on a calendar.
Ten thousand days is a generation-scale count, about 27.4 common years, and it will include a handful of February 29s. The exact landing date depends on the start. Dividing 10,000 by 365 and ignoring leap days lands you two or three days off, which is the entire point of counting them properly. Do the addition with the leap days included, or let a calendar that knows the Gregorian rule do it, then read the counter on that morning if you want the hours to confirm zero.
What the counter will not do with a milestone
It will not list the next round number for you. It will not keep two dates, so a start date and a target date cannot both be “the” count. It will not fire at the milestone if the tab is closed. It will not adjust the target because you traveled across a time zone; the device you open that morning uses the zone it is set to, as the time-zone guide describes. It will not treat a future target as a countdown. If you enter the milestone date itself before it arrives, the page shows zeros, because a future date is not “time since.”
To confirm a milestone after it has arrived, enter the original start date, not the milestone date. The milestone date as a start would begin a new count at zero. If the day figure is one away from the round number, check whether you included the start date as day 1, and check whether you are reading the page on the evening before the midnight. If it is still off after that, email contact@days-since.app with the start date, the milestone you expected, and the number on the screen.