How to Read F1 Practice Data — A Complete Guide

Every F1 weekend gives you three hours of practice data before a single competitive lap is set. Most casual fans ignore it completely. The best predictors? They treat it as the foundation of everything they do on Saturday and Sunday.

The catch is that not all practice data is created equal. FP1 lap times are almost meaningless. FP2 hides race-pace gold inside messy long-run stints. FP3 is the closest thing to a qualifying cheat sheet you'll find. Knowing which signals to trust and which to throw away is the single biggest edge you can build as a predictor.

This guide breaks down each session, shows you what to look for, and gives you a framework for turning three hours of practice into accurate predictions.

---

Why Practice Sessions Matter

Here's something important to understand upfront: practice exists for teams, not fans. Engineers use these sessions to gather data on tyre compounds, aerodynamic balance, fuel loads, and setup direction. The lap times you see are a byproduct of these engineering programs. Nobody is trying to go fast.

What does that mean for you?

• Headline lap times are often misleading. A driver running low fuel on soft tyres in FP1 will look much faster than someone gathering long-run data on hard tyres with a full tank. The gap between them says nothing about actual pace.
• The context behind the lap time matters more than the time itself. Was it a qualifying simulation? A race-fuel long run? An aero test with extra sensors? The same driver can be 2 seconds slower depending on what program they're running.
• Consistency matters more than peaks. A driver who posts ten laps within 0.3s of each other is showing you real pace. A driver who posts one fast lap and nine slow ones was probably on a completely different program.

---

FP1: What You Can (and Can't) Learn

FP1 is Friday morning (or Friday afternoon at some circuits). It's the first time cars hit the track, and it's the least predictive session for qualifying or race performance.

Here's what the top 10 looked like in FP1 at the 2026 Australian Grand Prix:

Ferrari 1-2, Mercedes P7-P8. If you'd used this to predict qualifying, you'd have had Ferrari on pole. And you'd have been completely wrong. Russell (Mercedes) took pole by 0.293 seconds over teammate Antonelli in a Mercedes 1-2 lockout, while Ferrari qualified P4 and P7, over eight tenths off pole.

The Noise in FP1

• Fuel loads vary wildly. Some teams run low fuel for aero validation; others run race fuel for baseline setup. A 10kg fuel difference is worth roughly 0.3s per lap.
• Tyre compounds differ. The driver on softs will always be faster than the one on hards. Without knowing which compound each driver used, headline times are meaningless.
• Test items and aero rakes. Teams sometimes run experimental parts or sensor equipment that adds drag. Academy drivers also often get FP1 seat time.
• Track evolution is minimal. On a green track (minimal rubber), the surface is at its least grippy. Times improve significantly across the weekend as rubber builds up.

The Signal in FP1

FP1 isn't entirely useless, though. You can learn:

• Who brought upgrades. If a midfield car is suddenly in the top 5, pay attention. It might signal a genuine step forward.
• Initial setup direction. Teams that are immediately comfortable (clean, consistent laps) versus those that are struggling (erratic times, oversteer, lockups) give you a directional signal.
• Long-run pace trends. Some teams start their race fuel program in FP1. Their lap times look slow, but their data may be the most valuable on the grid.

---

FP2: The Race Pace Session

FP2 is where the real data lives. This is typically the longest practice session, and teams use it to run their race simulations: extended stints on race fuel to understand tyre degradation and long-run pace.

The single-lap times in FP2 get the TV graphics. But the long-run data underneath is what actually matters for race predictions.

Understanding Long Runs

A long run is a stint of 8-15 laps on high fuel, simulating a race stint. Teams use this data to choose their race strategy: which compound to start on, when to pit, whether to attempt a 1-stop or 2-stop.

For predictors, long runs tell you three critical things:

• Baseline race pace. How fast is each car per lap over an extended stint?
• Degradation rate. How quickly do the lap times get slower as the tyres wear?
• Compound behavior. Which compound suits which car? Some cars are gentle on softs but struggle on hards, and vice versa.

Reading the Strip Plot

The best way to compare long-run data across drivers is a strip plot, a visualization where each dot represents a single lap time during a stint, colored by tyre compound. Here's the FP2 long-run data from Australia 2026:

How to read this:

Each horizontal row is one driver. The dots represent individual lap times during their long-run stints. White dots are hard compound, yellow are medium, red are soft. Dots further right are slower.

Here's what this specific data reveals:

1. Russell showed the best consistency. His 11-lap hard stint (median 1:23.5) had near-zero degradation. The dots barely spread out. That's a strong signal for race pace.

2. Antonelli was slightly slower on the same compound. His hard stint median was 1:24.1, about 0.6s slower than his teammate. Consistent, but off Russell's pace.

3. Hamilton's first stint looks fast but is misleading. His initial hard run (1:21.0-1:21.4 range) was likely on significantly lower fuel than the others. The second stint (1:24.4-1:24.5) is more representative.

4. Norris ran softs for his long run. Those red dots. A 1:23.5 median on softs sounds competitive, but soft compound times can't be directly compared to hard compound times. His underlying hard-compound pace would be slower.

5. Hadjar's medium stints were split. A fast early run (fuel effect) followed by a more representative later stint at 1:24.6.

Fuel Correction

Fuel burns off during a stint at roughly 0.06-0.08 seconds per lap of improvement. The first few laps of any long run are artificially slow (heavy fuel) and the last few laps are artificially fast (lighter car). The middle laps are most representative.

That's exactly why Hamilton's first stint looked so fast. He likely started with less fuel than others, making every lap quicker. Professional analysts subtract a fuel correction factor, but for prediction purposes, just focus on the middle portion of each stint for the most honest comparison.

---

FP3: The Qualifying Preview

As Pirelli's motorsport boss Mario Isola has noted, the compound gap is designed to be "seven to eight tenths between compounds in qualifying, around four tenths in race conditions" (Formula1.com). Those numbers are your correction factor when comparing drivers on different tyres.

FP3 runs on Saturday morning, 2-3 hours before qualifying. Teams dedicate this session to qualifying preparation: low fuel, fresh soft tyres, optimal setup. This is your single best predictor of Saturday afternoon's qualifying order.

Here's how the teams stacked up in FP3 qualifying simulations at Australia:

Russell was 0.616 seconds clear of Ferrari. In qualifying, he took pole by 0.293 seconds over Antonelli, with the nearest non-Mercedes 0.785 seconds adrift. The direction was spot-on. FP3 told you Mercedes would be dominant, and qualifying confirmed it emphatically.

Why FP3 Works So Well

• Same conditions. FP3 runs on the same day as qualifying, on the same track surface, at similar temperatures.
• Same tyre strategy. Teams run fresh softs with low fuel, exactly what they'll do in Q3.
• Representative driver effort. Unlike FP1/FP2 where drivers might hold back, FP3 qualifying sims are genuine maximum-attack laps.

When FP3 Lies

FP3 isn't perfect. Watch out for:

• Wet FP3, dry qualifying. If it rains in FP3, you lose your qualifying simulation data entirely. Fall back to FP2 single-lap times or pre-event form.
• Red flags. A shortened FP3 means fewer drivers complete their qualifying sims. The data is incomplete.
• Sandbaggers. Some teams (historically Mercedes) deliberately run conservative FP3 programs. If a top team looks slow in FP3 but has been fast all weekend, they may be hiding their true pace.

---

Track Evolution: The Invisible Variable

One thing that catches beginners off guard: the track gets faster over the weekend. This is called track evolution, and it happens because:

• Rubber build-up. As more cars run, they deposit rubber on the racing line, improving grip. Friday times are on a "green" track; Saturday times benefit from accumulated rubber.
• Temperature changes. Track temperature affects grip significantly. A 10 degree C difference in asphalt temperature can shift lap times by 0.5-1.0s.
• Cleaning effect. Dust, debris, and moisture get swept off the racing line over time, improving grip in later sessions.

At Australia 2026, this effect was dramatic. Mercedes went from P7 in FP1 (1.1 seconds off) to pole position by 0.785s in qualifying. Some of that was setup improvement, but a significant portion was the track evolving to suit their car's high-speed aero philosophy.

*via Hadjar (Verstappen incident in Q1)

The trend is clear: Friday position is almost meaningless by Saturday. Always look at the direction of travel. Is a team improving or declining across sessions? That trajectory is more predictive than any single session position.

---

Putting It Together: A Practical Framework

Here's how to turn practice data into predictions:

For Qualifying Predictions

1. Start with FP3 qualifying simulation data. This is your primary source.
2. Cross-reference with FP2 single-lap times. If FP3 and FP2 agree on the team order, that's a strong signal.
3. Check the trajectory. If a team improved from FP1 to FP3, they may find even more in qualifying. If they declined, they might be plateauing.
4. Adjust for known qualifiers. Some drivers consistently overperform their car in qualifying (Leclerc, Russell). Others tend to underperform (historically, some second drivers).

For Race Predictions

1. Start with FP2 long-run data. Median pace and degradation rate on race-representative compounds.
2. Compare like-for-like. Only compare drivers on the same compound. A fast soft run doesn't mean fast hards.
3. Identify the low-deg cars. Teams with flat degradation profiles (tight dot clusters) are the most likely to outperform their grid position on Sunday.
4. Factor in strategy. If a team ran only hards in FP2, they may be planning a conservative strategy. If they focused on mediums, they may be targeting an aggressive 2-stop.

The Trust Hierarchy

When practice signals conflict, here's how to weight them:

• FP3 qualifying sims > FP2 single-lap > FP1 single-lap (for qualifying)
• FP2 long runs > FP1 long runs > pre-event data (for race pace)
• Session-to-session trajectory > any single session (for both)

Practice data doesn't predict the future, but it narrows the range of likely outcomes dramatically. The predictors who consistently beat the field aren't psychic. They're just better at reading what three practice sessions are actually telling them.

Ready to apply this framework? Start predicting on Podium Prophets — and check out our practice summary from Australia to see this analysis in action.