Performance Snapshot
TeamDocks Match Data
TeamDocks Rating
Our own 0–100 skill index, a weighted composite of every performance dimension we can measure from this player's parsed demos — not Leetify's rating. Each row below shows its raw value, its 0–100 sub-score and how many points it contributed to the final number.
Weighted across 8 measured dimensions; weights renormalize over whatever data we have.
Final score = weighted average of each dimension's 0–100 sub-score. Contribution = sub-score × (renormalized weight). Not affiliated with Valve/Leetify/FACEIT — this is our own measure from our own demo parsing.
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.
Our Own Match Data
-26.2%Peak single-match outcome anomaly 36.7/100 (rating/ADR/KD/HS% combined) — top few % of all analyzed performances. Confirmed-banned cheaters average ~2.3x the network's typical peak.
22.1% of kills through walls across 5 analyzed matches (penalty scales above 4%)
2.6% of analyzed kills had the crosshair already tracking the target under 150ms before the shot, at 10m+ range (penalty scales above 2.5%)
Recent Form
TeamDocks rating & ADR trend · last 5 analysed matches
Matches in our system
| Match | Map | K/D/A | ADR | Rating | Datum |
|---|---|---|---|---|---|
| CSGO-iqn8i-GNdhZ-OMAXY-yFjVV-j7xbE |  de_dust2 |
8/14/2 | 51.9 | 0.62 | 2026-07-03 01:53:45 · 19m 44s |
| CSGO-oUoAh-e9k3v-sDh9c-smyKF-zdTnB | de_dust2 |
25/12/9 | 132.8 | 1.85 | 2026-07-03 01:53:45 · 34m 11s |
| CSGO-rTaZn-WoW9s-Qc4Gs-sZbvi-uipNO |  de_overpass |
16/14/9 | 98.4 | 1.31 | 2026-07-03 01:53:45 · 34m 48s |
| CSGO-3eaoA-mimCt-ja4UL-LAKaS-xGUrC | de_dust2 |
20/14/2 | 82.4 | 1.30 | 2026-06-18 13:56:24 · 37m 16s |
| CSGO-LjAXc-9YXfb-bVzhh-iOZYq-ihtnC |  de_nuke |
8/11/5 | 61.8 | 0.87 | 2026-06-18 13:28:58 · 23m 18s |
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.