Running Pace Calculator

How this calculator works

Pace is one division. The calculator converts whatever distance unit you chose into a common base, converts your hours, minutes and seconds into total seconds, and divides. Everything else on the page — the split table, the speed conversions — comes from that single quotient.

The split table assumes you hold an even pace, which nobody does. Treat those numbers as the pacing plan, not the prediction. Most runners are two to four seconds per mile quicker than target through the first mile of a road race and pay for it in the last three.

A worked example

A runner finishes a half marathon in 1:52:30. That is 6,750 seconds over 21.0975 kilometres, or 13.1094 miles. Divide and you get 319.9 seconds per kilometre and 514.9 seconds per mile — 5:20 per kilometre, 8:35 per mile. Average speed is 3.13 metres per second, which is 11.25 km/h.

Now the useful part. At 3.13 m/s, the 10-kilometre mark arrives at 53:19. If the runner crossed 10 kilometres in 51:40 they ran the first half of the race roughly 1:39 too fast, and the story of that finish time is a positive split, not a pacing plan. This is the reason the split table exists: pace on its own tells you what happened, splits tell you why.

The other two tools on this page

The unit converter exists because most runners live in one system and race in another at some point. It applies the single conversion factor — one mile is 1.609344 kilometres — in both directions. The useful mental shortcut it encodes: multiply a per-kilometre pace by about 1.6 to get per-mile, so 5:00 per kilometre is roughly 8:03 per mile.

The speed converter matters mainly for treadmills, which display speed rather than pace. A belt set to 7.0 mph is 8:34 per mile, and having that number in your head before you step on saves the arithmetic mid-session. Speed and pace are reciprocals, so the conversion is 3600 divided by speed in km/h to get seconds per kilometre.

Three ways runners misuse pace

Averaging a pace that was never run

An average pace of 8:35 can describe a beautifully even race or a runner who went out at 7:50 and limped home at 9:30. Both produce the same headline number and completely different training conclusions. Always look at the distribution before you draw a lesson from the mean.

Treating pace as a fixed personal attribute

Pace is a readout of the conditions you ran in as much as the fitness you brought. Ten degrees of extra heat, a 300-metre climb, a headwind on an exposed causeway, three hours of sleep — each of these moves pace without touching fitness. Runners who anchor their identity to a number get discouraged by weather.

Converting between distances by simple multiplication

Doubling your 5K pace does not give your 10K pace, and it certainly does not give your marathon pace. Endurance decays with distance in a predictable but non-linear way. That is what the race time predictor handles, and it uses an exponent rather than a multiplier for exactly this reason.

Miles, kilometres and the awkward middle

One mile is 1.609344 kilometres, a conversion factor precise by international agreement since 1959. The practical consequence for runners is a useful mental shortcut: your per-mile pace is roughly your per-kilometre pace multiplied by 1.6, so 5:00 per kilometre is close to 8:03 per mile and 4:00 per kilometre is close to 6:26.

The marathon is 42.195 kilometres because of a 1908 London course length that was later fixed as the standard, which is why the distance refuses to be a round number in either system. The half is exactly half of it, 21.0975 kilometres, and the calculator uses those exact figures rather than the rounded 26.2 and 13.1 that appear on race merchandise. Over a marathon the difference between 42.195 and 42.16 kilometres is about five seconds of predicted finish time — small, but there is no reason to accept an avoidable error.

What this calculator will not tell you

It will not tell you whether the pace is sustainable. That question needs a fitness input, and pace alone contains none. If you want a defensible target for a race you have not run yet, start with a recent result and use the predictor. If you want to know which paces to train at, the training pace calculator derives them from a performance rather than from a wish.

It also will not adjust for terrain. A 9:00 mile up a five percent grade is a substantially harder effort than a 9:00 mile on the flat, and the treadmill and grade calculator exists to put a number on that gap.