Tools · Health & Fitness

Running Pace Calculator

Fill in any two of pace, time and distance, and the third follows. Everything is entered and returned in minutes and seconds, because a pace of 5.5 minutes per kilometre is 5∶30 — and reading it as 5∶50 puts every split twenty seconds out.

Minutes and seconds throughout, never decimal minutesHow it worksInputs stay on this device
Your inputs

Fill any two

The one you pick becomes the answer; the other two become the inputs.

Pace is per kilometre, and the race markers convert to match.

How far you ran, or plan to. A marathon is 42.195 km.

Whole minutes per kilometre — the part before the colon.

The part after the colon. 5∶30 is 5 and 30, never 5.5.

Your inputs are calculated locally and are not stored.
Finish time55:00

10 km at 5:30 per kilometre takes 55:00. Held all the way to a marathon, the same pace is 3:52:04.

Pace
5:30 per km
Speed
10.91 km/h
Finish time
55:00
Distance
10 km
Cumulative time at each marker, and at the standard race distances, if the pace holds
DistanceRaceElapsed
1 km5:30
2 km11:00
3 km16:30
4 km22:00
5 km5K27:30
6 km33:00
7 km38:30
8 km44:00
9 km49:30
10 km10K55:00
21.0975 kmHalf marathon1:56:02
42.195 kmMarathon3:52:04
Formula & methodology

One relationship, rearranged three ways

Pace, time and distance are a single equation. Name any two and the third is fixed — there is no modelling, no fitted curve and nothing to disagree with.

t = p × d  •  p = t ÷ d  •  d = t ÷ p
t
Elapsed time, in seconds
p
Pace, in seconds per kilometre or per mile
d
Distance, in the same unit the pace uses

The engine behind this page works entirely in seconds and never handles a minutes value at all. Minutes exist only in the two input boxes and in the display, and the conversion between the two happens in exactly one function — which is why the headline figure, the breakdown and the splits table can never disagree about what 330 seconds means.

Speed is the same relationship inverted: 3600 ÷ pace. A pace of 330 seconds per kilometre is 10.91 km/h. Runners talk in pace and cyclists in speed, and the two are the same number upside down.

Worked example

10 km at 5∶30 per kilometre

A pace of 5 minutes 30 seconds is 330 seconds. Ten kilometres at 330 seconds each is 3,300 seconds, and 3,300 seconds is 55 minutes exactly — so the finish time is 55∶00, with the 5K marker passed at 27∶30 and every kilometre marker 5∶30 after the last.

Run the same arithmetic out to the race distances and the marathon row reads 42.195 × 330 = 13,924 seconds, or 3∶52∶04. That figure is arithmetically correct and physiologically optimistic. Riegel’s endurance formula — 55∶00 × (42.195 ÷ 10)1.06 — puts the same runner at about 4∶13∶01, twenty-one minutes slower, and the gap is not an error in either calculation. It is what fatigue costs over four hours, and no amount of multiplication can see it.

Turn the question around and the answers stay consistent. Ask for the pace instead — 55∶00 over 10 km — and you get 330 seconds, 5∶30, not the 5.5 a keypad shows. Ask for the distance from 55∶00 at 5∶30 and you get 10 km back.

Assumptions

What this calculator assumes

  • The pace holds. Every row of the splits table is one pace multiplied by one distance. Most runners positive-split — the second half is slower than the first — so the table is a target to run against, not a prediction of what the watch will say.
  • No fatigue, terrain or weather model. Hills, heat, wind, altitude and how long you have been training are all absent. Two runners with the same 10K pace can be an hour apart over a marathon.
  • The distance is the course distance. Races are measured along the shortest legal route; a GPS watch records the line you actually ran, which is longer. A watch reading 42.5 km at the end of a marathon is normal and means your true pace was slightly faster than the watch reported.
  • Whole seconds. Results are rounded to the second, which is how paces and finish times are quoted everywhere outside a track meet. A mid-table row can therefore sit one second away from a hand multiplication of the displayed pace; the finish row always matches the total.
  • The mile is exactly 1609.344 metres. That has been the definition since 1959, so switching units introduces no error of its own.
Common questions

Running pace FAQ

Why is 5.5 minutes per kilometre 5∶30 and not 5∶50?

Because time is counted in sixties, not tens. Half a minute is 30 seconds, so 5.5 minutes is 5 minutes 30 seconds. The decimal 0.5 and the clock 50 look alike and mean different things — 5∶50 would be 5.833 minutes. This is the single most common error in pace arithmetic, and it is why this calculator never asks for or shows a decimal minute: you enter minutes and seconds in separate boxes, and every figure it returns is already in m∶ss.

Why is a marathon 42.195 km rather than a round number?

It is 26 miles 385 yards, which is the length of the 1908 Olympic course in London, from Windsor to the stadium at White City. That distance was adopted as the standard marathon in 1921 and has not moved since — so the metric figure is a conversion of an imperial oddity, and the imperial figure is an oddity because of how one particular course happened to be laid out. The half is exactly half of it: 21.0975 km, or 13 miles 192.5 yards.

Can I predict my marathon time from a 10K pace?

Not by multiplying, which is all a splits table does. Hold 5∶30 per km for 10 km and you finish in 55∶00; multiply that pace out to 42.195 km and you get 3∶52∶04, and almost nobody runs that. Pete Riegel's endurance formula — old time × (new distance ÷ old distance) raised to the power 1.06 — puts the same runner nearer 4∶13, and even that assumes the marathon training to back it up. Treat the long rows of the splits table as a pace target, not a forecast.

What is a negative split, and why is it rare?

A negative split is running the second half of a race faster than the first. Most runners do the opposite: they start faster than planned, and fatigue, heat and hills take the pace back later. That is why an even-pace table is best read as the line you are trying not to drift above — a race run 10 seconds per kilometre too fast for the first 10 km rarely gets those seconds back.

How do I convert a pace per kilometre into a pace per mile?

Multiply by 1.609344, the exact number of kilometres in a mile. 5∶30 per kilometre is 330 seconds, and 330 × 1.609344 is 531 seconds, which is 8∶51 per mile. Switching the unit toggle above does this for you, but it also reinterprets the distance you typed — 10 becomes 10 miles, not 10 kilometres — so check that field after you switch.

Primary sources

Sources and review notes

  1. World Athletics — the competition rules that fix the standard road distances, including the marathon at 42.195 km and the half at 21.0975 km
  2. NIST Special Publication 811 — the international mile as exactly 1609.344 metres, which is the only conversion factor this tool uses

The arithmetic here has no data behind it to go stale: a multiplication, a division, and one exact unit conversion. The sources above are cited for the race distances and the definition of the mile, not for the calculation.