What People Are Asking About the Hebrew Calendar Month
Kislev is the third month of the civil Hebrew calendar and the ninth month of the ecclesiastical count. It usually lands somewhere between late October and late December on the Gregorian calendar, which means its dates shift every year depending on where the lunisolar alignment puts it. The month itself is twenty-nine or thirty days long, and whether it has twenty-nine (chaseret) or thirty (maleh) days depends on a whole set of rabbinic rules about spacing out Yom Kippur and keeping Rosh Hashanah off certain weekdays. Most people come across Kislev because of Hanukkah, which begins on the 25th of Kislev and runs for eight days. If you're trying to figure out when Hanukkah falls in a given Gregorian year, you look up the Hebrew date first and then map it. The tricky part is that the Hebrew calendar doesn't repeat on a simple four-year cycle like a leap year schedule. It runs on a 19-year Metonic cycle with 7 leap months inserted at years 3, 6, 8, 11, 14, 17, and 19. So if you're building something that needs to predict holiday dates years ahead, you need the full arithmetic calendar, not just a rough approximation.
What Is The Month Of Kislev
I've built scheduling tools that needed to resolve Hebrew dates for decades into the future, and the first thing I learned the hard way is that Kislev can be a pain point. Here's the edge case I ran into: in some years, Kislev is missing a day entirely compared to what you'd expect. The month of Cheshven right after it also varies in length, and the combination affects when Hanukkah starts relative to Christmas and the Gregorian new year. In 2013, for example, Hanukkah started on December 5th. In 2014, it jumped to December 15th. That ten-day swing threw off a lot of naive date-conversion code I saw people using online. The workaround isn't complicated but it does require you to implement the full Hebrew calendar algorithm rather than relying on hardcoded lookup tables or approximations. You need to calculate the molad (the mean lunar conjunction) for Tishrei of the given year, apply the four dehiyot (postponement rules), determine the length of the prior year, then figure out whether Kislev is short or full based on the total year length. Once you have that, you know whether Hanukkah 25 Kislev maps to early December or mid-December. This process usually takes me about ten minutes to code correctly from scratch, but getting it right the first time is easy to fail at if you skip the dehiyot steps. One counter-intuitive thing most people miss: Kislev itself never has a leap month inserted into it. The leap month is Adar I, added before the regular Adar. So when someone says "leap year Kislev," they just mean Kislev in a year that also has an extra Adar earlier in the calendar. The month of Kislev behaves the same way in leap and non-leap years. The shift in Hanukkah dates across years comes from the accumulated drift of the lunar months against the solar year, not from any special rule in Kislev itself.
Another practical detail worth knowing: the 15th of Kislev, Tu BiShvat's close neighbor in the calendar, doesn't have major liturgical significance the way the 15th of Shevat does for the new year of the trees. But if you're doing anything with Jewish agricultural cycles or tithing dates, the proximity matters. Some communities mark the 15th of Kislev with minor fasts or commemorations tied to historical events, nothing uniform though. The Jerusalem Talmud mentions a fast on that date related to the removal of idols from the Temple, but it's not observed broadly today. If you need to work with Kislev programmatically, I'd recommend using an established library like hebrew-calendar or moment-hebrew rather than rolling your own. The arithmetic calendar is well-documented in works like Nachmanides' Sefer HaTemunah and the modern calculations behind the fixed Hebrew calendar attributed to Hillel II, but implementing it yourself is error-prone. Even with a library, always validate against known dates. I once caught a bug where a library incorrectly handled the year 5876 (2015-2016) by making Kislev thirty days when it should have been twenty-nine, which pushed Hanukkah forward by a day across the entire holiday window. The main downside of relying on any pre-built Hebrew date solution is that not all of them handle the full range of valid Hebrew years. Some stop at 2025 or 2100. If you're building something long-term, check the supported range and test edge cases around year boundaries where the molad calculations get unusual. The calendar is mathematically valid for thousands of years, but the software supporting it isn't always built with that longevity in mind.
Get the Full Details
