🆕 Newly Added Calculators:

🏃 Pace Calculator

Muhammad Yasir Yasin
By Muhammad Yasir Yasin · Updated 12 Nov 2026 Founder · 20 Year+ Telecom + IT Expert
Muhammad Yasir Yasin

Muhammad Yasir Yasin

Founder, metacalculator.org

Muhammad Yasir Yasin is a Telecom + IT expert from Pakistan with 20+ years of proven experience — the career documented on his LinkedIn. He has been in pure IT since 1998, and works as a crypto consultant & trader since 2016. He is the founder of metacalculator.org, seotools.metacalculator.org (SEO Tools) and metatrendonline.com (Digital Products Market Place): free tools built to give clear, checked answers, with no sign-ups and no paywalls.

Every calculator here is built from the published formula, tested by hand, and explained in plain words.

Pace Calculator

Result

Runners think in pace — minutes per kilometre or mile — because it tells you instantly whether you can hold the effort. Enter how far you ran and how long it took to get your pace in both units plus your average speed.

Use it backwards too: pick a target pace for race day and it shows what finish time that pace produces over your distance.

What this pace calculator does

Pace is the runner's unit of effort: not how fast you went in the abstract, but how many minutes each kilometre or mile took. Enter a distance and the time it took (or the time you are targeting), and this calculator returns your pace per kilometre, your pace per mile, and your average speed in km/h — all three from the same run, so you never have to convert between them by hand.

That covers the three jobs runners actually use it for: analysing a finished run ("what pace was that 5K, really?"), planning a race ("what per-kilometre pace hits 50 minutes for 10K?"), and translating between the metric world of most race plans and the miles used in others. It is pure arithmetic — no fitness estimates, no calorie guesses — which makes the outputs exact: the same figures any stopwatch and a long division would give you.

The formulas

Everything starts from the total time in seconds:

Total seconds = hours × 3600 + minutes × 60 + seconds Pace per km = total seconds ÷ distance in km Pace per mile = total seconds ÷ distance in miles

Pace is then written as minutes:seconds per unit. Distances convert with the exact international mile, 1 mile = 1.609344 km, in both directions — if you enter miles, the calculator converts to kilometres for the speed row using that same factor, so nothing is lost to a rounded 1.6 shortcut.

Average speed = distance in km ÷ (total seconds ÷ 3600), expressed in km/h. Pace and speed describe the same performance from opposite directions — pace rises as you slow down, speed falls — and they are exactly interchangeable, which the examples below demonstrate.

Worked examples

Example 1 — the calculator's own defaults. Distance 5 km, time 0:28:00. Total time 1,680 seconds. Pace per km = 1,680 ÷ 5 = 336 seconds = 5:36 /km. The run is 3.107 miles, so pace per mile = 1,680 ÷ 3.107 = 541 seconds = 9:01 /mi. Average speed = 5 km in 0.4667 hours = 10.71 km/h.

Example 2 — a 10K target. Distance 10 km, time 0:50:00. Pace per km = 3,000 ÷ 10 = 5:00 /km; pace per mile 8:03 /mi; speed 12 km/h. This is the classic sub-50 10K: hold five-minute kilometres and the target takes care of itself.

Example 3 — entering miles. Distance 5, unit Miles, time 0:45:00. The calculator converts 5 miles to 8.047 km. Pace per mile = 2,700 ÷ 5 = 9:00 /mi; pace per km = 2,700 ÷ 8.047 = 5:36 /km; speed 10.73 km/h.

Example 4 — a marathon time. 42.195 km in 3:30:00 works out to 4:59 /km and 8:01 /mi at 12.06 km/h — a useful reference point: a 3:30 marathon is, to within a rounding second, a five-minute-kilometre run held for 42 kilometres.

Reference table: common race performances

All figures computed with this calculator's formulas (1 mile = 1.609344 km):

PerformancePace per kmPace per mileAverage speed
5 km in 25:005:00 /km8:03 /mi12 km/h
5 km in 28:005:36 /km9:01 /mi10.71 km/h
10 km in 50:005:00 /km8:03 /mi12 km/h
Half marathon (21.0975 km) in 1:45:004:59 /km8:01 /mi12.06 km/h
Marathon (42.195 km) in 3:30:004:59 /km8:01 /mi12.06 km/h
5 miles in 45:005:36 /km9:00 /mi10.73 km/h

Pace or speed — which should you use?

Runners plan in pace because races are measured in distance and bodies budget effort per unit of ground: "run the first half at 5:10/km, then push" is an instruction you can execute with a watch at every kilometre marker. Speed is the better unit for comparing with cycling, treadmill displays (which often show km/h), and the speed rows in training apps. Neither is more correct; this calculator shows both so you can read whichever your plan uses. One caution when converting in your head: pace is not linear in the way intuition expects — going from 6:00 to 5:00 per kilometre is a much bigger speed jump (10 → 12 km/h) than going from 4:00 to 3:00 would suggest by symmetry (15 → 20 km/h).

Limits of an average pace

The calculator gives the average across the whole distance, and real runs are not average-shaped. Hills, wind, heat, trail surfaces and simple fatigue make individual kilometres vary, sometimes by a minute or more either side of the mean; a race that averages 5:36/km may have contained a 5:10 kilometre and a 6:05 one. Treat the average as the summary it is. Also note the calculator assumes the distance you enter is accurate: a GPS watch that measured your "5K" as 4.92 km will quietly flatter every figure, which is why race-day calculations from a certified course distance are firmer than training-run estimates.

Putting a pace to work in training

An average pace becomes useful when it anchors the rest of the week. Most structured running revolves around three effort bands relative to your current fitness, and a recent race result — converted here — is the usual way to set them. Easy pace is typically 60–90 seconds per kilometre slower than your 10K pace: for the sub-50 runner of Example 2, that means recovery runs around 5:45–6:30/km, slow enough for full conversation. Threshold pace sits close to the pace you could hold for about an hour — for most runners near their 10K pace or a touch slower — and is used for sustained 15–25-minute blocks that teach the body to clear lactate. Interval pace is faster than 5K pace and is only ever used for short repetitions with recoveries. The calculator's role in all three is translation: turn each session's distance and target time into the per-km and per-mile numbers your watch displays, before you go out, rather than doing division at a kilometre marker with tired legs.

One planning habit the numbers reward: set the target from the total time and let the calculator split it, instead of picking a round per-km pace and discovering the total afterwards. Aiming for "about 5:30s" across a half marathon can mean anything from 1:55 to 1:57 at the finish; aiming for 1:56:00 and reading off the exact 5:30/km it requires removes the ambiguity — and if that pace looks ambitious against your recent training, you find out at your desk, not at kilometre 18.

Common mistakes

  • Entering pace where time belongs. The three time boxes want your total finish time (hours, minutes, seconds), not a per-kilometre figure. Entering 5:30 as "5 hours 30 minutes" produces a spectacularly slow — and obviously wrong — result.
  • Mixing units mid-calculation. If your race plan is in miles, switch the unit select to Miles and enter the distance in miles. Entering 26.2 with the unit left on km calculates a very different event.
  • Using a rounded mile conversion elsewhere. 1 mile is 1.609344 km, not 1.6. Over a marathon, the shortcut misplaces you by nearly 400 metres — the calculator uses the exact factor, so trust its conversions over mental ones.
  • Rounding splits too early. Chasing a target by rounding every kilometre to the nearest 5 seconds can drift a marathon plan by minutes. Work from the exact average pace the calculator shows.

Using the numbers on race day

The calculator's averages convert directly into the split targets runners actually race against. For the sub-50 10K of Example 2, even pacing means passing 1 km in 5:00, 5 km in 25:00 and 8 km in 40:00 — check any one of those on the course clocks and you know, within seconds, whether the plan is alive. For the 3:30 marathon, the same discipline gives 5 km in about 24:53, 10 km in about 49:46 and halfway (21.0975 km) in exactly 1:45:00 — half the target for half the distance, as even pacing demands. Most experienced runners aim a few seconds slower than even pace for the first quarter of a long race and claw the time back later, when the alternative — banking time early at a few seconds per kilometre too fast — is the single most reliable way to turn the last 10 km into a walk. However you distribute it, the workflow is the one this page exists for: choose the finish time, divide it here, and pin the resulting per-km and per-mile figures to your plan before the start, not after the gun.

Key terms

  • Pace — time per unit distance, written minutes:seconds per km or per mile.
  • Split — the time for one segment (usually 1 km or 1 mile) within a longer run.
  • Average speed — distance divided by time, here always shown in km/h.
  • Negative split — racing the second half faster than the first.
  • 5K / 10K / half / marathon — 5 km, 10 km, 21.0975 km and 42.195 km standard race distances.

Related calculators

Frequently asked questions

What is a good pace for a 5K?

It depends entirely on the runner. For reference, 5 km in 25:00 is 5:00 per km — a strong club-runner pace — while 5 km in 28:00 is 5:36 per km and 5 km in 35:00 is 7:00 per km. Beginners often start between 6:30 and 8:00 per km; what is "good" is the pace you can sustain evenly.

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

Multiply by 1.609344 — a mile is that many kilometres, so each mile takes that much longer at the same speed. A 5:36/km pace becomes about 9:01 per mile. This calculator shows both figures automatically, converted with the exact factor.

What pace do I need for a sub-50-minute 10K?

Exactly 5:00 per kilometre (about 8:03 per mile), held evenly. In practice, aim to run the early kilometres a few seconds under 5:00 so that small slowdowns later do not cost the target.

Why does the calculator show speed in km/h even when I enter miles?

Because the speed row is standardised to km/h, as its note states — the unit select only governs the distance you enter. A 5-mile run in 45:00 shows 10.73 km/h alongside its 9:00 per mile pace.

My watch shows a different pace from this calculator. Which is right?

Probably both, from different inputs. The calculator divides exactly the distance and time you type in; a watch divides its GPS-measured distance, which is usually a little short or long. On a certified course, trust the official distance with your finish time — and this calculator.

What is the difference between pace and speed?

Pace is time per distance (minutes per km); speed is distance per time (km per hour). They are two views of the same performance: a 6:00/km pace is a speed of 10 km/h, and a 5:00/km pace is 12 km/h.

Can I use this for cycling or swimming?

Yes — the arithmetic is the same for any activity measured in distance and time. Cyclists usually prefer the km/h row, and swimmers often work with pace per 100 m, which you can get by entering the distance in km (400 m = 0.4 km) and reading the per-km pace divided by ten.

Disclaimer: This calculator is for educational and informational purposes only and is not a substitute for medical advice. Results are general estimates. Please consult a qualified healthcare professional for personal medical guidance.