Running Pace Calculator
Pace, time and distance — plus splits and race predictions.
At a glance
- Input:
- Numbers you enter
- Processing:
- Runs locally in your browser
- Privacy:
- Nothing you type is sent to a server
Last updated: 2026-11-11
Common use cases
- Working out your pace for a 10K in 50:00 — 5:00/km, 8:03/mile
- Seeing what a 50:00 10K predicts for a marathon — 3:50:01 by Riegel
- Setting the treadmill to hold 5:00/km — 12 km/h
- Printing even splits for a half marathon at your goal pace
About this tool
Enter any two of pace, time and distance and get the third — in min/km and min/mile, with the treadmill speed and an even-pace split table. A 10K in 50:00 is 5:00/km (8:03/mile) at 12 km/h. The race predictor uses Riegel's formula (T2 = T1 × (D2 ÷ D1)^1.06, Peter Riegel, American Scientist 1981): the same 10K predicts a marathon of 3:50:01 — slower than the 3:30:59 that even pace would give, because fatigue compounds over distance. Predictions are marked by reliability: short jumps are far more certain than long ones, and anything outside the formula's 3.5–230 minute fitted range is flagged. Everything runs locally in your browser — no signup, no upload.
How to use it
- Pick what to find — pace, time or distance. Finding pace with the 10K-in-50:00 example is the default.
- Enter the two values you know — 10 km and 50:00 for the default example — or tap a race preset (5K, 10K, 10-miler, half, marathon).
- Read the third value — 5:00/km and 8:03/mile for the default — plus the treadmill speed and the even-pace splits.
- Scroll to the race predictor, enter a recent race result — 10K in 50:00 by default — and read the predicted times with their reliability.
- Check the reliability column before quoting a prediction — 10K-to-half is far more certain than 5K-to-marathon.
Worked examples
Input: 10K in 50:00
Output: 5:00/km · 8:03/mile · 12 km/h · 7.5 mph
50:00 ÷ 10 km = 5:00/km; × 1.609344 = 8:03/mile. Treadmill speed is 3600 ÷ 300 s = 12 km/h.
Input: 10K in 50:00 → marathon prediction
Output: 3:50:01 predicted marathon (Riegel) · even pace would give 3:30:59
Riegel: 50:00 × (42.195 ÷ 10)^1.06 = 3:50:01. Even pace at 5:00/km over 42.195 km is 3:30:59 — the 19-minute gap is fatigue, and it is why the prediction is slower than pace × distance.
Input: 5K in 25:00 → marathon prediction
Output: 5:00/km · 8:03/mile · predicted marathon 3:59:47 (less certain)
Same 5:00/km pace, but the jump is 8.4× the distance — a 5K-to-marathon prediction is far less certain than 10K-to-half, so it is marked less certain.
Practical tips
- Work in the unit you think in — the page converts between min/km and min/mile automatically.
- Use a recent result for predictions — a 10K from last month predicts far better than a 5K from two years ago.
- Compare the Riegel time with the even-pace time — the gap tells you how much fatigue the formula expects.
- Set the treadmill by speed, not pace — 5:00/km is 12 km/h, and most treadmills take km/h directly.
Common mistakes
- Multiplying pace by distance for a marathon — 5:00/km × 42.195 km is 3:30:59 of even running, but no one holds 10K pace for a marathon; Riegel says 3:50:01.
- Quoting a 5K-to-marathon prediction as certain — it is the least reliable jump on this page; 10K-to-half is far more certain.
- Mixing up min/km and min/mile — 5:00/km is 8:03/mile, not 5:00/mile; the mile number is always bigger.
How this compares
Most pace calculators solve one equation — pace from time and distance — and stop. This calculator does the same three-way solve, then adds what runners actually need next: an even-pace split table, treadmill speed in km/h and mph, and a Riegel race predictor that labels every prediction by reliability instead of printing one confident number. The tradeoff: there is no GPS import and no training plan — it predicts from one result, it does not coach you to it.
Good to know
- Riegel's formula is an estimate fitted to efforts of about 3.5 to 230 minutes — predictions outside that range are marked less reliable, and the formula was never fitted to ultramarathons or sprints.
- Long jumps are far less certain than short ones — 5K-to-marathon is the least reliable prediction on this page; 10K-to-half is far more certain.
- Even splits assume you hold one pace the whole way — hills, wind, heat and fatigue make real splits uneven.
- No terrain, weather, altitude or fitness adjustment — a hilly 10K and a flat 10K in the same time predict the same marathon here.
- Estimates only — a prediction is not a promise; train for the distance, don't just trust the number.
Frequently asked questions
How do I calculate running pace?
Divide your time by the distance. A 10K in 50:00 is 50 ÷ 10 = 5:00 per kilometre. The same run is 8:03 per mile, because 1 mile is 1.609344 km — multiply the per-km pace by 1.609.
How do I convert min/km to min/mile?
Multiply by 1.609344. 5:00/km × 1.609 = 8:03/mile. To go the other way, divide the per-mile pace by 1.609 — 8:03/mile ÷ 1.609 = 5:00/km.
What is Riegel's formula?
T2 = T1 × (D2 ÷ D1)^1.06 — Peter Riegel, American Scientist 1981. It predicts a race time at one distance from a result at another: a 10K in 50:00 predicts a marathon of 3:50:01. It is an estimate fitted to efforts of about 3.5 to 230 minutes, not a guarantee.
How accurate are Riegel race predictions?
Short jumps are far more reliable than long ones. A 10K-to-half prediction is much more certain than a 5K-to-marathon one — training, fueling and pacing dominate at long distances. Predictions outside the 3.5–230 minute fitted range are marked less reliable on this page.
Why is my predicted marathon slower than my pace × distance?
Because you cannot hold 10K pace for a marathon. At 5:00/km, 42.195 km is 3:30:59 of even running — but Riegel predicts 3:50:01 from a 50:00 10K. Fatigue compounds over distance; that gap is exactly what the formula captures.
What are even splits?
Running every kilometre at the same pace — the split table on this page. They are a plan, not a promise: hills, wind and fatigue make real splits uneven, and most runners run the second half of a marathon slower than the first.
Is my data uploaded?
No. The calculation runs entirely in your browser — your times and distances never leave this tab, and nothing is stored.

