EliGE

EliGE — CS2 Stats

SO76561199522735068[U:1:1562469340]Steam profile ↗✓ No bans

26Tracked matches64%Win rate2024Tracked since
33Hours in CS
CSDB Rating · provisional4.6 DevelopingPositional Player
Ladder ranks via Leetify

Performance scores

Aim41
Positioning51
Utility23

0–100 skill scores via Leetify.

Recent form

STEADY17–9Last 2665%Win rateWLLLWLWWLL

Last 10 vs previous 10: −40pp win rate · −0.01 avg rating · +9.9pp headshot accuracy · +78ms reaction

Win rate down 40pp across the last 10 against the 10 before — more than a 10-match window's normal noise (±20pp).

Last 5 · 10 · 20 matches

Last 5

  • 2–3 · 40% win rate
  • Avg rating 0.01
  • Avg headshot accuracy 17%
  • Avg reaction 647ms

Last 10

  • 4–6 · 40% win rate
  • Avg rating -0.01
  • Avg headshot accuracy 24%
  • Avg reaction 715ms

Last 20

  • 12–8 · 60% win rate
  • Avg rating -0.01
  • Avg headshot accuracy 19%
  • Avg reaction 676ms

Newest first, from the last 26 tracked matches. Each block is its own sample — one result moves a 5-match win rate by 20 points.

Player DNA

Primary style: Positional Player — Positioning stands above the rest of this profile (+1.1 against its own average).

Aim4.1
Utility2.3
Positioning5.1
Opening Duels4.5

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

donk

Plays most like donk 84% playstyle similarity

Most alike: positioning profile, utility contribution.

Where you differ: lower opening-duel success; lower aim 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

Areas to improve

Reaction time. 680ms 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

Aim4.1
Positioning5.1
Utility2.3
Mechanics5.5
Opening Duels1.8
Win Impact9.7

Composite 4.6/10 (Developing, provisional — under 30 tracked matches), a weighted mean of the bars with a small opposition adjustment (×1.00 for this rank band). Formula versioned (v1) and documented in code.

Trends

Match rating-0.01−0.09
first ⅓ avg 0.08 → last ⅓ avg -0.01
Reaction time673ms+19ms
first ⅓ avg 654ms → last ⅓ avg 673ms
Headshot accuracy25.2%+10.5%
first ⅓ avg 14.7% → last ⅓ avg 25.2%

Rolling 5-match average across the last 26 tracked matches, oldest to newest. The delta compares the first third of the window with the last.

Personal bests

0.18Best match rating · 9–1 · inferno, 19 Nov →
75%Best headshot accuracy · 6–12 · nuke, 19 Jun →
539msFastest reaction time · 13–9 · ancient, 18 Jun →
12–1Biggest win · nuke, 20 May →

Across the last 26 tracked matches.

Highlights

8Longest win streak

Map breakdown

Strongest and weakest map need 5+ matches on two different maps — 1 of 8 maps qualify so far.

MapGradePlayedRecordWin rateAvg rating
dust2S97–278%0.01
inferno—43–175%0.06
mirage—43–175%0.02
overpass—21–150%-0.03
anubis—20–20%-0.03
nuke—22–0100%-0.05
vertigo—20–20%0.06
ancient—11–0100%0.02

Across the last 26 tracked matches.

Lifetime stats

4,002Lifetime kills
2.32K/D · Top 1% of tracked players
57Matches
36.8%Match win rate
75.5%Headshot % · Top 1% of tracked players
0.0%Shot accuracy
79MVPs
33Hours (in match)
25Bombs planted
16Bombs defused

Most-used weapons

Lifetime map wins

130dust2
61inferno
20vertigo
19nuke
8train
1ar_shoots
1ar_baggage

Lifetime totals via Steam — visible because this profile's game details are public. Spans CS:GO and CS2.

Skill profile

Aggregate performance across tracked matches — stats via Leetify. Percentile context against other CSDB-tracked players arrives as our own benchmark data accumulates.

18.0%Headshot accuracy
29.8%Accuracy (enemy spotted)
33.8%Spray accuracy
74.8%Counter-strafing
11.5°Preaim
680msReaction time
31.7%T opening success
42.9%CT opening success
0.48Enemies flashed / flash
4.6%Flash assists
6.47HE damage / grenade
7.70Flashes / match

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.

  1. Grenades & Utility

    Most of your flashes are blinding nobody. A handful of reliable pop-flash lineups fixes this faster than anything else.

    Enemies flashed per flash 0.4751 — below the 0.5 mark we flag

    Grenade Lineups →
  2. 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 31.6636% — below the 40% mark we flag

Recent matches

MapScoreRatingHS%Date
inferno9–10.1818%19 Nov →
inferno5–13-0.0516%19 Nov →
mirage6–13-0.0312%19 Nov →
overpass3–13-0.0527%19 Nov →
dust213–9-0.0114%16 Nov →
anubis7–11-0.0323%21 Jun →
nuke6–12-0.1075%19 Jun →
ancient13–90.0217%18 Jun →
dust28–13-0.0720%18 Jun →
dust26–13-0.0122%16 Jun →
anubis2–6-0.0231%16 Jun →
dust213–6-0.0615%14 Jun →
mirage13–7-0.0515%14 Jun →
inferno13–6-0.049%7 Jun →
mirage13–110.0112%7 Jun →
dust213–4-0.0119%20 May →
nuke12–1-0.000%20 May →
dust213–8-0.0012%29 Jun →
overpass13–5-0.0011%18 Apr →
vertigo10–130.0921%29 Feb →
dust213–40.0810%29 Feb →
dust213–70.1512%29 Feb →
dust213–50.0116%29 Feb →
vertigo6–130.0320%19 Feb →
inferno13–80.1311%15 Feb →
mirage13–110.1518%14 Feb →

Match data via Leetify.

Recent teammates

Compare this player with someone →Inventory value for this account →Where does this rating sit? Premier rank tiers →

This profile is built from public Steam data. If it is yours, you can remove it, or delete your CSDB account.