Running Pace Calculator

What Is Running Pace?

Pace is a rate expressed as time over distance, and it is written the way a clock reads: 5:00 per kilometer means five minutes and zero seconds to cover each kilometer. Speed and power both climb as a run gets faster. Pace is the exception — a smaller number is a faster run, and 4:30 beats 5:00 by thirty seconds on every kilometer you cover.

Runners work in pace rather than speed because race distances are fixed and pace multiplies straight into a finish time. Hold 5:00 per kilometer and 10 km takes exactly 50 minutes; the same pace over the 42.195 km marathon comes to 3:30:59. Nothing about a speed of 12.00 km/h tells you that as directly.

Pace and Speed Are One Number Upside Down

The two figures this calculator prints are not independent measurements. Each is the other divided into 3,600, the number of seconds in an hour:

speed in km/h = 3,600 ÷ pace in seconds per km
pace in seconds per km = 3,600 ÷ speed in km/h

So 5:00 per kilometer is 300 seconds, and 3,600 ÷ 300 is 12.00 km/h. Slow to 6:00 and the speed falls to 10.00; lift to 4:30 and it rises to 13.33. Because the relationship is a division rather than a subtraction, equal steps in pace are not equal steps in speed: moving from 7:00 to 6:00 adds 1.43 km/h, while moving from 4:00 to 3:00 adds 5.00.

That curvature is the practical argument for pace. Thirty seconds per kilometer means the same thing to a five-minute runner and a nine-minute runner — five extra minutes over 10 km either way — whereas one km/h means very different things at each end.

Minutes per Kilometer and Minutes per Mile

Two conventions are in daily use. Most of the world works in minutes per kilometer. Road running in the United States and much of the United Kingdom quotes minutes per mile. Converting between them is one multiplication, because the international mile is exactly 1,609.344 meters, as NIST’s conversion table gives it.

minutes per mile = minutes per kilometer × 1.609344
minutes per kilometer = minutes per mile ÷ 1.609344

A 5:00 kilometer is an 8:03 mile. An 8:00 mile is a 4:58 kilometer. Reading one unit as though it were the other is the expensive mistake, and the size of it is the conversion factor itself: a 5:00 pace per mile is 61 percent faster than a 5:00 pace per kilometer.

This calculator always answers per kilometer. Its code multiplies a mile entry by 1.60934 rather than the exact 1.609344, a difference of about 2.5 parts per million. That is under a hundredth of a second per kilometer at any pace a human runs, and far below the whole second the panel rounds to.

How Do You Calculate Running Pace?

One division does the whole job, and everything else on this page is that division rearranged or repeated. You can reproduce every figure below on a phone calculator, which is the point of showing the steps rather than only the answers.

The Running Pace Formula

The arithmetic the tool runs, in the order it runs it:

total seconds  = hours × 3,600 + minutes × 60 + seconds
distance in km = miles × 1.60934      (only when the unit is set to Miles)

pace in seconds per km = total seconds ÷ distance in km
speed in km/h          = distance in km ÷ (total seconds ÷ 3,600)

The pace in seconds is then split back into clock units for display: whole minutes are the pace divided by 60 and rounded down, and the leftover seconds are rounded to the nearest whole second. An hours field appears in front only when a single kilometer takes longer than an hour, which is why a walk of 2 km in 3 hours reports 1h 30m 0s per km while everything faster reports minutes and seconds alone.

Nothing else enters the equation. Not your weight, not the hills, not the wind, not whether you stopped at a crossing. Two runs sharing a distance and a time are the same run as far as this formula is concerned.

Step by Step

To work a pace out by hand, or to check what the panel returned:

• Turn the time into seconds. 50 minutes is 50 × 60 = 3,000 seconds; 1 hour 55 minutes is 3,600 + 3,300 = 6,900.
• If you ran in miles, turn the distance into kilometers: 6 miles × 1.60934 = 9.656 km.
• Divide the seconds by the kilometers. 3,000 ÷ 10 = 300 seconds per kilometer.
• Split that back into minutes and seconds. 300 seconds is 5 minutes 0 seconds; 335.5 seconds is 5 minutes 36 seconds once the remainder rounds.
• For the speed, divide the kilometers by the hours. 10 ÷ (3,000 ÷ 3,600) = 12.00 km/h.

Step two is the one to watch. Convert the distance before dividing, never after — dividing a time by a mileage and then multiplying that answer by 1.609 gives a pace per kilometer roughly two and a half times too slow.

Worked Example: 10 Kilometers in 50 Minutes

Enter 10 in Distance, leave the unit control on Kilometers, then put 0 in Hours, 50 in Minutes and 0 in Seconds, and press Calculate.

50 × 60 = 3,000 seconds
3,000 ÷ 10 km = 300 seconds per km
300 seconds = 5 minutes 0 seconds
10 ÷ (3,000 ÷ 3,600) = 12.00 km/h

What the result panel returns

Distance: 10 km, Time: 0h 50m 0s, Pace: 5m 0s per km, Average Speed: 12.00 km/h

That whole line is the readout. This formula returns a single sentence rather than the pipe-separated segments other calculators here use, so nothing appears in the breakdown rows beneath the big number — the four clauses stay together, and a Copy result button underneath puts them on your clipboard.

Five minutes per kilometer is 8:03 per mile. Carried across the standard distances it gives 25:00 for 5K, 50:00 for 10K, 1:45:29 for a half marathon and 3:30:59 for a marathon.

Worked Example: Six Miles in 54 Minutes

Now the imperial path. Set the unit control to Miles, enter 6 in Distance, then 0 hours, 54 minutes and 0 seconds. Fifty-four minutes over six miles is exactly nine minutes a mile.

6 × 1.60934 = 9.656 km
54 × 60 = 3,240 seconds
3,240 ÷ 9.656 = 335.5 seconds per km
335.5 seconds = 5 minutes 36 seconds
9.656 ÷ 0.9 = 10.73 km/h

What the result panel returns

Distance: 6 mi, Time: 0h 54m 0s, Pace: 5m 36s per km, Average Speed: 10.73 km/h

Read the echo carefully. “Distance: 6 mi” is your own entry played back with the unit code rather than the word, and it is the last imperial thing on the line: the pace is per kilometer and the speed is in km/h, not mph. A nine-minute mile is a 5:36 kilometer and 10.73 km/h, and that holds at any distance — five miles in 45:00 and three miles in 27:00 both return the identical 5m 36s per km at 10.73 km/h.

To read the answer back in miles, multiply the pace by 1.609: 5 minutes 36 seconds is 336 seconds, and 336 × 1.609 is 541 seconds, or 9:01. The one-second drift from the 9:00 you actually ran is the whole-second rounding the panel applied on the way out.

Worked Example: A 1:55 Half Marathon

A half marathon is 21.0975 km under the World Athletics standard, which most watches and race entries round to 13.1 miles. Enter 13.1 with the unit on Miles, then 1 hour, 55 minutes and 0 seconds.

13.1 × 1.60934 = 21.082 km
1 h 55 min = 6,900 seconds
6,900 ÷ 21.082 = 327.3 seconds per km
327.3 seconds = 5 minutes 27 seconds
21.082 ÷ (6,900 ÷ 3,600) = 11.00 km/h

What the result panel returns

Distance: 13.1 mi, Time: 1h 55m 0s, Pace: 5m 27s per km, Average Speed: 11.00 km/h

Type the official 21.0975 km instead, with the unit on Kilometers, and the pace is unchanged at 5m 27s per km while the speed ticks up to 11.01 km/h. The gap is the 15 meters the rounded 13.1 miles leaves off the true distance — too small to move a pace rounded to the second, just large enough to move a speed carried to two decimals.

Running Pace Chart: Kilometers, Miles and Race Times

Three views of the same arithmetic. Race times use the standard distances — 5 km, 10 km, 21.0975 km and 42.195 km — and every value was computed from the exact figures and rounded once, at the end, to the nearest second.

Pace per Kilometer Chart

Start here if your watch is set to metric. Read across from your pace to find the mile equivalent, the speed, and what that pace delivers over each race distance:

The marathon column reappears in the half marathon column at double the pace, because doubling the distance and doubling the pace both double the time. A marathon at 3:30 per kilometer and a half at 7:00 both come to 2:27:41; a marathon at 4:00 and a half at 8:00 both come to 2:48:47. That symmetry is arithmetic, not physiology, and the race-prediction section below is where the difference bites.

Pace per Mile Chart

The same table built the other way around, for anyone whose watch reads in minutes per mile:

None of the finish times land on round numbers here, and the reason is that the races are metric. A 5K is 3.107 miles and a 10K is 6.214, so an even mile pace never produces an even race time. The 8:00 mile is the one worth memorizing: it is a 3:29:45 marathon, fifteen seconds inside the round number people aim at.

Goal Time to Required Pace

Working backwards from a target. Divide the goal time by the race distance and you have the pace you must average for every kilometer of it:

The last eight rows pair off exactly: a two-hour half and a four-hour marathon both demand 5:41 per kilometer, and a 1:45 half and a 3:30 marathon both demand 4:59. As arithmetic that is inevitable. As goals the two halves of each pair are nothing alike, and a runner who has just run 1:45 for a half should not treat 3:30 as available.

A pace target is only half a race plan. The effort that sustains it is the other half, and that half is measured in beats rather than seconds — for the heart rates that go with an easy, endurance or hard session, from your age and the goal of the run, use the Heart Rate Zone Calculator.

How to Use the Running Pace Calculator

Five fields, two buttons, and one habit worth knowing about.

• Distance — the number you ran. Its label prints (km) whatever you do; the control underneath is what actually decides how the number is read.
• Distance Unit — two buttons, Kilometers and Miles. Kilometers is selected when the page opens.
• Hours, Minutes and Seconds — three separate boxes, and all three have to hold a number. Put 0 in the ones you do not need; a box left blank stops the calculation instead of counting as zero.
• Calculate runs the formula. Reset clears the form and returns the panel to its empty dash.

The page works nothing out on arrival, because all four number boxes start empty and the on-load run only fires when every field already carries a value. It does not recalculate as you type, either — the form listens for the Calculate button and nothing else. Change a figure and press it again.

Press Calculate with a box empty and the panel names the box rather than answering: “Enter a value for Hours.”, or “Enter a value for: Hours, Seconds.” when more than one is missing. Once every box holds a number, only two entries are refused: a distance of zero or less, and a time whose hours, minutes and seconds are all zero. Either returns an amber notice reading “Please enter valid distance and time.” Nothing else is checked. The boxes carry no minimum or maximum and the form is submitted without browser validation, so a negative time is accepted and comes back as a negative pace — 10 km entered with −1 in Hours, and 0 in both Minutes and Seconds, returns a pace of −6m 0s per km at −10.00 km/h.

How to Read Your Result

The panel gives you one sentence. Knowing which parts of it are your own entry, which part is the answer, and which unit each is in takes about ten seconds and saves the occasional wasted run.

The Four Clauses on the Line

For 10 kilometers in 50 minutes, the readout is exactly this:

Result panel

Distance: 10 km, Time: 0h 50m 0s, Pace: 5m 0s per km, Average Speed: 12.00 km/h

Clause one repeats your distance and the unit code you chose. Clause two repeats your time in the three boxes you filled. Clause three is the answer. Clause four is that same answer as a speed, always in km/h — there is no mph anywhere in this tool, and no per-mile pace either.

The first two clauses exist to be checked. A pace that looks wrong is usually a distance typed under the wrong unit or a time typed into the wrong box, and the echo shows you which before you go hunting for a training explanation.

What Your Pace Costs in Effort

A pace is also an intensity. The 2024 Adult Compendium of Physical Activities rates running by speed in METs, where one MET is the energy of sitting quietly, so the rating is a multiple of resting metabolism:

The last column is the one runners rarely see. Doubling the speed from a 12-minute mile to a 6-minute mile raises the rate by 74 percent, from 8.5 METs to 14.8 — but the fast mile is over in half the time, so the mile itself gets cheaper, falling from 102 MET-minutes to 88.8, a saving of about 13 percent. Distance, not pace, is what drives the energy cost of a run.

Treat these as laboratory averages rather than readings from your own body. MET values are population figures, they have shifted between editions of the Compendium, and a calculator elsewhere may quote a slightly different number for the same pace.

Turning any of those ratings into calories needs two more facts — your body weight and how long you were out — which is the job of the Calories Burned Calculator.

Is That Pace Moderate or Vigorous?

Public-health guidance splits activity into moderate and vigorous, and the NHS offers a test that needs no numbers at all: at moderate intensity “you can still talk, but not sing”, while vigorous intensity “makes you breathe hard and fast” and you “will not be able to say more than a few words without pausing for breath”. The NHS lists running among its vigorous activities and asks adults for at least 150 minutes of moderate activity a week or 75 minutes of vigorous.

Which side of that line your own pace falls on is personal, and it moves. The same 6:13 kilometer that leaves one runner able to hold a conversation leaves another unable to finish a sentence, and for either of them it changes with fitness, with heat, and with how recently they last ran hard. The pace is objective; the effort behind it is not.

Turning a Pace Into a Race Prediction

The charts above answer “what finish time does this pace produce?” They do not answer “what pace could I hold over a longer race?”, which is a different question with a standard answer. Peter Riegel published the usual model in American Scientist in 1981:

time for race Y = time for race X × (distance Y ÷ distance X) ^ k

The exponent k is a fatigue factor: how much your speed decays as the race lengthens. Riegel cited 1.08 for elite runners and 1.05 to 1.06 for male recreational runners aged 40 to 70; Runner’s World has long used 1.06, and Vickers and Vertosick chose 1.07 as an average when they tested it. At k = 1.06 every doubling of race distance multiplies your pace by 2 raised to 0.06, which is 1.0425 — about 13 seconds per kilometer for someone racing at 5:00, and about 15 for someone racing at 6:00.

Read the bottom row as a ceiling rather than a target. Vickers and Vertosick tested Riegel against 2,303 recreational runners and found it well calibrated up to the half marathon but “dramatically underestimated marathon time, giving times at least 10 min too fast for half of runners”; a sensitivity check at k = 1.08 improved matters only slightly. The 3:59:47 above is a sub-four marathon on paper that around half of comparable runners would miss by ten minutes or more.

Limits: Where an Average Pace Stops Being Useful

An average is a summary, and every summary throws something away. Four things this one discards.

An Average Erases the Splits

Cover the first 5 km of a 10 km in 23:20 and the second in 26:40 and you finish in 50:00 — the same 5m 0s per km the calculator reports for a run held level throughout. The two halves were 4m 40s and 5m 20s, a forty-second spread the single figure cannot show.

That matters because a fading second half and an even effort call for opposite responses in training. If you know your split times, run the tool once per segment rather than once for the whole thing: 5 km in 23:20 returns 4m 40s per km, and 5 km in 26:40 returns 5m 20s.

Your Watch and the Course Rarely Agree

Certified road courses are measured along the shortest route a runner could legally take. Nobody runs that route — you drift wide on bends, weave through crowds and cross to a water table — so a GPS watch usually records more distance than the race claims, and the pace it shows is faster than the pace your official time implies.

Finish a marathon in 4:00:00 with a watch reading 42.60 km and this calculator returns 5m 38s per km. Enter the official 42.195 km for the same finish time and it returns 5m 41s. Three seconds per kilometer, from nothing but which distance you typed. Neither figure is wrong; they answer different questions, and only the second matches what the race results will say.

Terrain, Heat, Wind and Altitude

Pace is what effort and conditions produce together, which is why the same effort returns a different number on a different day. Hills add vertical work no flat-ground pace accounts for. Heat sends blood to the skin for cooling that would otherwise be serving the legs. A headwind, soft ground, technical trail and thin air at altitude each take their cut, and a treadmill belt hands some of it back.

So a slower pace on a hot, hilly Sunday is not evidence of lost fitness. Compare like with like — the same route in similar weather, or the same session on a track — and log the figure so the comparison exists to be made. One run tells you almost nothing; twenty of them on the same loop tell you a great deal.

What This Tool Does Not Do

The scope is deliberately narrow, and the edges are worth stating:

• It does not predict race times. The charts convert a pace you already ran; predicting a longer race needs the Riegel model above, with its known marathon bias.
• It does not report pace per mile or speed in mph. Miles go in, kilometers come out.
• It has no field for splits, elevation, heart rate or body weight, so none of those can influence the answer.
• It does not store or compare runs — nothing carries over between visits, so keep your own log.

Everything it does do, it does exactly — a division, a unit conversion and a rounding to the nearest second — with one quirk in how that last step is printed. Knowing where the tool stops is what keeps the number honest.

The minutes are rounded down while the seconds are rounded to the nearest whole second, and those two roundings disagree when a pace lands within half a second of the next full minute: the seconds field prints 60. Ten kilometers in 49:56 is 299.6 seconds per kilometer, and the panel returns “Distance: 10 km, Time: 0h 49m 56s, Pace: 4m 60s per km, Average Speed: 12.02 km/h”. Nothing has gone wrong — 4m 60s is 5m 0s written the long way. Read any 60 in that field as zero and add the minute yourself.