Race Time Predictor Calculator
Race Time Predictor
This calculator predicts your race time for any distance from a time you have actually run. Enter a recent result — a 5K you raced last month, a half marathon from the spring — and it estimates what you could run at another distance, using the same underlying fitness.
The prediction is built on the Riegel formula, a widely used model that relates times across distances: as the distance grows, your time grows slightly faster than the distance ratio, because endurance (not just speed) becomes the limiting factor[wikipedia-riegel]. A runner who can do 25:00 for a 5K is not predicted to do exactly 50:00 for a 10K — the formula says a bit more, around 52:00, because the 10K tests endurance the 5K does not.
This is the inverse of the Marathon Time Calculator: that tool turns a target pace into a finish time; this one turns an actual result into equivalent results at other distances. The two work together — the predictor tells you what to target, the pace calculator tells you what pace to hold.
- Select your known race distance from the dropdown — the race you have actually run recently.
- Enter your time for that race (hours, minutes, seconds).
- Select the target distance — what you want to predict.
- The calculator updates instantly with your predicted time, the equivalent pace in min/km and min/mile, and the source race you entered.
For best results, use a recent, genuinely hard effort — a race or a full-out time trial, not an easy training run. A time you could have beaten by a minute is not a reliable input. If you have run several distances recently, use the longest one, because it carries the most endurance information.
Riegel's formula predicts the time at a new distance from the time at a known distance:
Where is your known time, is the known distance, is the target distance, and is the predicted time. The exponent captures the endurance cost of running farther: doubling the distance multiplies the time by about , slightly more than double.
The formula is a power law, which means it is linear in log-space — on a log-log plot of time versus distance, your performances should fall on a straight line. That is why equivalent-performance tables work at all: most runners' times across distances lie close to a smooth curve, and Riegel's 1.06 exponent is the slope of that curve fitted to real race data[wikipedia-running].
A worked example: a 25:00 5K (1500 seconds) predicting a 10K:
And predicting a marathon from the same 5K:
The 5K predicts a ~3:59 marathon — a reasonable but demanding projection, because the formula assumes your endurance scales with the exponent. Runners who have not trained for the distance will run slower than the prediction; the formula is an upper bound on what the same fitness can do.
The 1.06 in Riegel's formula is not arbitrary — it encodes something real about how running changes with distance. If humans were purely aerobic machines, doubling the distance would exactly double the time. They are not, for two compounding reasons[wikipedia-running].
First, energy systems blend. At 5K pace, your body already relies partly on anaerobic energy, which is powerful but unsustainable. At marathon pace, the effort must stay comfortably within aerobic capacity, because running anaerobically for two hours is impossible. The longer the race, the smaller the fraction of VO₂ max you can actually hold, and the exponent captures that decline.
Second, efficiency degrades with fatigue. Over 42 kilometers, glycogen depletes, form breaks down, and the effort per kilometer rises even at a constant heart rate. The exponent is the statistical average of all these effects across thousands of runners: a 1.06 means a 10% distance increase demands roughly a 6.4% time increase, and a doubling demands about 8% more than double.
The exponent also explains why equivalent-performance tables are roughly consistent across athletes. Different runners have slightly different exponents — a speed-focused runner might sit near 1.05, an endurance specialist near 1.08 — but the differences are small enough that a single exponent predicts most runners within a few percent. That consistency is what makes the tool useful at all: it is not a guess, it is the fitted shape of how running actually scales[mcmillan].
The table shows predicted times across distances for a range of common results, using the Riegel formula:
| Your 5K | Predicted 10K | Predicted Half | Predicted Marathon |
|---|---|---|---|
| 20:00 | 41:42 | 1:32:00 | 3:11:49 |
| 22:00 | 45:52 | 1:41:12 | 3:31:00 |
| 25:00 | 52:07 | 1:55:00 | 3:59:47 |
| 28:00 | 58:23 | 2:08:48 | 4:28:33 |
| 30:00 | 1:02:33 | 2:18:00 | 4:47:44 |
Two patterns worth noticing. First, the 10K prediction is slightly more than double the 5K — the 2.08 multiplier, not 2.0, is the endurance tax. Second, the marathon prediction is roughly nine to ten times the 5K, far more than the distance ratio (8.44×), because the marathon's endurance demands compound. This is why marathoners train long runs specifically: the prediction is only as good as your endurance base[mcmillan].
The Riegel formula works well when the assumptions hold, and fails predictably when they do not. It is reliable when your input is a recent, genuinely hard effort, and your training includes enough distance to support the target (for a marathon, the long runs). Under those conditions, the prediction is typically within a few percent of what you can run.
The prediction overestimates (gives times too fast) when:
- Your input is from a shorter race and you have not trained for the longer distance. A 5K runner with no long runs will not hit the predicted marathon.
- The target distance is much longer than anything in your training. The formula assumes endurance scales smoothly, but it does not.
- Conditions on the target race day are worse (heat, hills, wind) than your input race.
The prediction underestimates (gives times too slow) when:
- You are early in a training block — the formula uses current fitness, not the fitness you will have on race day after months of training.
- Your input race was run conservatively. Use your best recent effort, not a cautious one.
The practical rule: treat the prediction as a range, not a promise. Round it to the nearest minute for your A-goal, add a few minutes for your realistic B-goal, and keep a finish-upright C-goal. The predictor sets the target; training decides whether you reach it[runnersworld-predictor].
The reason a 5K can predict a marathon at all is that both distances run on the same engine: aerobic capacity (VO₂ max) and the endurance that lets you hold a fraction of it for longer. The Riegel exponent is a statistical average of how that fraction declines with distance for real runners[wikipedia-vo2].
This is why the prediction is more reliable when your distances agree. If your 5K, 10K, and half-marathon times all map to the same marathon projection, the projection is credible — your fitness transfers smoothly across distances. If they disagree wildly — a fast 5K but a slow half — the gap is your endurance, and the marathon prediction should lean on the longer race. The VO2 Max Calculator estimates the aerobic engine underneath, and the Running Pace Calculator converts any predicted time into the paces you need for training.
- Use your best recent effort, not your best ever. An old PR from a different fitness level will mislead. The formula predicts from now.
- Lean on the longest race you have. It carries the most endurance information and gives the most honest marathon projection.
- Expect more than double for double distance. The 2.08× 5K-to-10K multiplier and the ~9-10× 5K-to-marathon factor are the endurance taxes. Underestimating them is how runners blow up on race day.
- Correct for course and conditions. Hilly, hot, or windy races slow you; adjust the prediction down (slower) for those.
- Set a goal range, not a single number. A-goal (optimistic), B-goal (realistic), C-goal (finish) — the predictor informs all three.
- Re-predict as you train. Use it at the start of a block, then again after eight weeks; the improvement in the projection is the clearest sign training is working.
- Verify with the Running Pace Calculator once you have your target time, to get the exact pace to hold.
Race-time prediction is an estimate, not a measurement. The Riegel exponent (1.06) is an average across runners; individuals differ, and your own exponent may be higher (if you are endurance-strong) or lower (if you are speed-strong). The formula assumes smooth aerobic scaling, which fails for runners who lack the specific training for the target distance. It says nothing about weather, course profile, or race-day execution, any of which can swing the result by minutes. And the input matters as much as the formula: a soft or short effort produces a prediction that flatters. Use the number to plan and to track improvement, not as a guarantee — the only true prediction is the race itself.
- ❓ What is a race time predictor?
- ✅ A tool that estimates your time at one race distance from your actual time at another, using the Riegel formula (T2 = T1 × (D2/D1)^1.06). It assumes the same underlying fitness across distances.
- ❓ How does the Riegel formula work?
- ✅ It multiplies your known time by the distance ratio raised to the 1.06 power. Doubling the distance multiplies the time by about 2.08, capturing the endurance cost of running farther.
- ❓ Can I predict my marathon time from a 5K?
- ✅ Yes — the 5K predicts roughly 9-10 times its own time as a marathon (a 25:00 5K predicts about 3:59). The projection assumes you have trained for the distance; without long runs you will run slower.
- ❓ Is the prediction accurate?
- ✅ Within a few percent when your input is a recent hard effort and your training supports the target distance. It overestimates for runners untrained for the longer distance and under-estimates early in a training block.
- ❓ What distance should I use as my input?
- ✅ Your most recent, genuinely hard race — preferably the longest one, since it carries the most endurance information and gives the most honest projection for longer distances.
- ❓ Why is my 10K predicted time more than double my 5K?
- ✅ Because endurance, not just speed, limits longer distances. Riegel's 1.06 exponent makes the 10K about 2.08 times the 5K, and the marathon 9-10 times — the endurance taxes.
- ❓ How do I turn a predicted time into training paces?
- ✅ Use the predicted time with the Running Pace Calculator to get the min/km or min/mile pace, then build training around it. The VO2 Max Calculator estimates the aerobic engine that sets the ceiling.
- ❓ What if my races don't agree with the prediction?
- ✅ A fast 5K with a slow half-marathon points to an endurance gap. Lean on the longer race for marathon planning and add long-run training to close the gap between your predictions.
References
Last updated: August 15, 2026
UnByte — Independent Software Engineering
Every calculator references authoritative sources — Editorial policy
