About the Race Time Predictor
The Race Time Predictor estimates how long it would take you to finish a longer or shorter race distance based on a recent race result you already have. Rather than assuming pace stays constant across distances, it uses a well-established endurance-fatigue adjustment so predictions for distances like a marathon read more realistic than a simple linear scale-up from a 10K or half marathon time.
How It Works
You enter a known race distance in miles, the time it took to complete it in minutes, and the target distance you want a prediction for. The calculator scales your known time by the ratio of target distance to known distance, raised to an exponent that accounts for runners naturally slowing down over longer distances. The predicted time is then broken into hours, minutes, and seconds.
Formula & Methodology
The exponent 1.06 is what separates this from a naive linear pace projection. If pace scaled perfectly linearly with distance, doubling the distance would exactly double the time, equivalent to raising the distance ratio to the power of 1. Riegel's formula instead raises the ratio to 1.06, adding a small but compounding fatigue penalty that grows with the size of the distance jump.
Examples
10K to marathon prediction
A runner who completed a 6.2-mile (10K) race in 50 minutes wants a marathon (26.2-mile) prediction: 50 x (26.2 / 6.2)^1.06 works out to approximately 230 minutes, or about 3 hours 50 minutes 22 seconds.
Half marathon to 10K prediction
A runner with a half marathon (13.1-mile) time of 105 minutes predicts a 10K (6.2-mile) time: 105 x (6.2 / 13.1)^1.06 comes out to roughly 47.5 minutes, or about 47 minutes 31 seconds.
Advantages
- Uses a widely recognized formula (Riegel's) rather than a simplistic linear pace scale-up, producing more realistic longer-distance predictions.
- Works for any distance pair, not just standard race lengths, since both known and target distances are free-entry fields.
- Gives an immediate finish-time estimate in a readable hours-minutes-seconds format for race planning.
Common Mistakes
- Predicting a marathon from a very short known distance like a 5K, which stretches the formula beyond the distance range where it tends to be most accurate.
- Using a known race time from a poorly paced or undertrained effort, then treating the target-distance prediction as reliable despite that flawed input.
- Ignoring that the formula assumes similar race conditions and training state between the known result and the target race, when heat, hills, or reduced training can widen the gap.
Edge Cases to Watch For
- The formula becomes less reliable the further apart the known and target distances are, so predicting a marathon from a 5K result carries more uncertainty than predicting a half marathon from a 10K.
- It assumes the known race time reflects a genuine, well-paced effort; an underperformed or overperformed known result skews the prediction in the same direction.
- The formula has no awareness of course terrain, weather, or pacing strategy differences between the known race and the target race, both of which affect real-world finish times independent of endurance scaling alone.
Common Use Cases
- Runners setting a goal pace for an upcoming marathon or half marathon based on a recent shorter tune-up race.
- Coaches estimating athlete readiness for a longer target race distance using existing race data.
- Recreational racers curious how a personal best at one distance translates to an equivalent effort at another.