Frequently asked questions

cstracker.gg is a Counter-Strike 2 statistics site that turns processed match data into searchable player profiles, match reports, leaderboards, and charts.

Profiles can show Steam identifiers, aliases seen in matches, avatars from Steam, inferred country or region signals when available, rank and performance statistics, teammate and opponent history, and match-derived events such as kills, damage, grenades, rounds, and timings.

Steam supplies publicly reachable profile and account information. External match indexes and share codes supplied by users help cstracker.gg discover matches. The site then downloads available CS2 demos and parses them to calculate player statistics, match reports, events, and timelines.

A match appears only when its demo can be found, downloaded, and parsed. Matches may be absent because the site has not discovered them, the demo is unavailable or expired, processing is still pending, or the demo could not be parsed. You can help us cover more matches and players by signing in and adding your match share codes.

Match reports appear after the match has been discovered, downloaded, and processed. Player summaries, leaderboards, and charts use cached aggregate data that normally refreshes hourly, so they may update later than the individual match report.

Yes. Sign in with Steam and add your game authentication code and match sharing code. This lets cstracker.gg discover subsequent matches for that Steam account. Unfortunately, manual demo uploads are not supported, as this allows bad actors to change player stats.

Not necessarily. The supplied sharing code acts as a starting point for discovering later matches. Older matches are not guaranteed to be available, and Valve retains demos for only about 30 days.

No. It is the separate CS2 match-history authentication code created through Steam Support. Never enter your Steam password or Steam Guard code on cstracker.gg.

They are stored server-side, associated with the Steam account that submitted them, and used to request future match sharing codes from Steam. You can revoke the game authentication code through Steam Support at any time.

Authentication is performed by Steam through OpenID. cstracker.gg receives your SteamID; it does not receive your Steam password or Steam Guard code.

Signed-in users can search tracked players by name, view complete leaderboards, inspect frequent teammates and grenade locations, see player location estimates, and request Steam or FACEIT profile refreshes. SteamID and vanity-URL searches remain available without signing in.

Not every demo contains every field, and some metrics need specific events or a minimum number of samples. A dash means the value could not be calculated reliably from the available tracked data.

Most profile totals cover all matches currently tracked for that player. The telemetry analysis and its percentile badges use only the player’s latest 90 tracked matches, or fewer if 90 are not available.

They compare the player with other tracked players who have data for that metric. “Top 5%” means the value falls within the strongest or most extreme five percent of that tracked cohort; it does not refer to every CS2 player.

ADR is average enemy damage per round. KAST is the percentage of rounds in which the player recorded a kill, assist, survived, or was traded. HLTV 2.0 rating is a combined performance estimate calculated from match statistics.

TTD is the time from first spotting an enemy to dealing damage. TTK is the time from spotting an enemy to securing the kill. Preaim measures the crosshair’s angular offset from the enemy before a fight. Crosshair placement measures the eye-angle adjustment between first seeing an enemy and the first damaging shot. Lower values are generally better.

They indicate values crossing cstracker.gg’s statistical review thresholds. They highlight unusual data; they are not definitive proof of cheating.

It is an experimental site score that starts at 100. Recent FACEIT activity can raise it, while Steam bans, VAC-live-like rating resets, unusual telemetry, kill patterns, disruptive behaviour, and low-trust teammate history can reduce it.

Not necessarily. The score is a heuristic, not an anti-cheat verdict. Strong players, unusual playstyles, small sample sizes, smurfs, or incomplete data can all affect it.

Ban information comes from the player’s Steam profile. A badge reports Steam’s account status; it does not mean cstracker.gg detected cheating or that a ban relates to a particular displayed match.

Ranks come from the latest tracked match containing rank data. FACEIT and Steam profiles are refreshed separately and may be cached, so the displayed value can lag behind the live service.

The relevant metric must exist in processed data and be greater than zero where applicable. Newly processed results may also wait for the next aggregate refresh, and leaderboards have a finite maximum size.

It is inferred from the player’s latency across known CS2 server locations. It is an approximation, not GPS data, and can be wrong because of routing, VPNs, distant servers, limited samples, or sparse regional server coverage.

For removal, correction, restriction, objection, access, deletion, GDPR, or other privacy requests, email [email protected]. Include the relevant Steam ID, profile URL, or match and enough detail to explain what you want reviewed.

For non-privacy operational issues, email [email protected].