Race Time Predictor
Last updated: 5 July 2026
Reviewed by Gavin Meiring, Lead research and primary author ยท Doctoral Candidate (Corporate Governance) ยท Research and drafting assisted by AI
- Most race-time predictors use the Riegel formula, published by engineer Peter Riegel in 'Runner's World' in 1977 โ it is based on the observation that fatigue slows you by a predictable power of distance.
- The relationship between running speed and race distance was first studied scientifically in 1925 by A.V. Hill โ the same physiologist who proposed the concept of VO2 max.
- Predictions are only estimates: Paula Radcliffe's marathon world record of 2:15:25 (2003) stood for 20 years until Tigst Assefa ran 2:11:53 in 2023, and Ruth Chepngetich then became the first woman under 2:10 with 2:09:56 in Chicago in 2024.
Race Time Predictor
A race time predictor works out estimated finish times for various race distances based on a known race performance, using physiological models that account for endurance-specific fatigue. It is used by recreational and competitive runners planning race calendars, coaches pacing athletes across training cycles, and fitness enthusiasts setting realistic goals.
The most widely used formula is Riegel's formula: T2 = T1 x (D2 / D1)^1.06, where T1 is the known time and D1 is the known distance. The exponent 1.06 was derived from Peter Riegel's 1977 research on running performance and has been validated across millions of athlete performances. Lower exponents (1.02-1.04) suit more elite athletes; higher exponents (1.08-1.10) suit beginners.
How to Use the Race Time Predictor
- Enter your recent race time and distance (e.g., 23:45 for a 5K, or 1:42:30 for a half marathon).
- Select the exponent (1.06 is the default for most adult runners).
- The calculator predicts finish times for 5K, 10K, half marathon, marathon, and any other distance.
- It also computes equivalent paces (per km and per mile) for each predicted distance.
- Optionally, input a target time for a future race to back-calculate the required training pace.
The Formula (Riegel's)
T2 = T1 x (D2 / D1)^1.06
Where:
- T1 = Known race time (any time unit, consistent with T2)
- D1 = Known race distance (any distance unit, consistent with D2)
- D2 = Target race distance
- T2 = Predicted time for target distance
- Exponent 1.06 = average for adult runners
The formula is most accurate for races between 5K and marathon. For shorter distances (800m, 1500m) or ultra-marathons, the predictions are less accurate without adjusting the exponent.
Why the Formula Isn't Perfect
Riegel's formula assumes a constant relationship between pace and distance, but real physiology is more complex:
- Trained runners have lower exponents (1.03-1.05) because their bodies are more efficient at sustained effort
- Beginner runners have higher exponents (1.08-1.12) because they slow down more as distance increases
- Hot weather, hills, and fatigue all increase the effective exponent
- Elite marathoners approach the theoretical 1.0 exponent (a tiny slowdown from 5K to marathon pace)
For more accurate predictions, use the Riegel formula with an exponent calibrated to your training history. Race 5K and 10K events of similar conditions, then calculate: Exponent = log(T10K / T5K) / log(2).
Equivalent Pace Tables
For a runner with a 20:00 5K time (4:00/km pace), the Riegel formula predicts:
- 10K: ~41:34 (4:09/km)
- Half marathon: ~1:31:12 (4:19/km)
- Marathon: ~3:08:42 (4:28/km)
The slowdown per km increases as distance increases, this is "cardiac drift" plus glycogen depletion plus accumulated muscular fatigue. Beginner runners see larger drift; elite runners see less.
Frequently Asked Questions
Are race time predictors accurate? Riegel's formula is accurate to within 2-5% for trained recreational runners, but the accuracy degrades for extreme distances (800m or 100K) and for runners with atypical physiology. The best use of race predictors is for setting realistic pace targets, not for predicting exact finish times. Use the predictions as a starting point and adjust based on training and conditions.
Why do my predicted times not match my actual race times? Common reasons predictions are off: the prediction assumes optimal conditions (cool weather, flat course, no wind), you didn't pace the source race evenly, you were undertrained or overtrained for the source race, or the source race had unusual conditions. Predictions are most accurate for runners who train consistently and pace evenly.
What exponent should I use? The default 1.06 works for most adult recreational runners. Adjust based on your own data: if your 10K is slower than the 1.06 prediction, your effective exponent is higher (you're a beginner; try 1.08). If your 10K is faster than the prediction, your exponent is lower (you're trained; try 1.04). Elite marathoners use 1.03-1.05.
Can I predict my marathon time from a half marathon? Yes, and this is one of the more accurate Riegel applications. A 1:30 half marathon typically predicts a 3:08-3:12 marathon. The Riegel formula is particularly good for races 5K to marathon because endurance running has well-understood physiology in this range. For ultramarathons (50K+), the formula breaks down and other models (like Cameron-Baker) are more accurate.
Should I use my best time or my most recent time? Use your most recent equivalent race if possible, because training adaptations over time change your effective fitness. A 5K from 6 months ago may not represent your current fitness. If you only have one race at a specific distance, use it but account for any training changes since then.
How does elevation affect race time predictions? Significant elevation gain (1,000+ feet) slows runners by 10-30 seconds per mile, with the exact effect depending on the runner's hill strength and pacing. Riegel's formula assumes flat courses. For hilly races, subtract 30-90 seconds per mile from your predicted flat time depending on the elevation profile. Boston Marathon runners, for example, deal with significant net downhill which can produce faster times than Riegel predicts. The Boston Marathon typically produces 1-3% faster times than equivalent flat marathons due to the net downhill. Steep uphills slow times more than moderate downhills speed them up, a 5% grade uphill adds about 30 seconds per mile, while a 5% grade downhill saves only 12-15 seconds per mile. Trail races with significant technical terrain (rocks, roots, mud) slow times further, 30-60 seconds per mile additional, because stride length and cadence decrease on uneven surfaces. Use a course-specific calculator (like the ones at Runner's World or McMillan Running) for any race where you have a detailed elevation profile.
Should I taper before a predicted race time? The Riegel prediction assumes peak fitness on race day. Most training plans include a 2-3 week taper before goal races, reducing volume 20-40% while maintaining intensity, to allow recovery and peak performance. A tapered runner typically runs 1-3% faster than their training times suggest, with first-time marathoners seeing larger improvements than experienced marathoners. For a goal race, predict your time using a recent race (not training) performance, ideally from 4-8 weeks before the goal race, then add 1-2 minutes of buffer for the final taper. Running the predicted time on race day is the goal; the prediction gives you a pacing target. Start at the predicted pace and adjust based on how you feel in the first 1-2 miles.
Inputs and Their Effects
Each field on the Race Time Predictor form plays a distinct part in the calculation.
- your recent race time and distance (e.g., 23:45 for a 5K, or 1:42:30 for a half marathon) - this value feeds the Race Time Predictor directly and shows up in the result.
- the exponent (1.06 is the default for most adult runners) - this value feeds the Race Time Predictor directly and shows up in the result.
- calculator predicts finish times for 5K, 10K, half marathon, marathon, and any other distance - this value feeds the Race Time Predictor directly and shows up in the result. Editing one field of the Race Time Predictor changes the output in line with the formula, so a misplaced value is visible in the answer.
Common Mistakes to Avoid
The errors that come up most often with the Race Time Predictor are easy to spot once you know them:
- Entering a value in the wrong unit for your recent race time and distance (e.g., 23:45 for a 5K, or 1:42:30 for a half marathon); the Race Time Predictor answer is only right when the unit matches the label.
- Mixing conventions, such as percentages and decimals, where the Race Time Predictor formula expects one form.
- Rounding the inputs before the Race Time Predictor runs; keep the full values and let the tool round the final answer.
- Treating the Race Time Predictor result as exact when the inputs themselves were estimates.
When to Use the Race Time Predictor
Use the Race Time Predictor whenever you need a quick, reliable answer that fits the tool's scope. Common situations for the Race Time Predictor include homework and study, on-the-job quick checks, sanity-checking a more complex calculation, or exploring a scenario for personal interest. If the Race Time Predictor answer will be used for a decision that has legal, medical, or financial consequences, treat the result as a starting point and verify it with a qualified professional.
How the Math Works
The calculation behind the Race Time Predictor follows the standard form for this kind of problem: T2 = T1 x (D2 / D1)^1.06 Where: T1 = Known race time (any time unit, consistent with T2) D1 = Known race distance (any distance unit, consistent with D2) D2 = Target race distance T2 = Predicted time for target distance Exponent 1.06 = aver The Race Time Predictor applies that relationship in the order the algebra prescribes, converting inputs to consistent units first where the formula needs them.
Related Concepts and Where This Fits
The Race Time Predictor fits alongside the other tools in its category, and the choice between them usually comes down to which inputs you already have. If the same numbers feed several tools, run them in one pass so the assumptions stay consistent across the comparison, which is where the Race Time Predictor earns its place.
Worked Examples
A typical Race Time Predictor run takes reasonable inputs, produces a sensible answer, and returns it in a single click. Example: Beyond the worked examples earlier in this page, a few additional cases illustrate how the Race Time Predictor behaves at the edges of its input range. Boundary inputs. Entering the smallest sensible value or the largest sensible value for a numeric input should produce a result at the corresponding end of the output range, not a runaway value or a silently clipped
References
- Riegel, P. S. (1981), Athletic Records and Human Endurance, American Scientist 69(3): 285, the original endurance-curve formula. https://www.jstor.org/stable/27850506
- Runner's World, Race Time Prediction, the practical application of Riegel's formula. https://www.runnersworld.com/tools/race-time-predictor