30 Esfand: the day that only exists in leap years

If you’ve seen “30 Esfand” on a document and then been told it’s not a real date, both things can be true, just in different years. It’s the Persian calendar’s version of 29 February, and it behaves the same way.

Check whether a specific 30 Esfand date is real by converting it:

Why Esfand is the one that changes

Every calendar that tracks the solar year has to absorb the leftover quarter-day somewhere. The Gregorian calendar puts it at the end of February. The Persian calendar puts it at the end of its year, in Esfand. In a common year Esfand has 29 days; in a leap year it has 30. The extra day is never inserted mid-year, it’s always 30 Esfand, the final day before Nowruz.

That makes 30 Esfand the direct counterpart of 29 February. Both are “the leap day,” both only appear in leap years, and both are where date bugs love to hide.

How to tell if a 30 Esfand date is valid

For example, a date like 30 Esfand 1403 is valid, because 1403 is a Persian leap year (it corresponds to 20 March 2025, the last day before Nowruz 1404). But 30 Esfand 1404 is not a real date, because 1404 is a common year, Esfand 1404 ends on the 29th. The leap rule that decides this comes from the Iranian calendar’s 33-year cycle (source: Encyclopædia Britannica, “Iranian calendar”).

The catch is that Persian leap years don’t follow the simple “every four years” pattern. They’re distributed as 8 leap years across a 33-year cycle, with an occasional five-year gap. So you can’t reliably eyeball whether a given year has a 30 Esfand. The mechanism is laid out in Persian (Jalali) leap years, explained, and the parallel with February is in why February has 28 days.

Why a good converter rejects the impossible ones

This is exactly where a careful tool earns its keep. If you enter 30 Esfand in a common year, the right behaviour is to reject it, not silently roll it forward into 1 Farvardin of the next year (which would quietly change both the day and the year). The converter treats a date as valid only when the calendar actually contains it, so an impossible 30 Esfand is flagged rather than fudged.

When it matters

If you’re recording a birth date, a contract date, or any official date near the end of the Persian year, 30 Esfand is worth double-checking. A date stored as 30 Esfand in the wrong year is a data error waiting to surface. Converting the exact date confirms whether it’s real. For the current year, see what year is it in the Persian calendar.

So 30 Esfand isn’t a typo or a glitch, it’s a real date in leap years and an impossible one otherwise. When in doubt, convert it and let the calendar decide.