Formula used
Riegel endurance model with distance-specific confidence framing.
Expected finish time for any race distance. Know your 5K? Predict marathon, half or 10K in seconds. Riegel formula: 20:00 5K → 3:11 marathon.
Race decision
Use a recent result to decide if the target is conservative, realistic, aggressive, or high risk before you commit to race-day pacing.
Enter a recent race result and a target distance to estimate your finish time with the Riegel formula. The result now includes required pace, confidence level, a realistic range, and the main assumption behind the prediction so you can decide whether the target is ready, optimistic, or needs more race-specific training.
The most-searched question: "What marathon time can I run based on my 5K?" Here are Riegel formula predictions for common 5K times:
| Your 5K Time | Predicted 10K | Predicted Half Marathon | Predicted Marathon |
|---|---|---|---|
| 18:00 (fast) | 37:26 | 1:22:32 | 2:52:32 |
| 20:00 | 41:35 | 1:31:36 | 3:11:53 |
| 22:00 | 45:43 | 1:40:41 | 3:31:13 |
| 25:00 | 51:56 | 1:55:24 | 3:58:01 |
| 28:00 | 58:09 | 2:07:55 | 4:29:15 |
| 30:00 | 62:17 | 2:16:59 | 4:48:35 |
| 35:00 | 72:44 | 2:39:37 | 5:36:30 |
Key benchmarks:
To predict from a half marathon: double your half marathon time and add 5–15 minutes (lower end for high-mileage runners; upper end for 30–40 miles/week). Or enter your half marathon time directly in the calculator above.
Race time prediction is based on the mathematical relationship between performance at different distances. A common model is Peter Riegel's formula, published in American Scientist:
T2 = T1 × (D2/D1)^1.06
Where T1 is a known race time, D1 is that race's distance, D2 is the target distance, and T2 is the predicted finish time. The exponent reflects the observation that performance does not scale linearly as distance increases.
Example: a runner with a 5K time of 22:00 predicts a marathon time of: 22:00 × (42.195/5)^1.06 = 22:00 × 9.12 = 200.6 minutes = 3:20:38.
Riegel's formula is useful for trained runners racing across a familiar distance range. The main limitation: it assumes broadly comparable preparation for both distances. If you have trained specifically for 5K but rarely do long runs, your marathon may be much slower than predicted.
Use this reference table to find predicted finish times across distances based on your known performance. Values use Riegel's formula (exponent 1.06):
| 5K Time | 10K | Half Marathon | Marathon |
|---|---|---|---|
| 17:00 | 35:22 | 1:18:00 | 2:42:51 |
| 18:00 | 37:26 | 1:22:32 | 2:52:32 |
| 19:00 | 39:30 | 1:27:04 | 3:02:12 |
| 20:00 | 41:35 | 1:31:36 | 3:11:53 |
| 22:00 | 45:43 | 1:40:41 | 3:31:13 |
| 24:00 | 49:52 | 1:49:45 | 3:50:34 |
| 26:00 | 54:00 | 1:58:50 | 4:09:54 |
| 28:00 | 58:09 | 2:07:55 | 4:29:15 |
| 30:00 | 62:17 | 2:16:59 | 4:48:35 |
| 35:00 | 72:44 | 2:39:37 | 5:36:30 |
Note that these predictions assume flat courses in moderate weather conditions (10–15°C) with appropriate race-specific preparation for both distances.
Riegel's formula gives a model-based estimate, but individual results vary. Several factors can make a prediction too fast or too slow:
For many recreational runners, a recent half marathon is a more practical marathon input than a much shorter race because the distance demands overlap more closely.
Several alternative models can complement Riegel's formula. Each has different strengths:
For practical race planning, Riegel's formula is useful because it is simple and transparent. For important goal-setting decisions, compare several signals: recent race result, distance specificity, training benchmarks, and race conditions.
Race time predictions aren't just useful for setting race goals — they're a powerful training tool. Here's how coaches use predicted times:
The Jack Daniels VDOT approach is especially powerful here: once you calculate your VDOT from any race, you have prescribed training paces AND predicted times for all standard distances simultaneously.
Raw race times often change with age because cardiorespiratory fitness, recovery, muscle mass, and training capacity can change over time. Age-graded performance tables adjust results against age and sex benchmarks, allowing a more contextual comparison than raw finish time alone.
For example, a 60-year-old running 4:30 in a marathon may score differently from a 30-year-old with the same finish time because the benchmark set is different. Treat age grading as a comparison tool, not a personal health assessment.
Age-graded times can also help with goal-setting as runners move through age groups, but recent training history and race specificity remain more important than any single conversion.
Riegel is the default model in this calculator because it is simple, transparent, and useful for common road-race planning. Other systems can still help you sanity-check the result, especially when the target race is much longer than the known race.
| Method | Best use | Main caution | Next action |
|---|---|---|---|
| Riegel formula | Quick finish-time projection from a recent race | Can be optimistic when jumping from short races to the marathon | Convert the prediction into pace and test it in workouts |
| VDOT-style comparison | Connecting equivalent performances to training paces | Still assumes the input race was a true current-fitness effort | Use the training zone calculator for paces |
| Half-marathon rule of thumb | Marathon goal checks from a recent half marathon | Mileage, long runs, fueling, and heat can move the result materially | Compare with marathon-specific workouts before committing |
| Training benchmark | Reality-checking a goal against recent workouts | Workout conditions and fatigue can distort the signal | Choose the conservative goal if target pace repeatedly fails |
For most runners, the best decision is not to average every model. Start with the calculator result, lower confidence when the distance jump is large, then let race-specific training decide whether the goal is ready or still optimistic.
Formula output should be checked against training reality. If race-specific workouts are consistently too hard, choose the more conservative goal even when the calculator predicts a faster time.
A finish-time prediction is most useful when you convert it into a practical pace, training target, or race-day strategy.
Race predictions are most useful when the input race is recent, hard, and close in distance to the target. Accuracy drops when you are trying a new distance, race conditions differ significantly, or your fitness is changing rapidly.
Riegel's formula: T2 = T1 × (D2/D1)^1.06. T1 = known time, D1 = known distance, D2 = target distance, T2 = predicted time. Example: 5K in 25:00 → marathon = 25 × (42.195/5)^1.06 = 25 × 9.12 = 228 minutes = 3:48:00.
Yes, with caveats. Riegel's formula provides a prediction, but marathon performance depends heavily on long-run training that a 5K does not test. A runner who only does 5Ks will often need a more conservative marathon goal than the formula suggests. A recent half marathon or marathon-specific workout block usually gives more relevant evidence.
Common reasons: insufficient long-run training, hitting the wall from going out too fast, inadequate fueling during the race, heat or hills not accounted for, or simply not having run enough marathon-specific mileage. Race prediction assumes your preparation is equal across distances — if it's not, adjust accordingly.
Hot weather can slow race performance, especially over longer distances. The exact adjustment depends on temperature, humidity, sun exposure, acclimation, hydration, and pace. In hot conditions, many runners use effort or heart rate instead of forcing a fixed time goal.
Using Riegel's formula, a sub-4:00 marathon (3:59:59) predicts back to approximately a 5K of 27:15 or faster. However, this assumes proper marathon-specific training. In practice, many coaches suggest you need a 5K time of 25:00 or faster to confidently target sub-4 hours with appropriate training.
Both methods often produce similar race-equivalent estimates in common road-race ranges. VDOT has the advantage of also providing training pace zones, while Riegel is simpler and easier to calculate. Treat both as estimates that depend on the quality of your input race.
Update your prediction after every significant race or time trial, typically every 4–8 weeks during a training cycle. As your fitness improves, your predicted times will decrease. Track your progress across training blocks — seeing your predicted marathon time drop from 3:40 to 3:30 over a 16-week cycle is a powerful motivator.
Daniels-style VDOT converts a recent race into equivalent performances and training paces. Pfitzinger-style marathon planning emphasizes specificity of preparation and gives more weight to longer recent races. Hansons-style planning uses training performance under cumulative fatigue as a reality check. None of these approaches should override clear signs that the target pace is not sustainable in training.
A recent half marathon is often one of the most useful marathon predictors because the distance demands overlap more closely than a 5K or 10K. A common rule of thumb is to double your half marathon time and add 5-15 minutes, with the lower end reserved for runners with strong marathon-specific preparation. The larger the distance jump, the more uncertainty you should add.
Riegel endurance model with distance-specific confidence framing.
You have a recent race or time trial and want a realistic target for another distance.
The known result was not all-out, conditions were extreme, or injury/illness changed effort.
Reviewed by RunCalc editorial review · Last reviewed 2026-08-08 · Scope: Race prediction formulas, Riegel/VDOT framing, model-accuracy language, age-performance claims, and training-specificity limits