Data methodology

Data sources and attribution

CrunchClash's Premier League dataset uses season and match statistics ingested from the Premier League Pulse Live SDP feed. The product is not affiliated with, endorsed by, or certified by the Premier League, its clubs, Opta, or StatsBomb.

Fantasy Premier League pages are separate from the Premier League dataset. Where stated on those pages, they use the official Fantasy Premier League feeds; those records are not merged into the Premier League MongoDB statistics.

Coverage

Public Premier League pages are scoped to the season marked active in the CrunchClash dataset. Available records can include clubs, players, fixtures, completed matches, standings, team-match statistics, player-match statistics, and player or club season aggregates.

Coverage differs by page and metric. Pages show a record count or a data-through date only when the query that powers that page can establish it. A missing value is displayed as unavailable rather than converted to zero.

Collection and ingestion

The data model preserves raw retrieval metadata, including source, endpoint, resource key, source URL when available, content hash, HTTP status, scraper version, and fetch time. Normalized records retain a scrapedAt timestamp; that means when CrunchClash retrieved the source, not necessarily when the underlying match was last changed.

Ingestion runs are recorded with job type, run status, start and finish time, and step outcomes. CrunchClash does not publish a guaranteed update schedule. A public “Latest source fetch” signal is shown only when the page query has a stored source-fetch timestamp, and it is deliberately distinct from the match date covered by the data.

Normalization and relationships

CrunchClash keeps Premier League source identifiers alongside internal MongoDB identifiers. Matches carry season, matchweek, kickoff, home and away club information. Match-level player and team records are associated with the relevant match, player or club, and season. Player registrations are used to associate a player with a club and position for a season where available.

The public metric catalog maps the fields that can be queried to their supported data grain. It prevents an interface or natural-language query from treating a season-only statistic as a player-match statistic.

Direct and derived statistics

Values such as goals, expected goals, expected assists, possession, shots, touches, duels, and passing fields are presented as source-supplied statistics when they are available in the relevant dataset. Their exact availability depends on the record type and season data returned by the source.

CrunchClash labels documented calculations. For example, club xGA is the sum of opponents' recorded xG in the same matches; per-90 values divide the source total by minutes played and multiply by 90; goal difference is goals for minus goals against; and Goals − xG is a descriptive difference, not a rating or prediction. Pizza charts show percentiles within the stated eligible season population.

Reliability and limitations

Source data can be incomplete, delayed, corrected, or unavailable. A completed fixture can exist before all supporting team or player statistics are present. Player-match xG and xA are not available in the current Premier League dataset, so pages do not infer them from season totals. Unsupported metrics are omitted.

Standings, source statistics, derived views, and interactive filters can update at different times. Treat the displayed coverage and latest source-fetch information as the scope of the page, not a promise of real-time or complete league coverage.

Report a discrepancy

If a scoreline, statistic, identity, or coverage signal looks incorrect, please include the page URL, the season, the affected entity or match, and the value you expected when you contact CrunchClash. We can then compare the displayed record with the applicable source and ingestion history.