Data sources
APEX has no data of its own. Every number on this site was published by someone else, and the five upstreams below settle at genuinely different speeds. This page exists so you can tell which one you are looking at.
Where each number comes from
| Source | What it provides | How fresh |
|---|---|---|
| FastF1 | Telemetry, lap times, tyre stints, pit stops, session classifications | After a session ends — never live |
| OpenF1 | Near-live timing on Live and Watch, and the per-session weather on every race page | Seconds to minutes behind |
| Jolpica (successor to Ergast) | Standings, results, the schedule, and historical constructor seasons back to 1950 | Once results are published; rate limited |
| Wikipedia | Constructor heritage prose on Teams | Effectively static |
| OpenTopoData | Circuit elevation, used to build the 3D track models | Built once per circuit |
How often this updates
A sync job runs hourly. It only asks an upstream for a session once that session should have finished — a race is given four hours before anything computed from the whole race is read, so a half-run session cannot be mistaken for a complete one.
This means a result can appear here up to about an hour after it appears on the official timing screen. That is a deliberate trade: asking more often would cost more than this project can spend, and asking too early returns half a session.
Why our numbers may differ from the official screen
Mostly because the upstreams disagree with each other before they agree. Provisional classifications get amended, penalties land after the flag, and each provider publishes on its own schedule. If APEX and the official app disagree an hour after a session, APEX is the one that is wrong — trust the official source.
Two specifics worth knowing. Weather is a single sample taken mid-session from OpenF1, not an average, so a track temperature here describes one moment rather than the whole hour; rainfall is the exception and is computed across every sample in the session, reported with the share of the session that was wet. Telemetry is never live: FastF1 publishes after a session ends, so anything on a car-data page is a replay.
Known limitations
- FastF1's live-timing source is intermittently unreachable from the cloud region this runs in. It fails soft rather than erroring, so a round can be briefly incomplete and then fill in on a later sync.
- Jolpica rate-limits, so a season's worth of historical requests is deliberately throttled and can lag.
- Rounds cached before a change to how a figure is computed keep the old shape until the next sync back-fills them.
Terms and attribution
Data is used under each provider's own terms. Wikipedia-derived text is available under CC BY-SA 4.0. Attributions lists every source, image and font with the licence it is used under — including the assets that are not freely licensed.
None of these providers is affiliated with APEX, and APEX is not affiliated with Formula 1 — see the disclaimer. For how the assistant uses this data, see AI disclosure.