The last leap year was 2024. Leap day fell on Thursday, February 29, 2024. The next one arrives in 2028, when February again has 29 days. That answer sounds simple, but the rule behind it is a three-part test, and the reasoning explains why most people cannot state the century exception correctly.
Why February 29 exists at all
A calendar is a rounding device. Earth's tropical year, the average interval between March equinoxes, runs about 365.2422 days. A calendar of exactly 365 days drifts against the seasons by roughly 0.2422 days per year, which is about one full day every four years.
That drift is not cosmetic. Left alone for a few centuries, it pushes the solstices and equinoxes away from their dates. Farming schedules, religious observances tied to solar events, and the administrative definition of seasons all depend on the calendar staying synchronized with the sky.
The leap day is the correction. Adding February 29 every four years injects 0.25 days per year on average, slightly overshooting the true 0.2422. The overshoot is small per year but accumulates. That is why the Julian calendar's simple four-year rule eventually needed refinement.
The Gregorian reform addressed the overshoot with subtraction rules. A year is a leap year if it is divisible by 4, except century years, which must be divisible by 400. The logic: 0.25 minus the century corrections lands close to 0.2422 without requiring fractional days.
In plain terms, the calendar borrows a quarter day per year and pays it back with an extra day, then claws back the overpayment at century boundaries.
Quantifying the correction
The arithmetic matters because small residuals compound. A calendar that is off by one day per 128 years looks fine on a human timescale but fails over millennia.
| Rule | Average year length (days) | Drift vs. tropical year |
|---|---|---|
| 365-day calendar | 365.0000 | About 1 day every 4 years |
| Julian (every 4 years) | 365.2500 | About 1 day every 128 years |
| Gregorian (4/100/400) | 365.2425 | About 1 day every 3,200 years |
| Tropical year (reference) | About 365.2422 | Baseline |
The Gregorian average of 365.2425 days sits within about 0.0003 days of the tropical year. That residual translates to roughly one day of drift every 3,000-plus years, far beyond any practical calendar concern.
The pattern of leap years is also uneven by design. In any 400-year Gregorian cycle there are 97 leap years, not 100. Three century years (such as 1700, 1800, and 1900) are skipped, while 2000 is retained because it divides by 400. That is the counterintuitive detail most people miss: a year ending in 00 is usually not a leap year.
Edge cases that trip people up
The century rule creates a trap. 1900 was not a leap year. 2000 was. Anyone who learned "every four years" without the century exception will misdate February 29 in 1900, 2100, and 2200.
Leap day placement is another quirk. February 29 is inserted into the shortest month, but nothing in astronomy requires February specifically. The choice is historical, inherited from the Roman calendar structure. The date is a convention, not a physical event.
Leap seconds are a separate mechanism and often confused with leap days. Leap seconds adjust clock time to match Earth's rotation, which varies slightly. They are not calendar corrections and do not add a date to February.
Timezone boundaries can make "the last leap year" ambiguous at the margins. February 29, 2024 existed everywhere, but the exact instant of local midnight differs by location. For calendar purposes, the date is global; for timestamp precision, it is not.
A year ending in 00 is a leap year only if divisible by 400. 1900 was not a leap year; 2000 was. 2100 will not be a leap year. Leap seconds adjust clocks, not calendars, and are unrelated to February 29. The leap day is always February 29 in the Gregorian system.
Misconceptions worth correcting
The most common error is treating the four-year rule as complete. It is not. The century exception is what keeps the calendar accurate over long spans, and skipping it produces errors that surface only at century boundaries.
A second misconception is that leap years exist to fix a "broken" calendar. The calendar is a model, and the leap day tunes the model to reality. The system is working as intended, not patching a mistake.
A third is that leap years are evenly spaced. They are not. The gap between 1896 and 1904 was eight years because 1900 was skipped. The gap between 2096 and 2104 will also be eight years because 2100 is skipped. Long gaps cluster at centuries.
A professional caveat: software date libraries handle the Gregorian rules well, but legacy systems and hand-written date math sometimes hard-code the four-year rule. A system that miscalculates 1900 or 2100 can produce wrong ages, wrong interest accruals, and wrong scheduling. Verify date logic against the full rule, not the shortcut.
One more subtlety: the Gregorian calendar was adopted at different times in different regions. For historical dates before widespread adoption, "leap year" depends on which calendar system was in local use. The 2024 answer is unambiguous in the modern Gregorian system.
Practical steps for dates and systems
For everyday use, confirm the year is divisible by 4, then check the century exception. 2024 divides by 4 and is not a century year, so it is a leap year. 2028 will be too.
For software, test date handling against known boundary cases. Run 1900, 2000, and 2100 through the system and confirm the outputs match the Gregorian rule.
Verify divisibility by 4 first, then apply the century exception. Test systems against 1900 (not leap), 2000 (leap), and 2100 (not leap). Do not assume an eight-year gap is an error; it is expected at skipped centuries. Treat leap seconds as a separate concern from leap days. For historical dates, identify which calendar system was in local use.
For scheduling and financial calculations, confirm whether the contract or policy uses calendar days or business days, since February 29 can shift accrual and deadline logic. A one-day ambiguity on a leap day can matter in interest and billing contexts.
For anyone building age or anniversary logic, decide explicitly how February 29 birthdays are handled in non-leap years. Common conventions include March 1 or February 28, but the choice is policy, not astronomy, and should be documented.
Limits of the rule and what it cannot tell you
The Gregorian rule is accurate enough for civil use but is not exact. The residual drift of roughly one day per 3,200 years means the calendar will eventually need adjustment if long-term precision matters. No current civil system schedules that correction.
The rule also cannot answer historical questions without calendar context. Before Gregorian adoption, local calendars governed, and retrofitting modern rules onto old dates can misstate real events.
Finally, calendar rules are conventions, not physical laws. They can be changed by agreement. The 2024 leap year is certain under current rules, but the rules themselves are a human decision, and this article states the mechanism rather than predicting any future reform.