Race Time Predictor
Predict your finish time at every common distance — 1500 m to the marathon — from one recent race result, using the Riegel or Cameron model.
Inputs
Results
Based on 5 km in 25:00, your predicted time for 42.195 km is ....
| Target Distance (km) | Predicted Time (hrs:min:sec) | Predicted Pace (min:sec/km) |
|---|---|---|
Predicting a Race From Another Race
You ran a 10K in 45 minutes. What's a realistic marathon target? You set a 20-minute 5K — could you run a sub-90 half? Race-time prediction answers these questions by extrapolating from a known performance to a different distance. Enter one recent race result and this calculator returns a headline prediction for your target distance plus a table of predictions for every standard distance from 1500 m to the marathon, using either of two established models.
The Riegel Model
The most widely used formula is Riegel's (Pete Riegel, 1981). It observes that race time scales with distance raised to a power slightly above 1:
Take logs and it linearizes:
The exponent — standard value 1.06 — captures the empirical fact that you slow down a little for each doubling of distance. At $e = 1.06$, doubling the distance costs about 4.3% on pace (). An exponent of 1.0 would imply you can hold any pace for any distance (impossible); 1.20 would imply a much steeper drop than trained runners actually show.
Because the exponent is an empirical best-fit rather than a law of physiology, this calculator lets you adjust it. Lower it toward 1.03 if you are a speed-oriented runner whose pace holds up well over distance; raise it toward 1.10 if your endurance fades faster than average — research by Tanda and others suggests the marathon in particular is often better fit by an exponent above 1.06.
The Cameron Model
Riegel uses one exponent for all distances. Cameron's formula (David Cameron, 1998) instead uses a distance-dependent fatigue function, fitted to world-class results from 400 m to 50 miles:
with in metres. Because the fatigue term changes shape across distances, Cameron is often slightly more realistic at the long end, predicting marathon times a little slower than Riegel. Switch between the two models and compare: if they agree closely, the prediction is robust; if they diverge, the truth is usually somewhere between.
Examples
| Known | Time | Target | Riegel (1.06) | Cameron |
|---|---|---|---|---|
| 5K | 20:00 | 10K | 41:42 | 41:40 |
| 5K | 25:00 | Half marathon | 1:55:00 | 1:54:49 |
| 10K | 45:00 | Marathon | 3:27:01 | 3:30:14 |
| Half | 1:30:00 | Marathon | 3:07:39 | 3:10:11 |
The two models track closely at nearby distances and fan apart as the gap from the known race grows — exactly where a prediction is least certain anyway.
Practical Scenarios
1. Setting a Marathon Goal
A common rookie mistake is targeting a marathon time by simply doubling a recent half. Both models warn you off it: a 45-minute 10K predicts a ~3:27–3:30 marathon, not 3:00 (which would need a 37:30 10K). Many would-be sub-3 marathoners have a 10K time that quietly tells them the goal needs more training first.
2. Choosing a Pace Group
Race-day pace groups are offered at fixed intervals (3:30, 3:40, 3:50 marathon, etc.). Read your predicted time off the table and pick the group that matches it — not your aspirational time. When Riegel and Cameron straddle a boundary, the more cautious group is the safer start.
3. Comparing Distances Across Runners
Two friends ran different races: a 19:30 5K and a 1:30 half marathon. Who is faster? The all-distance table converts any result to a common basis — read the 5K runner's predicted half (or the half runner's predicted 5K) and compare directly.
4. Pacing a Track Event
The formulas also extrapolate down: a 16:00 5K predicts roughly a 4:28 1500 ma 16:00 5K predicts roughly a 4:49 mile. Track athletes use this to check that their endurance translates into race-distance speed.
Where Prediction Falls Short
- It assumes consistent training across distances. A runner who only trains 5Ks will under-perform the marathon prediction; long-run endurance is a separate adaptation.
- The models are empirical. Riegel's exponent and Cameron's fatigue function are regression fits, not derivations. Real marathon performance often lags both predictions for runners not specifically marathon-trained.
- They break at the extremes. Sub-1500 m sprintsSub-mile sprints and ultra-distances (50K+) follow different physiology and neither model extrapolates cleanly there.
- They cannot account for course profile, weather, or pacing. Predictions assume similar conditions; a flat fast 10K and a hilly windy marathon are not directly comparable.
For amateur runners targeting standard distances under similar conditions, race prediction is a useful planning tool — better than guessing — but treat the numbers as a ballpark, not a guarantee.
Frequently Asked Questions (FAQ)
What does the Riegel exponent 1.06 represent?
It is an empirical fitting parameter from Pete Riegel's 1981 analysis of competitive race results. The fact that 1.06 > 1.0 captures the reality that pace slows slightly as distance increases — about 4% per doubling of distance. The exponent is a regression best-fit, not a derivation from physiology, which is why this calculator lets you adjust it.
Should I use the Riegel or the Cameron model?
Riegel is the simplest and most widely cited model — one power law, easy to reason about, and adjustable via the exponent. Cameron’s formula uses a distance-dependent fatigue function fitted to elite results and is often slightly more realistic at the long end, predicting marathon times a touch slower than Riegel. Compare both: if they agree closely, the prediction is robust; if they diverge, the truth is usually somewhere between, and the longer your target relative to your known race, the more cautious estimate is the safer plan.
How accurate is the prediction for a marathon from a shorter race?
Both models tend to be optimistic at marathon distance for runners not specifically trained for it. A 45:00 10K predicts roughly a 3:27 marathon, but many runners with that 10K capability finish closer to 3:45–3:50 because marathon endurance is a separate adaptation. Treat marathon predictions as a ceiling, not a target.
Can I use this for ultra distances or sprints?
Not reliably. Both formulas were fit to mid-distance through marathon performances; they extrapolate poorly to sub-1500 m sprints (where physiology shifts to anaerobic) and to 50K+ ultras (where pacing strategy, terrain, and fuelling dominate the result more than aerobic capacity).
Not reliably. Both formulas were fit to mid-distance through marathon performances; they extrapolate poorly to sub-mile sprints (where physiology shifts to anaerobic) and to 50K+ ultras (where pacing strategy, terrain, and fuelling dominate the result more than aerobic capacity).
Disclaimer
Predictions assume comparable training, course, and weather conditions. Real race times depend on factors the formulas cannot model — terrain, heat, pacing strategy, fuelling, and event-specific preparation. Use the result as a planning estimate, not a guarantee.
Recommended Next
Running Pace Calculator
Solve for pace, time, or distance — enter any two and the calculator finds the third, with speed and a per-split table.