Rainbow Six Siege
Ubisoft · 5v5 · advanced data via authorized replays & recordings
Siege is played through the building as much as across it. A hatch opened above a site changes what is reachable whether or not anyone shoots through it, so the structural decisions come first here. The Rainbow Six Siege 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 Rainbow Six Siege results. No production credential for a Rainbow Six Siege reference source is active, so the reference layer is empty rather than partially filled. Source coverage. 7 competitive maps have no coverage at all: Clubhouse, Oregon, Kafe Dostoyevsky, Border, Chalet, Bank, Skyscraper.
Where the fight goes vertical
kills from the attacker's floor to the victim'sNo Siege kill in this corpus carries both an attacker and a victim floor.
Reading it 0.0% of recorded kills cross a floor. The diagonal ribbons are same-floor fights; everything else is a vertical engagement — a hole, a hatch, or a soft ceiling.
Structure
how much of the building each round opens up- Rounds recorded
- 0
- Defence round win
- —
- Openings per round
- —
- 0 hatches, soft floors and ceilings
Operators
counted from engagements, not from a roster field| Operator | Kills | Deaths | Opening kills | Head |
|---|
Gadgets
deployed, destroyed, and what they bought| Gadget | Deployed | Destroyed | Opened | Spots |
|---|
Scope Gadget records name the device, not the operator who owns it. Breach outcomes by floor →
Site setup
anchors against roamers| Site | Rounds | Anchors | Roamers | Def win |
|---|
Naming Site names come from the map schematic each round was resolved against. Grouped by map →
Season leaders
minimum samples enforcedNo Rainbow Six Siege 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- Map Floors
- Kills, setups and vertical connections floor by floor across 0 engagements.
- Operators
- Per-operator engagement record, opening duels included.
- Breaches
- Hard breaches and charges with their recorded outcome, by floor and region.
- Sites
- Site selection and defensive shape, grouped by map.
- Entry and Trades
- Opening-duel value and the trade network around each death.
- Intel
- Drone and camera value, from spot to engagement.
- Utility
- Gadget denial and enemy-utility removal, ranked by player.
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.
- 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.
- Vision events
- 0 of 0 matchesunavailable
- No telemetry has been ingested for this game yet.
- Floor coordinates
- 0 of 0 matchesunavailable
- No telemetry has been ingested for this game yet.
Data sources
how this game is coveredOfficial Rainbow Six Esports pages are parse-ready but disabled pending operator review. Authorized replays and observer recordings feed the advanced baseline.
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