Running Pace Calculator — 5K, 10K, Marathon Times
Calculate running pace, finish time, and race projections for 5K, 10K, half marathon and full marathon — using Riegel's endurance formula rather than a straight multiplication.
Finish Time
0:25:00
Pace per km
5:00/km
Pace per mile
8:03/mi
Speed
12.00 km/h
Race Projections
Riegel's formula allows for the fact that pace slows as distance grows. The straight-multiplication column is shown alongside to make the gap visible — it is what most pace calculators report, and it is optimistic by a wide margin at the longer distances.
| Race | Riegel projection | Straight multiplication |
|---|---|---|
| 5K | 0:25:00 | 0:25:00 |
| 10K | 0:52:07 | 0:50:00 |
| Half Marathon | 1:55:00 | 1:45:29 |
| Marathon | 3:59:47 | 3:30:59 |
Projections assume training appropriate to the distance. Riegel tends to be optimistic for a marathon predicted from a 5K unless you have done the endurance work to back it up.
Analysis & insights
Your projected race times at this pace (0.00 mph): 5K —, 10K —, half marathon —, marathon —. An easy/conversational pace — the right zone for aerobic base building. Most weekly mileage should be at THIS pace, not faster. Remember: projected marathon time from short-distance pace is optimistic. Real marathon pace is typically 30-60 seconds/mile slower than 5K pace.
Walk / build pace
Brisk walking territory. Walk-run intervals are how most beginners build to running.
Risk & benchmark gauge
Current band
Walk / build
0.00 mph
Industry benchmarks
- Your pace—
- 5K split—
- 10K split—
- Half marathon—
- Marathon—
- Sub-elite (M) 5K~16-18 min
- BQ marathon (M 35-39)<3h 05m
Key insights
Race pace ≠ training pace
Most training runs should be 1-2 minutes per mile SLOWER than your race pace. Most amateur runners chronically over-train at moderate-hard pace and under-train at both easy and very-hard.
Marathon pace fades — projected splits don't hold
The projected marathon time assumes you can maintain 5K pace for 26.2 miles, which is almost never true. A trained runner's actual marathon pace is typically 30-60 seconds/mile slower than 5K pace.
80/20 training works
Spend 80% of weekly volume at easy/conversational pace, 20% at threshold/interval pace. This polarized pattern outperforms running everything at "moderate" pace.
Recommended actions(5)
Slow your easy runs
High priorityEasy days should feel almost too slow — you should be able to hold a conversation in full sentences. This is where aerobic adaptation happens.
Impact: Most runners can drop their race times by simply running easier on easy days and harder on hard days.
Build mileage gradually
High priorityThe "10% rule" — increase weekly volume by no more than 10% — has decent injury-prevention data behind it. Skip the rule and you skip injury-free training.
Add one quality session per week
Medium priorityTempo run (20-40 min at threshold) or intervals (e.g. 6x800m at 5K pace). Builds the high-end speed that easy mileage alone won't.
Related Calculators
This tool is for informational purposes only and does not constitute medical advice. Consult a healthcare professional for advice specific to your situation.
What is Running Pace and Race Prediction?
Pace is time divided by distance, and that part is trivial. The interesting question is the one every runner actually asks: given what I can do over one distance, what can I do over another?
The naive answer — multiply your pace by the new distance — is wrong in a way that matters. It assumes you can hold 5K pace for a marathon. Nobody can. Physiology does not work that way, and a plan built on that assumption falls apart somewhere around mile 18.
The standard correction is Riegel's formula, published by Peter Riegel in 1977: predicted time scales with distance raised to the power 1.06. That small exponent above 1 is the entire story — it encodes the fact that pace necessarily slows as distance grows.
The formula — how to calculate Running Pace and Race Prediction
- T₁, D₁
- = a time and distance you have actually run
- 1.06
- = the fatigue exponent — Riegel's fit to distance-running results
At an exponent of exactly 1 the formula collapses into straight multiplication. The 6% above 1 is what separates a usable prediction from an optimistic one.
Step-by-step example
- 01A 25-minute 5K — 5:00 per km, or 8:03 per mile.
- 02Straight multiplication to marathon distance: 5:00 × 42.195 = 3:30:59.
- 03Riegel: 25 min × (42.195 ÷ 5)^1.06 = 25 × 9.59 = 3:59:47.
- 04The difference is nearly 29 minutes, and the linear figure is the optimistic one. A runner who set out at 5:00/km on that basis would be in serious trouble well before the finish.
- 05The gap widens with distance. For the 10K the two methods differ by about two minutes; for the half marathon, around ten; for the marathon, nearly twenty-nine.
- 06Working the other way is more reliable. A 4-hour marathon back-predicts a 25:01 5K under Riegel, and short-distance predictions from long-distance results are generally more trustworthy than the reverse.
Why pace slows with distance
The physiology is straightforward once stated. Short races run largely on anaerobic capacity and stored glycogen at high intensity. As distance grows, the sustainable intensity drops toward the level your aerobic system can supply indefinitely.
The binding constraint changes too. A 5K is limited mostly by how much oxygen you can process. A marathon is limited by fuel — you carry roughly 90 minutes to two hours of glycogen at race intensity — and by the accumulating mechanical damage of tens of thousands of foot strikes.
This is why the marathon is not simply a long 10K. Around the 20-mile mark most runners approach glycogen depletion, which is the physiological event behind "hitting the wall". No amount of pacing arithmetic avoids it; only training and fuelling do.
Riegel's exponent captures the average of all this empirically. It does not model any single mechanism — it just fits the observed relationship across a large body of race results.
Riegel assumes you trained for the distance
The formula predicts what an equivalently trained runner would achieve. It does not know whether you have done the long runs. A 5K runner with no mileage base will not run their Riegel marathon time, and the error is largest exactly where it hurts most — predicting up from a short race to a long one. Treat marathon predictions from a 5K as a ceiling, not a target.
Reading the projections
Predictions are most reliable when the two distances are close. A 10K predicted from a 5K is usually within a couple of percent for a trained runner. A marathon predicted from a 5K is a much longer extrapolation and should be treated with corresponding caution.
Some coaches prefer an exponent of 1.07 or 1.08 for marathon predictions specifically, on the basis that Riegel is slightly optimistic at that end. If your marathon results have consistently come in behind the prediction, that is the adjustment to make.
Equivalent performances from a 25:00 5K
| Race | Riegel prediction | Straight multiplication |
|---|---|---|
| 5K | 25:00 | 25:00 |
| 10K | 52:07 | 50:00 |
| Half marathon | 1:55:00 | 1:45:29 |
| Marathon | 3:59:47 | 3:30:59 |
The two agree at the reference distance by definition and diverge steadily from there. Anywhere the linear column looks appealing is exactly where it is least reliable.
Pacing a race with these numbers
An even split — the same pace throughout — is close to optimal for most distances and most runners, and it is far harder to execute than it sounds because everyone feels good in the first mile.
A slight negative split, running the second half a little faster, is the pattern behind a large share of personal bests. It costs almost nothing if it fails and protects against the far more common failure of starting too fast.
The classic marathon error is banking time: running the first half a few minutes quicker than target in the belief it can be held in reserve. It cannot. Glycogen spent early is not recoverable, and the second half loses far more than the first half gained.
Course profile and heat both shift the calculation. Hills cost more going up than they return coming down, and performance falls measurably above roughly 15°C, with the effect growing sharply through the marathon distance.
- Even split —
- the same pace throughout; the default plan and usually the right one.
- Negative split —
- second half faster than the first; the pattern most personal bests follow.
- Positive split —
- slowing in the second half; almost always the result of starting too fast rather than a chosen strategy.
- Threshold pace —
- roughly the pace you could hold for an hour — close to 10K pace for many runners, and the anchor most training paces are derived from.
- Easy pace —
- conversational. Most weekly mileage should be here, and running easy days too hard is the most common training mistake there is.
Metric and imperial, and the arithmetic between them
Race distances are metric almost everywhere, while a great many runners think in minutes per mile. Both are shown here to avoid the conversion becoming its own source of error.
The relationship: a mile is 1.609344 km, so a pace per mile is the pace per km multiplied by 1.609. A 5:00/km pace is 8:03/mile.
Useful anchors: 5:00/km is a 25-minute 5K and a 3:30 marathon under straight multiplication — but a 3:58 marathon under Riegel, which is the number to plan around. A 4:00/km pace is a 20-minute 5K. A 6:00/km pace is a 30-minute 5K.
One quiet source of confusion on race day: your watch will almost always record a longer distance than the official course. Courses are measured along the shortest legal route, and nobody runs that line exactly. Finishing a marathon with 42.5 km on the watch is normal, and it means your actual pace was slightly faster than the watch suggested.
Common mistakes to avoid
- Multiplying pace by distance to predict a longer race. It is optimistic by nearly half an hour at the marathon.
- Predicting a marathon from a 5K without the mileage base to support it.
- Banking time in the first half. Glycogen spent early does not come back.
- Running easy days too hard, which is the most common training error in distance running.
- Ignoring heat and course profile when setting a target pace.
- Trusting watch distance over the official course measurement.
- Confusing pace per km with pace per mile — a 61% difference in the number.
Frequently asked questions
Sources & references
Written and fact-checked by the CalcProLabs Editorial Team. Read our calculation methodology and editorial policy.
Last updated