How to Figure Out Running Pace: Formula and Chart

To figure out running pace, divide your total elapsed time by the distance covered, then express the result as minutes and seconds per kilometre or mile. A 50-minute 10K is 5:00/km; the same run is about 8:03/mile. Pace means time per unit of distance—the inverse of speed—and the calculation works for a lap, training run, or race.

Calculate running pace from time and distance

Use this relationship:

`pace = time ÷ distance`

The basic rule matches the method published by CalculatorSoup. Calculator.net also treats pace, time, and distance as a three-variable relationship: knowing any two lets you calculate the third.

Convert the full time to seconds first

Working in seconds prevents mistakes when the result is not a whole minute. Suppose you run 10 km in 52:40:

1. Convert the time: `(52 × 60) + 40 = 3,160 seconds`.
2. Divide by 10 km: `3,160 ÷ 10 = 316 seconds per km`.
3. Convert back: 316 seconds is 5:16/km.

The same result is about 8:29/mile because 10 km equals approximately 6.2137 miles. Its average speed is 11.39 km/h.

A calculator may return a decimal such as 5.2667 minutes per kilometre. The digits after the decimal represent a fraction of a minute, not seconds. Multiply `0.2667 × 60` to get 16 seconds, producing 5:16/km rather than 5:27/km.

Calculate a target finish time or distance

If you know pace and distance, multiply them. Running 8 km at 5:30/km takes 44 minutes.

If you know time and pace, divide instead. A 60-minute run at 5:00/km covers 12 km, assuming that pace remains constant.

For a 1:45 half-marathon target, calculate with the full 21.0975 km distance:

`6,300 seconds ÷ 21.0975 = 298.61 seconds per km`

That is 4:58.6/km, not exactly 5:00/km. The extra precision matters when a rounded pace is repeated over a long distance. For more per-kilometre examples, see the running pace calculator per km guide.

Convert pace between kilometres, miles, and speed

Pace and speed describe the same movement from opposite directions. Pace answers how long one unit of distance takes; speed answers how much distance is covered in one hour.

Convert min/km to min/mile

Multiply pace in seconds by 1.609344:

`seconds per mile = seconds per km × 1.609344`

A 5:00/km pace is 300 seconds per kilometre. Multiplying by 1.609344 gives 482.8 seconds, or 8:03/mile after rounding.

To convert in the other direction, divide seconds per mile by 1.609344. An 8:00/mile pace becomes 4:58/km.

Convert running pace to km/h or mph

Use decimal minutes for this calculation:

• `km/h = 60 ÷ minutes per km`
• `mph = 60 ÷ minutes per mile`

At 5:00/km, speed is `60 ÷ 5 = 12 km/h`. At 8:00/mile, speed is `60 ÷ 8 = 7.5 mph`.

A miles-per-minute calculator expresses the same speed in a less familiar direction. At 8:00/mile, you cover 0.125 miles per minute because `1 ÷ 8 = 0.125`. For running plans and race splits, minutes per mile is usually easier to apply.

Running pace chart for common targets

These are mathematical even-pace totals, not finish-time predictions. They assume the stated pace is held across the full measured distance without additional distance, stops, or course adjustments.

Do not reverse-engineer a race goal by reading only the nearest rounded row. A 3:30:00 marathon requires 4:58.61/km. Holding the displayed 4:59/km produces approximately 3:30:16, while 4:58/km produces about 3:29:34. Cumulative checkpoints preserve the intended finish time more reliably than repeatedly multiplying a rounded watch pace.

Why your watch and calculator can disagree

The arithmetic is simple. Choosing inconsistent inputs is the common failure mode.

Moving time and elapsed time answer different questions

Elapsed time includes the entire period between start and finish. Moving time may exclude pauses identified by an app or watch. Use elapsed time for an event result or an uninterrupted benchmark; use moving time only when you deliberately want stops removed.

For a nominal 10K, 52:00 elapsed is 5:12/km, while 49:30 moving time is 4:57/km. That input choice creates a 15-second-per-kilometre difference before any fitness interpretation begins.

Small distance differences change the displayed pace

A route label, course measurement, and watch recording do not necessarily provide the same input. Treat the value you select as part of the result.

For the same 52:40 time:

• 9.94 km produces approximately 5:18/km.
• 10.00 km produces 5:16/km.
• 10.06 km produces approximately 5:14/km.

That is roughly a four-second-per-kilometre spread between the outer readings (3.8 seconds before rounding). When comparing two runs, use the same distance source and time definition before attributing the difference to performance.

Do not average run/walk paces directly

A run/walk pace calculator must combine time and distance, not take the midpoint of two pace numbers. Consider a repeating cycle of four minutes running at 6:00/km and one minute walking at 10:00/km:

• The run covers `4 ÷ 6 = 0.6667 km`.
• The walk covers `1 ÷ 10 = 0.1000 km`.
• The cycle covers 0.7667 km in five minutes.
• Combined pace is `5 ÷ 0.7667 = 6.52 min/km`, or about 6:31/km.

The simple midpoint of 6:00 and 10:00 is 8:00/km, which is wrong for this timed cycle. The segments do not contribute equal time or equal distance.

Turn average pace into a usable target

A calculated average describes what happened or what a finish target requires. It does not, by itself, identify an appropriate easy pace, threshold pace, or race strategy.

Start with a comparable recent result

Use a recent run that resembles the decision you are making. Record five details with the pace:

• elapsed or moving time;
• measured distance and unit;
• route profile and surface;
• temperature, wind, and rain;
• whether the run was an easy session, controlled benchmark, or race effort.

For an October or November benchmark, repeat the same route under reasonably similar conditions when possible. If conditions differ, preserve the raw result and note the difference instead of silently rewriting the pace. The heat-adjusted pace calculator guide explains why the pace you feed into a heat adjustment should be an unadjusted baseline, and how to avoid adjusting the same number twice.

Match the method to the question

A flat average is the calculation layer; a race-day plan is the decision layer. For a course with meaningful elevation, wind, or changing conditions, use the average as a reference and then decide where constant pace is unrealistic. This pace adjustment guide for elevation, wind, and altitude shows the additional inputs to inspect. For specific races, TrainingFlow turns a recent result and the course's elevation profile into course-adjusted splits and shows how much time the course costs compared with a flat run.

FAQ

Is 2 miles in 30 minutes a good pace?

Two miles in 30 minutes equals 15:00/mile, approximately 9:19/km, or 4 mph. Whether it is suitable depends on the purpose of the session and your own comparable baseline; the calculation alone cannot rate the effort.

Is 7 mph a good jogging pace?

Seven mph equals approximately 8:34/mile or 5:20/km. Instead of assigning a universal label, compare it with the effort you intended, the duration you can sustain, and recent runs completed under similar conditions.

What is a good running pace for my age?

Age alone does not determine a useful pace. Distance, route, conditions, training history, and intended effort also change what the number means, so compare like-for-like results and track your own trend before using an age-based table.

How do I find my ideal running pace?

Choose the purpose first: easy run, workout, benchmark, or race. Calculate your recent pace from a representative result, keep the time and distance inputs consistent, and then use a method designed for that purpose rather than treating one pace as suitable for every run.