MANKI

MANKI — CS2 Stats

76561199161488019[U:1:1201222291]Steam profile ↗✓ No bans

51Tracked matches67%Win rate2021Tracked since
CSDB Rating7.2 StrongAll-Rounder
Ladder ranks via Leetify

Rating over time

4,683Peak Premier in tracked matches
24Days played since 2021-04-28

Premier comes from this profile’s tracked match history, so it reaches back as far as those matches do.

Performance scores

Aim78
Positioning70
Utility63

0–100 skill scores via Leetify.

Recent form

HOT25–15–1Last 4161%Win rateWWWWLWLWWW

Last 10 vs previous 10: +10pp win rate · +0.02 avg rating · +6.1pp headshot accuracy · −70ms 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

  • 4–1 · 80% win rate
  • Avg rating 0.02
  • Avg headshot accuracy 23%
  • Avg reaction 450ms

Last 10

  • 8–2 · 80% win rate
  • Avg rating 0.06
  • Avg headshot accuracy 31%
  • Avg reaction 526ms

Last 20

  • 15–5 · 75% win rate
  • Avg rating 0.05
  • Avg headshot accuracy 28%
  • Avg reaction 561ms

Newest first, from the last 41 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.8
Utility6.3
Positioning7.0
Opening Duels6.3

Effective flashes

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

Twistzz

Plays most like Twistzz 87% 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. 579ms 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.8
Positioning7.0
Utility6.3
Mechanics6.5
Opening Duels5.3
Win Impact10.0

Composite 7.2/10 (Strong), 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.07+0.03
first ⅓ avg 0.04 → last ⅓ avg 0.07
Reaction time548ms−48ms
first ⅓ avg 595ms → last ⅓ avg 548ms
Headshot accuracy30.7%+7.1%
first ⅓ avg 23.6% → last ⅓ avg 30.7%

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

Personal bests

0.19Best match rating · 13–4 · mirage, 31 Jul →
60%Best headshot accuracy · 13–8 · nuke, 5 Jul →
344msFastest reaction time · 4–0 · cache, 28 Oct →
13–0Biggest win · dust2, 3 Nov →

Across the last 41 tracked matches.

Highlights

7Longest win streak
W4Current streak
5–2In matches decided by ≤2 rounds
14Overtime games

Map breakdown

infernoBest map · 70% over 10mirageWeakest map · 40% over 5
MapGradePlayedRecordWin rateAvg rating
infernoS107–370%0.03
dust2A95–456%0.03
nukeS64–267%0.06
mirageC52–340%0.04
cache—31–233%0.04
ancient—22–0100%0.02
overpass—21–150%0.04
office—21–150%0.07
alpine—11–0100%0.15
vertigo—11–0100%0.18

Across the last 41 tracked matches.

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

Skill profile

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

28.1%Headshot accuracy
33.2%Accuracy (enemy spotted)
35.3%Spray accuracy
79.4%Counter-strafing
9.8°Preaim
579msReaction time
51.7%T opening success
51.0%CT opening success
0.73Enemies flashed / flash
10.4%Flash assists
11.20HE damage / grenade
14.70Flashes / match

Recommended for you

Spend your practice time on Mirage

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 5 tracked games — your weakest map with enough games to be worth reading into.

Mirage callouts & strategy →Mirage grenade lineups →

Recent matches

MapScoreRatingHS%Date
nuke16–13-0.0120%29 Oct →
ancient13–10-0.0227%28 Oct →
cache4–00.070%28 Oct →
inferno13–110.0547%31 Jul →
dust26–130.0321%31 Jul →
mirage13–40.1930%31 Jul →
dust210–130.0737%5 Jul →
inferno13–7-0.0139%5 Jul →
nuke13–80.1360%5 Jul →
dust213–30.0828%3 Jul →
inferno12–160.0724%10 May →
overpass10–130.0726%16 Mar →
alpine13–110.1541%19 Feb →
dust213–11-0.0415%16 Nov →
inferno13–3-0.0221%16 Nov →
overpass13–110.0118%16 Nov →
mirage9–13-0.0321%16 Nov →
dust211–20.0335%16 Nov →
inferno13–80.0329%16 Nov →
nuke13–30.0917%16 Nov →
dust213–30.0413%16 Nov →
ancient13–90.0528%15 Nov →
office13–100.1035%4 Nov →
nuke13–100.0731%3 Nov →
mirage6–130.0029%3 Nov →
dust213–0-0.0111%3 Nov →
dust29–130.0237%25 Oct →
nuke13–160.0924%25 Oct →
dust214–160.0431%14 Oct →
mirage8–130.0125%14 Oct →
office6–160.0416%8 Apr →
inferno16–100.1229%8 Apr →
mirage16–50.0218%20 Jun →
vertigo16–60.1828%14 May →
inferno8–80.0326%24 Mar →
cache1–16-0.0317%18 Jan →
inferno16–80.0421%13 Jan →
cache14–160.0818%29 Aug →
inferno12–170.0035%23 Aug →
inferno16–140.0027%29 Apr →
nuke8–160.0015%28 Apr →

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.