Reading F1 Telemetry — A Beginner's Guide
What F1 telemetry actually is, the five charts that matter, and how to read them. A no-jargon beginner's guide for fans who want to understand the data.
You have heard people on F1 Twitter say things like "Verstappen was 0.3 seconds a lap quicker through Sector 2" or "Norris is leaving 5 km/h on the table at the speed trap." This is how they know. They are reading telemetry, and once you know what to look at, so can you.
This guide is for the fan who keeps seeing telemetry charts on broadcasts and YouTube breakdowns and wants to actually understand what's on the screen. No engineering background needed. By the end you will know what telemetry is, the five charts that matter, and what to look for in each one.
If you are still figuring out the basics of F1 prediction itself, start with F1 Predictions for Beginners first, then come back here.
What F1 Telemetry Actually Is
Telemetry is the live data stream that every F1 car broadcasts during a session. Sensors on the car sample dozens of channels at very high frequency (speed, throttle, brake pressure, gear, RPM, steering angle, DRS state, lap and sector splits) and the data is transmitted to the team garage in real time. It is also captured by the FIA timing system and a chunk of it is made public.
The teams use it to set the car up, debrief the driver, and find performance. Fans use a smaller, simpler subset to understand why a lap was fast or slow.
A few terms worth defining before we go further:
- DRS stands for Drag Reduction System. It is a flap on the rear wing that opens on designated straights to reduce drag and let the car go faster. On telemetry it shows up as a 0/1 channel: closed or open.
- Sector means one of the three sections every lap is split into for timing. Each circuit has timing loops at fixed points, so S1, S2, and S3 are consistent across all drivers.
- Trail braking is the technique of staying on the brake pedal as the driver turns into a corner, gradually releasing pressure. It rotates the car into the apex. You can see it on a brake trace as a slope down to zero rather than a cliff.
That's all the jargon you need for the rest of this post.
The Five Charts You Actually Look At
There are dozens of telemetry channels in a real engineering session. You do not need most of them. These five do the heavy lifting:
1. Speed Trace
A speed trace plots speed (Y axis, in km/h) against either distance around the lap or elapsed lap time (X axis). Drop two drivers on the same chart and the picture tells the story.
The line goes up on straights, falls off a cliff into braking zones, dips through corners, and climbs again on exit. Where the two lines diverge is where time is being made.
Three patterns to watch for:
- One driver higher on the straight means a top-speed advantage. Could be lower drag, better DRS deployment, or a tow from another car.
- One driver higher mid-corner means more grip or more commitment. Either the car has more downforce or the driver is willing to carry more speed where the other lifts.
- A later dip on entry means later braking. The driver who keeps the line up longer before the dip is braking later. That gains entry but only counts if the line doesn't drop further than the other driver's at the bottom.
A clean speed trace comparison will often answer the question "where did Driver A find that 0.2s?" in about ten seconds of looking.
2. Throttle Trace
Throttle is the percentage of pedal the driver is applying, from 0 to 100. It is one of the most readable channels on the car.
The pattern is binary in feel: full throttle on straights, zero through the slow part of a corner, then a ramp back up on exit. The interesting bit is that ramp.
Throttle traces are weirdly satisfying to read. There is a Verstappen-shape that you start to recognise after enough races: pinpoint apex, full throttle 30 metres earlier than anyone, then he just holds it pinned. Other drivers feed it in more gently, sometimes because the car can't take it, sometimes because they're managing degradation.
What to look for:
- Earlier full throttle on exit is a faster corner. Almost always.
- Throttle modulation in the middle of a corner means the driver is balancing the rear, often a sign of a car that wants to step out.
- A short lift in the middle of a straight is usually engine map, fuel saving, or DRS being denied. Worth noting but not a driving signal.
3. Brake Trace
Brake pressure works the same way: 0 to 100 percent, plotted around the lap. Cliffs at corner entry, zero on straights and through the corner itself.
The difference between drivers shows up at the edges:
- Where the brakes come on. A later brake application is a later braking point. Costs nothing if the corner still works.
- How they come off. A vertical drop to zero is a stab. A slope down to zero is trail braking, where the driver keeps a touch of brake while turning in to help the car rotate. Most modern F1 drivers trail brake. The exact slope is a fingerprint of style.
- A double application in the same braking zone usually means a missed marker or a small lockup correction.
Brake traces won't tell you everything on their own, but combined with the speed trace they explain why one driver carried more speed into the apex.
4. Sector Deltas
Sectors are the simplest tool here, and the one most non-engineers can already read. Every lap is broken into three sectors. The delta is the difference between two drivers' sector times.
If Driver A is 0.4s faster overall and the deltas show +0.05, +0.30, +0.05, the lap was won in S2. That narrows the analysis from the whole lap to one section of track. From there you go look at the speed and throttle traces for just that sector and the answer is usually obvious.
We have a full breakdown of sector analysis (including the difference between sector times and speed trap readings) in F1 Speed Trap & Sector Times Explained.
5. Long-Run / Stint Pace
The first four charts compare single laps, usually qualifying. This one is for race pace, and it is the one that matters most for race predictions.
A stint plot shows every lap of a long run on the same compound, on race fuel, lap by lap. Each driver is one row of dots. The Y axis is lap time. Spread tells you consistency. Slope tells you tyre degradation. Median tells you raw race pace.
Qualifying telemetry shows you peak. Race telemetry shows you truth.
For a deeper walkthrough of long runs and what to do with the data, see How to Read F1 Practice Data. Tyre compound choice changes everything in those plots, and the tyre strategy guide covers what each compound is doing under the rubber.
What to Look For — A Concrete Example
Generic descriptions are easy. Reading actual data is the skill. Here is the kind of read you will start making once you have spent a few sessions with telemetry charts.
Take the 2026 Australian Grand Prix qualifying. Russell took pole by 0.293 seconds over Antonelli, with the nearest non-Mercedes (Hadjar in the Red Bull) 0.785 seconds back. Look at the telemetry comparison between Russell and Hadjar and the story isn't a single big gap. It is a slow bleed.
Start with the sector deltas. Hadjar's lap was down in all three sectors, not concentrated in one — exactly the pattern you'd expect when the lap is being lost in lots of small places rather than one corner.
Hadjar vs Russell — Sector Deltas (Australia 2026 Qualifying)
Hadjar was actually competitive in the slower technical sections. Mid-corner speeds were close. But on every full-throttle exit, Russell got to 100 percent throttle a beat earlier and held a slight top-speed advantage all the way down each straight. Five exits, a tenth or two each, and you have eight tenths of qualifying gap that lap times alone would never explain.
Two things you would not have known without telemetry:
- The gap was not a corner-grip problem. Hadjar's mid-corner numbers were fine.
- It was traction and deployment. That tells you to expect the same gap to show up in the race, not narrow once tyres come in.
Quali pace alone said "Mercedes is faster." Telemetry told you why, and which kind of faster.
What Telemetry Can't Tell You
Telemetry is powerful but it is not omniscient. A few things that are not in the public data:
- Fuel load. A car running 10 kg lighter is roughly 0.3s a lap quicker. You will not see fuel level on a public telemetry chart, and it is one of the biggest reasons FP1 single-lap comparisons mislead.
- Engine modes. Power units have multiple performance modes. A car running a lower mode in practice for reliability or sandbagging looks slower than it actually is, and the channel that would tell you isn't published.
- Exact tyre wear state. You can see degradation through lap times. You cannot see whether it is graining, blistering, thermal degradation, or surface wear without team data.
- Driver radio context. Maybe the driver was managing a brake issue, saving fuel, or under team orders. The chart shows what happened. It does not tell you why the driver chose to do it.
Telemetry is best used as a hypothesis generator. It tells you what changed. Combine it with timing data, broadcast context, and (sometimes) post-race quotes to figure out why.
Where to Actually Look at It
A few options, from easiest to most technical:
- Sky F1's onboard graphics during broadcasts. Speed, throttle, brake, gear shown as overlays on the in-car camera. The most accessible entry point.
- Podium Prophets embeddable telemetry widgets. Lap-by-lap telemetry comparisons after every finished session, with sector deltas and the same speed/throttle/brake traces this guide describes. Drop them into any blog or site, or browse them in the embed showcase.
- The official F1 app for live sector splits, speed trap readings, and timing data during sessions.
- FastF1 if you are technically inclined. It is an open-source Python library that pulls historical telemetry directly from the F1 timing service. It is the same data the analysis tools above are built on.
A Simple Workflow for Reading Any Comparison
Once you start looking at telemetry comparisons, this five-step pass works for almost any "why was Driver A faster than Driver B?" question:
- Sector deltas first. Find which sector the lap was won in. Ignore the others for now.
- Speed trace for that sector. See where the lines diverge. Straight, braking, mid-corner, or exit.
- Throttle trace for the same corner. Check who got to full throttle first.
- Brake trace for the same corner. Check who braked later, and whether they trail braked.
- Cross-check with stint pace if it matters for race predictions, not just one-lap pace.
Five minutes of looking and you have a real answer instead of a vibe.
Telemetry is the language F1 speaks to itself. You do not need to be fluent. You just need enough vocabulary to follow the conversation, and that is a couple of practice sessions of looking at charts.
If you want to try this on real data, browse the embed gallery — the telemetry widget compares any two laps from any session of the 2026 season. Pick a race you watched, line up two drivers, and see what the charts say.