How to calculate running pace and set realistic targets

Quick answer

Calculate running pace by dividing time by distance. Convert the time to seconds first, divide by miles or kilometers, then convert the result back to minutes and seconds. A 5-mile run in 47:30 averages 9:30 per mile, equivalent to approximately 5:54 per kilometer over 8.05 km.

That calculation describes a run or a goal. It does not decide whether the pace is appropriate today. Choose training pace from the session’s purpose, recent running, breathing, perceived effort, and conditions; choose race targets from preparation as well as arithmetic.

Key facts

• Pace divides time by distance and expresses minutes per mile or kilometer.
• Speed divides distance by time and rises when a runner moves faster, while the pace number falls.
• Seconds preserve calculation accuracy because clock time is not a decimal number.
• Equal-distance splits reveal pacing changes that a whole-run average can hide.
• Effort and conditions qualify a pace target because identical speeds can demand different work.

Start with two trustworthy inputs

You need a duration and a distance that describe the same part of the run. If you time a 20-minute work segment, use that segment’s distance rather than the entire outing including warm-up and cool-down.

Decide which clock answers your question:

• Elapsed time includes stops. It describes the time needed to complete an outing or race.
• Moving time excludes whatever an app identifies as a stop. It describes a different quantity and depends on how movement is detected.
• Work-interval time covers only the planned effort, with recoveries recorded separately.

A run with traffic stops can have a faster moving pace than elapsed pace. Neither number is automatically wrong. Comparing one with the other creates a misleading improvement. For race planning, use the clock that will count on the day, including walking, aid stations, and other pauses.

Distance also carries uncertainty. In an instrument-validation study, recorded distances varied across urban, forest, and open settings, with greater errors during running than walking or cycling in most tested devices (Gilgen-Ammann et al., 2020). The study tested older devices, so its numerical errors are not a rating of every current model. Its useful lesson is to question a surprising distance before interpreting a few seconds as a fitness change.

Calculate pace without the decimal-time trap

Use the following steps for any distance:

1. Convert hours to seconds by multiplying by 3,600.
2. Convert minutes to seconds by multiplying by 60.
3. Add the remaining seconds.
4. Divide total seconds by distance in the unit you want.
5. Convert the quotient back to minutes and seconds.

For 5 miles in 47 minutes 30 seconds:

Total seconds = (47 × 60) + 30 = 2850
Seconds per mile = 2850 ÷ 5 = 570
570 seconds = 9 minutes 30 seconds
Average pace = 9:30 min/mi

For the metric equivalent, divide by the unrounded distance, 8.04672 km, to obtain approximately 354.18 seconds per kilometer: 5:54 min/km after rounding.

47:30 is 47.5 minutes, not 47.30 minutes. Likewise, 9:30 is 9.5 decimal minutes. If a calculator returns 9.5, multiply the fractional part, 0.5, by 60 to recover 30 seconds. A result of 9.3 minutes means 9:18, not 9:30.

Keep full precision until the final display. Rounding distance and pace at every step can make a long-race finish estimate disagree with its own split chart.

Convert pace, speed, miles, and kilometers

One international mile equals exactly 1.609344 km, as listed by NIST. The same factor works for pace, but the direction matters:

Seconds per km = seconds per mile ÷ 1.609344
Seconds per mile = seconds per km × 1.609344
Speed in mph = 3600 ÷ seconds per mile
Speed in km/h = 3600 ÷ seconds per km

The table rounds pace to the nearest second and speed to two decimal places. These are conversions, not recommendations for a runner’s ability or age.

Pace per mile	Pace per kilometer	Speed in mph	Speed in km/h
8:00	4:58	7.50	12.07
9:00	5:36	6.67	10.73
10:00	6:13	6.00	9.66
11:00	6:50	5.45	8.78
12:00	7:27	5.00	8.05

Check the treadmill unit before entering a number. A speed of 6 mph is about 9.66 km/h; 6 km/h is a substantially slower setting. A display labeled “6” is not enough information.

Turn a finish goal into useful splits

The reverse calculation is equally simple: divide your target finish time by race distance to find required average pace. Multiply that pace by a checkpoint distance to get cumulative time.

For the 47:30 five-mile example, even one-mile checkpoints are 9:30, 19:00, 28:30, 38:00, and 47:30. A lap split describes one segment; a cumulative split describes everything since the start. Label your notes so you do not confuse them while tired.

Here are additional arithmetic examples, with conventional race names retained. Distances in miles are rounded for display; pace calculations use the metric race distances, including the standard 42.195 km marathon described by World Athletics.

Distance	Finish goal	Required pace per mile	Required pace per kilometer
3.11 miles (5K)	30:00	9:39	6:00
6.21 miles (10K)	55:00	8:51	5:30
13.11 miles (half marathon, 21.0975 km)	2:10:00	9:55	6:10
26.22 miles (marathon, 42.195 km)	4:20:00	9:55	6:10

The final two rows share the same average speed because both distance and time double. They do not imply that completing the half marathon makes that marathon goal realistic. Sustaining a speed for twice as long is a separate endurance problem.

Nor must every split be identical. Hills, turns, congestion, and wind alter the cost of a fixed speed. Use official course markers and total time to check progress without sprinting to repair every small discrepancy. The negative split guide explains how to distribute effort once a realistic overall target exists.

Choose training pace from the job of the run

A pace calculation answers “how fast?” Training also requires “for what purpose?” Easy running, steady work, intervals, and racing should not all inherit the same target.

For an easy run, begin with comfortable, complete-sentence speech. The CDC talk test distinguishes moderate activity, during which conversation remains possible, from vigorous activity, during which speech breaks into short fragments. This is a practical intensity check, not a precise threshold test or a guarantee of safety.

Run easily for a few minutes before looking at pace. Note the range that accompanies comfortable breathing on that route and day. Repeat under similar conditions before treating it as a useful personal range. The perceived-exertion guide helps you describe the internal effort consistently.

For a planned harder session, use the session’s own prescription and a recent performance anchor. Do not make easy pace faster merely because a race calculator predicts that you “should” manage it. Our steady-state running guide covers that particular workout’s effort, duration, and progression.

Heart rate can add context, but a single fixed beats-per-minute target cannot prescribe the right pace for everyone. The heart-rate zones guide explains the uncertainty in age-based estimates and why your own response matters.

If you are new or returning, establish repeatable running before performing a maximal test. The beginner running guide offers a progression that does not require a competitive pace. A walking break can be part of a successful run rather than a failed calculation.

Check whether a race prediction fits your preparation

Distinguish required pace from predicted capability. The first is arithmetic. The second estimates a human performance under uncertain conditions.

Start with a recent completed race or controlled benchmark, then ask whether the new distance is supported by your training, long-run tolerance, fueling practice, recovery, and course conditions. A short personal best from years ago is a weak anchor after an interrupted training block.

In a study of 2,303 recreational runners, a commonly used race-conversion formula performed reasonably through the half marathon but predicted marathon times at least 10 minutes too fast for half the runners (Vickers and Vertosick, 2016). This was a survey-based cohort, not a universal correction rule. It supports keeping a margin around predictions, especially when extrapolating to an unfamiliar longer event.

Weather matters too. An analysis of marathon results across multiple race years found progressively slower performances as heat stress rose (Ely et al., 2007). Do not apply a precise heat adjustment from one study to every run. Let conditions change the goal rather than forcing a cool-weather number at any cost.

Choose a working range and a fallback plan. If breathing, symptoms, or coordination make the planned effort inappropriate, slow down or stop. A calculator cannot clear you for exercise; chest pressure, fainting, or severe unusual breathlessness require stopping and urgent medical assessment.

Put pace in the wider recovery picture

After the calculation and training decisions are clear, SuperAge can help place running alongside activity, sleep, resting heart rate, and heart-rate variability trends available through Apple Health. Use the context to ask whether a familiar pace feels more manageable across several comparable runs, with normal recovery afterward.

An unusually fast run with poor sleep and persistent fatigue is a different story from gradually improved pace at a similar effort. Neither a biological-age estimate nor a normal recovery trend certifies race readiness, diagnoses an injury, or replaces symptoms and coaching judgment. The complete exercise guide places running alongside strength, balance, and sustainable weekly activity.

Three common mistakes that change the answer

Averaging pace numbers without weighting distance. If you run equal distances at 10:00 and 8:00 per mile, the combined average is 9:00. If you spend equal amounts of time at those paces, you cover different distances, and the answer changes. Use total time divided by total distance instead of averaging arbitrary screen readings.

Including recovery in an interval target. An outing averaging 11:00 per mile can contain correctly executed 8:30 work intervals. Judge the work segments separately; a slower whole-session average does not mean the intervals failed.

Chasing instantaneous GPS pace. A momentary jump can reflect measurement noise rather than acceleration. Prefer a meaningful lap or segment average, check known markers, and keep effort steady while the reading settles. Do not surge into traffic or poor footing to correct a display.

Frequently asked questions

How do I calculate running pace in minutes per kilometer?

Convert total duration to seconds, divide by kilometers, then convert back to minutes and seconds. A 30-minute 5K is 1,800 divided by 5: 360 seconds, or 6:00 per kilometer, approximately 9:39 per mile.

Is a lower pace number faster?

Yes, when comparing the same unit. An 8:00 mile is faster than a 10:00 mile. Speed behaves in the opposite direction: a higher number in mph or km/h means faster movement.

How do I convert 9:30 per mile to minutes per kilometer?

Convert 9:30 to 570 seconds and divide by 1.609344. The result is about 354 seconds, or 5:54 per kilometer. Do not divide the clock-looking number 9.30 directly.

Is four laps of a 400-meter track exactly one mile?

No. Four 400-meter laps total 1,600 meters, while one international mile is 1,609.344 meters. Use the correct start and finish marks and lane when accuracy matters.

Should walking breaks count in my average pace?

They count when you want the total pace for completing a route or race. You can also record running-only segments, but label them clearly and do not compare them directly with an elapsed-time average.

What is a good running pace for my age?

There is no single healthy pace for an age group. Training history, fitness, terrain, conditions, symptoms, and the purpose of the run matter. Compare your repeatable effort and recovery before using someone else’s pace as a target.

Can a 5K time predict my marathon pace?

It can inform an estimate, but it cannot prove marathon endurance. Longer-distance preparation, fueling, conditions, and fatigue resistance can make the actual result substantially slower than a short-race prediction.

Why is my normal pace harder on some days?

Heat, wind, hills, fatigue, poor sleep, illness, and measurement differences can change the relationship between pace and effort. Adjust the session to the day’s response. Investigate a persistent unexplained change instead of repeatedly forcing the old pace.

Key takeaways

• Divide total time by distance and calculate in seconds before formatting the result.
• Keep units and time definitions consistent across comparisons.
• Use conversions and split tables as arithmetic tools, not fitness prescriptions.
• Select training targets with effort, session purpose, and recent running.
• Treat race predictions as estimates that need preparation and condition checks.
• Judge progress across comparable runs and sustainable recovery.

Keep the numbers useful

Download SuperAge to keep activity and recovery trends in view as your running develops. Let the calculation organize the run, and let effort, symptoms, and conditions guide the decision.

References

1. NIST. Revised unit conversion factors. Updated 2026.
2. CDC. How to measure physical activity intensity. Updated 2025.
3. World Athletics. Marathon: standard race distance.
4. Gilgen-Ammann R, Schweizer T, Wyss T. Accuracy of distance recordings in eight positioning-enabled sport watches: instrument validation study. JMIR mHealth and uHealth. 2020.
5. Vickers AJ, Vertosick EA. An empirical study of race times in recreational endurance runners. BMC Sports Science, Medicine and Rehabilitation. 2016.
6. Ely MR, Cheuvront SN, Roberts WO, Montain SJ. Impact of weather on marathon-running performance. Medicine & Science in Sports & Exercise. 2007.

Educational information, not an individualized medical assessment or training prescription.