How to Calculate Running Pace (With a Real Example)
Running pace is your total time divided by your distance. Run 10 km in 52 minutes and your pace is 5:12 per km, meaning every kilometer took an average of 5 minutes and 12 seconds. That single division is the whole formula; everything else in this article is just applying it to different situations.
The pace, time, distance and speed formulas
Four numbers, three formulas, all built from the same relationship:
- Pace = total time ÷ distance
- Time = distance × pace
- Distance = total time ÷ pace
- Speed = distance ÷ total time (in hours)
Pace and speed describe the same run from opposite directions. Pace tells you how long a unit of distance takes, speed tells you how much distance a unit of time covers. Knowing any two of time, distance, and pace lets you solve for the third, and speed comes along for free once you have distance and time.
You’ll reach for different pairs of these depending on the situation. Planning a race, you usually start from a goal time and the fixed distance, then solve for the pace you need to hold. Checking a training log, you already know the distance you ran and the pace on your watch, and you’re solving for total time to see how it compares with last week. Same formulas, different starting point each time.
Worked example: 10 km in 52 minutes
Take a runner who finishes 10 km in 52:00, no seconds left over.
First, convert the time to seconds: 52 minutes is 3,120 seconds. Divide that by the distance:
3,120 sec ÷ 10 km = 312 sec/km = 5:12 per km
For speed, convert the time to hours instead (3,120 ÷ 3,600 = 0.867 h) and divide distance by that:
10 km ÷ 0.867 h = 11.54 km/h
The same run looks different in miles. 10 km is about 6.21 miles, so the pace stretches out to roughly 8:22 per mile, and speed drops to about 7.17 mph. Nothing about the run changed, only the ruler used to measure it. This is exactly why a race result posted in one unit can feel confusing if you train by the other.
Notice that pace and speed moved in opposite directions when the unit changed too. A mile is longer than a kilometer, so it takes more time to cover one (8:22 versus 5:12), but that same run still covers fewer miles than kilometers in an hour, which is why the mph figure (7.17) sits lower than the km/h figure (11.54). Once you’ve done this conversion once for a real run, it’s much easier to sanity-check any pace or speed number you see quoted in the other unit.
What pace do you need for a sub-X race?
Once you can convert time, distance, and pace, planning a race becomes a lookup rather than a guess. Here’s how three common training paces per kilometer play out across standard race distances:
| Distance | 5:00 /km | 5:30 /km | 6:00 /km |
|---|---|---|---|
| 5K | 25:00 | 27:30 | 30:00 |
| 10K | 50:00 | 55:00 | 1:00:00 |
| Half marathon (21.1 km) | 1:45:29 | 1:56:02 | 2:06:35 |
| Marathon (42.2 km) | 3:30:59 | 3:52:04 | 4:13:10 |
The gaps widen as the distance grows. A 30-second-per-km swing barely registers over a 5K (2:30 total), but stretch that same pace band across a marathon and 5:00 versus 5:30 pace is a 21-minute difference at the finish line. Push it to 5:00 versus 6:00 and the gap nearly doubles to about 42 minutes. That’s the compounding effect of pace: small, comfortable-feeling adjustments per kilometer turn into finish-time swings that decide whether a goal is realistic.
Calculate your own pace
Enter any two of distance, time, and pace below and the calculator fills in the third, along with your average speed in both km and miles.
Common mistakes and edge cases
Confusing pace with speed. They move in opposite directions. Get faster and your pace number goes down (less time per km), while your speed number goes up (more distance per hour). A runner improving from 6:00/km to 5:00/km is getting faster even though the pace number dropped, and their speed climbs from 10 km/h to 12 km/h to match.
Mixing up km and miles. Most of the world posts race distances and paces in kilometers; the US, and a few other countries, mostly use miles. A “7:00 pace” means something completely different depending on which unit it refers to, and a training plan copied from a source in the other unit will send you out at the wrong effort if you don’t convert first.
Trusting watch distance over official distance. A GPS watch rarely measures a course to the exact meter. Signal reflection, tree cover, and tight turns you don’t cut as tightly as the official route all add up, so a certified “10K” often reads 10.05 to 10.15 km on your wrist. Calculate pace from that inflated distance and it’ll look slightly slower than your actual effort, even though nothing about your running changed. If you want your official race pace rather than your watch pace, divide the official finish time by the official distance, not the number your watch recorded.
Expecting treadmill pace to match outdoor effort. A treadmill belt moves at a fixed speed with zero wind resistance and a perfectly flat, consistent surface. Outdoors you’re pushing against air and dealing with whatever camber or incline the road has, so the same displayed pace typically feels harder outside. Runners often need to nudge the treadmill a notch faster than their outdoor pace to match perceived effort, and a 1% incline is a common adjustment coaches suggest to approximate flat outdoor running.
Frequently asked questions
How do I calculate my pace from a race result? Take your finish time and convert it fully to seconds, then divide by the distance in km or miles. A 10K finished in 48:30 is 2,910 seconds; divide by 10 and you get 291 seconds per km, or 4:51/km.
What’s a good running pace for beginners? It varies a lot by fitness level, but many new runners settle into easy training paces somewhere between 6:30 and 8:00 per km. Race pace runs faster than that and depends heavily on distance and experience, a 5K effort is rarely sustainable over a marathon.
How do I convert running pace to speed (km/h or mph)? Divide the distance by the total time expressed in hours. If pace is already in minutes per km, one shortcut is 60 divided by the pace in minutes, so a 5:00/km pace gives 60 ÷ 5 = 12 km/h.
Why do some countries measure running in miles and others in kilometers? It comes down to each country’s broader system of measurement. The US, and a handful of others, standardized on imperial units for everyday distances, so races and training plans there default to miles. Most of the rest of the world adopted the metric system, which makes kilometers the natural unit for road races and track training alike.
Can I use this for walking or cycling pace too? Yes. The underlying math, distance divided by time, or time divided by distance, doesn’t care what activity produced the numbers. Plug in a walking split or a cycling segment the same way you would a run and the pace or speed comes out just as accurately. Cyclists usually think in speed rather than pace, but the calculator’s speed output covers that without any extra steps.
Why does my pace look different on race day compared to training? Adrenaline, taper rest, a flatter course, and other runners to pace off all tend to make race-day pace faster than an equivalent training effort. Weather matters too: heat and humidity slow almost everyone down regardless of fitness. None of that changes the formula, it just changes which pace number you should expect to see on a given day.