Nomad — CS2 Stats
NZ76561198075791699[U:1:115525971]Steam profile ↗✓ No bans
What changed since last observed
CSDB last observed this profile on 19 Oct 2026 (27 days ago). Ranks are recorded once per day this page is viewed.
Rating over time
Faceit ELO
- At peak — 1,761
- 0 over 30 days · steady
- Next: Level 10 at 2,001 — 240 to go
- Reached: Level 9 · Level 8 · Level 7 · Level 6
- Level 9 first seen 2026-09-15
- Level 8 first seen 2026-09-15
Premier CS Rating
- At peak — 27,373
- +3,595 over 30 days · improving
- Next: Gold band at 30,000 — 2,627 to go
- Reached: Red band · Pink band · Purple band · Blue band
- Pink band first seen 2026-09-15
- Purple band first seen 2026-09-15
Premier is CSDB’s own observation — it builds from the day a profile is first viewed and cannot be backfilled. Faceit ELO is CSDB’s own observation — no feed exposes ELO per match, so that line only has the days the profile was viewed and cannot be backfilled.
Share this profile
The image is a snapshot; the link keeps updating. Nothing here is published anywhere — it is generated in your browser when you click.
Performance scores
0–100 skill scores via Leetify.
Player DNA
Primary style: Support — Utility contribution stands above the rest of this profile (+2.3 against its own average).
Sharp aimerStrong CT-side opener
Style profile from tracked-match aggregates — how this player plays, not how good they are. Classification rules are deterministic and documented in code.
What this cannot see yet: which weapons you use — so CSDB cannot identify an AWPer, and no style here implies a rifle or a sniper. It also cannot see how often you take opening duels, only how often you win them, nor where you hold, so roles that depend on those (entry, lurk, anchor) are deliberately absent rather than guessed. All of it needs round-by-round demo data, which is the next thing being built.
Your pro match
Plays most like NiKo 92% playstyle similarity
Most alike: utility contribution, positioning profile.
Similarity of playstyle shape across shared dimensions — it says how you play, not that you play at their level. Full comparison →
Strengths & areas to improve
Strengths
Aim. Aim score of 86 — the mechanical foundation is a clear strength.
Areas to improve
Positioning. Positioning trails aim by 31 points — deaths here waste a strong aim profile.
T-side openings. Opening success drops from 53% on CT to 27% on T — the same duels are being taken with worse setups on the attacking side.
Reaction time. 602ms from enemy-visible to first shot leaves fights decided before they start — warmup routines move this number more than anything else.
Generated by fixed rules over this profile's own numbers — no model, no guessing; silent when the sample is too small to support a claim.
CSDB Rating breakdown
Composite 7.1/10 (Strong), a weighted mean of the bars with a small opposition adjustment (×1.05 for this rank band). Formula versioned (v1) and documented in code.
Faceit stats
Combat
Clutches & streaks
Recent Faceit resultsWWWWL
| Map | Matches | Win rate | Avg K/D | Avg kills |
|---|---|---|---|---|
| Mirage | 94 | 44% | 1.08 | 15.2 |
| Dust2 | 55 | 53% | 1.09 | 15.2 |
| Inferno | 46 | 65% | 1.20 | 15.4 |
| Ancient | 27 | 48% | 0.98 | 14.2 |
| Nuke | 21 | 43% | 0.96 | 14.1 |
| Anubis | 16 | 50% | 0.97 | 14.3 |
| Cache | 14 | 57% | 1.27 | 13.4 |
| Overpass | 10 | 30% | 0.76 | 12.6 |
Faceit-match stats via the FACEIT Data API — a separate match pool from the sections above.
Skill profile
Aggregate performance across tracked matches — stats via Leetify. Percentile context against other CSDB-tracked players arrives as our own benchmark data accumulates.
Recommended for you
Chosen by comparing your tracked metrics against the thresholds we flag — the measurement behind each one is shown, so you can disagree with it.
- Advanced Mechanics
You are losing most of the first duels you take on T side, which is usually a peeking and spacing problem, not aim.
T opening duels 27.3936% — below the 40% mark we flag
Milestones
This profile is built from public Steam data. If it is yours, you can remove it, or delete your CSDB account.