Onslaught

Onslaught — CS2 Stats

76561198004777684[U:1:44511956]Steam profile ↗✓ No bans

2,564Tracked matches57%Win rate2020Tracked since
CSDB Rating6.9 SolidSupport
Premier CS Rating20,000Top 50% of 212,379 CSDB-tracked playersPink band · top ~8.5% of ranked players (population est.)
CSDB Leaderboard#82906 of 259189 tracked
FaceitLevel 8 · 1,732 ELOTop 31.2% of ranked FACEIT players
Ladder ranks via Leetify

What changed since last observed

CSDB last observed this profile on 29 Oct 2026 (3 days ago). Ranks are recorded once per day this page is viewed.

No change since then. Play, then come back: the next observation lands here.

Rating over time

Premier CS Rating: 20,000 +255 1 Sept – 29 Oct · 25 days played
19,37020,381peak 20,3811 Sept29 Oct
20,381Peak Premier in tracked matches
1,732Highest Faceit ELO seen on CSDB
35Days played since 2026-09-01

Faceit ELO

  • At peak — 1,732
  • Next: Level 9 at 1,751 — 19 to go
  • Reached: Level 8 · Level 7 · Level 6 · Level 5
  • Level 8 first seen 2026-09-01
  • Level 7 first seen 2026-09-01

Premier CS Rating

  • 381 below peak (20,381)
  • +124 over 30 days · steady
  • Next: Red band at 25,000 — 5,000 to go
  • Reached: Pink band · Purple band · Blue band · Light Blue band
  • Pink band first seen 2026-09-03
  • Purple band first seen 2026-09-01

Premier comes from this profile’s tracked match history, so it reaches back as far as those matches do. Faceit ELO is recorded after matches CSDB sees, so those points are days actually played — but only from the day tracking started: no feed exposes the ELO a past match ended on, so nothing before it can be backfilled.

Share this profile

CSDB.GGOnslaughtFACEITLevel 8 · 1,732 ELOSTANDINGTop 31.2% of rankedPREMIER20,000 · Pink bandPEAK ELO1,732csdb.gg/stats

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

Aim74
Positioning63
Utility65

0–100 skill scores via Leetify.

Recent form

STEADY48–51–1Last 10048%Win rateWLLLLWWLWW

Last 10 vs previous 10: −10pp win rate · −0.01 avg rating · +1.1pp headshot accuracy · −27ms reaction

Win rate −10pp across the last 10 against the 10 before — within the normal variation of a 10-match window (±20pp), so no real shift yet.

Last 5 · 10 · 20 matches

Last 5

  • 1–4 · 20% win rate
  • Avg rating -0.00
  • Avg headshot accuracy 19%
  • Avg reaction 556ms

Last 10

  • 5–5 · 50% win rate
  • Avg rating 0.01
  • Avg headshot accuracy 23%
  • Avg reaction 551ms

Last 20

  • 11–9 · 55% win rate
  • Avg rating 0.02
  • Avg headshot accuracy 22%
  • Avg reaction 564ms

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

Player DNA

Primary style: Support — Utility contribution stands above the rest of this profile (+1.6 against its own average).

Aim7.4
Utility6.5
Positioning6.3
Opening Duels3.1
Clutch3.6

Strong 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

iM

Plays most like iM 85% playstyle similarity

Most alike: opening-duel success, positioning profile.

Where you differ: 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. 583ms 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

Aim7.4
Positioning6.3
Utility6.5
Mechanics7.5
Opening Duels5.0
Win Impact7.2

Composite 6.9/10 (Solid), a weighted mean of the bars with a small opposition adjustment (×1.02 for this rank band). Formula versioned (v1) and documented in code.

Trends

Match rating0.01+0.01
first ⅓ avg -0.00 → last ⅓ avg 0.01
Reaction time584ms−20ms
first ⅓ avg 605ms → last ⅓ avg 584ms
Headshot accuracy20.8%−0.9%
first ⅓ avg 21.7% → last ⅓ avg 20.8%

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

Personal bests

0.18Best match rating · 11–13 · inferno, 25 Sept →
50%Best headshot accuracy · 2–13 · cache, 17 Sept →
391msFastest reaction time · 10–13 · anubis, 12 Sept →
13–2Biggest win · dust2, 25 Oct →

Across the last 100 tracked matches.

Highlights

7Longest win streak
10–8In matches decided by ≤2 rounds
12Overtime games

Map breakdown

anubisBest map · 57% over 14nukeWeakest map · 40% over 10
MapGradePlayedRecordWin rateAvg rating
infernoB199–1047%0.03
dust2C177–1041%0.00
ancientC167–944%0.00
anubisA148–657%0.00
mirageB126–650%0.00
cacheA116–555%0.02
nukeC104–640%0.01
fachwerk—11–0100%0.04

Across the last 100 tracked matches.

Nuke is currently your weakest sufficiently-sampled map (40% over 10). Start with the 6 essential Nuke lineups, review the callouts, then spin up a practice server.

Faceit stats

Combat

1,187Matches
50%Win rate
1.21Avg K/D
80.3ADR
49%Headshot %

Clutches & streaks

38%1v1 clutch win
27%1v2 clutch win
12Longest win streak

Recent Faceit resultsWLLLW

MapMatchesWin rateAvg K/DAvg kills
Ancient17257%1.1216.2
Inferno14054%1.2416.5
Dust212744%1.2016.8
Mirage11949%1.1215.9
Anubis9355%1.1116.1
Nuke8743%1.1516.8
Overpass3855%1.1717.5
Cache2236%1.1515.4

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.

21.6%Headshot accuracy
35.2%Accuracy (enemy spotted)
34.0%Spray accuracy
83.7%Counter-strafing
10.3°Preaim
583msReaction time
47.9%T opening success
51.7%CT opening success
0.47Enemies flashed / flash
7.5%Flash assists
9.35HE damage / grenade
16.23Flashes / 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.4668 — below the 0.5 mark we flag

    Grenade Lineups →
Spend your practice time on Nuke

Map knowledge compounds faster than mechanics — lineups and callouts you learn once keep paying out every time the map comes up.

40% win rate across 10 tracked games — your weakest map with enough games to be worth reading into.

Nuke callouts & strategy →Nuke grenade lineups →

Recent matches

MapScoreRatingHS%Date
ancient13–40.0215%30 Oct →
ancient3–13-0.0811%29 Oct →
dust27–130.0121%29 Oct →
inferno6–130.0622%29 Oct →
dust210–13-0.0224%29 Oct →
cache16–120.0621%27 Oct →
inferno13–80.0034%27 Oct →
inferno11–130.0232%27 Oct →
dust216–140.0622%26 Oct →
ancient13–110.0126%26 Oct →
mirage13–50.0720%26 Oct →
inferno13–70.0622%25 Oct →
dust213–20.0316%25 Oct →
ancient13–110.0723%25 Oct →
nuke13–90.0531%25 Oct →
ancient2–13-0.0513%25 Oct →
ancient13–6-0.0023%24 Oct →
dust28–130.0120%24 Oct →
nuke9–130.0021%24 Oct →
cache4–13-0.0228%24 Oct →
mirage20–220.0418%24 Oct →
nuke11–13-0.0122%23 Oct →
dust213–10-0.0414%23 Oct →
anubis13–100.0212%23 Oct →
nuke16–130.0329%23 Oct →
anubis13–40.0131%23 Oct →
dust26–13-0.0218%20 Oct →
cache13–30.0223%19 Oct →
dust212–16-0.0123%19 Oct →
inferno13–110.0311%16 Oct →
mirage13–20.0414%16 Oct →
inferno7–13-0.0710%16 Oct →
ancient16–130.0118%15 Oct →
anubis13–90.0427%15 Oct →
anubis16–120.0027%15 Oct →
nuke8–13-0.0430%15 Oct →
cache16–130.0222%11 Oct →
anubis13–100.0318%11 Oct →
inferno13–4-0.0044%11 Oct →
inferno14–160.0223%11 Oct →
mirage10–13-0.0419%10 Oct →
cache13–80.0929%10 Oct →
anubis8–130.0328%10 Oct →
inferno13–110.0120%10 Oct →
nuke9–13-0.0225%10 Oct →
ancient2–130.0115%7 Oct →
nuke13–80.1027%7 Oct →
inferno13–60.1424%7 Oct →
inferno11–13-0.0214%6 Oct →
inferno15–15-0.0121%6 Oct →
cache13–70.1121%6 Oct →
ancient13–9-0.0711%6 Oct →
cache11–13-0.0114%5 Oct →
inferno13–6-0.0017%5 Oct →
nuke13–50.0631%1 Oct →
fachwerk13–50.0437%1 Oct →
mirage8–130.0118%1 Oct →
mirage13–40.0718%1 Oct →
dust25–130.0420%30 Sept →
ancient6–130.1225%30 Sept →
mirage9–13-0.0828%28 Sept →
inferno13–90.0922%27 Sept →
ancient10–130.0120%27 Sept →
mirage19–15-0.0817%27 Sept →
ancient7–13-0.0020%26 Sept →
anubis13–90.0320%26 Sept →
anubis8–130.0021%26 Sept →
dust23–13-0.0112%26 Sept →
dust22–13-0.0219%26 Sept →
cache7–13-0.0222%25 Sept →
anubis5–13-0.1033%25 Sept →
mirage13–11-0.0123%25 Sept →
ancient8–130.0120%25 Sept →
dust213–90.0332%25 Sept →
cache11–13-0.0232%25 Sept →
inferno11–130.1819%25 Sept →
dust213–9-0.0115%23 Sept →
anubis10–13-0.0113%21 Sept →
inferno13–11-0.0218%21 Sept →
mirage10–13-0.0327%19 Sept →
mirage13–70.0621%18 Sept →
anubis16–14-0.0124%18 Sept →
anubis13–10-0.0027%17 Sept →
dust213–90.0221%17 Sept →
inferno5–130.0029%17 Sept →
cache2–13-0.0750%17 Sept →
ancient13–11-0.0120%16 Sept →
inferno9–13-0.0121%14 Sept →
anubis10–130.0214%12 Sept →
inferno7–130.0113%12 Sept →
mirage7–130.0019%12 Sept →
dust213–30.1217%12 Sept →
dust25–13-0.0412%11 Sept →
anubis7–13-0.0621%11 Sept →
cache13–110.0227%11 Sept →
ancient3–13-0.0517%9 Sept →
nuke7–130.0027%8 Sept →
ancient9–130.0713%7 Sept →
dust24–13-0.0814%7 Sept →
nuke6–13-0.0423%4 Sept →

Match data via Leetify.

Recent teammates

Milestones

1,000 Matches
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.