Know your evidence.

Our workspace. Traceable inputs.

Orient Analytics Hub provides the club’s interface and analysis workspace. Source match events and expected metrics come from the local Opta database. Provider xG and xA are not presented as proprietary Orient models.

Last expected-feed fetch recorded: 2026-09-14T10:39:15.975004+00:00. This timestamp is not a guarantee of complete coverage or a live API connection.

What is available

8 matches, 13,867 events and 148 player–team records. Current views include all imported competitions and dates. The player pool is not a league-wide dataset.

0 raw match payload(s) contain a provider error or unreadable content. These are not used as score evidence.

Definitions & limits

Interactive event views: shot xG is joined by fixture and event ID. Shootouts and own-goal events are excluded. Coordinates remain in provider orientation; maps do not establish attacking direction. Event filters do not alter full-fixture player xG, xA or minutes.

Review prompts: the under-450-minute flag signals limited exposure for analyst review, not a statistical confidence interval. Descriptive insights are not predictions.

xG: the expected-goals value supplied by the source. Overview totals use only Orient fixtures with xG available for both teams.

xA / 90: summed supplied expected assists × 90 ÷ recorded minutes. It is shown only when every player-stat fixture has minutes and the total is positive. Missing xA rows may still limit comparability.

Missing values: a dash means no usable value. Sparse player-stat totals sum recorded values, which may not represent full coverage. No missing statistic is silently filled with zero.

Scores: full-time scores come from match details. Shootout scores are shown separately. If match details are missing, the score remains unavailable.

Player comparisons: consider role, opposition, minutes and competition before drawing conclusions. No valuation, tactical-fit or predictive score has been invented.