Race Time Predictor
Predict race times for different distances
🔒 Private · Method · · Disclaimer · Race Time Predictor
Working out how to predict race times for different distances is easier with Race Time Predictor, which answers as you type. Type Known Distance (km) and Known Time (min) into Race Time Predictor; each keystroke re-runs the math. The answer from Race Time Predictor arrives with its working attached. Use Race Time Predictor for a reliable number, fast. Nothing is uploaded while Race Time Predictor works, and the figures stay put. Race Time Predictor handles race time predictor the same way as free online race time predictor calculator — one of the Fitness & Exercise tools on CalcProMaster. Run Race Time Predictor twice to find the driving input. Race Time Predictor is free, instant and local.
What the defaults give
A 10 km in 55 minutes predicts 26 min for 5K, 55 min for 10K (the input itself), 121 min for a half and 253 min for a marathon.
The predictions widen as the distance grows: the marathon is 4.6 times the 10K time, not 4.2 times the distance.
The idea behind the model
Race times do not scale linearly with distance. Doubling the distance costs more than double the time, because fatigue accumulates faster than the distance does. The tool applies an endurance exponent to your known performance, so every predicted distance comes from one measured effort.
Worked examples
10 km in 55 min → 5K 26 min, half 121 min, marathon 253 min
5 km in 55 min → 5K 55 min, 10K 115 min, marathon 528 min
20 km in 55 min → 5K 13 min, marathon 121 min
10 km in 27.5 min → 5K 13 min, marathon 127 min
10 km in 110 min → 5K 53 min, marathon 506 min
The scale factor is what makes the table readable: 55 minutes over 10 km is exactly twice 27.5 minutes, and every prediction doubles with it. That linearity is a property of the model rather than of runners — in practice a runner who doubles their 10K time does not double their marathon time.
Where predictions go wrong
The biggest error comes from using a short race to predict a long one. Speed over 5K depends on VO2 max and running economy; a marathon depends on fat oxidation, fuelling and durability. A runner with a fast 5K and no long-run base will be predicted far too quickly over 42 km.
Enter a recent race, not a personal best from years ago, and enter a distance you actually raced. A training run time is not a race effort, and the model has no way to know the difference.
How to use it
Pick the prediction for a distance you are training for and treat it as a target, then check it against a longer race once you have one. If the marathon prediction is 4:13 but your longest run is 18 km, the gap is training, not talent.
Course and conditions move real times by minutes: heat of 25°C costs most runners 3–5% over a marathon, and a hilly course more. The model assumes flat, cool and well-fuelled.
Frequently Asked Questions
What does a 55-minute 10K predict for a marathon?
253 minutes, or 4:13. The model treats the marathon as 4.6 times the 10K time rather than 4.2 times the distance.
How accurate are race predictions?
Good within a training block, poor across distances far apart. A 5K is a reasonable predictor of a 10K and a weak one for a marathon.
Should I enter a training run or a race?
A race. Training paces are not maximal efforts, so a training time makes every prediction too slow.
What about hills and heat?
Not modelled. Heat of 25°C typically adds 3–5% to a marathon, and a hilly course adds more than the flat-distance equivalence suggests.
Why is the half marathon 121 minutes?
It is a little over twice the 10K time, which is the endurance penalty the model applies for doubling the distance.
Burpee Test Calculator and other Fitness tools
Burpee Test Calculator · Weekly Training Volume · Rowing Split Calculator · Max Heart Rate Calculator · Sports Calorie Calculator · Squat Standards by Body Weight · Fitness Guides