How a lactate test predicts your race time
From a step test to a finish-time prediction: what LT1 and LT2 actually are, how thresholds become a physics simulation, and why durability decides the last hour.
A lactate step test locates the two intensities your race economy is built on: LT1, the highest effort your body clears without accumulating lactate, and LT2, the ceiling you can hold for about an hour. Feed those into a physics simulation of the course and you get a finish time, a pacing plan, and an honest uncertainty band.
Every finish time you have ever run is the output of the same machine: an aerobic engine with two measurable gears, a small anaerobic battery, and a fatigue curve. A lactate step test measures the gears. The rest is physics. This is, start to finish, how Labthlete turns a handful of blood samples into a pacing plan.
Step one: the test finds your two thresholds
In a step test you ride or run at a fixed intensity for 4 to 6 minutes, take a lactate sample, raise the intensity, and repeat until the curve takes off. Two landmarks come out of the fitted curve:
| Landmark | What it is | What it anchors |
|---|---|---|
| LT1 (aerobic threshold) | First rise above baseline lactate | All-day and long-race pacing |
| LT2 (anaerobic threshold) | Where accumulation accelerates | FTP on the bike, critical speed on the run |
Labthlete fits the curve with three published detection methods side by side and shows you where they disagree, because a threshold is an estimate, not a revelation. You can drag the fit yourself; the app never hides the raw points.
Step two: thresholds become an engine model
LT2 plus the anaerobic battery (W′ on the bike, D′ on the run) define the classic critical-power model: how far above threshold you can surge and for how long, following Skiba’s W′-balance formulation. LT1 sets the intensity your long races are actually paced at. One more number completes the engine: durability, the rate at which your thresholds fade per 1000 kJ of work, which is what separates a strong 10K runner from a strong marathoner.
Step three: physics rides the actual course
A finish time is the engine model pushed through the resistances of the real world. On the bike that is the standard power balance (aerodynamic drag from your CdA, rolling resistance, gravity on every gradient, drivetrain losses, air density from temperature and altitude). On the run it is the metabolic cost of grade from Minetti’s measurements, with heat and altitude corrections. Labthlete simulates the course metre by metre from the GPX, then optimizes where you should push and where you should float, so the plan reads like a race brief: hold this on the flats, cap the climbs here, let the descents come to you.
Step four: the race-day forecast
A single predicted number is marketing; a range is a forecast. The Labthlete race-day simulator runs hundreds of versions of your race through the same physics: your form wobbling a couple of percent, as it genuinely does between good and bad days; the weather drawn around the forecast; and the small but real chance that something goes wrong on the day (cramps, stomach, a bad patch). Out comes a P10, P50 and P90 finish forecast whose median is pinned to the prediction itself, with a longer slow tail, because a bad day costs more than a good day gains. If the tank empties before the line at your chosen intensity, the app says so instead of printing a fantasy split.
The fastest way to feel the difference is to try it: the free predictor runs the full physics with population defaults, and an account replaces every default with your own tested numbers.
Frequently asked questions
Do I need a laboratory for a lactate test?
No. A field step test with a portable analyzer (Lactate Pro 2, Lactate Scout and similar) on a trainer, track or treadmill gives curves that are perfectly usable for threshold detection, as long as the protocol is consistent: 4 to 6 minute steps, small increments, samples at the end of every step.
How accurate is a race prediction built this way?
Honest predictions come as a range, not a single number. Labthlete simulates hundreds of race days (day-to-day form, weather, incident risk) and returns P10, P50 and P90 finish times, with the median pinned to the deterministic prediction; for a well tested athlete on a known course the band is typically a few percent wide. The single biggest source of error is not the model but stale inputs: thresholds drift with training, so test regularly.
How often should I repeat the test?
Every 6 to 10 weeks during structured training, or after any clear change in fitness. Durability (how your thresholds fade with accumulated work) changes more slowly and can be re-estimated a couple of times per season from paired fresh versus pre-loaded tests.
What is the difference between LT1 and LT2?
LT1 is the first rise of lactate above baseline: below it you can go for many hours, and long races are paced just around it. LT2 is where accumulation accelerates: it marks roughly one hour of maximal effort and anchors FTP on the bike and critical speed in running.
The free Labthlete predictor simulates your race from your own physiology: watts, thresholds, durability and the course. No account needed.
Try the predictor