Is someone cheating in your CS2 match?
CS2Scan analyses any public Steam profile and returns a cheat-probability score built from real CS2 statistics, enforcement history and friend-graph ban density. No downloads, no sign-ups — paste a URL and get a scored breakdown in seconds.
Profile analysis
8 enginesTwo public Steam accounts, here only to show what a finished readout looks like.
Recent scans
- 46m ago32Anomaly index 32 of 100, Minor Anomalies, confidence 80 percent, 46m ago.
- 2h ago—LimitedAnomaly index — of 100, Indeterminate, confidence 24 percent, 2h ago, limited data.
- 5h ago8Anomaly index 8 of 100, Clean Player, confidence 84 percent, 5h ago.
- 11h ago24Anomaly index 24 of 100, Clean Player, confidence 77 percent, 11h ago.
- 11h ago—LimitedAnomaly index — of 100, Indeterminate, confidence 24 percent, 11h ago, limited data.
- 11h ago—LimitedAnomaly index — of 100, Indeterminate, confidence 24 percent, 11h ago, limited data.
- 11h ago8–20Anomaly index 8–20 of 100, Clean Player, confidence 69 percent, 11h ago.
- 11h ago—LimitedAnomaly index — of 100, Indeterminate, confidence 24 percent, 11h ago, limited data.
- 11h ago17–35Anomaly index 17–35 of 100, Clean Player, confidence 52 percent, 11h ago.
- 14h ago13–31Anomaly index 13–31 of 100, Clean Player, confidence 49 percent, 14h ago.
- 16h ago30Anomaly index 30 of 100, Clean Player, confidence 80 percent, 16h ago.
- 19h ago16–28Anomaly index 16–28 of 100, Clean Player, confidence 67 percent, 19h ago.
Scores only — no names, avatars or profile links. A statistical estimate is not evidence, so we do not attach one to a person in public.
Eight engines, one verdict
Accuracy
Shot-to-hit conversion overall and per weapon class, against the population curve.
Precision
Headshot conversion rate and its distance from the legitimate distribution.
Network
Ban density across the friend graph — the strongest signal in public Steam data.
History
VAC, game, economy and community enforcement plus account provenance.
Efficiency
K/D, kills per hour, damage per round, MVP rate and win rate.
Competitive
Per-match Valve matchmaking data — the only mode-pure signal available.
Opacity
How much of the account is deliberately hidden from inspection.
Anomaly
Multi-dimensional outlier distance from the population centroid.
Consensus
Weighted vote across all eight, scaled by each engine's data confidence.
What the score means
Bands at full confidence. Below 70% confidence the scale collapses to three; below 35%, to one.
Clean Player
Normal gameplay patterns detected. Player statistics align with expected legitimate behavior.
Minor Anomalies
Some unusual patterns observed but still within legitimate parameters. Likely a skilled player.
Threshold Zone
Confidence threshold exceeded. Player flagged for potential cheating behavior requiring review.
Likely Cheating
Multiple suspicious patterns detected. Strong indicators suggest use of external assistance.
High Confidence
Overwhelming statistical evidence. Anomalies far exceed normal gameplay patterns.
Confirmed Cheater
Extreme confidence level. Patterns match known cheat signatures with near certainty.
From Steam URL to verdict
Find the player
Paste a profile URL, search by display name, or drop your CS2 `status` console output to scan the whole lobby.
Engines analyse
Eight engines pull live Steam and Leetify data and score every readable feature against population baselines.
Read and share
A consensus score with per-engine breakdown, evidence rows, confidence — and a shareable link.
How to check if a CS2 player is cheating
Detecting cheaters in Counter-Strike 2 is hard. VAC bans can take weeks or months to land, and plenty of cheaters stay under the radar with subtle aim assistance or wall hacks that are not obvious mid-match.
CS2Scan reads every behavioural and statistical feature exposed by the Steam Web API for a given account, scores each one against a population baseline, and combines the results into a single probability with an explicit confidence level.
Unlike basic profile checkers that only echo VAC ban history, CS2Scan looks at the shape of the account: accuracy consistency across weapon classes, headshot conversion, output per hour, how much of the profile is hidden, and how many people in the friend graph are already banned.
Every number on the results page traces back to a specific Steam API field. Nothing is decorative — if an engine could not read the data it needs, it reports N/A and drops out of the vote.
Questions worth asking first
How accurate is the score?
Honestly: unquantified. The engines are hand-weighted heuristics scored against hand-set population baselines, not a model validated on a labelled dataset. Anyone publishing an F1 score for a tool in this category owes you the validation run that produced it. We don’t have one yet, so we don’t print one. Treat the score as a structured second opinion, not a verdict.
Does a high score mean the player is definitely cheating?
No. A high score means the account’s public statistics sit far from what is typical. Genuinely excellent players, smurf accounts and people who mostly play deathmatch all produce elevated scores for entirely legitimate reasons. The only body that can actually determine cheating is Valve.
Why does it say CS2 stats are unavailable?
Two possible reasons. Either the player set their game details to private, or Valve’s legacy stats endpoint simply has no record for that account — which is common on CS2-era profiles and is a limitation on Valve’s side, not a sign of anything. When it happens, several of the eight engines go dark and the confidence figure drops to match.
Why does the friend list matter so much?
Ban density across a friend graph is the strongest signal available from public Steam data. Cheaters cluster: they buy from the same sellers, queue together and add each other. An individual stat line is noisy because a very good legitimate player looks much like a cautious cheater — but a friend list where a quarter of accounts are banned is hard to produce by accident.
Can I analyze a private profile?
Partly. Ban history is public for every account, so the History Engine always runs. The Opacity Engine treats hidden data as weakly informative in itself. Everything else needs readable stats, so a private profile returns a low-confidence result — and the page tells you so rather than quietly guessing.
Will being scored here get someone banned?
No. CS2Scan has no connection to Valve, no ability to action accounts, and reports nothing to anyone. It reads the same public endpoints any Steam user can read. If you genuinely believe someone is cheating, use the in-game report function — that is the channel Valve actually acts on.
Is this affiliated with Valve?
No. CS2Scan is an independent project and is not affiliated with, endorsed by, or connected to Valve Corporation. Counter-Strike is a trademark of Valve.
How do I get my profile removed?
Use the contact form below and pick “Profile removal”. Include the profile URL. Cached results for that account will be dropped. Note that nothing here is republished or indexed on your behalf — results exist only when someone actively looks a profile up.
Can I use this to name and shame someone?
Please don’t, and it isn’t built for it. There is no public leaderboard and no directory of flagged accounts. The recent-scans feed shows scores only — no names, avatars or profile links — deliberately. Posting a statistical score as an accusation against a named person is how people get harassed over false positives.
Get in touch
Bug reports, disputed scores and API questions all go here. If you think a score is wrong, tell us which engine looks off — the breakdown on the results page names every input it used, so a specific complaint is actionable.
Want your profile out of the cache? Pick Profile removal and include the URL. No justification needed.