Kim

Kim — CS2 Stats

NO76561198012606320[U:1:52340592]Steam profile ↗✓ No bans

724Tracked matches81%Win rate2020Tracked since
1,913Hours in CS
CSDB Rating6.4 SolidAll-Rounder
Ladder ranks via Leetify

Performance scores

Aim71
Positioning54
Utility50

0–100 skill scores via Leetify.

Recent form

HOT50–41–9Last 10050%Win rateWWWWWWWWTL

Last 10 vs previous 10: 0pp win rate · −0.01 avg rating · +2.1pp headshot accuracy · −56ms reaction

Win rate 0pp 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

  • 5–0 · 100% win rate
  • Avg rating 0.00
  • Avg headshot accuracy 17%
  • Avg reaction 608ms

Last 10

  • 8–1–1 · 80% win rate
  • Avg rating 0.00
  • Avg headshot accuracy 16%
  • Avg reaction 602ms

Last 20

  • 16–3–1 · 80% win rate
  • Avg rating 0.01
  • Avg headshot accuracy 15%
  • Avg reaction 629ms

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: All-Rounder — No style dimension stands clear of the others in this profile.

Aim7.1
Utility5.0
Positioning5.4
Opening Duels6.3

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

s1mple

Plays most like s1mple 88% playstyle similarity

Most alike: utility contribution, aim profile.

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

Areas to improve

T-side openings. Opening success drops from 59% on CT to 41% on T — the same duels are being taken with worse setups on the attacking side.

Reaction time. 641ms 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.1
Positioning5.4
Utility5.0
Mechanics6.1
Opening Duels5.0
Win Impact10.0

Composite 6.4/10 (Solid), 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 rating0.00+0.01
first ⅓ avg -0.01 → last ⅓ avg 0.00
Reaction time646ms+19ms
first ⅓ avg 627ms → last ⅓ avg 646ms
Headshot accuracy16.7%−0.3%
first ⅓ avg 17.1% → last ⅓ avg 16.7%

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.13Best match rating · 13–5 · cache, 19 Jun →
34%Best headshot accuracy · 13–11 · cache, 21 Jul →
484msFastest reaction time · 7–13 · inferno, 12 Jun →
13–0Biggest win · cache, 20 Jul →

Across the last 100 tracked matches.

Highlights

8Longest win streak
W8Current streak
2–5In matches decided by ≤2 rounds

Map breakdown

nukeBest map · 57% over 14dust2Weakest map · 40% over 10
MapGradePlayedRecordWin rateAvg rating
cacheB2312–1152%-0.00
mirageC177–1041%-0.02
infernoB178–947%-0.01
nukeA148–657%0.01
ancientA116–555%-0.03
dust2C104–640%-0.01
overpassA74–357%0.03
anubis—11–0100%0.02

Across the last 100 tracked matches.

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

Lifetime stats

58,113Lifetime kills
1.13K/D · Top 50% of tracked players
2,481Matches
47.0%Match win rate · Top 50% of tracked players
50.0%Headshot % · Top 25% of tracked players
16.0%Shot accuracy · Top 25% of tracked players
4,704MVPs
1,913Hours (in match)
2,085Bombs planted
524Bombs defused

Most-used weapons

Lifetime map wins

3,588inferno
3,555dust2
2,002nuke
683train
396cbble
374office
161vertigo
106aztec

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.

16.8%Headshot accuracy
37.8%Accuracy (enemy spotted)
43.1%Spray accuracy
77.4%Counter-strafing
9.9°Preaim
641msReaction time
41.0%T opening success
58.7%CT opening success
0.55Enemies flashed / flash
9.0%Flash assists
4.46HE damage / grenade
8.23Flashes / match

Recommended for you

Spend your practice time on Dust 2

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.

Dust 2 callouts & strategy →Dust 2 grenade lineups →

Recent matches

MapScoreRatingHS%Date
mirage13–70.0120%18 Oct →
inferno13–7-0.0524%18 Oct →
mirage13–3-0.0014%13 Oct →
inferno13–50.0520%13 Oct →
overpass13–100.009%30 Jul →
cache13–8-0.0412%30 Jul →
nuke13–90.0320%30 Jul →
overpass13–50.0522%29 Jul →
nuke12–120.0113%29 Jul →
cache11–13-0.037%29 Jul →
ancient11–13-0.0118%29 Jul →
dust213–9-0.078%29 Jul →
mirage7–13-0.0413%28 Jul →
ancient13–90.0514%28 Jul →
dust213–30.0723%27 Jul →
overpass13–80.0819%27 Jul →
ancient13–60.0015%27 Jul →
nuke13–30.0514%27 Jul →
inferno13–1-0.049%27 Jul →
cache8–10.058%27 Jul →
inferno9–13-0.0314%22 Jul →
dust212–12-0.0523%22 Jul →
cache12–120.0115%21 Jul →
mirage13–7-0.0524%21 Jul →
nuke13–30.0723%21 Jul →
mirage4–13-0.0711%21 Jul →
cache13–110.0234%21 Jul →
dust213–9-0.0217%21 Jul →
nuke13–30.0526%20 Jul →
ancient13–4-0.0113%20 Jul →
cache13–00.0212%20 Jul →
inferno13–100.0218%20 Jul →
mirage4–13-0.0223%20 Jul →
nuke13–60.0416%19 Jul →
cache13–50.0117%19 Jul →
inferno12–12-0.0320%19 Jul →
mirage10–13-0.029%19 Jul →
cache8–6-0.0619%16 Jul →
mirage7–13-0.0227%16 Jul →
dust213–20.0617%16 Jul →
dust28–13-0.0323%15 Jul →
ancient13–11-0.0217%15 Jul →
cache13–40.0516%15 Jul →
anubis13–50.0216%14 Jul →
mirage9–13-0.0418%14 Jul →
cache13–90.0233%14 Jul →
ancient12–12-0.0220%13 Jul →
nuke8–130.0131%13 Jul →
inferno13–6-0.0116%10 Jul →
cache10–130.0420%10 Jul →
nuke13–70.0318%9 Jul →
mirage3–13-0.0017%9 Jul →
inferno4–13-0.0117%9 Jul →
dust28–13-0.0113%9 Jul →
ancient5–13-0.0622%4 Jul →
cache9–13-0.0220%4 Jul →
nuke6–13-0.0819%3 Jul →
inferno9–13-0.0124%3 Jul →
inferno8–13-0.039%1 Jul →
ancient11–13-0.0414%1 Jul →
cache13–90.0311%30 Jun →
dust28–130.0218%30 Jun →
mirage12–12-0.0715%29 Jun →
nuke9–13-0.0419%29 Jun →
dust212–12-0.0516%27 Jun →
cache7–13-0.0811%27 Jun →
inferno13–60.0512%27 Jun →
mirage8–130.0016%27 Jun →
nuke8–13-0.089%26 Jun →
overpass8–13-0.0014%26 Jun →
cache2–13-0.0328%26 Jun →
dust23–13-0.0613%26 Jun →
mirage7–130.0210%25 Jun →
inferno11–13-0.0813%25 Jun →
ancient13–3-0.0410%25 Jun →
ancient13–8-0.0317%22 Jun →
mirage13–9-0.0322%22 Jun →
cache4–130.0015%22 Jun →
overpass7–13-0.0718%20 Jun →
cache4–13-0.1029%20 Jun →
inferno13–60.0213%20 Jun →
nuke10–13-0.0413%20 Jun →
mirage13–6-0.065%20 Jun →
nuke13–50.1026%19 Jun →
overpass7–130.0724%19 Jun →
cache13–50.1323%19 Jun →
inferno12–120.0123%19 Jun →
cache3–13-0.0813%16 Jun →
ancient5–13-0.1314%16 Jun →
overpass13–60.0714%16 Jun →
cache13–80.0114%15 Jun →
mirage13–80.0721%15 Jun →
inferno12–120.0425%14 Jun →
mirage13–2-0.0014%14 Jun →
cache13–100.0219%14 Jun →
cache13–5-0.0321%13 Jun →
inferno13–80.0015%13 Jun →
nuke13–10-0.0217%13 Jun →
inferno7–13-0.0111%12 Jun →
cache8–13-0.0325%12 Jun →

Match data via Leetify.

Recent teammates

Milestones

500 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.