‘Game of Thrones’ map: Where every character died

Viewers returning to Game of Thrones for fresh rewatches or tuning into 2026 House of the Dragon episodes want a precise way to track where every major character met their end. The answer sits in a handful of interactive tools that turn the Washington Post’s 2019 death database into live, clickable Game of Thrones map overlays. Those maps let fans isolate exact pins for Ned Stark’s beheading, the Red Wedding, and Daenerys’s final moments without flipping between wikis.

Washington Post numbers set the baseline

The Post’s frame-by-frame count logged 6,887 on-screen deaths across the original series. Winterfell topped the list with 3,709 fatalities, almost all during the Battle of Winterfell. King’s Landing followed with 1,357, and the lands Beyond the Wall added 1,092. Those raw figures still feed every major interactive map released since.

The Post project also distinguished single-event massacres from sprawling battles. The Red Wedding at the Twins killed fewer than a hundred named characters, yet it remains one of the most referenced pins on every subsequent Game of Thrones map. That contrast helps users toggle between intimate betrayals and continent-wide slaughter.

Because the data is public, developers can append new pins without rebuilding the entire dataset. Polygon, ThroneAtlas, and GameRant all cite the same source sheet, ensuring consistent coordinates for every named death from the HBO canon.

Polygon’s filters keep spin-offs straight

Polygon’s January 2026 update added separate toggles for Game of Thrones, House of the Dragon, and A Knight of the Seven Kingdoms. Users can hide background deaths and surface only named-character pins, trimming thousands of wight markers from crowded scenes.

Tooltips now display episode numbers, so a viewer can jump straight to the scene where Robb Stark falls at the Twins. The same layer shows Daenerys’s destruction of King’s Landing in season eight, episode five, with exact street coordinates inside the Red Keep.

The map also layers travel routes that end at death sites. Fans tracing Jon Snow’s path from Castle Black to King’s Landing can see every waypoint where an ally or enemy met their end, turning the Game of Thrones map into a narrative timeline as well as a geography lesson.

ThroneAtlas adds house territories and routes

ThroneAtlas refreshed its atlas in May 2026 with eighty-plus death pins and dynamic route layers. Viewers can overlay Stark, Lannister, or Targaryen holdings to understand why certain characters died where they did.

The route tool highlights Robb Stark’s doomed march to the Twins and Daenerys’s sail from Meereen to Dragonstone, each stop marked by prior fatalities. This visual context turns a simple pin into a cause-and-effect chain across Westeros and Essos.

Because the project remains fan-maintained, it updates within days of new House of the Dragon episodes. The latest pins mark dragon deaths at the Battle of the Gullet, already integrated into the same map that tracks original-series casualties.

GameRant focuses on TV canon only

GameRant’s map excludes book-only deaths, keeping the dataset aligned with what HBO viewers have actually seen. That decision reduces confusion when showrunners change fates between page and screen.

The site pushes updates within forty-eight hours of each new episode, so Tumbleton’s fiery toll from recent House of the Dragon installments already appears as a cluster of red markers. Users can toggle named deaths versus battlefield totals to avoid visual overload.

GameRant also links each pin to a short clip hosted on its own servers, letting casual fans confirm the location without hunting through eight seasons of footage. The feature has made the map a default second-screen companion for U.S. viewers during Sunday-night airings.

Social media turns maps into group events

Discord servers now host weekly “death tour” watch parties where participants screen-share a shared Game of Thrones map and place bets on which pin lights up next. The format has migrated to TikTok, where clipped map zooms rack up millions of views each week.

Reddit’s r/freefolk subreddit maintains a sticky thread ranking the most shocking death locations, measured by distance from a character’s home castle. The data pulls directly from ThroneAtlas coordinates, giving the discussion a consistent reference point.

Twitter Spaces dedicated to House of the Dragon Season 3 have started embedding live map links, allowing listeners to follow along as hosts break down new casualties in real time. The practice keeps geography central to spoiler conversations rather than an afterthought.

Spin-off seasons test map scalability

House of the Dragon Season 3 added two major battles in its first four episodes, pushing the total on-screen death count past 7,400. Each new location required fresh coordinates that still align with the Washington Post’s original grid system.

A Knight of the Seven Kingdoms presents a different challenge: smaller-scale fights in rural riverlands. The maps now include toggleable layers for village-level detail, preventing rural pins from disappearing inside larger region markers.

Developers report that server load spikes every Sunday night when new episodes drop. Polygon added a queue system to keep the interactive Game of Thrones map responsive even when thousands of viewers open it simultaneously.

Accuracy debates surface with each update

Some fans argue that off-screen deaths, such as Viserys Targaryen’s reported end in the Dothraki sea, should remain off the map. Polygon keeps those entries grayed out, while ThroneAtlas offers an optional “book canon” toggle that includes them.

Coordinate drift has also become an issue. Slight repositioning of King’s Landing’s Red Keep after season-eight reshoots forced every map to recalibrate street-level pins. The change affected roughly forty named-character deaths, prompting a community-wide verification pass.

Despite the tweaks, the core Washington Post numbers remain unchallenged. No competing count has emerged that matches the Post’s frame-by-frame methodology, so the maps continue to share a single authoritative dataset.

Accessibility features expand reach

Polygon introduced color-blind modes in its January 2026 patch, replacing red death pins with high-contrast symbols. Screen-reader support now reads episode numbers and cause-of-death aloud, widening the map’s utility for visually impaired fans.

ThroneAtlas added downloadable KML files so users can import the full Game of Thrones map into Google Earth for offline study. The files preserve every layer, including house territories and travel routes, without requiring an internet connection.

These upgrades coincide with renewed streaming numbers. HBO Max reported a 34 percent uptick in Game of Thrones rewatches during the first quarter of 2026, and map sites recorded matching traffic spikes.

Next steps for map developers

Teams are already preparing for potential Bloodmoon and Sea Snake spin-offs by building modular data tables that accept new region coordinates without breaking existing pins. The goal is to keep one master Game of Thrones map functional across every announced project.

Partnership talks with HBO’s official website are ongoing. If a deal closes, the current fan-built tools could migrate to an official domain while retaining the open-source data that made them reliable in the first place.

Until then, viewers rely on the same three sites to answer the evergreen question of where every major character actually died, turning eight seasons of scattered violence into a single, clickable atlas.

Practical takeaway for viewers

Bookmark one map, keep the Washington Post numbers as reference, and toggle layers according to the series you are currently rewatching. The geography of death in Westeros stays consistent; only the pins multiply as new episodes air.