76561199378537123
Performance Snapshot
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
-12%Game details are private - can't verify CS2 playtime
Game details are private - can't verify game library (already accounted for once via CS2 Hours above)
Friends list is private - can't verify
Inventory is private - can't verify
Profile is private - signals can't be verified
Combined 'can't verify' penalties from private profile/inventory/hours/friends totalled -22%. Being private is a weak signal, not evidence - capped at -12% so privacy alone can't push a clean account out of the Trusted band.
Ban History
-13%Base penalty -25% (1 ban × 25%, capped 50%) × age weight 0.5
Our Own Match Data
-0.8%Peak single-match outcome anomaly 8.4/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.
Leetify Breakdown
Matches in our system
| Match | Map | K/D/A | ADR | Rating | Datum |
|---|---|---|---|---|---|
| CSGO-Cptbd-99yCD-Aqcst-eVanj-iP5mA |  de_ancient |
10/14/3 | 58.8 | 0.79 | 2026-07-03 16:08:17 · 23m 54s |
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.