prince — CS2 Stats
76561197976147385[U:1:15881657]Steam profile ↗✓ No bans
CSDB reads this profile's Premier rating from its tracked match history, and records Faceit ELO once on every day the page is viewed. Today is the first observation — history builds from here and cannot be backfilled. Come back after the next session and the change shows above.
Is this you? Sign in with Steam to claim it and connect match tracking →
How this compares with the same rank
Median values for Level 9 among CSDB-tracked players (n=12,569), from Valve's own lifetime stats. Aim, positioning and utility scores are deliberately not benchmarked here — those are a third-party provider's derived metrics, which CSDB does not store.
| Metric | This player | Level 9 median | Level 10 median | vs Level 10 |
|---|---|---|---|---|
| Headshot rate | 65.9% | 48.3% | 51.0% | above |
| Shot accuracy | 18.7% | 13.2% | 13.7% | above |
| Kill/death ratio | 1.11 | 1.07 | 1.09 | above |
| Match win rate | 68.0% | 46.9% | 48.4% | above |
Across every metric we can compare, this profile already matches the typical Level 10 player. Rank still comes from winning matches — this is a performance comparison, not a prediction.
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: Opening Duellist — Winning opening duels is what stands out in this profile (+1 against its own average). How often you WIN the first duel — CSDB cannot yet see how often you take it.
Sharp aimer
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 m0NESY 95% playstyle similarity
Most alike: aim profile, positioning profile.
Where you differ: lower utility contribution.
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 92 — the mechanical foundation is a clear strength.
CT openings. 67% CT opening-duel success — winning the first fight on the defending side is rare and valuable.
Areas to improve
Utility. Utility contribution runs far behind the mechanical game — the cheapest rating gain on this profile is thrown, not aimed.
T-side openings. Opening success drops from 67% on CT to 47% on T — the same duels are being taken with worse setups on the attacking side.
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.9/10 (Strong), a weighted mean of the bars with a small opposition adjustment (×1.02 for this rank band). Formula versioned (v1) and documented in code.
Lifetime stats
Most-used weapons
Lifetime map wins
Lifetime totals via Steam — visible because this profile's game details are public. Spans CS:GO and CS2.
Faceit stats
Combat
Clutches & streaks
Recent Faceit resultsLWLWL
| Map | Matches | Win rate | Avg K/D | Avg kills |
|---|---|---|---|---|
| Mirage | 26 | 65% | 1.77 | 21.9 |
| Dust2 | 16 | 69% | 2.19 | 24.6 |
| Ancient | 8 | 50% | 1.55 | 23.0 |
| Inferno | 5 | 100% | 1.26 | 20.4 |
| Overpass | 4 | 50% | 1.65 | 23.5 |
| Nuke | 1 | 100% | 1.82 | 20.0 |
| Train | 1 | 100% | 1.40 | 21.0 |
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.