Running Pace: How It Is Calculated, What Affects It, and How to Improve

What running pace actually measures

Running pace is the amount of time it takes to cover one unit of distance — usually one kilometre or one mile. It is speed, but flipped. A pace of 5:00 per km means each kilometre takes five minutes, and that is the same physical fact as a speed of 12 km/h — the maths is simply more useful for runners, who can tick off kilometre markers on a watch and compare each split to a target. The running pace calculator on this site takes any distance and finish time and returns the pace per km and per mile, the equivalent speed in km/h and mph, and projected finish times at the four standard road-race distances.

Why bother distinguishing pace from speed at all? Because pace is the unit a runner can actually feel. A 5:00 per km pace is concrete in a way "12 km/h" is not when each kilometre marker tells you whether you ran the last segment faster or slower than the last one. Cyclists prefer speed because they cover ground fast enough that the per-hour framing is more legible; runners prefer pace because the per-kilometre framing matches the rhythm of effort. Both numbers describe the same motion, so the pace calculator shows both.

The pace and speed formulas

The relationship is trivial algebra:

pace = total time ÷ distance

speed = distance ÷ total time

Pace and speed are reciprocals of each other once you sort out the units. If pace comes out in seconds per kilometre, then speed in kilometres per hour is 3600 ÷ pace. Twelve km/h is 300 seconds per km, which is 5:00 per km in minute:second notation. The same kilometre at half that speed (6 km/h, a brisk walk) would take 600 seconds — 10:00 per km.

Converting between pace per kilometre and pace per mile uses the exact NIST factor 1 international mile = 1.609344 kilometres, published in NIST Special Publication 811, Appendix B.8. So pace per mile equals pace per kilometre multiplied by 1.609344. A 5:00 per km pace is 5 × 1.609344 = 8.047 minutes per mile, or about 8:02.8 per mile. As a rule of thumb, pace per mile is about 60 % slower than pace per km, because a mile is about 60 % longer than a kilometre. The pace calculator uses the exact factor internally, so you never need to round mid-calculation.

The standard race distances

World Athletics — the governing body for the sport, formerly the IAAF — sets the official road-race distances in Technical Rule TR4.3. The seven recognised distances are 5 km, 10 km, 15 km, 20 km, half marathon at 21.0975 km, 25 km, 30 km, and marathon at 42.195 km. Of these, the 5K, 10K, half marathon and marathon are the four that dominate amateur racing, and they are the four the pace calculator projects finish times for.

The marathon distance has a story behind it. The 1908 London Olympics ran the marathon from Windsor Castle to the White City stadium — about 26 miles — with an extra 385 yards tacked on so the finish line would sit in front of King Edward VII's royal box. That distance, 26 miles 385 yards = 42.195 km, was adopted by the IAAF as the official marathon distance in 1921 and has not changed since. The half marathon is exactly half of this: 21.0975 km, or 13 miles 192.5 yards. Five kilometres is 3.107 miles and 10 km is 6.214 miles.

Worked example: 5 km in 25 minutes

Take a 5 km parkrun finished in 25 minutes flat. Pace per km is 25 ÷ 5 = 5:00 per km. Speed is 5 km ÷ (25/60) h = 12.00 km/h. Converting to mph: 12 × 0.6213712 = 7.46 mph. Pace per mile is 5:00 × 1.609344 = 8:02 per mile.

Now project that pace to the longer distances. Maths only, no fatigue correction yet:

10 K: 10 × 5:00 = 50:00.
Half marathon: 21.0975 × 5:00 = 105:29 — that is one hour, 45 minutes and 29 seconds.
Marathon: 42.195 × 5:00 = 210:59, which is three hours, 30 minutes and 59 seconds.

Those are the numbers the pace calculator returns when you enter 5 km and 25:00. They are mathematically correct projections — but they are also, as the next section explains, the optimistic ceiling rather than a realistic prediction.

Why long-distance projections overestimate (and how to correct)

Constant-pace projection assumes a runner can hold the same pace for forty-two kilometres that they held for five. Almost nobody can. Aerobic capacity, glycogen stores, thermoregulation and muscle fatigue all degrade across hours of running, so the further the prediction extrapolates from the run you actually finished, the more it will overestimate.

The classic correction is the Riegel formula, published by Pete Riegel in a 1981 paper "Athletic Records and Human Endurance" (American Scientist, vol. 69). It models the slowdown as a power law:

T₂ = T₁ × (D₂ / D₁)^1.06

where T₁ is your known finish time over distance D₁, and T₂ is the predicted time over the longer distance D₂. The exponent 1.06 is empirically fitted — anything above 1.00 means each doubling of distance costs more than a doubling of time. Apply it to the worked example: a 25-minute 5K predicts a marathon time of 25 × (42.195 / 5)^1.06 ≈ 25 × 9.62 = 240 minutes, or four hours flat. The pure-pace projection said 3:30:59. The fatigue correction adds roughly 29 minutes — about 14 % — and that is the more honest number for race-day planning.

The Riegel exponent is not a constant for everyone. Elite marathoners with deep aerobic conditioning hold closer to 1.04; casual runners with limited long-distance training are nearer 1.08 or higher. Use 1.06 as a default and adjust if your own race history says otherwise. Jack Daniels' VDOT tables are an alternative model that incorporates VO₂ max equivalents and works well for trained runners. Either way, the pace calculator here returns the pure-pace projection — use it to plan target pace per km, then apply Riegel or VDOT for race-day expectations.

Factors that affect pace

Training volume and intensity

The biggest lever, by a wide margin, is weekly mileage and the quality of that mileage. Runners who consistently log 60-100 km per week with a mix of easy aerobic running, tempo intervals and a long run see substantial pace improvements over months and years. Genetic ceiling matters at the elite level, but almost every recreational runner is well below their own ceiling and can drop their 5K pace by 30-60 seconds per km with two years of structured training.

Terrain and elevation

Hills slow you down going up by more than they speed you up going down. A 5 % gradient typically costs 15-25 seconds per km on the ascent and gives back only 5-10 seconds on the descent of equal length. Trail surfaces, sand, snow and mud all slow pace further, sometimes by minutes per kilometre. Pace projections from the pace calculator assume the runner can sustain the same effort across the projected distance, which is reasonable on a flat road but optimistic on a hilly trail.

Heat and humidity

Pace degrades sharply above about 12 °C ambient temperature for most runners. Research published in the Journal of Applied Physiology shows marathon finish times slow by roughly 1.5-3 % for every 5 °C rise above the optimal range, with humidity compounding the effect because evaporative cooling becomes less effective. A 3:30 marathoner in 8 °C conditions might run 3:38-3:45 in 22 °C, all else equal. The London Marathon's slowest years almost always correlate with the warmest race days.

Body composition and fuel

Carrying excess weight directly slows pace because more energy is needed to move each step. The often-cited rule of thumb is that each kilogram of weight loss is worth around 2-3 seconds per kilometre at moderate paces. Glycogen stores set the upper limit on how far you can sustain marathon-equivalent pace before "hitting the wall" — typically around 30-35 km if you have not fuelled. The carbohydrate calculator helps with daily intake; race-day fuelling is a separate protocol of 30-90 g carbs per hour during the run.

Pacing strategy itself

Even pacing produces faster finish times than positive splitting (starting faster than you finish) for almost everyone. The world records for the marathon are run with the second half within seconds of the first half. Amateur runners often start too fast, blow up around 25-30 km, and finish minutes slower than an evenly paced run would have produced. Use the pace calculator to set a target average pace, then aim to run each 5K split within 2-3 seconds per km of that target.

How to improve your pace

Pace improvement at amateur level is mostly about consistency over months, not heroic individual workouts. The methods that repeatedly produce results in published training studies:

Run more total kilometres, mostly easy. Lydiard, Daniels and modern elite training plans all converge on around 80 % of weekly volume at conversational pace, with the remaining 20 % at moderate or hard intensity. Easy running builds aerobic capacity without breaking down the body, and aerobic capacity is the single biggest determinant of race pace across 5K to marathon.

Add one weekly long run. Build up to a long run that is 25-30 % of weekly mileage. For a 50 km/week runner, that is a 12-15 km long run. The long run trains glycogen efficiency, mitochondrial density and the mental skill of holding pace when tired.

Add one weekly tempo or interval session. Tempo runs at lactate-threshold pace (about 10K race pace for 20-40 minutes) and interval workouts (5-10 reps of 400-1000 m at 5K pace or faster) raise the ceiling of sustainable pace. One quality session per week is enough for most amateurs; two is the maximum before injury risk climbs.

Strength train twice a week. Heavy compound lifting — squats, deadlifts, lunges — improves running economy by 2-5 % across most studies. Better economy means the same pace costs less oxygen, which means you can hold the pace longer.

Lose body fat if there is fat to lose. Sustainable weight loss at 0.3-0.5 kg per week, without compromising training volume, tends to produce the biggest pace gains per unit of effort. The healthy weight calculator sets a realistic target; the calorie calculator sets the daily deficit.

Sleep eight hours. Sleep deprivation degrades VO₂ max, reaction time and perceived exertion. The runners who improve fastest are usually the ones who sleep well, not the ones who train hardest.

Common mistakes

Confusing average pace with current pace. The average pace over a 10 km run with a 4-minute first kilometre and a 6-minute last kilometre is 5:00 per km, but neither kilometre was actually run at that pace. When the watch shows "average pace 5:00" mid-run, that is a summary of the whole run so far, not a target for the next kilometre.

Projecting marathon time from a single 5K. Riegel and VDOT models work better with race times from two or three different distances, because a single time confounds aerobic fitness with race-specific endurance. A runner who has done a 5K but never run further than 8 km in training will underperform a Riegel prediction by 10-20 % in their first marathon. Build the training base before trusting the projection.

Ignoring the metric/imperial unit switch. A 7:00 split on the watch could be 7:00 per km or 7:00 per mile — those are 4:21 per km and 4:21 per mile, respectively. Set the watch unit deliberately, then stick to it for the whole training block. The pace calculator shows both side by side so you can sanity-check your watch.

Treating pace as a constant target across terrain. A 5:00 per km flat-road pace becomes maybe 5:25 per km on a rolling course and 6:00+ per km on serious trails at the same heart rate. Train by effort, race by pace where the course allows.

When to seek a coach

Most runners do well with a generic plan from a reputable source — Hal Higdon, Jack Daniels, Pete Pfitzinger — for as long as they are still improving on it. A coach earns their cost when one of three things happens: progress stalls despite consistent training, recurrent injuries suggest a biomechanical issue, or a specific race goal needs individualised periodisation (a Boston-qualifying marathon, for example). For pure recreational running, the pace calculator, a heart-rate monitor and a written plan are usually enough.

Frequently asked questions

How accurate are the projected finish times? They are mathematically exact projections of the entered pace, but they assume constant effort across the projected distance — which is unrealistic for projections that stretch much beyond the original distance. A 5K time used to project a marathon will overestimate the marathon time by roughly 10-15 % for most amateur runners. Use the pure-pace number as the upper bound and apply the Riegel correction (or a published table like Jack Daniels' VDOT) for race-day expectations.

What is a good 5K time for a recreational runner? parkrun median finish times sit around 28-32 minutes depending on event and demographics, so anything under 25 minutes is solid for a casual runner. Sub-20 minutes is club-quality and sub-18 is competitive at most local races. World Athletics outdoor world records are 12:35 (Joshua Cheptegei, 2020) and 14:00 (Beatrice Chebet, 2024).

Why does the calculator use 1.609344 for mile to km? That is the exact, internationally agreed conversion factor for one international mile to kilometres, published in NIST Special Publication 811, Appendix B.8. The earlier US survey mile differed by about 3 mm per mile and was formally retired in 2022. For all modern road racing, the international mile is the one that matters.

Is pace per kilometre or per mile better to train with? Use whichever matches the race you are training for. UK, European and most international road races use kilometre markers, so pace per km is the natural target. US road races almost universally use mile markers, so pace per mile is more natural there. Track sessions in metric units use per-km splits; on a 400 m track, that is one and a quarter laps per split.

Can I improve my pace at any age? Yes, within limits. Untrained runners of any age can drop their 5K pace substantially in the first 12-24 months of consistent training. After age 35, peak aerobic capacity declines at roughly 5-7 % per decade, but training can offset most of that decline well into the sixties. Masters runners (40 plus) regularly set personal bests after years of training, especially if they came to running later in life.

How does pace relate to calories burned? Faster pace burns slightly more calories per kilometre, but the dominant variable is body weight and total distance, not pace. A 70 kg runner burns roughly 70 kcal per kilometre at any pace from easy jog to 5K race pace. The difference between paces becomes meaningful at sprint intensities and over long durations. The calorie calculator and BMR calculator handle the daily totals; running adds to those numbers in proportion to distance more than pace.

Why does the marathon end in such an odd distance? The 42.195 km figure dates to the 1908 London Olympics. The course ran from Windsor Castle to the White City stadium, about 26 miles, with an extra 385 yards added so the finish would be in front of King Edward VII's royal box. The resulting distance — 26 miles 385 yards — was adopted by the IAAF as the official marathon distance in 1921 and every World Athletics marathon since has used it. The half marathon, at exactly half of this, came along later.