We use cookies for ads
RacePace Analytics is free, supported by advertising. With your consent, Google and its partners use cookies to show personalised ads and measure how they perform. Decline and you'll still see ads — just non-personalised ones. You can change this any time in Cookie settings. See our Privacy Policy.
RacePace Analytics is only as good as the data behind it, so we're transparent about where every number comes from and how we handle it. Nothing on this site is invented or estimated unless we say so explicitly.
Timing and telemetry. Lap times, sector splits, tyre compounds, pit-stop timing, and car telemetry — speed, throttle, brake, gear, RPM, and DRS — are sourced from the official Formula 1 timing feed through the open-source fastf1 library and the OpenF1 project. Telemetry is sampled at roughly 4 Hz, which gives a position trace accurate to within a few centimetres around the lap. This is the same underlying data race engineers and broadcasters work from.
Results and standings. Session classifications and Driver and Constructor Championship standings come from the Jolpica F1 API, the maintained successor to the long-running Ergast database. Standings update after each round is processed by the source.
News. Headlines in the News tab are aggregated from public RSS feeds, including BBC Sport and Autosport. We link directly to the original publisher; we don't republish full articles.
How we process it. We normalise lap times across stints and compounds so you can compare true pace rather than strategic noise. Laps run under a Safety Car or Virtual Safety Car, and out-laps and in-laps, are flagged as inaccurate by the source and excluded from pace comparisons so they don't distort the picture. Telemetry traces are aligned by lap distance so two drivers can be overlaid fairly, and the time-delta chart is computed cumulatively from the fastest reference driver.
Coverage and limits. We cover the 2023–2026 seasons in full. Telemetry exists from 2018 onward, but some early sessions have incomplete source data — where that happens, we show what exists and label the gaps rather than guessing. The first load of any session can take 30–60 seconds while data is fetched and cached; after that it is near-instant.
Corrections. If you find an error, email [email protected] with the session and driver, and we'll check it against the source. See also our Contact page.