Running Pace Predictor Guide: Race Time Estimation Methods
Quick Answer
- *Riegel’s formula: T2 = T1 × (D2/D1)^1.06.
- *A 25-min 5K predicts roughly a 52-min 10K and 3:50 marathon.
- *VDOT (Jack Daniels) gives equivalent times AND training paces.
- *Predictions assume distance-specific training. Less accurate for untrained distances.
Riegel’s Formula
Peter Riegel published his race prediction formula in 1977, and it remains the most widely used method. The idea is simple: as race distance increases, pace slows in a predictable way due to fatigue.
T2 = T1 × (D2 / D1)^1.06
T1 = known race time, D1 = known distance, D2 = target distance. The exponent 1.06 represents the “fatigue factor.” It’s an average across distances and fitness levels. Elite runners may have a lower factor (1.04–1.05); recreational runners often have a higher one (1.07–1.10).
Sample Predictions
| 5K Time | 10K | Half Marathon | Marathon |
|---|---|---|---|
| 20:00 | 41:40 | 1:32:35 | 3:12:50 |
| 25:00 | 52:05 | 1:55:45 | 4:01:05 |
| 30:00 | 62:30 | 2:18:55 | 4:49:20 |
| 35:00 | 72:55 | 2:42:05 | 5:37:35 |
Jack Daniels’ VDOT
VDOT goes beyond predictions. Jack Daniels’ system assigns a single fitness number based on a recent race result, then provides equivalent performances at every distance and specific training paces for five intensity zones.
The five training zones: Easy (E), Marathon (M), Threshold/Tempo (T), Interval (I), and Repetition (R). Each serves a different physiological purpose. Easy runs build aerobic base. Tempo runs push lactate threshold. Intervals develop VO2max. Most runners run their easy days too fast and their hard days too slow.
Why Predictions Break Down
The marathon multiplier problem: Predicting a marathon from a 5K is notoriously unreliable. The marathon introduces glycogen depletion (“the wall” at mile 18–22), which doesn’t factor into shorter races. A runner who can hit their predicted 10K time might miss their predicted marathon by 15–30 minutes without proper long-run training.
Course and conditions: Predictions assume flat courses and mild weather. Hills, wind, heat, and altitude all slow you down. Heat alone can add 1–3% per 5°F above 55°F. Altitude above 5,000 feet reduces performance by 3–8%.
Using Predictions for Race Strategy
The best use of pace prediction isn’t setting a goal time — it’s preventing you from starting too fast. Most amateur runners go out 10–20 seconds per mile too fast in the first half and pay for it dearly in the second half.
Use your predicted pace as an upper limit for the first half. Aim for even splits (same pace throughout) or slight negative splits (second half slightly faster). If your predicted marathon pace is 9:00/mile, run the first half at 9:05–9:10 and have something left for the finish.
Predict your race times from any recent result
Use our free Running Pace Predictor →Frequently Asked Questions
How do race time predictors work?
Most use Riegel’s formula: T2 = T1 × (D2/D1)^1.06. It extrapolates from a known race time using a fatigue exponent. Assumes equal fitness and training for both distances.
What is VDOT in running?
A fitness value from Jack Daniels’ system based on VO2max adjusted for running economy. It provides equivalent race performances and specific training paces across five intensity zones.
Why are predictions less accurate for longer distances?
Glycogen depletion, heat management, fueling, and distance-specific training matter more at longer distances. A fast 5K runner without marathon training will underperform predictions.
How do I calculate my pace per mile?
Divide total time by distance. A 25:00 5K: 25 ÷ 3.1 = 8:04/mile. A 4:00 marathon: 240 ÷ 26.2 = 9:10/mile.
What training paces should I run?
Easy: 1–2 min/mile slower than 5K pace (80% of mileage). Tempo: ~10K to half-marathon pace. Intervals: 3K–5K pace. Most runners go too fast on easy days and too slow on hard days.