Running Pace Predictor

How Race Time Prediction Works

The Riegel model

Peter Riegel, an engineer and runner, published his endurance formula in 1977: time scales with distance raised to the power 1.06. That exponent captures how pace inevitably slows as distance grows — about 5–6% per doubling for trained runners. Fifty years on, it remains the backbone of most race-prediction tools because it's remarkably accurate between 1,500 m and the half marathon for runners with appropriate training.

Where predictions break down

The marathon is the model's weak spot. Riegel assumes fatigue accumulates smoothly, but the marathon adds a discrete event — glycogen depletion around mile 18–20 — that shorter races never touch. Runners averaging under 40 miles/week typically finish 5–8% slower than their Riegel projection. Heat, hills, and crowded starts add further drift. Elite runners with 100-mile weeks routinely beat the formula; first-timers rarely do.

Using predictions to set training paces

The prediction's best use isn't race-day fantasy — it's calibrating workouts. Your predicted 10K pace approximates threshold effort; predicted marathon pace sets long-run quality segments. Training at paces your current fitness supports, rather than paces you wish you had, is the single most protective habit against injury and burnout in recreational running.

Predicted times across distances: a reference grid

Enter one race above and the Riegel formula projects the rest. This grid shows the pattern for common 5K times, so you can sanity-check a prediction or set a target. Read across from your 5K to see what equivalent fitness looks like at longer distances — assuming you've trained appropriately for them.

The marathon column carries the biggest asterisk. These projections assume marathon-specific endurance — the long runs that teach your body to burn fat and spare glycogen past mile 18. Without that training, real marathon times land 10–20 minutes slower than the grid, no matter how fast your 5K. Treat the 10K and half columns as reliable; treat the marathon as a best-case ceiling.

Common mistakes in reading a race prediction

• Predicting the marathon from a 5K. The distance gap is too large — the marathon adds glycogen depletion that shorter races never test. Use the longest race you've run for the most trustworthy projection.
• Using a time trial instead of a race. Competition extracts 1–2% more than a solo effort. A predicted time built on a lonely tempo run will overestimate what race-day adrenaline can't fully close.
• Ignoring conditions. Heat, humidity, hills, and wind can add minutes. A prediction from a cool, flat PR won't hold on a hot, hilly course.
• Racing at predicted pace without building up. The prediction reflects fitness, not readiness. Attempting predicted marathon pace off low mileage is how runners blow up at mile 20.

The history behind the 1.06 exponent

Peter Riegel, a mechanical engineer and marathoner, published his endurance formula in a 1977 article and refined it in 1981: race time scales with distance raised to the power 1.06. That exponent isn't arbitrary — it was fitted to real race data and captures the roughly 5–6% pace slowdown per doubling of distance that trained runners experience. Nearly five decades later it remains the backbone of race predictors because it's remarkably accurate between about 1,500 meters and the half marathon. Some coaches nudge the exponent to 1.07–1.08 for recreational runners (who fade more) or 1.05 for elites (who fade less). If your own results consistently beat or miss the standard prediction, you've effectively discovered your personal exponent — and more aerobic base training is the lever that lowers it over time.

Using predictions to set training paces

The prediction's best use isn't race-day fantasy — it's calibrating your workouts so you train at paces your current fitness supports rather than paces you wish you had. Your predicted 10K pace approximates threshold effort, the "comfortably hard" zone that builds your ability to sustain speed; your predicted marathon pace sets the quality segments of long runs. Training to real fitness, not aspirational fitness, is the single most protective habit against injury and burnout in recreational running, because most overuse injuries trace back to running too fast on easy days and too hard on quality days. Feed the calculator your most recent all-out race, ideally within eight weeks, and let the equivalent paces anchor your week. As your races get faster, the predicted paces follow, and your training tightens with them — a self-correcting loop that keeps effort honest. One more practical use: the equivalent paces reveal your relative strengths. If your real race times consistently beat the prediction at shorter distances but miss it at longer ones, you're speed-biased and need aerobic volume; the reverse means you have endurance but lack top-end turnover and would benefit from interval work. Reading the gap between predicted and actual across distances is a free training diagnosis most runners never think to run. Treat it as a compass rather than a crystal ball: the prediction points you toward the training your body actually needs right now, which is far more valuable than any single race-time guess it produces.

Frequently asked questions

How accurate is the Riegel formula?

Within 1–2% between adjacent distances for appropriately trained runners — better than most GPS watches' race predictors. Accuracy degrades with distance gaps: 5K-to-marathon projections carry ±5% error even with good training.

Why 1.06 as the exponent?

It's empirical — fitted from elite and club runner data across distances. Some coaches use 1.07–1.08 for recreational runners (more slowdown) or 1.05 for elites. If your real results consistently lag predictions, your personal exponent is higher; more aerobic volume lowers it.

Which recent race gives the best prediction?

The longest recent race you ran all-out, ideally within eight weeks. A 10K predicts a half marathon far better than a 5K does, and race efforts predict better than time trials — competition reliably extracts 1–2% more.

Why is my marathon prediction always too optimistic?

Because Riegel assumes you've trained for the marathon's specific demands. The formula models smooth fatigue, but the marathon adds a discrete event — glycogen depletion around mile 18–20 — that shorter races don't. Runners under about 40 miles per week typically finish 5–8% slower than predicted.

Can I use a treadmill run to predict outdoor race times?

Cautiously. Treadmill running is slightly easier than outdoor (no wind resistance, assisted turnover), so set a 1% incline to approximate outdoor effort. Even then, outdoor races add pacing variability, terrain, and weather that a controlled treadmill effort won't capture.