Skip to content
eStatcast

How we label data

Every value on this site carries provenance: where it came from, which parser or model produced it, how confident we are, and whether a human verified it. The promise is simple — official data for what happened; documented models for how, why, and how difficult it was — and the two are never mixed silently.

The labels

OFFICIAL

Directly from a documented first-party publisher source (API, official page, official download). Schedules, results, rosters, basic box scores.

REPLAY

Extracted from an authorized replay/demo artifact by a deterministic, versioned parser. One parse produces both basic stats and telemetry.

BROADCAST

Extracted from authorized broadcast or VOD footage via the vision pipeline. Carries per-field confidence; low-confidence values go to human review.

SUBMITTED

From an authorized upload or administrator import. The submitter attests to their rights over the artifact.

MODEL

Computed by a documented statistical model (xDuel, win probability, value-added metrics). Model key + version attach to every value; model cards are public.

VERIFIED

A reviewer confirmed this value against the source artifact.

PARTIAL

Some fields of the record verified; others pending.

Source authority

When two permitted sources disagree about the same field, both values are preserved, the conflict is flagged for review, and the display value follows a fixed authority order:

  1. Documented first-party publisher API
  2. Official publisher esports API / data portal
  3. Official publisher pages (tournament, leaderboard, match)
  4. Official organizer pages or exports
  5. Official replay/demo artifacts
  6. Authorized team/player/tournament/user submissions
  7. Authorized broadcast/VOD extraction
  8. Manual administrator import
  9. Derived statistical/ML results

What we never do

  • Depend on unofficial stats APIs or community stat sites (HLTV, VLR, Tracker.gg, Liquipedia, Oracle's Elixir, and similar).
  • Use undocumented or reverse-engineered publisher endpoints, or circumvent rate limits, authentication, or anti-bot systems.
  • Read game-client memory, inject into processes, or interfere with anti-cheat.
  • Present model output or synthetic demo data as official publisher data.
  • Publish a metric without its public documentation page and model card.

Demo mode

Without production credentials, the platform runs on a clearly-labeled synthetic corpus: fictional teams and players generated to exercise the real pipeline. Every synthetic row is flagged (the DEMO badge) and removable with one command. Nothing synthetic ever references real esports history.

Metric glossary → ·Source registry →