76561198020402893
dust2
train
anubis
ancient
Performance Snapshot
Aim Analysis
Reference: pro level (dashed) · to the right = better than a typical pro = suspicion signal.
TeamDocks Match Data
Wallbang/smoke/distance signals need at least 2 of this player's matches processed with kill-level analysis - will fill in as more of their matches get analyzed.
Trust Breakdown
Our own heuristic from Steam signals, playtime, FACEIT and Leetify behaviour. Not a cheat verdict, not affiliated with Valve/Steam/Leetify/FACEIT/HLTV.
Score starts at 100. Every row below shows the exact rule that fired and its effect in percent - directly the same points that make up the 0-100 score.
Account Signals
+7%Account is 1+ years old
300h+ in CS2
2000h+ across the whole Steam library
10+ games owned - real library
Friends list is private - can't verify
round(level / 10), capped at +3
3+ badges owned
Inventory is private - can't verify
Cross-Platform Consistency
-15%Premier 27090 (top ~5% band) with zero FACEIT presence and Leetify aim rating 88.1/100 - two independent elite-skill signals with no FACEIT corroboration
Our Own Match Data
-3%Peak single-match outcome anomaly 17.9/100 (rating/ADR/KD/HS% combined) — above the network average of all analyzed performances. Confirmed-banned cheaters average ~2.3x the network's typical peak. Dampened — only 1 of this player's matches analyzed so far, so this is provisional.
Recent Form · last 30 matches
Aim profile (Ø %)
Leetify Breakdown
Matches in our system
| Match | Map | K/D/A | ADR | Rating | Datum |
|---|---|---|---|---|---|
| CSGO-eOaUq-NWwyw-3eHkB-CSZzT-vaChP | de_dust2 |
23/12/4 | 86.2 | 1.58 | 2026-06-23 14:01:55 · 30m 52s |
Kill & death map
Where this player gets their kills (and dies), aggregated across every match we've parsed, drawn over the map radar.
Mechanics
Utility usage, movement discipline, and spray control - computed from real per-tick demo data, not estimated. Only matches we've fully processed count toward these numbers.
Friends Network
Steam friends list signals - not from our own match data. Only computed on demand, cached 6h.