10K to Marathon Predictor: Chart, Formula and Reality Check
Use a 10K to marathon predictor chart, compare Riegel with the 5× minus 10 rule, and turn one race result into a practical pacing range.
Kristian Hoffmann
SaaS founder and operator
A 10K to marathon predictor gives a transparent baseline by multiplying a recent 10K race time by roughly 4.60. With a 45:00 10K, the Riegel equation projects about 3:27:00 for the marathon, equivalent to 4:54 per km. Treat that number as a fitness-equivalent estimate rather than a promised finish: the calculation cannot see your marathon-specific training, course, weather, fuelling execution, or pacing decisions.
Free 10K to marathon predictor chart
A common Riegel calculation is:
`Marathon time = 10K time × (42.195 / 10)^1.06`
The distance ratio is 4.2195; applying the 1.06 exponent produces a multiplier of approximately 4.600. This is the ratio-based approach described in HillRunner's discussion of predicting a marathon from a 10K.
| 10K time | Riegel projection | Average marathon pace | 5× 10K minus 10 minutes |
|---|---|---|---|
| 40:00 | 3:04:00 | 4:22/km | 3:10:00 |
| 42:30 | 3:15:30 | 4:38/km | 3:22:30 |
| 45:00 | 3:27:00 | 4:54/km | 3:35:00 |
| 47:30 | 3:38:30 | 5:11/km | 3:47:30 |
| 50:00 | 3:50:00 | 5:27/km | 4:00:00 |
| 55:00 | 4:13:00 | 6:00/km | 4:25:00 |
| 60:00 | 4:36:00 | 6:32/km | 4:50:00 |
Times are calculated from the two formulas and rounded to the nearest 30 seconds. The final column uses the separate shortcut reported by Runner's World: five times the 10K time minus 10 minutes. It is an alternative assumption, not an accuracy ranking.
Why two clean formulas produce different answers
For a 45:00 runner, the Riegel projection is 3:27:00 while the 5× shortcut gives 3:35:00—an eight-minute difference before either method considers the runner or the race.
The Riegel exponent also matters. Starting from 47:30 for 10K:
- Exponent 1.04 projects approximately 3:32.
- Exponent 1.06 projects approximately 3:38:30.
- Exponent 1.08 projects approximately 3:45.
A change of 0.04 creates a 13-minute span. Extra decimal places do not remove that model uncertainty.
The useful output is therefore not one authoritative finish time. It is a baseline plus evidence about whether you can sustain the implied effort for 42.195 km.
The input failure that makes a predictor misleading
The usual failure mode is feeding an old 10K personal best into a calculator and treating the resulting average marathon pace as an opening pace for a different training phase, course, and climate.
Check the input before using the output:
- Use elapsed time over a measured 10K. Moving time from a GPS activity may omit stops, while an inaccurate route changes both distance and pace.
- Choose a representative effort. A hard race or deliberate time trial says more about current race fitness than an ordinary training run.
- Match the training phase. A result from the current block is more relevant than a faster performance from a materially different period.
- Cross-check endurance. A recent half-marathon result, marathon-specific workout, or completed long-run progression can expose a prediction supported mainly by short-distance speed.
- Separate equivalent time from race strategy. A flat mathematical projection does not specify where to spend or conserve effort on climbs, descents, exposed sections, or crowded early kilometres.
A half-marathon input requires less extrapolation: the marathon is twice the half-marathon distance, compared with 4.2195 times the 10K distance. If both results are equally recent and representative, the longer race can provide a useful cross-check.
A six-point readiness check for the projection
This scorecard is a planning heuristic, not a validated physiological test. Score each category from zero to two.
| Category | 0 points | 1 point | 2 points |
|---|---|---|---|
| Input quality | Old result or ordinary run | Controlled solo time trial | Recent, measured 10K raced at a representative effort |
| Endurance evidence | Prediction rests mainly on 10K speed | Mixed marathon-specific evidence | Planned long runs and marathon-specific sessions completed consistently |
| Race match | Several unmodelled differences | One material course or climate difference | Conditions are broadly comparable or explicitly adjusted |
Use the total as a decision rule:
- 5–6 points: Keep the formula result near the centre of your planning range, then adjust for the actual course and conditions.
- 3–4 points: Preserve both predictor outputs as a range and seek a longer-distance check before fixing the goal pace.
- 0–2 points: Treat the calculation as a fitness equivalent, not a marathon target. Collect a more representative result first.
Turn the estimate into a race-day plan
Take the 47:30 example. The Riegel output is about 3:38:30, or 5:11/km. That average is useful for checking the scale of a goal, but copying 5:11 into every kilometre ignores the shape of the course.
Use this workflow:
- Calculate at least two transparent projections and retain the gap between them.
- Apply the readiness score instead of choosing the faster number automatically.
- Convert the working finish-time range into average pace and cumulative checkpoints.
- Adjust the splits for course elevation, expected conditions, and sections where even pace would require uneven effort.
- Recalculate when a newer 10K or half-marathon result materially changes the input.
For the underlying model choices, see Marathon pace predictor: estimate your finish time from recent races. Once the target range is credible, Free marathon pacing preview: test your race strategy explains how to inspect the pacing structure before race day.
Questions runners ask about 10K predictions
Can I use a training run instead of a 10K race?
Yes, if you label the output as a scenario. A training run with unknown spare effort does not represent the same input as a hard race, so the predicted marathon time should carry a wider practical range.
What should I do when calculators disagree?
Record the model, exponent, and output from each calculator. Do not average the answers blindly: first determine whether the difference comes from formula assumptions or additional inputs such as training volume, course profile, or conditions.
Is the projected pace my starting pace?
Not automatically. It is the constant pace that matches the projected finish on paper. Set the opening pace only after mapping that target to the real course and deciding how conservatively the early kilometres should be run.