Start here: understand the session, its coverage, and which view answers your question.
Loading the session dataset…
Make sense of the laps.
M
Event outcomes
Race podium and fastest lap at a glance. Expand other sessions for their top three.
Session results
Other session summaries
Results use the final session classification. Race and sprint fastest laps use recorded timing, excluding identifiable deleted laps, pit-out laps and disqualified drivers.
Lap coverage
Recorded data
Annotated laps stay in the dataset. Derived pace and stint fits use eligible samples, with their counts shown.
Session context
What would you like to understand?
Reading the data: recorded, derived and estimated
Recorded
Lap and sector durations, stint records, race-control messages and radio audio from OpenF1. Coverage can vary by session.
Derived
Rolling pace, rankings, stint slopes and reconstructed gaps calculated from recorded data. Each view explains its sample rules.
Estimated
Qualifying mini-sector timing interpolated from location samples. It is distinct from recorded lap and sector durations.
Unflagged
A timed lap with none of this app’s annotations. It is not a guarantee of a traffic-free or representative lap.
Session results
Full classification for the selected session.
COMPARE THE WHOLE FIELD
Field pace
Start with lap times. Use driver focus to follow one race or session.
Recorded + derived
Lap times across the field
Recorded data
Lower is faster for lap-time metrics. Driver colors identify the lines; select a chip to focus. Arrows mark values beyond the current range.
Cumulative lap durations against a fixed average-pace baseline.
Reconstructed timing
Zero is reference pace × lap count. Negative values are ahead of that pace; positive values are behind. The reference driver finishes their continuous timed sequence at zero. Select a driver chip above to focus.
Race positions
Follow each driver's recorded position through the race.
Recorded positions · lap snapshots
Observed pace ranking
Median and fastest laps use eligible recorded lap times across all compounds.
Derived summary
Driver
Median lap
Middle 50% · seconds
Fastest eligible
Laps analyzed
Laps analyzed counts the eligible timed laps used for each driver’s median, middle 50%, and fastest eligible lap. Unavailable times and laps excluded by the sample rules are not counted.
Rankings use the whole selected session, not just the focused driver. Fuel load, stint timing, weather and traffic are not normalized; cross-compound comparisons need extra care.
Pit laps, race-control-affected laps, opening laps, deleted times and timing anomalies are excluded. Tire conflicts do not exclude pace samples.
⚠ marks drivers whose reported tire data may be incorrect. Drivers without eligible samples show unavailable values.
Tire stints
Compare drivers on the same compound, then inspect each stint’s observed pace change.
Tire strategyAll drivers · finishing order
Tire strategy
Recorded stints
● Soft● Medium● Hard● Intermediate● Wet● Unknown
Qualifying tire sets remain available in Tire strategy. Degradation analysis is unavailable: qualifying runs target peak lap time rather than sustained race pace.
1. Choose a compound
2. Choose driversNone selected
Select up to six drivers.
Lap time vs. session lap
Select a point to inspect its context.
Solid lines join laps within a stint. Dashed lines show fits to unflagged laps. Diamonds mark annotations; arrows retain off-scale values.
SESSION LAP WINDOW—
Observed stint slopes
Derived · unflagged
+ slope: laps get slower as the tire ages. − slope: laps get faster.
This is observed pace change, not isolated tire wear. Fuel burn, traffic, weather and track evolution also contribute.
Each stint needs four unflagged timed laps for a fit.
Annotations and chart context Show details
Counts refer to the tire selection; a lap can have several tags. Yellow flags indicate possible exposure rather than a confirmed position match.
Selected lap records Inspect / filter
Same compound, drivers and lap window as the tire chart.
Driver
Lap
Stint / tire age
Lap time
Context
—
1 / 1
How tire laps and fits are calculated
Lap records are joined to stint ranges. Event tags use timestamp overlap; pit-out laps use the provider flag, and pit-in laps use pit records.
Opening laps, identifiable deleted times, missing times, unknown compounds and within-stint pace anomalies are labeled. Fits use at least four unflagged timed laps per stint in the displayed window.
Tire age includes reported age at stint start. All recorded values remain available in Lap data.
TWO LAPS, ONE SESSION
Lap comparisons
Choose any timed laps from the selected session. Pit and annotated laps remain labeled.
Selected session
VS
Estimated timing
Recorded lap and sector times anchor the comparison. Location samples estimate mini-sector timing and distance between those anchors.
Where time was found
Estimated
Mini-sector times are estimated from location samples. Small differences may reflect sampling or interpolation noise.
Select a map segment to inspect estimated times.
LAP COMPARISON
Choose two drivers and compare laps.
Estimated cumulative delta
Positive: A ahead. Negative: B ahead. Select a mini-sector on the map to highlight its distance range here.
Recorded lap and sector timing anchor the alignment; intermediate distance is estimated from location samples.
Track-map method and confidence
OpenF1’s mini-sector fields contain status codes, not split times. Both location traces are projected onto Driver A’s path. Recorded lap start, available shared sector boundaries, and finish anchor the timing. Within each anchored sector, location progress is mapped onto the shared track path; sample timestamps are retained. Each recorded sector is divided into 5, 10, or 15 equal-distance mini-sectors. Complete sector timing is required for this comparison.
Sampling and location alignment affect intermediate precision. Incomplete or discontinuous coverage produces an explicit unavailable state.
Differences under 0.020 seconds are ties. Team colors identify the winner; teammates use distinct shades.
Speed, delta and throttle
Recorded channels from the selected laps, aligned on one shared lap path.
Recorded + estimated
Use the slider or chart to inspect both laps.
Solid line: Driver A. Dashed line: Driver B. Speed is km/h; throttle is %. Delta is estimated from location transit times: positive means A ahead. S1/S2/S3 positions are approximate and use Driver A’s recorded sector durations. Horizontal position is shared lap progress, not measured meters.
Recorded lap leaderboard
Fastest eligible lap per driver across the selected session.
Recorded durations
Driver
Best lap
Gap · seconds
Best S1 / S2 / S3 · seconds
Ideal lap
A lap-time leaderboard, not an official Q1/Q2/Q3 classification. Pit laps and identifiable deleted times are excluded.
Ideal lap is a derived sum of the driver’s best recorded sectors and may not correspond to an actual lap.
FROM THE COCKPIT
Team radios
Choose a driver to hear the available recordings from the selected session.
Recorded audio
Original audio · no transcript text from OpenF1Coverage is a selection of transmissions, not a complete radio log. Tire and pace filters do not affect this view.
Select a driver card below to show their available audio clips.
Championship
Follow the title fight, or go back to the standings after any completed race.
Drivers
After selected race
Pos
Change
Driver
Points
Race gain
Constructors
After selected race
Pos
Change
Team
Points
Race gain
Driver race points
Points earned at each race through the selected event.
Race columns show the reported post-race total minus the pre-race total. Sprint points are included in the championship total, but not these race columns.
— means a record is unavailable; 0 means no race points. Source corrections can appear as negative changes.
Driver points progression
Cumulative points through the selected race.
Focus a driverShow teams and drivers
Standings use OpenF1’s reported championship totals after each race, including points already awarded in sprints. Race gain is the difference between its reported pre-race and post-race totals. Change compares the reported pre-race and post-race championship positions. These beta endpoints can have missing coverage or later corrections.
The graph breaks at missing race snapshots; absent records are not treated as zero points. Driver colors use the selected race’s roster, with the latest available season roster for drivers absent from that race. Numbered labels indicate missing driver metadata. Round numbers follow the completed races available in the session catalogue.
Pit stops
Recorded pit visits and available stop timings for the selected session.
Recorded timing
Driver / team
Visit
Lap
Stationary stop
Total pit lane
Time · UTC
Stationary stop is the reported time the car was stopped. Total pit lane includes time traveling through the lane as well as any stop.
A pit visit does not necessarily mean a tire change or even a stationary stop. Drive-throughs and safety-car routing through the pits can also appear here. Visit numbers count recorded entries for each driver.
Unavailable means the timing was not supplied; we do not estimate it from lap times. Stationary timing is supported by OpenF1 from the 2024 US Grand Prix onward, but individual records may still be missing.
Race control
Official messages from the selected session.
Race-control log —
Original messages for the full session, in UTC. Their lap references may be the leader’s lap; app annotations match lap timestamps.
SCVSCYellowRed / stoppedGreen / clearBlue
INSPECT THE SOURCE, WITH CONTEXT
Lap data
Explore the whole selected session independently of the tire and pace selections.
Driver
Lap
Compound
Stint / age
Lap time
Context
—
1 / 1
Lap-time comparison
Select drivers to compare their recorded times on each lap. Tire filters do not apply.
What the annotations mean
Race-control context
Safety car, VSC, red flags and possible yellow-flag exposure. Tags come from period overlap with the timed lap.
Lap context
Pit-in, pit-out and standing-start laps. These stay visible but do not enter unflagged summaries.
Data quality
Missing duration, unknown compound and identifiable deleted time. Missing values appear as unavailable.
Pace anomaly
A robust within-stint timing anomaly, not proof of its cause. A lap can have multiple tags; annotation counts need not add up to the lap total.