Running Pace Calculator

Enter the distance you ran and the time it took, and the calculator shows your pace per kilometer, pace per mile, and average speed in km/h and mph. The distance can be logged in either unit — both pace figures always appear, converted at exactly 1.609344 km to the mile. Runners use it to set a race target, check a watch reading, or translate a friend's mile pace into familiar terms. Read the primary result, pace per kilometer, as minutes and seconds for every kilometer you cover: a lower number is faster.

Pace and speed from the same three numbers

Pace is elapsed time divided by distance, and speed is the same fraction the other way up:

pace = T ÷ d, speed = 3600 × d ÷ T

with T in seconds and d in whichever unit you care about. Taking the defaults, 10 km in 0:52:30 gives T = 52 × 60 + 30 = 3,150 seconds. Per kilometer that is 3,150 ÷ 10 = 315 seconds, shown as 5:15. Ten kilometers is 6.2137 miles, so the mile pace is 3,150 ÷ 6.2137 ≈ 507 seconds, or 8:27. Average speed is 10 km ÷ 0.875 hours = 11.43 km/h, equal to 7.10 mph. The result is always an average across the whole distance: a run that started slow and finished fast lands on the same figure as a perfectly even one, so pace tells you what happened overall, not how the effort was distributed.

Where the idea of pace comes from

The word pace descends from the Latin passus, a full stride, and for most of history a pace was a unit of ground rather than a rate of effort. Turning it into time-per-distance needed two things that arrived late: standard distances and accurate clocks. Competitive running is ancient — the stadion sprint at Olympia was a single length of the track — but pace as runners now use it belongs to the era of the measured course and the stopwatch.

Distances hardened into fixed numbers only gradually. The mile comes from the Roman mille passuum, a thousand paces, yet its exact modern length — 1,609.344 metres, or 1.609344 km — was not settled until the 1959 International Yard and Pound Agreement defined the yard as precisely 0.9144 metre. That single ratio is what lets any pace-per-km convert cleanly to pace-per-mile, and it is the number this tool uses. On the track the metric system won outright: races settled on the 400-metre lap, so a 10,000-metre race is twenty-five laps and the kilometer became the natural yardstick for pace.

The marathon shows how arbitrary a standard distance can be. The first modern Olympic marathon, proposed for the 1896 Athens Games by the French philologist Michel Bréal, ran roughly 40 km from the town of Marathon to Athens, echoing the legend of a messenger, usually named Pheidippides, who was said to have carried news of victory over Persia and died on arrival. The earliest surviving source, Herodotus, writing decades after the battle, tells a different story: a runner sent from Athens to Sparta, more than 240 km, to ask for help, with no death and no run back from Marathon. That second errand surfaces only centuries later, in Plutarch, who names the herald Thersippus or Eucles, and in Lucian, who supplies the collapse and the dying words. Robert Browning's 1879 poem welded the two together under the name Pheidippides, and that composite is the version the Games inherited. The 42.195 km distance now used everywhere comes from the 1908 London Games, whose course ran from Windsor Castle to the White City Stadium and closed with a partial lap of the track. The International Amateur Athletic Federation made that figure official in May 1921.

From trackside stopwatch to the wrist

Knowing pace during a run, rather than after it, is a recent luxury. For most of the twentieth century the tools were a stopwatch at the trackside and markers every lap or mile, and a runner learned pace by hearing split times called out. Holding a target pace was therefore a job delegated to pacemakers, and the most celebrated instance is Roger Bannister's first sub-four-minute mile on 6 May 1954 at Oxford's Iffley Road track, run in 3:59.4. Chris Brasher led the opening two laps and went through halfway in 1:58, Chris Chataway then took the front and passed three-quarters in 3:01, and Bannister kicked from there. Even that run was not evenly paced — the third lap was the slowest of the four — which is precisely the drift a live pace readout now exposes while there is still time to correct it.

The measurement moved onto the wrist in 2003, when Garmin released its first Forerunner watches. A GPS receiver could log distance and display live pace on any road, with no measured track required, and within a few years pace-per-km was something an ordinary runner could read mid-stride. The same period gave the weekly 5K its modern hold: parkrun began when Paul Sinton-Hewitt started a single free timed run with thirteen runners in London's Bushy Park on 2 October 2004, and the format has since made a 5K time a common shorthand for everyday fitness.

Common target paces

The table shows what a few round paces produce over the two most raced distances. The marathon column assumes the pace holds for all 42.195 km, which takes specific training rather than optimism.

What a pace does and does not predict

Holding 5:15 per km for 10 km does not mean you can hold it for a marathon. The standard correction is Peter Riegel's endurance formula: predicted time equals known time × (new distance ÷ known distance)^1.06. Riegel, a research engineer at the Battelle Memorial Institute in Columbus, Ohio, introduced the idea in Runner's World in August 1977 in a piece called Time Predicting, then set it out fully in the May–June 1981 issue of American Scientist under the title Athletic Records and Human Endurance. He fitted the 1.06 exponent to record data for running, swimming and walking, and found it held across efforts in the endurance range, lasting roughly 3.5 to 230 minutes. Applied to the default 52:30 10K, it predicts roughly 1:56 for a half marathon and 4:01 for a marathon — a full 20 minutes slower than naive pace scaling. Even that assumes you have trained for the longer distance. Heat, hills, and a fast opening split all push real finishes further out, and predictions across more than about a fourfold jump in distance grow unreliable.

Min per km or min per mile

The US runs on min per mile, and American treadmills display mph. Continental Europe, Canada, and Australia use min per km throughout. The UK sits in between: races are 5K and 10K, yet many British club runners still think in min per mile because road distances are signed in miles. Watches and apps let you pick either, and this calculator simply shows both, so a mile-pace target and a kilometer-pace target read side by side.

Pace figures are arithmetic, not fitness advice; build up to new race distances gradually and check with a physician if unsure. See the site disclaimer.

Frequently asked questions

What pace do I need to break 4 hours in a marathon?

A 3:59:59 marathon means averaging 5:41 per kilometer, or 9:09 per mile, over the full 42.195 km. Most training plans target slightly faster — around 5:35 per km — to leave a buffer for water stations and the crowded opening kilometers. Enter 42.195 km and 3:59:00 here to see the exact numbers.

How do I convert pace per km to pace per mile?

Multiply by 1.609344, since a mile is that many kilometers long. A 5:00 per km pace is 300 seconds, and 300 × 1.609344 ≈ 483 seconds, which is 8:03 per mile. Going the other way, divide: an 8:00 mile works out to 4:58 per kilometer.

Is 5:15 per kilometer a good running pace?

It is a solid recreational pace — 11.43 km/h, a 52:30 10K, and about a 1:50:46 half marathon if held the whole way. For context, the median parkrun 5K finish in the UK is around 32 minutes, or 6:24 per km, so 5:15 per km is comfortably quicker than the typical weekend runner.

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

Roughly, with Riegel's formula: multiply the 10K time by (42.195 ÷ 10) raised to the power 1.06, a factor of about 4.6. A 52:30 10K therefore predicts a marathon just over 4 hours. The prediction assumes the long-run training has been done; without it, expect to finish 15 to 30 minutes slower.