| Distance | Riegel | Cameron | Goal Pace (Riegel) |
|---|
Riegel uses a fixed 1.06 fade exponent (1.05/1.10 for the marathon depending on experience). Cameron uses a variable exponent that decays with input distance, which is more accurate for long extrapolations. Predictions assume race-specific training and similar conditions.
How Race Time Prediction Works
Every race time predictor relies on a simple insight: as race distance grows, average pace slows in a predictable way. A 5K is run at a pace your aerobic system can hold for roughly 15-30 minutes; a marathon must be paced for 2-5+ hours. Your body's ability to hold pace fades because lactate, glycogen depletion, fatigue, and thermoregulation all compound over time.
A race time predictor models that fade with a power law. Plug in a known race time, and the calculator scales the pace upward based on the distance ratio. The most reliable models — Riegel, Cameron, and Daniels' VDOT tables — all agree on the shape of the curve and disagree only on how quickly pace fades. The Running Genie predictor shows two of the most respected formulas side by side, so you can sanity-check predictions before locking in a race goal.
What goes into a prediction
- Input distance and time: the more recent and well-paced the race, the better the prediction.
- Distance ratio: how far you are extrapolating. A 5K to 10K prediction is far more reliable than a 5K to marathon prediction.
- Fade exponent: how quickly pace decays with distance. Faster runners and well-trained runners fade less.
- Training specificity: a marathon prediction assumes you have done the long runs. Without them, the prediction is a fitness ceiling, not a forecast.
The Riegel Formula Explained
Pete Riegel published his race time prediction formula in Runner's World in 1977 and refined it in 1981. It is the most widely used race predictor in the world. The formula:
T2 = T1 × (D2 / D1)1.06
- T1 — your known race time (in seconds)
- D1 — the distance of that race
- D2 — the distance you want to predict
- 1.06 — the fade exponent (Riegel's empirically derived constant)
The exponent 1.06 was derived from analyzing world-class race performances at every distance from 800m to the marathon. It is essentially a constant for trained runners. If the fade exponent were exactly 1.0, your pace would never slow — which is obviously false. The 0.06 above 1.0 is the small but compounding penalty for going farther.
Quick example: a 20:00 5K predicts a 10K of 20 × (10/5)1.06 = 20 × 2.0852 ≈ 41:42. A 1:30:00 half marathon predicts a marathon of 90 × (42.195/21.0975)1.06 ≈ 187 minutes ≈ 3:07.
The Cameron Formula — More Accurate for Long Extrapolations
David Cameron proposed a refinement in 1998 that addresses Riegel's main weakness: a fixed 1.06 exponent over-predicts for elite runners and under-predicts for slower runners. The Cameron formula uses an exponent that varies with the input race distance. The Running Genie predictor uses an approximation in this form:
T2 = T1 × (D2 / D1)(1.06 − 0.0026 × D1mi)
The longer your input race, the lower the fade exponent — which mirrors what we see in real races. The Cameron formula tends to be 1-3% closer to actual marathon times than Riegel when extrapolating from a 5K or 10K. For predictions between similar distances (say, 10K to half marathon), Riegel and Cameron usually agree within seconds.
Why Marathon Predictions Are Less Accurate
Predicting a marathon time from a 5K or 10K is the hardest job for any race time predictor. A 5K is a pure aerobic-power test — fitness in, time out. A marathon is fitness, fueling, pacing discipline, mental toughness, weather, and 20+ miles of muscular endurance all compounded together. Even with a perfect formula, four big things degrade the prediction:
- Detraining of long-run endurance. A runner with a fast 5K but no recent long runs will fade hard after 18-20 miles. The predictor assumes you have done the work.
- Fueling and hydration errors. Bonking, GI distress, or dehydration can cost 5-15 minutes in a marathon — none of which a predictor can anticipate.
- The wall. Glycogen depletion typically hits between mile 18 and 22. Runners new to the distance often slow by 30-90 seconds per mile in the final 10K.
- Pace drift. Even small mistakes in early-race pacing — going out 10 seconds per mile too fast — get magnified across 26.2 miles.
This is why The Running Genie predictor offers a beginner / intermediate / advanced toggle that adjusts the marathon fade exponent. If you have run only a handful of marathons or none at all, choose beginner — your marathon time will be slower than the textbook formula predicts, because the wall hits harder.
How to Make Your Prediction More Accurate
Race time prediction is a fitness ceiling, not a guarantee. To close the gap between predicted and actual:
- Train at race-specific paces. If you want to run a 3:30 marathon (8:00 pace), do at least one long run with 8-12 miles at goal marathon pace.
- Build the long run. Marathon predictions assume you have peaked at 18-22 mile long runs. Without them, expect to slow by a minute or more per mile in the last 10K.
- Taper properly. A good 2-3 week taper can be worth 2-5% on race day; a missed taper costs the same.
- Account for race-day conditions. Headwinds, heat above 60°F, hills, and altitude all degrade race times. As a rule of thumb, expect to lose 1-2% per 5°F above 60°F.
- Use multiple input races. Predict from a recent 5K, 10K, and half — if all three agree, the prediction is solid. If they disagree, your fitness is improving (or fading) quickly.
- Practice race-day fueling. A marathon prediction assumes you take in 30-60g of carbs per hour. Practice it on every long run.
From 5K to Marathon: Prediction Accuracy
The accuracy of race time prediction degrades with distance for one simple reason: a marathon is 8.4 times longer than a 5K, and the formula has to extrapolate over that entire span. Here is roughly how reliable each prediction is, assuming consistent training:
- 5K → 10K: typically within 30-60 seconds. Very reliable for trained runners.
- 5K → half marathon: typically within 1-3 minutes. Reliable if you have logged at least one long run of 12+ miles.
- 5K → marathon: typically within 5-15 minutes for experienced runners; can be off by 30+ minutes for runners without long-run endurance.
- 10K → half marathon: typically within 1-2 minutes. Among the most reliable predictions in running.
- 10K → marathon: typically within 4-10 minutes for experienced marathoners.
- Half → marathon: typically within 2-6 minutes. Often the best baseline for a marathon goal.
If you want a single best practice: use a recent half marathon to predict your marathon. The half is long enough that aerobic endurance, fueling, and pacing discipline are all on display, but not so long that one bad day skews the result.
Train for Your Predicted Time
A predictor tells you what's possible. The Running Genie builds the adaptive 16-week plan that turns a prediction into a finish line. Personalized paces, smart taper, race-day fueling — download free.
Related Calculators
Race Time Predictor FAQ
How accurate is a race time predictor?
A race time predictor is most accurate when extrapolating between similar distances — for example 5K to 10K, or 10K to half marathon, where predictions typically fall within 1-3% of actual race time. Predictions become less accurate as the distance gap widens, especially when projecting from a 5K to a marathon, because endurance and fueling start to dominate over pure aerobic speed.
What is the Riegel formula?
The Riegel formula is T2 = T1 × (D2/D1)1.06, where T1 is your known time at distance D1 and T2 is the predicted time at the new distance D2. The exponent 1.06 represents how much pace fades as distance increases. Pete Riegel published the formula in 1977 and refined it in 1981; it remains the most widely used race time predictor in the world.
Riegel vs Cameron formula — which is more accurate?
The Cameron formula uses a variable exponent that accounts for the original race distance, which makes it more accurate when extrapolating across very different distances (for example a 5K to a marathon). The Riegel formula is simpler and excellent for nearby distances. The Running Genie shows both side by side so you can compare and choose the more conservative goal.
How do I predict a marathon time from a half marathon?
Multiply your half marathon time by approximately 2.11 (the Riegel approximation, 2 × 20.06) for a rough estimate. A more reliable approach: use a recent half marathon as input, then verify with a 16-22 mile long run at goal marathon pace. Beginners should add 5-10% to the predicted marathon time, because the wall and fueling errors hit harder for runners new to the distance.
Should beginners and advanced runners use different predictions?
Yes. Beginners typically fade more than the Riegel exponent suggests, especially in the marathon. The Running Genie predictor offers an experience selector — beginner runners use a 1.10 fade exponent for the marathon prediction, intermediate runners use 1.06, and advanced runners use 1.05. Choose the one that matches your training history and marathon experience.
Can I use treadmill times in the race time predictor?
Treadmill times tend to be slightly faster than equivalent road times because there is no wind resistance and the belt assists turnover. To convert, set your treadmill at a 1% incline during the run. If your time was at 0% incline, add roughly 1-2% to your treadmill time before plugging it into the predictor for a more realistic outdoor estimate.
Does altitude affect race time predictions?
Yes. At elevations above ~1000 meters (3300 ft), aerobic performance drops by roughly 1-2% per 300m of additional altitude. If your input race was at altitude and your goal race is at sea level, the predictor will under-call your sea-level potential. The reverse is also true — sea-level predictions are optimistic for high-altitude races.
How does VDOT relate to race prediction?
VDOT is Jack Daniels' single-number expression of running fitness based on race performance. Two runners with the same VDOT should — in theory — run similar times across all race distances. The Running Genie predictor estimates your implied VDOT from your input time and uses that to suggest training paces and goal race paces across every distance.
Why does my marathon prediction look too fast?
If you are predicting a marathon from a 5K or 10K, the formula assumes you have done the long-run training to actually hold pace for 26.2 miles. Without consistent 18-22 mile long runs, marathon-pace work, and a fueling strategy, the marathon prediction will be optimistic by 5-15%. Train the gap — The Running Genie app builds the adaptive plan that closes it.
How often should I re-run the predictor?
Update your prediction after every race or hard time trial — typically every 4-8 weeks during a training cycle. If your VDOT or predicted times jump by more than 1.5 points in a month, your training is working and you can recalibrate goal paces. If predictions fall, dial back volume or intensity for a recovery week.
Train for Your Predicted Time with The Running Genie
Once you know what you can run, the next step is training to actually run it. The Running Genie builds personalized, adaptive training plans for every distance — from 5K to ultra — with paces tuned to your VDOT and a smart taper that gets you to the start line fresh.