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.
Provisional — based on only 2 analyzed matches. Firms up as more of this player's games get processed.
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
Our Own Match Data
-28.4%15.6% of kills through walls across 2 analyzed matches (penalty scales above 4%)
6.3% of analyzed kills had the crosshair already tracking the target under 150ms before the shot, at 10m+ range (penalty scales above 2.5%)
Matches in our system
| Match | Map | K/D/A | ADR | Rating | Datum |
|---|---|---|---|---|---|
| CSGO-yEdR6-3J965-O5MJJ-3CzhV-FaFSQ |  de_dust2 |
22/19/2 | 90.8 | 1.26 | 2026-07-02 12:17:51 · 36m 51s |
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.