Running Pace Calculator
Turn one honest race result into the five training paces that actually build fitness — easy, marathon, threshold, interval and long run — derived from your result, not a table.
Running Pace Calculator
Results recalculate instantly on every keystroke. Nothing you type is transmitted.
What this result does not account for
- Built on a single race result — one data point cannot capture an endurance profile.
- Riegel's exponent was fitted to world-record data and flatters recreational runners, increasingly so as the projection distance grows.
- The easy-pace band is a convention, not a physiological measurement.
- Ignores gradient, heat, altitude and surface entirely.
- Cannot distinguish a durable runner from a fast but fragile one.
In short: Training paces should be derived from your own race performance, not copied from a generic chart. A 50:00 10 km runner has a threshold pace of about 5:03 per kilometre, an interval pace of about 4:35, and an easy pace of 6:03 to 6:33 — far slower than most runners train. The single most common training error is running easy days too hard.
Formula
T2 = T1 × (D2 ÷ D1)1.06
threshold pace = 3,600 s ÷ D60 where T(D60) = 3,600 s
easy pace = threshold pace + 60 to 90 s/km
D60 is the distance the runner would cover in exactly one hour under their own Riegel curve, found by bisection. Threshold is defined as one-hour race pace; interval pace uses the same solve at 11 minutes.
Worked Example
- Convert the race result to seconds and kilometres.
- Solve Riegel's curve by bisection for the distance covered in 3,600 seconds — that is D60.
- Threshold pace is 3,600 divided by D60.
- Repeat the solve at 660 seconds for the VO2max interval pace.
- Project to 42.195 km for marathon pace.
- Add 60 to 90 seconds per kilometre to threshold for the easy range.
A 50:00 10 km gives D60 = 11.88 km, so threshold is 3,600 ÷ 11.88 = 5:03 per kilometre; interval pace is 4:35; easy is 6:03 to 6:33 — a full minute per kilometre slower than the race just run.
Strengths & Limits Of This Model
Where this engine is strong
- Paces derived from your own performance rather than a generic chart
- States plainly which figures are derived and which are convention
- Makes the easy/hard gap explicit, which is where most training goes wrong
Where it stops
- Needs a genuine recent all-out result to be meaningful
- Single-distance input cannot detect a speed/endurance imbalance
Practical Use Cases
Making easy days genuinely easy
Sets tomorrow's easy pace from your own race result rather than from feel, which is usually too fast.
Prescribing a threshold session
Turns a recent parkrun into a defensible tempo pace.
Diagnosing the grey zone
Shows the gap between easy and threshold, which is where stalled training usually hides.
Converting a coach's zones
Expresses a zone prescription as numbers your watch can display.
Re-anchoring after a fitness change
Recalculate after each race; the Race Predictor Calculator cross-checks the result.
Methodology & Editorial Standards
The engine implements the standard published formula for this calculation. Inputs are validated for domain and sign before evaluation, and any undefined case returns an em-dash rather than a spurious value. Threshold and interval paces are solved by bisection from the runner's own Riegel curve at 3,600 s and 660 s respectively, rather than read from a lookup table. The easy-pace offset of 60–90 s/km is a coaching convention and is labelled as one in the engine output rather than presented as derived.
Computation runs in IEEE-754 double precision at full internal precision; rounding to two decimal places occurs strictly at the display layer, so no cumulative drift enters the result. All monetary outputs use accounting presentation — grouped thousands, two decimals, negatives in parentheses — so figures can be transcribed directly into a model or working paper. Division-by-zero and out-of-domain inputs return an em-dash rather than a misleading number.
This engine was reconciled against an independent reference implementation and hand-verified for the worked example above before release. Our full five-stage review process is published on the About Us page.
Disclaimer. This calculator is provided for informational and modelling purposes only and does not constitute financial, tax, legal, medical, or engineering advice. Verify all figures with a qualified professional before acting on them.
Running Pace Calculator — 20 Expert FAQs
20 analyst-written answers to the questions practitioners actually ask — optimised for voice and answer-engine retrieval.
How slow should my easy runs actually be?
For a 50:00 10 km runner, 6:03 to 6:33 per kilometre — around a minute per kilometre slower than race pace. The talk test is a good cross-check: if you cannot hold a conversation in full sentences, you are running too fast for an easy day, whatever the watch says.
What is threshold pace and why one hour?
Threshold pace is the fastest pace you could hold for roughly an hour, which corresponds closely to the lactate threshold — the intensity above which blood lactate accumulates faster than it can be cleared. One hour is used because it is the duration at which most trained runners' threshold and race pace converge.
Why are my training paces derived rather than looked up in a table?
Because a table cannot know your fatigue resistance. Solving your own race result for the distance you would cover in an hour uses your demonstrated performance as the anchor. Two runners with the same 10 km time but different endurance profiles still get the same answer here, which is this method's main limitation, but at least the anchor is real.
What is the 80/20 rule?
Roughly 80 per cent of weekly training volume at easy intensity and 20 per cent hard. It is one of the more robust findings in endurance training research, observed consistently in elite runners across disciplines and countries. Most recreational runners invert it accidentally by running easy days too hard and hard days too easy.
How often should I recalculate my paces?
After every race, or every 8 to 12 weeks of consistent training. Paces derived from a result older than about six weeks may describe a fitness level you no longer have — which is as much a problem when you have improved as when you have detrained.
Can I use a training run instead of a race?
Only if it was an genuine all-out effort over a measured distance. A tempo run at 90 per cent effort will shift every pace in this table too fast, and you will then train too hard across the board. A parkrun or a hard time trial works well.
What is the grey zone and why is it bad?
It is the moderately hard intensity between easy and threshold — too hard to recover from, too easy to drive adaptation. Training there accumulates fatigue without a matching stimulus. Runners who plateau despite consistent mileage are usually living in it.
Should my long run be at marathon pace?
Generally no. The long run's purpose is aerobic development and time on feet, and running it hard compromises the next quality session. Marathon-pace segments within a long run are a legitimate and useful workout, but they are a hard session, not an easy one, and should be counted as such.
Why is my interval pace based on 11 minutes?
VO2max intervals are typically prescribed at the intensity you could sustain for 10 to 12 minutes in a maximal effort, because that intensity elicits close to maximal oxygen uptake. Eleven minutes sits in the middle of that window. Individual repetitions are far shorter — usually 3 to 5 minutes.
Do these paces work for trail running?
Not directly. Gradient and technical terrain dominate pace on trails to the point where pace stops being a useful prescription at all. Most trail runners use effort or heart rate instead, and treat pace as an outcome rather than a target.
Are the easy pace numbers derived or a convention?
A convention, and the engine says so explicitly. Threshold, interval and marathon paces are solved from your own Riegel curve. Easy pace is threshold plus 60 to 90 seconds per kilometre, which is a widely used coaching heuristic rather than a derived physiological quantity.
Should older runners use different zones?
The relative structure holds, but maximum heart rate declines with age and recovery takes longer, so many masters runners need more easy days between hard sessions rather than different paces. The paces here are anchored to your current performance, so they already reflect your current age.
What if my race was on a hilly course?
Your derived paces will be slightly conservative, because the same effort on a flat course would have produced a faster time. Use a flat, accurately measured result where possible, and prefer recent results over favourable ones.
Is heart rate better than pace for controlling intensity?
Each fails differently. Heart rate lags at the start of an interval, drifts upward in heat and when dehydrated, and is unreliable on short repetitions. Pace ignores gradient, wind and terrain. Experienced runners use pace on the flat, heart rate on hills and in heat, and perceived effort as the tiebreaker.
Why is my marathon projection slower than my goal?
Because the projection reflects the fitness your recent race demonstrated, not the fitness you intend to have on race day. If the gap is large, the honest reading is that you need either more training time or a more realistic goal — and note that Riegel is optimistic at the marathon in the first place.
Does this work for beginners?
Yes, with a caveat: a beginner's race result is often limited by inexperience and pacing rather than aerobic fitness, so the derived paces may be conservative. That is a safe direction to err in. Recalculate after a few more races once you have learned to pace properly.
Is this running pace calculator free to use?
Yes. It is free, requires no account, and has no usage limits. ApexConverter is funded by contextual advertising, never by selling user data.
Is my data sent to a server?
No. The engine runs as Vanilla JavaScript inside your browser under our Zero-Server Client-Side Execution model. Your figures are computed locally and are never transmitted, logged, or stored.
How accurate is this calculator?
It applies the standard closed-form formula in IEEE-754 double precision, rounding only at the display layer. The engine is reconciled against an independent reference implementation before release.
Does it work on mobile?
Yes. The interface is mobile-first with numeric keypad hints and is tested down to a 320-pixel viewport with no horizontal scrolling.