A Song Of Ice And Fire Calendar

Building a Functional A Song Of Ice And Fire Calendar

The Westerosi calendar in George R.R. Martin's universe is built around lunar months and a year that varies wildly in length because the seasons themselves are unpredictable. Getting one right on paper or in code isn't hard, but actually making it useful for roleplaying or fan projects requires you to account for several structural quirks that most people gloss over. Most fantasy calendars just fake it with twelve 30-day months. Westeros does something more interesting. The months follow moon cycles, roughly 30 days each, but the actual names and order come from the books. There are seven named months in regular sequence, plus intercalary months called "nameless months" that get inserted when the year runs long. A full year can be anywhere from about 365 days to potentially over 400 depending on how the lore scales the seasonal drift. The year count also doesn't use a simple AD/BC system. Events are dated by regnal years of kings or relative to major canonical moments, which means any calendar you build needs a reference epoch to be useful. The standard anchor point most fans use is the Conquest — Aegon's landing at Dragonstone — which marks Year 0 or Year 1 depending on which source you trust. Martin himself was deliberately vague about this, so you will see discrepancies between different fan sources.

How I Built One and What Went Wrong

I spent a weekend putting together a working A Song Of Ice And Fire Calendar for a homebrew campaign. My first pass was a straightforward 7-month system, each month 30 days, leap months added every few years. Clean on paper. The problem hit when I tried to map actual book events to dates. Chapter references, seasonal descriptions, and timeline cross-references didn't align. A scene explicitly set in "the month of the Maiden" during a winter that lasts eight years creates a logical contradiction if you assume standard month lengths. The workaround was simpler than I expected. I stopped trying to force every book reference onto a fixed grid and instead built the calendar around the known anchor points — key events with explicit dating — and let the gaps between them breathe. I used a base of 30-day months, added a nameless month roughly every third or fourth year, and flagged any date that fell in a book-reference gap as speculative. That's honest and it's what serious wikis end up doing anyway.

The Month List and Structure

The canonical months, in order, are: 1. First Moon — the year begins, typically associated with crowning or new beginnings
2. Second Moon
3. Third Moon
4. Fourth Moon
5. Fifth Moon
6. Sixth Moon
7. Seventh Moon — the year ends, often linked to harvest or death
Nameless Month(s) — inserted irregularly based on seasonal necessity Each month is approximately 30 days. The exact day count per month varies by source, with some references suggesting 28 to 32 days depending on the moon phase alignment of that particular year.

Seasonal Complexity You Need to Account For

This is where the A Song Of Ice And Fire Calendar gets genuinely tricky. In Westeros, a "year" isn't a fixed unit because summers and winters can last years. A single season might run for three calendar years or more. When you're dating events, you have to specify not just the month and regnal year but also which season is active. Something dated "Third Moon, Year 298" means very different things depending on whether it's summer or winter, because the political and logistical context around those dates changes completely. A common pitfall is assuming that because book events happen in a certain order, the calendar must march forward linearly. It doesn't. Time in Westeros is sometimes ambiguous, sometimes contradictory, and Martin intentionally leaves room for interpretation. If you need absolute precision for a project, pick a single canonical timeline (the Wikipedia consensus timeline or the "Westeros.org" wiki chronology are the two most cited) and stick to it. Don't blend sources without noting where you're making editorial choices.

Counting Years and Regnal Dating

The most practical approach for most users is to use the "After Conquest" (AC) system. Year 1 AC marks Aegon's landing. Everything before it is "Before Conquest" (BC). Most of the books take place between roughly 298 AC and 305 AC. Robert's Rebellion was around 283 AC. The Targaryen dynasty started at 1 AC and ended at 283 AC. If you're building a tool or spreadsheet, I recommend storing dates in three fields: AC year, month number (1-7 plus negative indices for nameless months), and season tag. This gives you enough resolution for plot tracking without locking yourself into false precision. A full year counter in days is tempting but ultimately misleading given how the source material treats time.

Practical Tools and Where to Find Them

There are several community-maintained resources. The Westeros.org wiki has a detailed timeline page that maps book events to dates. Fan-made spreadsheet converters exist that translate AC dates into roughly equivalent Earth calendar dates, though you should treat those as approximate at best. For a downloadable A Song Of Ice And Fire Calendar that you can actually use for RPG tracking or writing reference, the most reliable options are community spreadsheets hosted on Google Sheets or Notion templates shared in r/asoiaf and the Westeros forums. I keep a personal copy that I update whenever new canonical dates get clarified in the published text. One thing to watch for with any template you download: check the revision date. The calendar gets refined as Martin publishes new material and as fans resolve old contradictions. A template from 2019 is almost certainly missing corrections that came out after The Winds of Winter drafts circulated.

When This System Breaks Down

The A Song Of Ice And Fire Calendar isn't designed for rigorous chronological work. It's a narrative tool, not a scientific one. If you need exact date math — like calculating how many days elapsed between two specific chapters — you will run into contradictions. Different passages imply different durations. Some events overlap impossibly. This is by design in the source material, not a bug in your calendar. For casual tracking, roleplaying, and general reference, the 7-month system with nameless intercalations and AC dating is more than sufficient. It captures the flavor of the world and gives you a framework that feels authentic without pretending to know more than the books actually tell you. If you need higher precision, you're better off building a custom timeline from primary text references rather than relying on any pre-made calendar. No existing template handles the ambiguities as honestly as a careful reader would want.