Calculator

How race-time prediction actually works

Every race-time predictor on the internet is doing one of two things. Either it is fitting a power law to your input (Pete Riegel's 1981 method), or it is running you through a physiology model that estimates the fraction of VO2max you can sustain for a given duration (Jack Daniels' 1979 method). Both approaches converge on similar answers for trained runners across moderate distance jumps. Both quietly fail in predictable ways at the marathon.

This page runs both methods on your input simultaneously, so you can see the spread. When they agree, the prediction is solid. When they disagree by more than 2-3%, that itself is a useful signal about how confident to be.

Method 1: Pete Riegel's endurance formula (1981)

Pete Riegel was a mechanical engineer and a competitive distance runner who, in American Scientist in 1981, fit a simple power law to world-record performances across distances from 1500m to the marathon. He found that finish time scales with distance to a small power greater than 1:

T₂ = T₁ × ( D₂ / D₁ )1.06

The exponent 1.06 captures the fact that you cannot hold a given pace forever. As distance doubles, time slightly more than doubles. Riegel found the exponent was relatively stable across distances from 800m to the marathon for elite athletes.

The formula's strength is its simplicity. It needs no physiology, no oxygen costs, no training context. The weakness is that the exponent 1.06 was fit to world records. For recreational runners, the effective exponent at marathon distance is closer to 1.07 to 1.10, which is why Riegel predictions tend to flatter amateur marathon performance.

Method 2: Daniels and Gilbert's VDOT model (1979)

Two years before Riegel, exercise physiologist Jack Daniels and mathematician Jimmy Gilbert published a different approach in Oxygen Power: Performance Tables for Distance Runners. They built a two-equation system that goes through physiology rather than around it.

The first equation gives the oxygen cost of running at a given velocity:

VO₂ = −4.60 + 0.182258 · v + 0.000104 · v²

The second gives the fraction of maximum aerobic capacity sustainable for a race of duration t:

% VO₂max = 0.8 + 0.1894393 · e−0.012778 · t + 0.2989558 · e−0.1932605 · t

From your input race, the system derives a fitness score (VDOT). To predict a time at another distance, it finds the duration at which oxygen cost equals VDOT times the sustainable fraction. The model has a physiological story for every number.

If you want the full background, see our VDOT explainer and the dedicated VDOT calculator, which exposes the underlying VDOT score and adds training paces.

Why both methods overestimate amateur marathons

The cleanest evidence comes from Vickers and Vertosick (2016), who collected 2,303 race performances from 304 recreational endurance runners and tested how well 5K, 10K, and half-marathon times predict marathon times. Their finding: marathon times were systematically slower than Riegel's prediction by an average of 4-5%, with much wider scatter than predictions at shorter distances. The longer the prediction jump, the worse the fit.

This is not a flaw in either formula. It reflects something real:

The honest takeaway: a race-time predictor tells you what is possible if you train. It does not tell you what you will run on race day. The gap between the two is closed by consistent marathon-specific training - typically 16-22 weeks, 50-70 km per week, long runs progressing to 28-32 km, with marathon-pace and threshold work in the final block. See our guides on how long marathon training takes and Pfitzinger vs Daniels vs Canova for what that actually looks like.

When to trust the prediction

The prediction is most reliable when:

The prediction is least reliable when:

Practical use

Use the prediction as a planning target, not a guarantee:

Frequently asked

How is this different from the VDOT calculator?

The VDOT calculator focuses on training paces (Easy, Marathon, Threshold, Interval, Repetition) derived from your fitness score. This page focuses on cross-distance race predictions and shows two methods side by side. The underlying Daniels math is identical; the framing and outputs differ.

Why does my marathon prediction differ between sites?

Almost every site uses one of three approaches: Riegel with exponent 1.06, Riegel with a tweaked exponent (often 1.08 for marathon predictions), or a Daniels-style VDOT model. Some calculators (McMillan, RunSMART) tune their tables on top of these formulas. Across calculators, expect ±3-5% spread on marathon predictions from the same 5K input.

Can I use this predictor for ultras?

No, neither model is reliable past the marathon. Ultra performance depends on factors (terrain, climbing, nutrition, sleep, fuelling strategy) that road race predictors do not model. Use ultra-specific calculators or coach guidance.

What if my input race was on a hilly course?

Subtract roughly 1-2% from your finish time for every 100m of climb on the course before plugging it in. Or trust the result and mentally add 2-3% back to the marathon prediction. The model assumes flat conditions.

How do I improve my predicted time?

The predictor is downstream of fitness, not the cause of it. To move the prediction, raise VDOT - which means consistent volume at Easy pace plus targeted weekly Threshold and Interval work. See what VDOT is and how training load drives fitness.

References

Turn this prediction into a real plan

Smart Runner takes one race result and builds an adaptive 16-22 week plan that progresses you toward your predicted time. 14-day free trial.

Get Smart Runner on the App Store