A Hebrew birthday on the 30th: when the date is missing
What happens when 30 Cheshvan, 30 Kislev or 30 Adar I is absent? Learn Hebcal’s stated birthday rule and why anniversary types matter.
The birthday moves to the next month under Hebcal’s rule
Hebcal states that a person born on 30 Cheshvan, 30 Kislev or 30 Adar I has the birthday postponed to the first of the following month in a year when that day is absent. It identifies its algorithm as the one in Calendrical Calculations by Edward Reingold and Nachum Dershowitz, in accordance with Ashkenazic practice. That attribution is part of the answer, not a claim that every community handles every anniversary identically.
The original birth date remains the original birth date. An anniversary convention tells you which date to use in a target year with a different calendar shape; it does not edit the historical record. Save both separately so a future change in practice or a new question can be resolved from the original information.
Source notes: Hebcal · Birthday and yahrzeit anniversary algorithms
Which thirtieth days can disappear?
Cheshvan and Kislev can each contain 29 or 30 days. Adar I has 30 days in a leap year, while the single Adar of a common year has 29. Those are the three thirtieth-day cases addressed by Hebcal’s birthday rule. Most other month lengths are fixed, so a birthday on 30 Nisan does not face the same missing-date problem.
First confirm the complete Hebrew date, including the birth year and the full Adar label. Next check the target year’s month length. Only then apply a missing-date rule. That order helps distinguish three possible issues: an incorrect conversion, an incomplete original record and an anniversary that is validly carried into a year where its original day does not occur.
Source notes: Hebcal · Days in a Hebrew month
What the rule means in each case
For a 30 Cheshvan birthday in a year with only 29 days of Cheshvan, Hebcal’s stated birthday algorithm uses 1 Kislev. For 30 Kislev in a short Kislev year, it uses 1 Tevet. For 30 Adar I carried into a common year, it uses 1 Nisan. In a target leap year, 30 Adar I exists and can be retained.
Write the reason beside the calculated anniversary. “1 Kislev because Cheshvan has 29 days this year” is much easier to understand than a date that appears to have changed without explanation. If you share the date with family, include the original birthday in the same note. This gives people a clear account of the calendar adjustment without inviting them to correct the historic month.
Source notes: Hebcal · Birthday and yahrzeit anniversary algorithms · Hebcal · Days in a Hebrew month
A verified Cheshvan example
Consider a birth during the daytime on 1 December 2024: Hebcal verifies that date as 30 Cheshvan 5785. The first birthday, in 5786, falls in a year without 30 Cheshvan. Under Hebcal’s birthday rule it is carried to 1 Kislev 5786, which the annual table verifies as 21 November 2025. The original birthday remains 30 Cheshvan.
There is a useful limitation on that table: Hebcal explicitly warns that the displayed dates use a simple date conversion and do not implement the more complicated yahrzeit rules. A table can demonstrate how dates fall without deciding every observance. Read its label before using it. For this article’s birthday example, the result is consistent with the separately documented birthday algorithm.
Source notes: Hebcal · Birthday and yahrzeit anniversary algorithms · Hebcal · 30 Cheshvan 5785 and annual conversion table
A yahrzeit is a different calculation
Do not copy a birthday rule into a memorial reminder. For a death on 30 Cheshvan, Hebcal uses the day before 1 Kislev if the first anniversary lacked 30 Cheshvan. Chabad clarifies that, if the first anniversary had a thirtieth day, later short years use 1 Kislev. Hebcal gives the analogous first-anniversary distinction for 30 Kislev, using the day before 1 Tevet when that first anniversary lacked 30 Kislev. These are yahrzeit rules, not birthday rules.
This is also why a familiar answer from a family birthday may be inappropriate for a bar or bat mitzvah question, a memorial observance or another religious obligation. State the occasion explicitly when seeking guidance. The present guide explains a named calculator’s birthday algorithm. Where community practice or religious consequences are involved, bring the original date and the target year to the relevant community authority.
Source notes: Hebcal · Birthday and yahrzeit anniversary algorithms · Chabad · Yahrtzeit When the Date Does Not Exist?
Make the answer reproducible
Keep the original civil birth date, original Hebrew date, any known evening-boundary information, the target Hebrew year and the anniversary convention together. If the birth time is uncertain, resolve or preserve that uncertainty before applying a missing-day rule. An accurately calculated adjustment cannot repair an original date that was never established.
For a recurring reminder, use a tool that calculates Hebrew anniversaries by year rather than repeating one Gregorian date forever. Recheck the next occurrence before arranging a celebration. If your family follows a different documented practice, record its name and source alongside the result. A clear record respects both the calendar’s changing structure and the particular tradition through which a birthday is observed.
Source notes: Hebcal · Birthday and yahrzeit anniversary algorithms