fuzenko CS2 stats
regainsince 7 Oct 2025UkraineRiflerResults through 10 Oct 2026
fuzenko has played 60 recorded maps in the last 12 months, and averaged 80.5 damage per round and 1.09 kills per death.
- Maps played
- 60
- last 12 months
- ADR
- 80.5
- top 25%
- from 60 recorded maps
- KAST
- 77.6%
- top 10%
- from 60 recorded maps
- K/D
- 1.09
- top 25%
- from 60 recorded maps
Bands are among 1,082 players with at least 30 recorded maps at S-, A- or B-tier events, or 20 at S- or A-tier events, in the last 12 months. fuzenko has fewer than 20 recorded maps at S- or A-tier events in that time, so each figure shows a band, not an exact percentile. Each figure is compared only among those who have it, so its group can be a little smaller.
filled box: the band the figure falls in
left to right: below the middle · around the middle · above the middle · top 25% · top 10%
fuzenko CS2 stats by map
The five Active Duty maps fuzenko has recorded maps on in the last 12 months. Each bar compares a map with fuzenko's own figure on all maps, not with other players.
ADR, KAST and K/D on each map
- All maps60 maps
- ADR
- 80.5
- KAST
- 77.6%
- K/D
- 1.09
incl. 4 on Overpass
- Inferno17 recorded maps
- ADR
- 79.1
- −1.4
- KAST
- 82.4%
- +4.8
- K/D
- 1.12
- +0.03
- Ancient15 recorded maps
- ADR
- 82.3
- +1.8
- KAST
- 77.3%
- −0.3
- K/D
- 1.19
- +0.10
- Mirage14 recorded maps
- ADR
- 84.2
- +3.7
- KAST
- 76.8%
- −0.8
- K/D
- 1.04
- −0.05
- Dust28 recorded maps · not enough maps
- ADR
- —
- KAST
- —
- K/D
- —
- Anubis2 recorded maps · not enough maps
- ADR
- —
- KAST
- —
- K/D
- —
The small bar is the difference from fuzenko's all-maps figure in the top row: right of the line is above it, left is below. A dash means fewer than 10 maps carry that figure.
On the maps with 10 or more recorded maps, fuzenko's damage per round runs from 79.1 on Inferno to 84.2 on Mirage, against 80.5 on all maps. Overpass has left the Active Duty pool: its 4 recorded maps count in the all-maps row but are not shown on its own.
How fuzenko plays
Five round-level records from the last 12 months. The filled box is the band each figure falls in among 1,082 players.
Opening duels won
Share of the round's first duels won
52.2% · above the middlefrom 60 recorded maps
Multi-kill rounds
Share of rounds with two or more kills
19.1% · top 10%from 60 recorded maps
Clutches won
Clutch rounds won, per recorded map
0.18 · below the middlefrom 60 recorded maps
Trade kills
Share of kills that were trades
25.3% · top 10%from 60 recorded maps
Headshot kills
Share of kills with a final shot to the head
55.1% · above the middlefrom 60 recorded maps
View this chart as a table
| Record | fuzenko | Band | Sample |
|---|---|---|---|
| Opening duels won | 52.2% | above the middle | from 60 recorded maps |
| Multi-kill rounds | 19.1% | top 10% | from 60 recorded maps |
| Clutches won | 0.18 | below the middle | from 60 recorded maps |
| Trade kills | 25.3% | top 10% | from 60 recorded maps |
| Headshot kills | 55.1% | above the middle | from 60 recorded maps |
fuzenko recent matches
The last 10 matches, newest first, with fuzenko's kills per death and damage per round in each. Scores are regain first.
- 2–0
ESL Challenger League Season 52: North America - Cup 3
K/D 1.21 (34–28) · ADR 77.4
- 1–2
ESL Challenger League Season 52: North America - Cup 3
K/D 0.93 (56–60) · ADR 83.1
- 2–0Day Traders
ESL Challenger League Season 52: North America - Cup 3
K/D 1.74 (40–23) · ADR 100.0
- 0–2
ESL Challenger League Season 52: North America - Cup 2
K/D 0.77 (23–30) · ADR 74.7
- 0–2
ESL Challenger League Season 52: North America - Cup 2
K/D 1.22 (39–32) · ADR 96.4
- 2–0
ESL Challenger League Season 52: North America - Cup 2
K/D 1.00 (29–29) · ADR 84.4
- 0–2
NSTLGA League Season 2
K/D 0.93 (26–28) · ADR 88.0
- 2–0
NSTLGA League Season 2
K/D 0.97 (31–32) · ADR 77.1
- 2–1
NSTLGA League Season 2
K/D 1.03 (60–58) · ADR 75.4
- 0–1
NSTLGA League Season 2
K/D 1.00 (18–18) · ADR 101.9
K/D is kills per death over the whole match, with kills–deaths beneath. ADR is damage per round.
regain won five of these 10 matches, and fuzenko had more kills than deaths in four of them.
fuzenko team history
The teams fuzenko has played recorded matches for in the CS2 era, newest first. A run of fewer than three matches is left out unless it is the current one, so a stand-in appearance does not read as a move.
Teams in the CS2 era
- regain
7 Oct 2025 – now65 recorded maps · 31 matches
- ASPYRE
12 Aug 2025 – 11 Sep 202513 recorded maps · 6 matches
- regain
16 Jan 2025 – 29 Jan 202512 recorded maps · 5 matches
- current team
- earlier team
- a gap between bars is time with no recorded map
fuzenko has 90 recorded maps in the CS2 era with the three teams listed, 65 of them with regain.
Are you this player?
If you are this player and want this page taken down, ask us. You do not need to give a reason. If the player is under 18, a parent or guardian, or their team or organisation, can ask instead.
Ask us to remove this page →About these figures
- Window
- The figures cover the 12 months to 10 Oct 2026; recent matches and team history cover the CS2 era. The windows are fixed.
- Recorded maps
- A recorded map is a completed CS2 map, played to a result on a competitive map in a match that was not a walkover, with a stats line for the player. A figure also needs its own inputs, so each figure counts only the recorded maps that have them, and none is shown from fewer than 10.
- Bands
- Exact percentiles and the weapon and hit-group figures are shown for players with at least 20 recorded maps at S- or A-tier events in the last 12 months. fuzenko has fewer, so each figure shows one of five bands: top 10%, top 25%, above the middle, around the middle or below the middle.
- What these are
- Records of what happened in recorded matches, not a judgement of ability. Every figure is our own count from match records; there is no player score on this page.
How the figures are worked out →Spotted a wrong figure? data@esportsodds.ggHow we handle player data →
Pull this CS2 data yourself
One plan — $49/mo for 50,000 requests. Rankings, results, maps and rosters over one REST API.