From share code to match history
After you submit a match share code, Steam makes the demo available. FragLedger reads the file, checks the stats, and adds the match to your history.
What happens to your demo
- Find the demo — Steam uses your Game Authentication Code to look up the match and provide a demo link when the file is ready.
- Download — FragLedger downloads the Valve demo and records a hash of the file before reading it.
- Read the match — A parser running separately from the website reads the roster, rounds, deaths, damage, utility, and Valve’s cumulative totals.
- Check and save — The round events must agree with the scoreboard. FragLedger saves the match with a record of the demo used, so later parser updates don’t silently replace it.
Where each number comes from
Each stat is labeled by source. Match details such as the map and CS Rating come from Valve when available; stats such as KAST, trades, and Frag Rating are calculated from the demo. If there isn’t enough data, the stat is marked unavailable instead of shown as zero.
We only identify a queue when its source confirms it. Any FACEIT information is marked as coming from FACEIT.
What's public, what stays yours
Profiles are public by default. Your player page, search listing, and leaderboard entry are visible unless you make your profile private in Account settings. Your dashboard and match history require sign-in; we never publish tracking codes or demo files.
Read the privacy notice for retention and deletion.
Account context
Lobby scan checks up to ten Steam accounts for public signals such as VAC, game, and community bans, account age, CS2 hours, and how the rating compares with those hours. It combines the available signals into a 0–100 score using published weights. Any VAC ban on record puts the account in the critical band. The score can’t tell you whether someone cheated.
No ban record doesn’t prove an account is clean; Valve issues bans in waves. Missing information isn’t treated as a clean result. Public player pages can also show gameplay integrity signals when there’s enough match data. These compare behavior with the wider player population and show likelihoods with the supporting evidence. The exact weights and bands are on the methodology page.
Why match results don’t change silently
Once the round events agree with Valve’s totals, FragLedger saves the stats with a hash of the demo file. A future parser update can add a new measurement without replacing the saved result.
If the death events differ too much from Valve’s totals, we mark the import as failed rather than save results that may be wrong.
What you get for free
Free includes Steam sign-in, share-code tracking, demo parsing, match history, progress updates, and public profile controls. You can revisit completed matches and choose whether your profile is public.
Pro adds Decision review, Habit tracker, Performance breakdown, and Practice drills, along with session grouping, match insights, utility stats, and the Windows client. These tools use the matches you already track. Pricing and team options are listed on the plans page.
Limits of the demo data
- Queue types that aren't identified in the Valve demo
- Utility, aim, or clutch stats when the demo lacks the required events
- Cheat verdicts based on lobby risk or integrity scores
- Live opponent walls or memory-injection overlays that would risk VAC
Some match pages will have gaps when the demo doesn't include enough detail. Read more in the demo stats and about FragLedger.
Track your first match
Sign in with Steam, add the FragLedger bot as a friend, then enter your Game Authentication Code and a match share code. When the demo is ready, you'll find the match in your history.
Find your saved matches
Open your dashboard to see saved matches, scoreboards, and processing status.