mizu CS2 stats

  • HOTUsince 15 Aug 2024
  • Russia
  • Rifler
  • Results through 29 Oct 2026

mizu has played 178 recorded maps in the last 12 months, and averaged 81.1 damage per round and 1.13 kills per death.

Maps playedlast 12 months
178
ADR91st percentile, from 178 recorded maps
81.1
KAST68th percentile, from 178 recorded maps
73.8%
K/D84th percentile, from 178 recorded maps
1.13

Percentiles are among 1,108 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. Each figure is compared only among those who have it, so its group can be a little smaller.

mizu CS2 stats by map

Each difference compares a map with mizu's own all-maps figure, not with other players.

mizu CS2 stats by map: maps, ADR, KAST and K/D on each Active Duty map over the last 12 months, with each figure's difference from the all-maps figure
MapMapsADRKASTK/D
All mapsincl. 11 on Overpass17881.173.8%1.13
Dust24379.7−1.474.8%+1.01.16+0.03
Ancient3778.9−2.273.6%−0.21.130.00
Mirage2481.8+0.771.5%−2.31.130.00
Cache2383.2+2.172.9%−0.91.14+0.01
Nuke2278.9−2.272.3%−1.51.04−0.09
Anubis1775.8−5.374.5%+0.71.04−0.09
Infernonot enough maps1———

On the maps with 10 or more recorded maps, mizu's damage per round runs from 75.8 on Anubis to 83.2 on Cache, against 81.1 on all maps. Overpass has left the Active Duty pool: its 11 recorded maps count in the all-maps row but are not shown on its own. A dash means fewer than 10 maps carry that figure.

How mizu plays

Five round-level records from the last 12 months, each placed among 1,108 players.

  • Opening duels won

    Share of the round's first duels won

    from 178 recorded maps

    51.4%
    66th
  • Multi-kill rounds

    Share of rounds with two or more kills

    from 178 recorded maps

    18.2%
    85th
  • Clutches won

    Clutch rounds won, per recorded map

    from 178 recorded maps

    0.30
    60th
  • Trade kills

    Share of kills that were trades

    from 178 recorded maps

    18.9%
    33rd
  • Headshot kills

    Share of kills with a final shot to the head

    from 178 recorded maps

    50.7%
    34th

mizu's multi-kill round share sits at the 85th percentile and the trade share at the 33rd. A percentile places one figure among other players' figures; it is not a score.

mizu weapons and hit groups

For players with 20 or more recorded maps at S- or A-tier events in the last 12 months. Figures to 29 Oct 2026.

Kills by weapon

  • AK-4741.0%1,143 kills
  • M4A123.7%661 kills
  • Galil AR6.5%182 kills
  • M4A44.9%137 kills
  • USP-S4.7%130 kills
  • Glock-183.8%107 kills
  • Tec-92.7%76 kills
  • FAMAS2.5%71 kills
  • Other weapons10.1%283 kills
The AK-47 accounts for 41.0% of mizu's 2,790 kills in 75 matches with weapon records, the M4A1 for 23.7%. Weapons outside the top eight are grouped as Other.

Where damaging hits landed

  • Head16.2%1,829 hits
  • Chest38.8%4,374 hits
  • Stomach13.7%1,542 hits
  • Arms8.8%991 hits
  • Legs4.7%531 hits
  • Other17.8%2,013 hits
11,280 damaging hits. 16.2% of mizu's damaging hits landed on the head and 38.8% on the chest. Headshot kills (50.7% of kills, above) count only the shot that finished each kill, so the two figures differ.

mizu recent matches

The last 10, newest first. Scores are HOTU first.

mizu recent matches: date, opponent, event, result, K/D and ADR, newest first
DateOpponentEventResultK/DADR
GamerLegionTesla Cup 2026Won 2–01.7440–23101.2
B8Tesla Cup 2026Won 2–01.2129–2484.1
GamerLegionTesla Cup 2026Won 2–01.1334–3078.2
LuminosityTesla Cup 2026Won 2–01.4035–2594.2
fnaticStake Pulse Beat IIILost 0–20.4918–3762.4
AstralisStake Pulse Beat IIILost 1–20.9143–4771.6
fnaticStake Pulse Beat IIIWon 2–01.1937–3176.5
fnatic1win Private Club 2: Closed QualifierLost 1–20.6931–4558.2
Acend1win Private Club 2: Closed QualifierWon 2–01.2634–2783.2
STATE1win Private Club 2: Closed QualifierWon 2–11.0744–4175.8

K/D is over the whole match, then kills and deaths. ADR is damage per round. HOTU won seven of these 10 matches, and mizu had more kills than deaths in seven of them.

mizu team history

Teams in the CS2 era, newest first. A run of fewer than three matches is left out unless it is the current one.

HOTU

15 Aug 2024 to now, 294 recorded maps in 127 matches. Current team.

Teammates

HOTU's five in the newest recorded match, 29 October 2026, with each player's own recorded maps in the last 12 months.

About these figures

Window
The figures cover the 12 months to 29 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.
Percentiles
A percentile is the share of the 1,108 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 whose figure is lower than mizu's, so the 80th percentile means higher than 80% of them.
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.

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

Every figure here is in the API

The player routes take an id or a slug: /performance for the 12-month figures and percentiles, then /maps, /matches, /teams and /weapons.

Player routes need a paid plan. Plans from $99 USD a month. The free sandbox key reads a fixed sample of past matches, not player statistics.

$ curl -H "Authorization: Bearer $ESPORTSODDS_API_KEY" \
  "https://api.esportsodds.gg/v1/cs2/players/mizu-cs-go/performance"

{
  "data": {
    "slug": "mizu-cs-go",
    "level": "established",
    "window": { "months": 12 },
    "population": { "n": 1108 },
    "metrics": [
      { "key": "kd", "value": 1.13 },
      { "key": "adr", "value": 81.1 }
    ]
  }
}
Trimmed: each metric also carries its label, unit, map count and percentile.