Race Predictor – Running Time Calculator

A race predictor takes one recent race result and projects what you could realistically run at other distances, using a mathematical relationship between distance and endurance-adjusted pace. It’s built on the Riegel formula, one of the most widely used and well-validated race-time prediction models in distance running. Coaches, training-plan apps, and everyday runners all lean on this same formula to set realistic goals ahead of an upcoming race.

Below the calculator you’ll find a manual step-by-step walkthrough, common prediction mistakes, a full benchmark table, why the Riegel formula works (and where it breaks down), what actually affects prediction accuracy, and an expanded FAQ.

Step-by-Step: How to Predict Race Times by Hand

The Riegel formula: T2 = T1 × (D2 ÷ D1) raised to the power 1.06, where T1 and D1 are your known recent race time and distance, and T2 and D2 are the predicted time and target distance. The 1.06 exponent (rather than a simple 1.0) accounts for the fact that pace naturally slows somewhat as race distance increases — it’s not a straight linear scaling. For example, a recent 5K in 25:00 (1,500 seconds): predicting a 10K, T2 = 1,500 × (10÷5)^1.06 = 1,500 × 2.085 = 3,127 seconds, or 52:07. Predicting a marathon, T2 = 1,500 × (42.195÷5)^1.06 = 1,500 × 9.592 = 14,388 seconds, or roughly 3:59:48.

Notice the predicted marathon pace is meaningfully slower per kilometer than the 5K pace that generated it — that built-in slowdown is exactly what the 1.06 exponent is modeling, reflecting the reality that sustaining a hard effort gets progressively harder as distance increases, even for well-trained runners with excellent endurance.

Common Mistakes When Using Race Predictors

The most common mistake is using a race result that wasn’t run at genuine maximal effort as the input — a comfortable training run or a race where you deliberately held back will produce an unrealistically slow prediction for longer distances. A second mistake is using a very short input distance (like a mile time trial) to predict a very long target distance (like a marathon) — the Riegel formula’s accuracy degrades the further apart the input and target distances are, since a mile effort draws almost entirely on different physiological systems than marathon endurance. A third mistake is treating the prediction as a guaranteed outcome rather than a starting estimate — actual race-day performance still depends heavily on specific training for the target distance, not just raw fitness extrapolated mathematically from a different race.

Pace Tier Benchmarks at a Glance

These are the exact thresholds this calculator uses (based on your input pace per km):

Why the Riegel Formula Works (and Where It Breaks Down)

Peter Riegel, an engineer and runner, developed the formula in the early 1980s by analyzing large sets of real race results across many distances and finding a remarkably consistent power-law relationship between distance and time for trained endurance athletes. The formula works because it captures a genuine physiological truth: sustainable pace declines predictably as duration increases, driven by factors like glycogen depletion, accumulated fatigue, and the shifting balance between aerobic and anaerobic energy systems as effort duration extends. For runners with balanced training across a range of distances, Riegel’s predictions tend to land impressively close to actual race results.

Where it breaks down is with runners who have a lopsided training background — a runner who has trained almost exclusively for 5Ks and never run anything close to marathon distance will often actually run slower than Riegel predicts for a marathon, since the formula assumes reasonably well-rounded endurance conditioning behind the input performance. Conversely, dedicated ultra-distance runners sometimes outperform Riegel’s marathon predictions generated from shorter race times, since their training has specifically built the long-duration endurance the formula assumes but doesn’t directly measure from a short input race alone.

What Actually Affects Prediction Accuracy

The closer your input race distance is to your target distance, the more accurate the Riegel prediction tends to be — predicting a 10K from a recent 5K is generally more reliable than predicting a marathon from that same 5K, since less extrapolation is required across the distance-and-duration relationship. Training specificity matters just as much: a prediction is only as good as the assumption that you’ve trained appropriately for the target distance, so a 5K predictor plugging in a marathon target should treat the number as an upper-bound “possible if properly trained” estimate rather than a guaranteed race-day outcome without dedicated marathon-specific preparation (long runs, fueling practice, endurance-focused mileage).

Race-day conditions on the day of the actual target race — weather, course terrain, taper quality, and even simple race-day nerves and adrenaline — introduce variance the formula has no way to account for, which is why serious runners treat a Riegel prediction as a well-informed target rather than a precise promise.

Using Race Predictions to Set Training Paces

Beyond just forecasting a goal finish time, race predictions are commonly used to set specific training paces for workouts. A predicted 10K time, for example, is often used to calculate threshold or tempo pace for interval sessions, since threshold pace is typically expressed as a percentage adjustment off current 10K fitness rather than an arbitrary number. Similarly, a predicted marathon time feeds directly into marathon-pace training runs, letting a runner practice race-specific pacing weeks or months before the actual event based on current fitness rather than a wished-for goal that may not match present conditioning.

Many training plans re-run this same prediction periodically throughout a training cycle, using the most recent time trial or race result as an updated input — since fitness improves (or occasionally declines) over weeks of training, refreshing the prediction keeps target paces aligned with current ability rather than a stale estimate from months earlier in the training block.

How Sensitive Is the Prediction to the Exponent?

The formula is from Peter Riegel’s 1981 article “Athletic Records and Human Endurance” in American Scientist (69(3):285–290). Riegel fitted world-record performances across running, swimming, cycling and other endurance sports and found that time scales with distance to a power very close to 1.06 for runs between roughly 3.5 minutes and 4 hours. That fit is excellent for elite, well-trained athletes — the population the records came from — and gets progressively rougher for recreational runners, whose fatigue curve is steeper.

The most rigorous check on this was published by Vickers and Vertosick in 2016 (BMC Sports Science, Medicine and Rehabilitation 8:26). Using race histories from more than 2,300 recreational runners, they found Riegel’s formula systematically predicted marathon times that were too fast, and that adding weekly training mileage to the model materially improved accuracy: a runner logging 25 km a week and one logging 80 km a week should not expect the same marathon from the same 10K, even though Riegel gives them identical predictions. The table shows what a small change in the exponent does to a marathon predicted from a 25:00 5K.

Two rules of thumb follow. Keep the distance jump small: a half-marathon predicts a marathon far better than a 5K does, because the exponent error compounds over an 8× distance ratio. And use the most recent, well-rested race you have — a time from a hot day or the end of a hard training block will drag every downstream prediction with it. Other predictors, such as Jack Daniels’ VDOT tables (Daniels and Gilbert, 1979), are built on oxygen-cost curves rather than a single exponent and can be a useful second opinion when the two disagree.

FAQ

How accurate is the Riegel formula for predicting marathon time?
It’s generally quite accurate for runners with well-rounded endurance training, but tends to overpredict (show faster than achievable) for runners who haven’t specifically trained for the longer target distance, since the formula assumes appropriate endurance conditioning behind the input performance.

What input race gives the most reliable prediction?
A recent, maximal-effort race at a distance reasonably close to your target distance gives the most reliable prediction — a 10K or half marathon input tends to predict marathon time more accurately than a very short 5K or mile input.

Why does the formula use an exponent of 1.06 instead of just scaling time linearly?
A linear scaling would assume pace stays exactly constant regardless of distance, which doesn’t match reality — the 1.06 exponent captures the natural, physiologically expected slowdown in sustainable pace as race duration increases.

Can I use this to predict a shorter distance from a longer race result?
Yes — the formula works in both directions, though predicting a shorter, faster distance from a longer endurance-focused race sometimes underestimates true speed if the runner hasn’t specifically trained their top-end speed for that shorter distance.

Should I trust this prediction over my own training-based goal time?
Treat it as one useful data point alongside your training log, not a replacement for it — if your specific target-distance training (like long runs for a marathon) tells a different story than the Riegel prediction, your training-specific data usually deserves more weight.

How often should I update my race prediction during a training cycle?
Many runners refresh it every few weeks using their most recent time trial or tune-up race, since fitness shifts meaningfully over the course of a training block and a prediction based on outdated data can steer training paces in the wrong direction.

Last reviewed September 2026 — formulas and references above were checked against the primary sources cited.

Related posts:

Step Counter Scuba Weight Calculator Cycling Wattage Calculator Running Calorie Calculator Running Pace Calculator