CS2 demo stats, explained
CS2 demos record far more than the final scoreboard. This guide explains what FragLedger reads from a demo and how those events become match stats.
What a demo shows beyond the scoreboard
End-of-match scoreboards are useful, but they collapse a round into a few counters. A .dem replay contains ordered deaths, damage, utility, bomb events, and the same official cumulative totals Valve shows in-game.
FragLedger compares the round-by-round kills, assists, and headshots with Valve’s cumulative totals. If they don’t agree, we flag the match instead of presenting the stats as complete.
What we extract today
- Map, terminal score, and complete 2v2 or 5v5 roster (SteamID64)
- Per-round kills, deaths, assists, damage, headshots, survival, trades
- Opening duels and trade window under a versioned five-second method
- Ordered death log (weapon, HS, flash assist, wallbang…)
- Diagnostic utility: flashes, grenade outcomes, bomb lifecycle (where present)
- Match aggregates: ADR, HS%, KAST, Frag Rating — see the glossary
When we don't have the data
Stats without a verified extractor stay unavailable instead of showing a zero. That includes unverified distance units, spray heatmaps, and matchmaking queue labels for Valve demos.
Surrendered matches can end early. If the demo shows a surrender, we record the match as it ended rather than filling in rounds that were never played.
Scoreboard-only trackers vs demo parsing
Scoreboard APIs are fast and show the final K/D. A demo can answer more detailed questions, such as who died first on banana in round 14, which weapon was used, and whether a teammate traded. FragLedger keeps the final score and adds those round details.
That choice has trade-offs. Demos are large. Parses take seconds to minutes. Some matches never publish a downloadable demo. When that happens, FragLedger shows that the demo is still unavailable rather than marking the match complete.
If you only need a leaderboard number, another site may be faster. For reviewing a round or talking through a match with friends, the demo provides the detailed event record.
Utility, aim, and geometry when the demo supports them
Grenade timelines, flash durations, HE damage, and fire damage appear when the demo includes those events. Smoke duration and position clusters also need coordinates in the file; without them, those stats aren’t available.
Kill geometry (attacker and victim positions at death) can feed Practice drills when it is present in the demo. Pro includes tools for reviewing decisions, cues, mechanics, and practice. A drill score does not show how you will perform in a live match.
For formulas that turn sample aggregates into Frag Rating or risk scores, see methodology. For component definitions, see the glossary.
A simple demo-review workflow
- Import the match via share code and wait for the parse to finish.
- Open the match and check the score, map, and your K/D/ADR before taking a closer look.
- Skim death order for the rounds you lost — who opened, who traded.
- Look for repeated death locations. Practice drills can turn recurring fights into practice when the demo includes position data.
- Compare utility usage on maps you play often. Empty stat groups mean the demo didn't include those events, not that you used none.
Parse your next demo
Sign in with Steam and add a match share code to start tracking. You can change your profile visibility in Account settings.
Open your match history
Saved matches include their scoreboards, round events, and processing status.