What are Python's per-map averages on Anubis?
| Metric | Value on Anubis | Elite benchmark |
|---|---|---|
| Maps played | 52 | 50+ |
| HLTV 2.0 rating | 0.83 | 1.15+ |
| ADR | 55.0 | 85+ |
| KAST | 85.7% | 74%+ |
| K/D ratio | 0.79 | 1.15+ |
| Headshot % | 54.5% | 50%+ |
Why split CS2 player stats by map?
Map selection is decided before a CS2 match starts. Every Best-of-3 and Best-of-5 series filters through a pick/ban phase where teams protect their strongest maps and attack their opponents' weakest. That means a player's career averages blend games played on their best maps (where they look elite) with games on their worst (where they struggle). Betting markets and fantasy lineups that only look at the blended number misprice matches where the opponent's map-ban sends play to the weaker half of a player's profile.
Our per-map pages isolate one map at a time so the number you see above is what Python actually produces when Anubis is the map on the server. For a cross-map view, see the career page; for the roster context, see their player profile.
Python on Anubis — FAQ
Is Anubis one of Python's best maps?
A 0.83 rating on Anubis is below their global career average — this is a below-standard map for them. Compare to their career average on the career page.
How is this per-map rating calculated?
The rating is a sample-weighted average of Python's HLTV 2.0 rating from every tracked professional game on Anubis in our database. Short samples (under 15 maps) show on the page but carry a noindex flag for search engines because they're too volatile to report as a statistically meaningful figure.