Running Pace Calculator

Pace is a division, speed is its reciprocal

Runners live in seconds per kilometre; cyclists and cars live in kilometres per hour; shop sensors, apps and race results report any of the three. This page takes the two raw inputs everyone has — a distance and a time — and converts them into the whole family at once: pace per kilometre, pace per mile, average speed in km/h and in mph. Pace and speed are the same trip expressed upside-down, so the panel gives you the number in the unit of whichever conversation you have joined, without the mental flip that consistently produces a hundred metres of misplaced confidence.

The division is tiny, and that is the trap: 10 km in 50 minutes is 5.0 minutes per kilometre, but 21.0975 km in 110 minutes is 5.2 minutes per kilometre and no human can multiply 5.2128 by 60 in their head without a slip. The tool's output is already in minutes and seconds — 5:13 per km — which is the form the runner's watch, the training plan and the race guide all expect.

A worked example, step by step

Problem: a runner completed 10 km in 50 minutes on a training loop. What pace should a 10K race plan show at the same effort, and what is that in miles?

1. Pace per km = time ÷ distance = 50 ÷ 10 = 5.0 minutes = 5:00 per km.
2. Pace per mile = 5.0 × 1.609344 = 8.04672 minutes → 8:03 per mile.
3. Speed = distance ÷ time = 10 ÷ (50 ÷ 60) = 12 km/h → 7.46 mph.
4. Meaningful read: 5:00 per km is a solid sub-50 10K effort, sitting between "easy long run" and "10K race pace" for most club runners.
5. Race projection at the same effort: a half marathon (21.0975 km) at that pace takes 21.0975 × 5.0 ≈ 105.5 minutes.

The conversion chain is where the value sits: one distance-time pair feeds four useful numbers, and each lives in a different context — the watch shows min/km, the treadmill shows km/h, the training partner asks in mile splits, the race web site prints target times.

Race targets and the pace they need

The two 5:41 rows are the same maths one size apart: a two-hour half and a four-hour marathon are the identical pace, which is why "two-hour half" plans map directly onto "four-hour marathon" training blocks.

Entering the time correctly

The tool wants decimal minutes: 52 minutes 30 seconds is 52.5, not 52.30 — the latter reads as 52 minutes 18 seconds and silently flatters your pace. If your watch reports "52:30", convert once as 52 + 30 ÷ 60. Everything downstream — per-km, per-mile, speed — inherits whatever you type, so this single field is the accuracy bottleneck of the page. Decimal minutes also make plans easy to compare: 5.5 minutes per km versus 5.2 is a 3.5% gap, which is a tier in training, not a rounding artefact.

Mistakes that quietly rewrite a training pace

• Typing mm:ss into a decimal field. 9.45 is 9 minutes 27 seconds, not 9:45; every reading downstream inherits the confusion.
• Using wall-clock time for a run with stops. Coffee-shop minutes dilute the pace; use moving time for the number that plans care about.
• Reading miles-per-hour as pace. Higher speed numbers are faster; higher pace numbers (more seconds per km) are slower — the direction flips and surprises everyone at least once.
• Rounding mid-conversion. 8.04672 truncates to 8 minutes flat; at half-marathon distance that shortcut rewrites your finish by tens of seconds.
• Comparing a hilly loop with a track time. Same pace, different effort; grade matters and this tool is the honest record of the flat case.

Keep exploring

• BMI Calculator — the other half of a training-health conversation, from height and weight.
• Water Intake Estimator — hydration targets scaled to session length.
• Statistics Calculator — summarise a season of paces: mean, median and spread of the runs you actually did.
• Guide: BMI and Calorie Estimates Explained.