F1 Long Run Pace Explained — How to Read It

Long-run pace is the single most underrated signal in F1 prediction. Most casual fans look at qualifying, copy the grid, and call it a prediction. They lose. Qualifying tells you who can string together one lap on fresh softs with low fuel. The race is 305 kilometres of degradation, fuel burn, traffic, and tyre management. Those are completely different problems, and they have different answers.

If you want to make sharper picks, the FP2 long-run stint data is where the gold is buried. The catch is that it's noisy, it's incomplete, and it lies if you read it wrong. Here's how to read it properly.

If you're brand new to all this, start with F1 Predictions for Beginners first. This post assumes you already know what FP2 is and why anyone cares.

---

What "Long Run" Actually Means

A long run is a multi-lap stint where a driver stays out on the same set of tyres for at least 5 laps, typically 8 to 15. Teams run them during practice (mostly FP2, sometimes FP1) on heavy fuel to simulate race conditions. The point is to gather degradation data, validate the strategy model, and let the driver build a feel for how the car behaves once the tyres start cooking.

Single hot laps in qualifying simulations don't help you here. You're looking for the pattern across laps, not the peak.

Where you find this data:

• FP2 is the main source. Most teams run their primary race simulation here.
• FP1 sometimes has long-run data, especially at sprint weekends when FP2 is replaced by sprint qualifying.
• FP3 is usually qualifying-prep only. Don't expect long runs.

For the broader practice context (single-lap pace, fuel correction, track evolution), see How to Read F1 Practice Data. This guide zooms in on just the long-run portion.

---

What You're Actually Looking At

When you stare at a long-run stint, you're looking at four things layered on top of each other:

1. The driver's underlying race pace on that compound, on that fuel load, in those conditions.
2. Tyre degradation, which makes lap times slower as the rubber wears (covered in detail in F1 Tire Degradation Explained).
3. Fuel burn, which makes lap times faster as the car gets lighter (roughly 0.06 to 0.08 seconds per lap).
4. Driver inputs, including pushing harder on some laps, lifting in traffic, sandbagging on others.

Items 1 and 2 are what you want. Items 3 and 4 are noise. The whole skill is filtering the signal from the noise.

You can't fully fuel-correct from outside the team. Nobody publishes the fuel load each car was carrying. But the degradation pattern (how lap times change over the stint) is still readable, because fuel burn is roughly linear and similar across cars, while tyre deg is the differentiator.

---

How to Compare Drivers Fairly

This is where most analyses fall apart. Two drivers running long stints in the same FP2 session can look 1.5 seconds apart and actually have identical race pace. Or look identical and actually have a half-second gap.

To make a fair comparison, drivers need to be matched on three things:

• Same tyre compound. A soft long-run will always look faster than a hard one, by anywhere from 0.4 to 1.0 seconds per lap depending on the circuit. If one driver runs softs and another runs hards, you can't compare medians. You can compare degradation slopes (how fast each one falls off), but not raw pace.
• Similar stint length. A 5-lap stint and a 15-lap stint aren't the same thing. The 15-lap stint is showing you more degradation. Compare the same window of laps when possible.
• Similar fuel state. This one you have to estimate. A driver who started their long run on lap 30 of FP2 is probably on lighter fuel than someone who started on lap 5. The first few laps of any stint are the heaviest.

For the compound-specific stuff, the F1 Tyre Strategy Guide goes deeper on what "soft", "medium", "hard" actually mean for race pace. The short version: never compare across compounds without a correction factor. And when you're trying to figure out whether a slow long-run is a driver problem or a car problem, Driver vs Team — Who's at Fault? covers the full attribution framework.

---

The Tricks (and How to Spot Them)

Long-run data is dirty. Here's what makes it dirty:

Sandbagging. Some teams (historically Mercedes, occasionally Red Bull) run conservative practice programs. Engine turned down, unusual setup, driver not pushing. The tell is consistency without speed: very flat laps, but slower than the team's quali pace would predict.

Traffic. A driver who catches a slower car mid-stint loses 1 to 3 seconds on that lap. One outlier in a stint of 10 means somebody got stuck behind a Williams in sector 2. Throw the lap out, don't average it in.

Fuel-saving laps. Late in long runs, drivers sometimes practice lift-and-coast. The lap times get slower in a way that looks like degradation but isn't. Usually shows up as a sudden drop-off rather than a gradual one.

Weather and setup changes. Track temperatures shift across FP2, and some teams test setup A on the first 5 laps and setup B on the next 5. If the data looks weird mid-stint, it might be the car changing, not the tyres.

The way you handle all of this is to be conservative. If a stint looks suspicious (too good, too perfect), discount it. If a stint has clear noise, use only the clean middle. Four to six clean laps from a driver is still better than nothing.

---

A Worked Example: 2026 Australian GP

Let's run this on actual data. Here's the FP2 long-run picture from Melbourne 2026:

What this told you before the race:

Russell on hards was a metronome. Eleven laps, range of 1:23.4 to 1:23.9, no degradation worth noting. That's a race-winning consistency profile. He took pole the next day, then won the race by 2.974 seconds with a hard stint at +0.001s/lap degradation. The long-run data called it.

Ferrari's race pace was hidden in plain sight. Hamilton's first hard stint at 1:21.0 to 1:21.4 looked unbelievably fast. Too fast. Clearly low fuel. His second hard stint at 1:24.4 to 1:24.5 was the honest one, and combined with Leclerc's data revealed Ferrari had the best tyre-life on the grid (-0.0565s/lap average degradation). On race day, Ferrari finished P3 and P4, gaining positions from their qualifying grid. The grid hid this. The strips didn't.

Norris on softs was a trap. A 1:23.5 median on the red compound looks competitive at a glance. But softs are 0.4 to 1.0 seconds faster than hards on race fuel, so his real hard-tyre pace was probably 1:24.0 to 1:24.5. McLaren had higher degradation than Ferrari and Mercedes, and Norris finished P5 with a 51-second deficit. The strip plot doesn't lie if you read the compounds.

The grid said Mercedes 1-2, Red Bull P3, Ferrari P4-P7. The race ended Mercedes 1-2, Ferrari P3-P4, Red Bull P6 (via Hadjar after Verstappen's recovery from P20). Long-run pace got Ferrari right. Qualifying didn't.

For the sector-by-sector layer that pairs with this (where on the track the gaps come from), see Understanding F1 Sector Times and Speed Traps.

---

Turning Long-Run Pace Into Predictions

Here's the actual workflow for using long-run pace in your P1-P10 race prediction:

1. Pull the FP2 stint data. Either from your favourite F1 data site, or grab a built-in long-run strip plot from the embeddable widgets — same data, same chart shape.
2. Group stints by compound. Hard runs in one bucket, mediums in another, softs in a third. Don't mix.
3. Take the median of the middle laps of each stint. Throw out the first 2 and last 2 if the stint is long enough.
4. Build a hard-tyre race pace ranking for the cars that ran hards. That's your race pace skeleton.
5. Adjust for known noise. Sandbagging teams move up. Heavy-fuel programs move up. Drivers with one ridiculously low time on light fuel move down.
6. Compare to the qualifying grid. Cars whose race pace is much better than their grid slot are the ones that climb on Sunday. Cars whose race pace is worse than their grid slot are the ones that get passed.
7. Apply DNF and safety-car risk. Long-run pace doesn't account for opening-lap chaos. At Melbourne, Singapore, Baku, and Monaco, weight raw pace less and bake in chaos.

The cars with the best race pace and the best degradation are your top-3 candidates, regardless of where they qualified. That's the whole game.

---

FAQ

What is long run pace in F1?

Long-run pace is the average lap time a car can sustain over a multi-lap stint on race fuel, typically measured during FP2. It tells you how fast the car will actually go in the race, accounting for tyre degradation and fuel burn, rather than the one-lap peak you see in qualifying.

When during a race weekend do drivers do long runs?

Mostly in FP2, which is when teams run their primary race simulations. At standard weekends, FP2 happens on Friday afternoon. At sprint weekends, FP2 is replaced by sprint qualifying, so long-run data has to come from FP1 or be inferred from the sprint race.

Why is qualifying pace different from race pace?

Qualifying is one lap on fresh softs, lightest fuel, peak engine modes. The race is 305 kilometres on heavier fuel, harder compounds, with traffic and tyre wear. Cars are tuned for different windows. Some cars peak in qualifying. Others (often Ferrari in 2026) come alive on race fuel.

How do you compare long-run pace fairly between drivers?

Match them on tyre compound first, stint length second, fuel state third. Use the median of the middle laps. Throw out laps contaminated by traffic. Never compare a soft run to a hard run without a compound correction (roughly 0.4 to 1.0 seconds).

Can long-run pace predict the race winner?

Not on its own, but it's the strongest single signal you have. Combine it with grid position, weather, safety-car probability, and team strategy tendencies, and you beat copying the qualifying order most weekends. The 2026 Australian GP is a textbook case: Mercedes won (matched their long-run consistency), Ferrari finished P3-P4 (the strips flagged it, the grid didn't), McLaren regressed (high degradation showed up).

---

Where to Go From Here

Make this part of your weekly routine. Pull the FP2 data on Friday evening, build your race pace ranking on Saturday morning, and submit your P1-P10 prediction once you've reconciled it with qualifying.

If you want the long-run analysis and the prediction in the same app, try Podium Prophets. The session analysis tools are built in, the data is loaded automatically after FP2, and your prediction is one drag-and-drop away. No tab-switching, no hand-rolled scripts, no spreadsheet.

Long-run pace is the closest thing to a cheat code F1 prediction has. The data is there every weekend. Use it.