Same car, same track — why is he 1.5 seconds faster?

You run the same car, the same track, the same session — and your mate is a second and a half up the road, every single stint. Same equipment, so it is not the car. And here is the uncomfortable, liberating truth: it is probably not talent either. A 1.5-second gap between two amateurs is almost never one heroic corner. It is a handful of small, repeatable differences — two tenths here, three tenths there — each one attached to a specific habit at a specific corner.

Repeatable is the key word. A difference that appears once might be a lucky lap. A difference that appears lap after lap is technique, and technique can be copied.

Where the gap usually hides

Across thousands of amateur sessions, the same patterns carry most driver-to-driver gaps: the faster driver brakes slightly later or releases the brakes better, carries more minimum speed through the apex, and gets to full throttle earlier — not by bravery, but because the car is pointed sooner. None of these are visible from the outside. All of them are visible in the data.

The apex-speed difference is the one that surprises drivers most. From the cockpit it feels like the fast guy is simply braver; the data usually says he turns in later and asks less of the car at entry. As a report puts it when apex speed is the finding:

Measure it instead of guessing

Ask your faster friend for one file — the .ibt from any session at that track, same car. Upload yours and theirs together as a Benchmark Debrief, and the comparison stops being a mystery: corner by corner, where they gain, how much, and how repeatably. The gap turns from a feeling of inferiority into a to-do list.

Then work it like any other debrief: biggest repeatable difference first, one change, three laps to judge, next session to confirm. The instruction attached to a slow-apex finding is characteristically undramatic:

Chasing a benchmark this way has a compounding property that solo practice lacks: every session, you are learning from someone who has already solved the corners you have not. That is how teams have always developed drivers — and it works exactly the same for two friends with two .ibt files.