Year progress is simply the day of the year divided by the number of days in that year:
Progress = day of year ÷ days in year × 100
Take 28 August 2026. Adding up the completed months — 31 + 28 + 31 + 30 + 31 + 30 + 31 = 212 through the end of July — then adding 28 gives day 240. 2026 is not a leap year, so 240 ÷ 365 = 65.75% complete, with 125 days left.
The same date in a leap year would be day 241 of 366, or 65.85% — a difference of a tenth of a percentage point, which is exactly why leap years cause almost no visible trouble here and enormous trouble in date libraries.
| Date | Day of year | Progress | Days left |
|---|---|---|---|
| 1 January | 1 | 0.27% | 364 |
| 1 April | 91 | 24.93% | 274 |
| 2 July | 183 | 50.14% | 182 |
| 1 October | 274 | 75.07% | 91 |
| 31 December | 365 | 100% | 0 |
The midpoint of a non-leap year falls at noon on 2 July. If you want the halfway marker, that is it.
Most people know the first clause and stop there, which is why the rule is worth stating completely:
So 2024 was a leap year, 1900 was not, and 2000 was. The correction exists because the tropical year is 365.2422 days rather than 365.25, so adding a day every four years overshoots slightly. The 100 and 400 rules trim the excess and leave the calendar accurate to about one day in 3,000 years.
The 1900 case is the source of a famous and still-live bug: early spreadsheet software treated 1900 as a leap year, and the error was deliberately preserved for backwards compatibility. Serial date numbers in some spreadsheet formats are therefore off by one for dates before March 1900.
Calendar year progress is often not the number you actually need.
Quarters are uneven, which surprises people building dashboards. Q1 is 90 days in a normal year, Q2 is 91, Q3 is 92 and Q4 is 92. A quarter-over-quarter comparison of daily-rate metrics is comparing slightly different lengths.
Fiscal years frequently do not start in January — the UK tax year begins 6 April, the US federal year on 1 October, Japan and India in April, Australia in July. If you are tracking a budget, calendar progress and budget progress diverge, and reporting one as the other is a real error.
ISO week numbers have their own edge case. An ISO week runs Monday to Sunday, and week 1 is the week containing the first Thursday of January. That means the first days of January can belong to week 52 or 53 of the previous year, and a year can contain 53 ISO weeks. Anyone who has built a weekly report that breaks every few Januaries has met this.
Automated accounts that post nothing but a year progress bar have accumulated millions of followers, which is odd for a number anyone could compute. The appeal seems to be that it is unarguable and shared — the same figure for everyone, arriving unrequested, with no advice attached.
The honest caveat: a progress bar measures elapsed time, not accomplishment. Seeing 65.75% in August tells you the calendar has moved; it says nothing about whether your year has gone well, and treating it as a scorecard on January resolutions mostly produces guilt. The useful version is the inverse figure — 125 days remaining is a workable amount of time, and it is more actionable than a percentage already spent.
Because day 1 is a day you are living through, so it counts as elapsed. If you prefer 0% on 1 January, use days completed rather than day-of-year, which shifts every figure down by about 0.27 points.
2 July at noon in a normal year, and 2 July at midnight in a leap year. The old rhyme about 1 July is close but not exact.
Yes, briefly. The day of year rolls over at local midnight, so for a few hours each day different parts of the world see different figures. This page uses your device local date.
No. The date comes from your device clock and the calculation runs in your browser; nothing is transmitted.
Every tool comes with a written guide, and every category is one click away.