‘Game of Thrones’ map tracks the show’s most brutal deaths

The Washington Post’s 6,887-death database has quietly powered every major Game of Thrones map since 2019, and 2026 updates now fold in the latest House of the Dragon casualties. Fans scanning for a Game of Thrones map that plots brutal deaths by exact location are finally getting what they asked for: clickable pins, episode numbers, and clear totals. The tools turn a gory spreadsheet into something you can zoom, filter, and share.

Database sets the baseline

The Post team logged every on-screen kill, named or not, across eight seasons. Winterfell leads with 3,709 deaths, almost all from the Battle of the Dead. King’s Landing sits second at 1,357, split between executions and the burning. Beyond the Wall clocks 1,092, mostly during the long march south.

Dragonfire tops the weapons list, followed by blades and arrows. The single bloodiest scene remains the Battle of Winterfell, with 3,512 fatalities in one night. The Burning of King’s Landing trails at 1,020, but the method—Drogon torching city blocks—keeps it in meme rotation years later.

Because the original numbers are public and verified frame-by-frame, every new Game of Thrones map simply layers fresh pins on top. No one rebuilds the count; they just add House of the Dragon episodes and A Knight of the Seven Kingdoms teases as they air.

Polygon adds filters and tooltips

Polygon’s January 2026 refresh keeps the series toggle front and center. Users can isolate the original run, House of the Dragon Season 3, or the upcoming Knight of the Seven Kingdoms prequel without losing the map view. Each pin carries the episode number and a brief method note, so a second-screen rewatch stays synced.

The filter that separates named characters from battlefield extras matters for rewatching parties. Casual viewers want to track only the Starks; completionists want the full 6,887. Polygon’s mobile layout lets groups pass a tablet around without losing place.

Red Wedding pins at the Twins still draw the loudest reactions. Clicking Robb’s death marker pulls up Catelyn and Talisa in the same tooltip, a compact reminder of how one location can end three major arcs in minutes.

ThroneAtlas traces the journeys

ThroneAtlas overlays 80-plus route lines on the same geography. Instead of static pins, you watch characters travel to their deaths: Jon Snow’s path from Winterfell to Castle Black, Daenerys’ march from Meereen to the Red Keep. The visual makes the geography feel smaller and the violence more inevitable.

The May refresh added a cluster view that highlights the Twins and King’s Landing as multi-year killing fields. Oberyn Martell’s skull-crushing still sits inside the same red zone where the later city burning will occur, turning the map into a timeline of political revenge rather than random carnage.

Because the tool exports shareable images, ThroneAtlas pins now show up in Reddit threads the morning after each House of the Dragon episode. Fans post side-by-side shots of Rhaenyra’s fleet losses next to the original Battle of Winterfell, comparing body counts in real time.

GameRant folds in spin-offs

GameRant’s January refresh added Battle of the Gullet and Tumbleton pins the week after those House of the Dragon Season 3 episodes aired. The map keeps the Washington Post baseline so totals stay consistent across platforms. Viewers no longer have to switch between separate trackers for prequel and sequel deaths.

The named-versus-extras toggle remains useful here. Dragonrider deaths draw the biggest social spikes, while unnamed sailor counts stay low on the share meter. GameRant’s data team posts weekly updates rather than waiting for season finales, keeping the Game of Thrones map current during the off-season.

Users can also export CSV files of any filtered set, which has become standard for fan podcasts that run live death-count segments. The open data approach keeps the map from becoming a walled garden and lets smaller sites build their own visualizations on top.

Iconic single kills still dominate

Ned Stark’s beheading in King’s Landing remains the most replayed individual clip on the maps. The pin links directly to the episode and shows the exact blade count—still one swing—next to the later mass executions in the same courtyard. The contrast keeps the moment sharp even for viewers who have seen it dozens of times.

Oberyn’s death in the same city draws steady traffic from new audiences discovering the show through streaming algorithms. The tooltip lists both the method (skull crush) and the immediate consequence (Cersei’s later glee), turning a single graphic kill into a two-season payoff.

Winterfell’s Lyanna Mormont and Edd Tollett pins sit only yards from the Night King’s final stand. The map clusters these three moments so tightly that mobile users sometimes miss the separation until they zoom. The visual density underscores how one location can host both intimate hero deaths and continent-wide zombie warfare in a single night.

Community use and social spikes

Reddit threads now treat the Game of Thrones map as a live scoreboard during House of the Dragon airings. After the Battle of the Gullet, users posted heat-map screenshots comparing naval losses to the original Blackwater numbers within an hour of the credits. The shared link became the top post on r/gameofthrones that night.

Podcast hosts pull static exports before recording so listeners can follow along without pausing video. One popular recap show runs a weekly segment titled “Where Did They Die This Week,” using ThroneAtlas route lines to trace each victim’s path to the kill site. The segment has become a reliable download spike.

Twitter bots scrape the public data and post daily tallies sorted by location. King’s Landing usually leads on execution-heavy weeks, while Winterfell spikes only during flashback or prequel episodes. The automated feed keeps the conversation alive between seasons without requiring new footage.

Production impact and future plans

HBO’s current showrunners have referenced the Washington Post numbers when discussing on-screen violence budgets for upcoming seasons. The data makes clear that large-scale battles cost more per minute than political scenes, and the maps quantify exactly how many extras appear in each location. That visibility influences where the next big fight is staged.

Polygon’s team has said the next refresh will add a “predicted deaths” layer based on leaked scripts for A Knight of the Seven Kingdoms. The feature stays locked until official air dates, but the code is already written. Early testers on Discord report the toggle works, just hidden behind a release-date check.

GameRant is exploring an AR version that overlays pins on a physical map of Westeros sold at Target. The prototype uses the same data set, meaning a coffee-table map could show every on-screen death without requiring a second screen. Retail placement is still under discussion, but the data layer is ready.

Why the maps keep evolving

Each new series adds deaths, but the original 6,887 remain the fixed reference point. Viewers trust the count because it came from frame-by-frame review rather than estimates. That trust turns the Game of Thrones map into the default second-screen companion whenever a new episode drops.

The tools also age well. A viewer who started with House of the Dragon can click backward to see where the same locations first turned deadly in the original run. The continuity keeps casual fans from feeling lost and gives completionists a single place to track every swing of the blade.

Because the data stays open, smaller creators keep building on it. The Game of Thrones map is no longer one site; it is a shared layer that any fan site or podcast can call. That openness is what keeps the project alive long after the original series ended.

Forward view

The next wave of pins will come from A Knight of the Seven Kingdoms and whatever follows House of the Dragon Season 3. As long as HBO keeps ordering new episodes set in the same geography, the Game of Thrones map will keep adding red dots. The underlying 6,887-death foundation stays unchanged, giving every future death a fixed coordinate and a running total that viewers can check the morning after each premiere.