Roughly one person in every 1,461 draws a birthday that the calendar only honors once every four years. That works out to somewhere around four to five million people worldwide, all sharing a date that legal systems have never fully agreed how to handle, that software has crashed over more times than most companies would like to admit, and that turns an ordinary birthday into a genuine administrative puzzle for three years out of every four. The odd part isn’t that February 29 is rare. It’s that nobody, not lawmakers, not programmers, not even most families, ever settled on a single clean answer for what to do with the people born on it.
The Actual Odds
The 1-in-1,461 figure comes directly from how leap years are distributed: 365 days times 4, plus the one extra day that shows up in the fourth year, gives 1,461 possible birthdates in a typical four-year cycle, and February 29 is exactly one of them. That works out to roughly 0.068 percent of the population. Statistics New Zealand has put a concrete number on what that looks like in practice: about 3,500 people in the country, or roughly seven in every 10,000, share the date. The reason the date exists at all traces back to the same quarter-day drift that leap years were invented to correct, the small mismatch between a 365-day calendar and the slightly longer solar year.
No Universal Answer: How the Law Assigns a Birthday
Turning 18, or 16, or 21 depends on reaching a specific calendar date, and for three years out of four, that date simply doesn’t appear on the calendar. Every legal system that cares about birthdays has had to pick a workaround, and remarkably, they haven’t converged on the same one.
New Zealand handled it with direct legislation. Under the Age of Majority Act 1970, a person born on February 29 is treated as having been born on February 28 for every legal purpose in a non-leap year, a rule confirmed by New Zealand’s official legislation register and applied consistently by government agencies. The United States never adopted a federal standard at all, which means the answer depends entirely on which state someone lives in. Nevada’s motor vehicle statutes fix February 28 as a leapling’s official date for driver’s licensing. Oregon takes a slightly different approach: a license issued to a leap-day baby simply expires on February 29 during leap years and on February 28 in every other year, letting the date float rather than fixing it. New York addressed the question through contract law rather than licensing, with a statute specifying that the leap day and the day immediately before it are treated as a single day for the purposes of calculating deadlines, which in practice makes February 28 the operative date.
The United Kingdom is the messiest case of all, and worth being honest about: sources describing UK practice don’t agree with each other. Some describe February 28 as the recognized legal birthday in non-leap years; others describe March 1. Part of the disagreement comes down to genuine legal reasoning rather than sloppy reporting. One line of argument, echoed by law professors asked about the American situation, holds that a person isn’t legally a year older until the day they were actually born has passed, which would make February 28 one day too early and push the real legal birthday to March 1. It’s a rare case where the law hasn’t so much resolved the question as left multiple plausible answers standing.
| Jurisdiction | Legal birthday in a non-leap year | Basis |
|---|---|---|
| New Zealand | February 28 | Age of Majority Act 1970 |
| Nevada, USA | February 28 | State motor vehicle statute |
| Oregon, USA | February 28 (license expiry only) | State motor vehicle statute |
| New York, USA | February 28 (by legal effect) | Contract and deadline computation statute |
| United Kingdom | February 28 or March 1, depending on source | No single settled rule |
The Software Never Agreed Either
Legal systems at least eventually pick an answer, however inconsistently. Software has a habit of not picking one at all, and the resulting failures are well documented enough to form their own small genre of engineering post-mortems. The failures tend to fall into one of two patterns: code that adds a year to a date without checking validity and tries to construct a February 29 that doesn’t exist in the target year, or code that simply never accounted for a year having 366 days in the first place and chokes on whichever calculation assumed 365. Depending on the language and the system, either pattern can throw an error, silently roll forward to March 1, or fail in a way nobody anticipated.
Some of the failures have been expensive. In 2012, Microsoft’s Azure cloud platform went offline for roughly 12 hours after a system generating security certificates miscalculated a date one year forward from February 29, crashing virtual machines across the service. That same year, Gmail’s chat logs briefly displayed December 31, 1969, as the save date for any conversation stored on February 29, a date that isn’t random: it’s exactly one day before the Unix epoch that much of the world’s software still counts time from, meaning the calculation itself had collapsed all the way back to a null timestamp. In 2016, a leap day bug in the baggage-handling software at Düsseldorf Airport kept more than 1,200 pieces of luggage from making their flights. New Zealand alone has been hit twice by the second pattern: a 1996 bug that failed to anticipate a 366-day year shut down the Tiwai Point aluminium smelter at the year’s final midnight, with repair costs across affected sites topping a million dollars, and a 2024 glitch left pay-at-pump fuel stations across the country unable to process transactions on the day itself.
Every one of those systems fixed itself by March 1. None of them fixed the underlying cause, because the underlying cause only matters for about twenty-four hours every four years. worldtimedata
The bugs aren’t limited to infrastructure. In 2008, Toys “R” Us discovered its own website couldn’t register a customer’s birthday as February 29 at all, which meant children born on leap day were quietly excluded from the store’s birthday club perks for years before anyone noticed. It’s the same root flaw as the aluminium smelter and the cloud outage, just showing up somewhere far lower stakes, and it points at the same lesson: date-handling code that only gets tested against three years out of four will eventually meet the fourth one unprepared. It’s a smaller, more frequent cousin of the kind of date-overflow failure that also drives the Y2038 problem, the same category of bug, just triggered by a four-year cycle instead of a 32-bit integer running out of room decades from now.
Culture Filled In Where the Rules Left a Gap
Where law and software mostly produced friction, tradition took a more forgiving approach. Leaplings, as people born on February 29 are commonly known, inherited at least one custom built specifically around the date: in Ireland and Britain, February 29 has long been informally recognized as the day a woman may propose marriage to a man, a reversal of the traditional gender roles in courtship that dates back centuries and is tied to the day’s own rule-breaking rarity.
Genuine multi-generational leap-day families exist and are documented well enough to appear in Guinness World Records. The Keogh family holds the record for three consecutive generations born on February 29: Peter Anthony Keogh, born in Ireland in 1940, his son Peter Eric, born in the UK in 1964, and his granddaughter Bethany Wealth, born in the UK in 1996. Separately, Karin Henriksen of Andenes, Norway, gave birth to three of her children on leap day across three different leap years: Heidi in 1960, and sons Olav and Leif-Martin in 1964 and 1968. The odds against either family tree happening by chance are steep enough that both cases get cited repeatedly as the standard examples whenever the subject of leap-day birthdays comes up.
A handful of well-known public figures share the date too, among them the rapper Ja Rule, born February 29, 1976, and actor Peter Scanavino, a fact that mostly serves as a reminder that the club of leaplings, small as it is by percentage, is still large enough in absolute terms to include people most of the world has heard of.
A Day the Calendar Includes but No System Fully Accounts For
What ties the legal patchwork and the software failures together is the same underlying fact: February 29 is real enough to be someone’s actual birthday, but rare enough that almost nothing built around the concept of “a birthday happens every year” was ever designed with it fully in mind. Lawmakers picked workarounds instead of universal rules. Engineers keep shipping code that assumes every year looks like the other three. Families and cultural traditions, with nothing to legislate and nothing to compile, simply adapted, which may be the closest thing to a clean resolution this particular date has ever gotten.
