76561197972347965
vertigo
Performance Snapshot
DKAim 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
-1%Account is 1+ years old
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)
5+ friends
round(level / 10), capped at +3
3+ badges owned
Inventory is private - can't verify
Our Own Match Data
-5.3%Peak single-match outcome anomaly 16.1/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.
3.2% 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 · last 30 matches
Aim profile (Ø %)
Leetify Breakdown
Matches in our system
| Match | Map | K/D/A | ADR | Rating | Datum |
|---|---|---|---|---|---|
| CSGO-iKACQ-JaCXX-GiFur-yv7Z9-nUoEM |  de_ancient |
31/19/6 | 103.6 | 1.50 | 2026-06-25 21:02:41 · 49m 6s |
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.