VALORANT
Riot Games · 5v5 · advanced data via authorized replays & recordings
VALORANT is a gunfight game wrapped in an ability economy: the same round can be won by aim, by a well-spent utility cycle, or by an ultimate held one round longer than the opponent expected. The VALORANT corpus holds 0 matches across 0 maps and 0 stored telemetry events, covering 0 players on 0 teams over no dated records.
Every record is Analytics Preview Lab data — fictional matches used to demonstrate the analysis, not real VALORANT results. No production credential for a VALORANT reference source is active, so the reference layer is empty rather than partially filled. Source coverage. 7 competitive maps have no coverage at all: Ascent, Bind, Haven, Split, Lotus, Sunset, Icebox.
How each agent spends its kit
casts per 100 rounds on the server, by slotNo VALORANT ability cast is stored for this corpus.
Normalisation Rates are per 100 rounds the agent was actually on the server, counted from the per-round ultimate-state record. Raw cast counts would simply rank the agents by pick rate.
Agents
0 agents appear in the recorded rounds| Agent | Rounds | Kills | First bloods | Head | Casts | Enemies / cast | Ult ready |
|---|
Sites
0 spike plants recordedJoin Each plant is matched to its own round's end reason, so a detonation is an attacking conversion and a defusal is a completed retake. Post-plant positions →
Economy and ultimates
the two currencies of a round- Rounds recorded
- 0
- Attack round win
- —
- Mean loadout value
- — atk · — def
- Mean shields
- — atk · — def
- Ultimate ready at round start
- —
- 0 per-player observations · 0 ultimates cast
Onward Buy bands by side →
Season leaders
minimum samples enforcedNo VALORANT player meets the minimum sample for these metrics in the current window.
Recent movement
30-day form against the season baselineNo player clears the minimum sample in both the 30-day and season windows, so there is no comparable pair to difference. Movement is a difference between two windows a player qualifies in — reporting it from one window alone would be reporting noise.
Nothing ingested for this game yet.
Where to look next
each opens a real aggregate over this corpus- Agents
- Per-agent kill, ability and ultimate profile, slot by slot.
- Compositions
- Which agent sets teams actually field together, and how often.
- Abilities
- Value created per cast, ranked by player.
- Ultimates
- Ult economy, availability, and conversion.
- Duels
- Gunfight outcomes measured apart from ability value.
- Sites
- Plant split, retake conversion, and where 0 post-plants were defended.
- Economy
- Loadout, shields and credits by band, for both sides.
Telemetry coverage
measured across 0 ingested matches- Event timestamps
- 0 of 0 matchesunavailable
- No telemetry has been ingested for this game yet.
- Player coordinates
- 0 of 0 matchesunavailable
- No telemetry has been ingested for this game yet.
- Hit groups
- 0 of 0 matchesunavailable
- No telemetry has been ingested for this game yet.
- Weapon state
- 0 of 0 matchesunavailable
- No telemetry has been ingested for this game yet.
- Economy state
- 0 of 0 matchesunavailable
- No telemetry has been ingested for this game yet.
- Utility events
- 0 of 0 matchesunavailable
- No telemetry has been ingested for this game yet.
- Ability casts
- 0 of 0 matchesunavailable
- No telemetry has been ingested for this game yet.
- Objective state
- 0 of 0 matchesunavailable
- No telemetry has been ingested for this game yet.
Data sources
how this game is coveredOfficial Riot VAL APIs cover player-consented ladder data (production key + RSO required). Pro-match advanced data comes from tournament exports and authorized recordings via the vision baseline — never from undocumented endpoints.
How this page is built
Every figure above is computed from stored records — Postgres for entities and results, ClickHouse for the telemetry event stream. Nothing is estimated or filled in. Shares that were never observed render as an em dash rather than as zero, and a section whose input the source does not emit says which field is missing instead of showing an empty chart.
There is no continuous position stream in this corpus: position_samples is empty, so nothing here reconstructs per-tick movement. Spatial statements are made from schematic regions, floors and named points recorded on individual events.
Full source registry · Known limitations · Query the raw events