Why FNCS Eliminations Are Team-Level
Why official competitive data cannot reliably assign every FNCS elimination to one player and how FantaFort handles the limitation.
What the public data contains
Tournament leaderboard sessions expose a TEAM_ELIMS statistic for the leaderboard entry. In duo, trio or squad formats, that entry represents the formation, not an individual kill feed. Epic account identifiers show who played together, but they do not split that team total between teammates.
Session history can also expose placement, match number, survival time and whether the team won. Those fields provide context for the formation result, but none creates a verified per-player elimination total.
How to read a provider row
Consider an illustrative duo session containing two Epic account IDs and TEAM_ELIMS = 12. The supported conclusion is that the duo recorded 12 eliminations in that session. It is not valid to record 12 for each player, split it automatically into six each or guess a share from the final placement.
The same boundary applies when a public leaderboard shows total tournament eliminations. Unless the provider adds an authoritative individual field, the formation remains the smallest verifiable unit.
Why FantaFort does not estimate individuals
Dividing eliminations equally or inventing a likely share would create false precision. A player may contribute through damage, support, survival or an elimination secured by a teammate. Without an authoritative individual field, FantaFort keeps the official team statistic and states the limitation.
How league modes account for the team result
Classic scoring values every selected teammate with the full official score. Balanced scoring divides points by formation size. Formation scoring counts the formation once. League owners can choose the trade-off they prefer, while the underlying source remains unchanged and auditable.
This treatment applies to the official total, not to an invented elimination split. Verified competitive rulings can remove or penalize a result only when an administrator records a reliable HTTPS source. Missing sessions or rumors are not treated as proof.
Sources and methodology
Competitive results come from Osirion. Implemented rules and data limits are documented on the How it works page.