Running Pace Calculator

The pace-time-distance conversion is the most-asked arithmetic in distance running, and the easiest place to mislead yourself about race-day performance. Pace doesn't stay constant across distances, GPS distance is approximate, and the same calorie cost looks very different at 4 minutes per kilometer than at 6 minutes per kilometer. This page covers the arithmetic the calculator handles, the empirical formulas that predict race times across distances, and the pacing strategies that distinguish well-run races from blow-ups.

Race benchmark paces, at a glance

The pace-finish-distance arithmetic, and where it breaks

Pace × distance = finish time. The conversion is mechanically exact. Where the calculator's output diverges from reality is the implicit assumption that pace stays constant for the full distance. It doesn't. Race pace slows with distance for the same reason that you can sprint 100 metres faster than your average per-100-metre marathon split — the body cannot maintain the same fractional VO2 max output indefinitely.

Empirical scaling: most amateur runners slow about 15–20 seconds per km between 10K and half marathon pace, then another 15–30 seconds between half and full marathon. The same person running a 50-minute 10K (5:00/km) typically runs the half at 5:20/km (~1:52) and the full at 5:40/km (~3:59).

Predicting race performance from another race

Pete Riegel's 1981 formula is the standard tool: T2 = T1 × (D2 / D1)^1.06, where T is time and D is distance. A 50-minute 10K predicts a 1:50:51 half (5:14/km) and a 3:51:42 full marathon (5:29/km). The exponent of 1.06 captures the empirically-observed pace decline with distance.

Riegel is accurate to within a few percent for trained runners with consistent training across the distance range. For undertrained marathon attempts (a runner who races 5Ks regularly but has never done a long run beyond 16 miles), the predicted marathon time often under-states reality by 5–15%. Specific endurance training is required to actualise the time the equation predicts.

Negative splits — why elites run the second half faster

Analysis of marathon majors consistently shows that elite runners run the second half ~30–60 seconds faster than the first half. The amateur pattern is the opposite: amateurs typically positive-split, running the second half 2–5 minutes slower than the first, the cumulative cost of going out too fast.

The mechanism: early-race adrenaline makes intended pace feel easy, so amateurs accelerate slightly above goal pace. The 5–10 seconds per km surplus is invisible at 5K, mild at 10K, and devastating at 30K when glycogen stores deplete and the body switches partially to fat oxidation. The runners who finish strong almost always started 10–15 seconds per km slower than their average target. The first 5K of a marathon should feel almost embarrassingly easy.

The polarised training distribution applied to pace

Most amateur runners train within a 20–30 second per km band around their race pace. Elite runners train across a 90–120 second per km spread: very slow on easy days, very fast on intervals, almost never at race pace. The result is a wider aerobic base and higher top-end speed than the band-trained amateur.

Practical translation: if your goal marathon pace is 5:00/km, easy runs should be 6:00–6:30/km — uncomfortably slow if your ego is involved. Interval work should be at 3:50–4:20/km, faster than you usually train. Most amateurs do neither end and live in the 5:20/km purgatory that builds neither.

Environmental adjustments

• Heat: roughly 1–3% pace penalty per 5°F above 60°F. The 2018 Boston Marathon, run in 38°F and rain (cold but wet), produced average times consistent with normal conditions; the 2012 Boston, in 80°F+ heat, saw amateur finish times slow by 15–30 minutes vs trained pace.
• Hills: lose 10–15 seconds per km on a moderate uphill, gain 5–10 on the corresponding downhill — never even. Net loss on a hilly course vs flat is typically 1–3% over the full distance.
• Altitude: above 5,000 feet, ~1.5–2% pace penalty per 1,000 feet of elevation. Pikes Peak Marathon runners (start 6,300 feet, peak 14,115 feet) accept 30–60% slower times.
• Wind: a 10-mph headwind costs ~3–5 seconds per km; tailwind savings are smaller (asymmetric due to drag mechanics).

GPS accuracy and the "short course" problem

Certified race courses are measured to within 0.1% accuracy along the shortest possible runner's path. GPS watches typically read 0.5–3% long because they sample position every few seconds and don't hug curves precisely. The result: your watch frequently shows you finished a 10K race at 10.2–10.3 km, with an apparent pace 1–2% slower than your actual race pace.

For pace evaluation, the official race time is the truth. For training, GPS pace is approximate. The implication for the calculator: if you input a pace from a GPS watch, expect the predicted finish time on a certified course to be 1–2% faster than the watch suggests.

Conversational pace, threshold pace, race pace

Three pace zones every distance runner should know:

• •Conversational: you can speak in full sentences while running. Most easy runs and long runs. 60–80 seconds per km slower than 10K pace.
• •Threshold (tempo): you can speak in short phrases. Sustainable for 30–60 minutes at max. Roughly 10–15 seconds per km slower than 10K race pace.
• •VO2 max / interval: speech reduced to single words. Sustainable for 3–8 minute reps. ~10–20 seconds per km faster than 5K race pace.

Knowing your real 5K and 10K times anchors all three zones. Without that data point, training paces are guesswork.