Fortnite
Epic Games · battle royale · advanced data via authorized replays & recordings
A battle royale has no win/loss axis. Every entrant finishes somewhere in a field, and the analysis is about how far a drop, a rotation and a fight selection carried them — not whether they beat one opponent. The Fortnite corpus holds 0 matches 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 Fortnite results. No production credential for a Fortnite reference source is active, so the reference layer is empty rather than partially filled. Source coverage. 1 competitive match has no coverage at all: Battle Royale Island.
How a lobby empties
the survival curve, and how much of it the storm takesNo Fortnite storm phase is stored for this corpus.
Construction The curve is cumulative attrition: a knock that was revived is not an exit, so only unrecovered eliminations remove an entrant. Field size averages — across 0 recorded lobbies.
Drops
where lobbies land, and where those landings finish| Point of interest | Landings | Squads / lobby | Median finish | Mean points |
|---|
Reading it Median finish is the middle placement of everyone who landed there, not an average — a single first place cannot pull the row. Squads per lobby is the number of distinct teams that chose the point, which is the quantity a drop call actually trades against.
Rotations
0 recorded waypoints- Mean distance moved per phase
- —
- Waypoints inside the circle
- —
Scope One waypoint per surviving player per phase — a sequence of positions, not a continuous track. Zone by zone →
Materials
harvested and spent, by phase| Phase | Collected | Spent | Builds |
|---|
Onward Inventory rarity by phase →
Scoring
placement points, the only standings a battle royale has- Entrants recorded
- 0
- across 0 lobbies
- Mean points per entrant
- —
- Best single-lobby score
- 0
Season leaders
minimum samples enforcedNo Fortnite 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- Drops
- Landings, contest, and finishing position for all 0 recorded entries.
- Zones
- Circle geometry, attrition and rotation pressure, phase by phase.
- Rotations
- Rotation efficiency ranked by player.
- Fights
- Engagement selection and knock-to-elimination conversion.
- Loadouts
- Rarity progression and inventory fill across the storm phases.
- Resources
- Material efficiency ranked by player.
- Sessions
- Cumulative points across a session's lobbies.
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.
- Weapon state
- 0 of 0 matchesunavailable
- No telemetry has been ingested for this game yet.
- Item / inventory state
- 0 of 0 matchesunavailable
- No telemetry has been ingested for this game yet.
- Build events
- 0 of 0 matchesunavailable
- No telemetry has been ingested for this game yet.
- Storm zones
- 0 of 0 matchesunavailable
- No telemetry has been ingested for this game yet.
Data sources
how this game is coveredOfficial competitive leaderboards are parsed only after an operator ToS/robots review (currently awaiting). Replay uploads from players/organizers 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