Skip to content
Racing Sheet Subscribe

How to Tell Local Speed from Time Gained Around an F1 Lap

Elena Marchetti

Local vehicle speed is not time gained: delta meaning depends on the reference, sign and alignment, while sectors anchor the net timing result.

A line’s height does not tell you whether it represents speed or time gained. First identify the metric, horizontal axis, selected laps, reference lap, sign convention, and alignment method. Then use official sector times to locate the broad difference before using telemetry to describe what happened within that section.

The short answer: local speed and accumulated time answer different questions

Display What it helps you compare What to verify
Speed trace Displayed vehicle speed around the lap Speed units and horizontal axis
Lap-time delta Time difference under the provider’s comparison method Reference lap, sign and alignment
Sector times Net differences across the lap’s timing sections Comparable laps and sector endpoints
Race trace Cumulative differences lap by lap Race reference and adjustments

For this article, “speed trace” means a chart whose vertical metric is vehicle speed. Its plotted values should be read only against the horizontal axis stated by the chart. Check whether that axis is labelled as distance, lap percentage, track position or elapsed time; do not assume those labels represent interchangeable forms of alignment.

A lap-time delta needs an even narrower reading because its meaning depends on the provider’s method. TracingInsights defines its lap-comparison delta as comparison-lap time minus reference-lap time. It separately offers lap-time, telemetry, sector and race-trace views, with the race trace showing cumulative differences lap by lap rather than a direct single-lap speed comparison (TracingInsights dashboard and chart documentation).

Do not transfer that convention to another tool. A positive, negative, rising or falling delta cannot be called a gain or loss until the chart’s reference and sign convention are known.

Sector times provide official timing anchors for broad sections of the lap. They establish the net result at each sector endpoint, while the speed trace can help describe the local pattern inside that section.

This distinction is the source of much chart-reading confusion. In one Russell-versus-Leclerc discussion, viewers questioned whether graphic height represented speed or pace and where the time difference arose. The discussion demonstrates how an insufficiently explained graphic can be misread; it does not verify where either driver gained time or why (Russell-versus-Leclerc discussion).

Check the chart before interpreting the drivers

Use this seven-item checklist:

  1. Metric: Does the line represent speed, elapsed time, lap-time delta, throttle, position or another quantity?
  2. Units: Is speed shown in km/h or mph? Is time shown in seconds or milliseconds?
  3. Horizontal axis: Is the chart labelled by distance, lap percentage, track position or elapsed time?
  4. Selected laps: Which exact laps are being compared, and were both representative flying laps?
  5. Reference lap: Which driver or lap defines zero?
  6. Delta sign convention: What do positive and negative values mean on this chart?
  7. Alignment or reconstruction method: How does the provider establish corresponding points between the laps?

Do not assume every displayed lap had the same purpose. A flying lap should not be compared uncritically with a preparation or cooldown lap. Even two fast laps may not be comparable if one was affected by traffic or abandoned before completion.

Identify the chart type before interpreting line height. A platform may place lap-time, telemetry, sector and race-trace charts beside one another even though their vertical measures answer different questions. Likewise, one provider’s delta convention says nothing about another provider’s convention.

Apply a practical stop rule: if the axes, reference lap or sign convention are missing, report only what is visibly different. You may say that one line is higher or that the lines separate in a particular section. Do not claim that a driver gained or lost time.

Read one corner in four phases: braking, turn-in, apex, and exit

Hypothetical example—not measured Formula 1 telemetry: Two drivers approach the same corner on aligned charts.

Phase 1: Braking. Driver A brakes later and therefore remains faster for longer on the approach. That local pattern is not proof of a time gain across the corner. Later braking also carries the risk of entering too quickly and compromising the next phases.

Phase 2: Turn-in and apex. Driver B slows earlier but follows a more effective route through turn-in and the apex. Apex accuracy, available grip and racing-line choice can affect how much speed the driver carries while maintaining a useful trajectory.

The fastest racing line need not be the physically shortest route. Drivers may use the available track width to increase the effective corner radius and carry more speed. Formula 1’s glossary also identifies S1, S2 and S3 as the lap’s sectors and notes that a rubbered-in surface can provide more grip (official Formula 1 glossary on racing lines, sectors and track grip).

Phase 3: Exit. Driver B’s execution might allow stronger carried speed beyond the apex, making the effect last longer than an isolated minimum- or peak-speed difference. Driver A might instead recover before the exit. The chart must show which pattern occurred; neither result follows automatically from the braking point.

Phase 4: Following straight. One car may eventually reach a higher top speed, but that peak alone does not establish which lap completed the corner-and-straight section faster. The other car may have reached the straight sooner or carried more speed through its early portion. Use the timing result at the relevant endpoint rather than awarding the gain to the taller speed peak.

Use sectors as timing anchors, then telemetry for diagnosis

Begin with the selected laps’ official S1, S2 and S3 times. Their endpoints identify the broad section in which the net gap increased or decreased.

Use this workflow:

  1. Verify total lap time. Confirm which complete lap was faster.
  2. Compare sector endpoints. Identify where the broad net difference occurred.
  3. Inspect the relevant section. Examine the speed trace and any other available channels inside that sector.
  4. Separate observation from explanation. Describe visible differences before proposing causes.

A faster sector establishes the net timing result across that sector. It does not establish whether the difference came from braking, cornering grip, tyres, setup, traffic, straight-line performance or several smaller effects.

This order also reduces cherry-picking. A conspicuous top-speed advantage may be too brief to offset losses elsewhere. Conversely, several modest differences through a corner sequence may produce a meaningful sector advantage without one dramatic peak.

Know which delta points are exact and which may be estimated

A delta curve does not necessarily consist entirely of official timing measurements. Its construction depends on the provider.

Under the documented TracingInsights method, the selected laps are divided using official S1, S2 and S3 times. Within each sector, the comparison lap’s distance is scaled to the first selected lap, time is interpolated, and the result is corrected so that the sector endpoint matches the official delta (TracingInsights methodology).

Under this specific method, the sector endpoints are exact, but the shape between them is estimated. That statement should not be generalized to platforms using different data or alignment techniques.

A clear visualization should distinguish official sector anchors from the reconstructed line between them—for example, by placing prominent endpoint markers over a lighter curve. This helps readers separate firm timing results from estimates of where the changes occurred within a sector.

Do not treat every small wiggle in an interpolated curve as proof that time changed at one precise braking point or apex. Minor movements can arise from interpolation, smoothing or alignment rather than an independently timed event.

Separate what the traces show from what might have caused it

Telemetry is most reliable when used to describe a visible pattern. Explaining its cause usually requires additional channels and context.

Observation supported by the chart Hypothesis requiring corroboration
One car is faster at a plotted position Its aerodynamic setup caused the difference
One lap has the faster S2 time Its tyres were in a better temperature window
The delta changes through a section One driver used more energy deployment
One car reaches a higher peak speed It had less fuel, a tow or lower drag

Braking point, apex execution, racing line and carried speed can influence lap performance, but a speed trace alone does not isolate their causes. Tyre compound and temperature affect available grip; clean air can support performance without the aerodynamic disturbance of traffic; and aerodynamics can affect cornering and straight-line performance (official Formula 1 glossary on performance factors).

Before treating two laps as a fair comparison, check:

  • tyre specification, age and condition;
  • track evolution and rubbering;
  • traffic, tow or clean air;
  • weather and track conditions;
  • whether both were representative flying laps;
  • reliable information about setup, fuel or lap purpose.

The Russell-versus-Leclerc discussion does not verify where either driver gained time, nor does it establish differences in engine deployment, fuel load or setup. Those conclusions would require synchronized data, a known chart methodology and corroborating context.

Use timing to locate the gain, telemetry to describe the visible pattern, and corroborating information before explaining the cause. The essential distinction is between a local observation and an accumulated timing result—not which line happens to look taller.