Running Pace Calculator

A running pace calculator converts between pace, speed, distance, and finish time for any running event. It is used by recreational runners and competitive athletes to plan race strategy, set training targets, and track progress.

How to Use the Running Pace Calculator

1. Select what you want to calculate: pace, finish time, or distance.
2. Enter the two values you know. For example, if you know your pace and distance, the tool calculates finish time.
3. Choose your preferred units: kilometres and min/km, or miles and min/mile.
4. Click Calculate to see your result along with a complete splits table.
5. Use the splits table to plan even or negative splits for your race.

The Formula

Finish time (in minutes) = pace (min/km or min/mile) multiplied by distance (km or miles). Pace = finish time divided by distance. Distance = finish time divided by pace. To convert between units, multiply min/km by 1.60934 to get min/mile. To convert km/h to min/km, divide 60 by the speed in km/h. To convert mph to min/mile, divide 60 by the speed in mph.

Real-World Example

A runner wants to complete a half marathon (21.0975 km) in 1 hour 45 minutes (105 minutes). Required pace = 105 divided by 21.0975 = 4.977 min/km = 4 minutes and 58.6 seconds per km. Rounding to 4:59 min/km as a target. At this pace, the 10 km split would be reached at 49:50, and the 15 km split at 1:14:45. In min/mile: 4.977 multiplied by 1.60934 = 8.009 min/mile, or approximately 8:00 per mile.

Race-Specific Pace Targets

For a sub-30-minute 5 km, you need to average faster than 6:00 min/km (9:39 min/mile). A sub-60-minute 10 km requires faster than 6:00 min/km. A sub-2-hour half marathon needs 5:41 min/km (9:09 min/mile). Breaking 4 hours in a marathon requires 5:41 min/km consistently. Knowing your exact per-kilometre target before race day prevents the common mistake of going out too fast and fading in the second half.

Frequently Asked Questions

What is the difference between pace and speed? Pace expresses how long it takes to cover one unit of distance (e.g., 5:30 per km). Speed expresses how much distance is covered per unit of time (e.g., 11 km/h). Runners typically use pace; cyclists typically use speed. To convert: speed in km/h = 60 divided by pace in min/km.

What is a good running pace for beginners? Most beginners run comfortably between 7:00 and 9:00 min/km (11 to 14 min/mile). A good starting benchmark is a pace where you can hold a full conversation without gasping. Speed improves naturally with consistent training over weeks and months.

How do I account for hills in my pace calculation? As a rule of thumb, add 30 to 40 seconds per km for each 1 percent of average gradient on a hilly course. Modern GPS watches with grade-adjusted pace (GAP) remove the guesswork. For race planning on hilly courses, use effort rather than pace as your guide on the climbs.

What is negative splitting and should I try it? Negative splitting means running the second half of a race faster than the first half. Research and race data consistently show it produces faster finish times and better racing experiences than going out fast. Starting 5 to 10 seconds per km slower than goal pace in the first third of a race is a reliable strategy.

Standard race distances and how they relate

Four distances cover almost every road race, and three of them are exact multiples or halves of each other, which is what makes pace arithmetic worth doing by hand.

The marathon is not twice the half marathon by accident or by approximation. It is twice the half marathon to the last decimal place, which means a runner who doubles their half marathon time to estimate a marathon time is not making an arithmetic error, only a physiological one. The times do not double, because pace falls as distance rises. That is the gap the rest of this page closes.

Pace to finish times at four distances

Pace converts to a finish time by one multiplication per event. The table takes a set of common paces and gives the finish time at each standard distance, with the speed equivalents beside them for riders and rowers who work in those units.

The second row is the page's own worked example, the 105 minute half marathon, carried across the distances at the same pace. It is the only row in the table where the half marathon is exactly 1:45:00, and the row shows how a single target pace turns into four very different target times.

Two rows in the table make the same point from opposite sides. Doubling the half marathon time gives exactly the marathon time at the same pace, because the marathon is exactly twice the distance: 1:45:29 doubled is 3:30:58. That arithmetic is exact, and it is also the trap, because nobody holds one pace for 42.195 km. The section below puts the fatigue back into the calculation.

Predicting one distance from another

A runner with a recent race time can estimate any other distance with one formula, published by Peter Riegel in American Scientist in 1981. Take the known time, multiply it by the new distance divided by the known distance, raised to the power of 1.06.

The exponent carries the whole idea. A runner does not hold the same pace as distance grows, and the rate at which pace falls is similar across runners of very different abilities. Doubling the distance multiplies the time by 2 to the power of 1.06, which is 2.084932, so a doubled course takes about 8.5% longer than twice the time rather than exactly twice.

The marathon row is the one to look at. A runner whose half marathon is 1:45:00 is predicted to run 3:38:55, which is 12 minutes and 55 seconds slower than simply doubling the half. That difference is not padding or caution. It is the fatigue factor the exponent encodes, and a marathon plan built on a doubled half marathon time will start a runner too fast on race day.

Read the table downward and the pace column tells a second story. The 5 km pace is about 25 seconds per km faster than the half marathon pace, and the marathon pace is about 13 seconds per km slower than it. The pace band widens as the distances grow apart, which is why a 5 km time is a poor guide to a marathon and a half marathon is a decent one.

Where the prediction stops being useful

The formula is a fit to world record progressions, so it describes what the best runners in the world do rather than what any individual runner will do.

Riegel put the valid range at race durations from about 3.5 minutes to about 230 minutes, which covers the 1500 metres to the marathon and no further. Inside that range the fit is strongest from the 5 km to the half marathon. At marathon distance it consistently underestimates how much recreational runners slow down, because the reasons for the slowdown compound with distance in ways a single exponent cannot express: fuelling, muscle damage, and the cost of time on the feet all grow faster than the power law assumes.

Three conditions push a real performance away from the prediction. A first marathon at any age will come in slower than predicted, because the specific endurance is not there yet. A course with significant climbing will come in slower, because the formula has no term for gradient. A hot day will come in slower, and the effect is larger than most runners expect, because the slowdown is not linear in the temperature.

Use the prediction as a target that a trained runner on a flat course in cool conditions can just about hit, and treat every departure from those conditions as a reason for the real time to be longer.

Grade adjustment in practice

The page's FAQ gives the working rule for hills: add 30 to 40 seconds per km for each 1% of average gradient. Applied to a pace rather than left as a number, the rule produces a target time for a climb.

The 10 second spread in the rule is there because the cost of a climb depends on the runner and on how steep the individual sections are. A climb that averages 5% in three short pitches costs less than the same average held for two kilometres without a break, because a runner can recover on the flat between pitches.

Notice also that the adjustment is stated per km and not per mile. The same rule in imperial units is about 48 to 64 seconds per mile for each 1% of gradient, since a mile is 1.609344 km long.

The arithmetic of a negative split

A negative split means covering the second half of a race faster than the first. The page's FAQ recommends starting 5 to 10 seconds per km slower than goal pace in the first third, and the arithmetic behind that number is simple enough to do while planning.

Take the 1:45:00 half marathon, which needs 4:58.61 per km on an even pace. Run the first third 10 seconds per km slower, at 5:08.61, and the first 7.0325 km take 36:10.3. That leaves 1:08:49.7 for the remaining 14.065 km, which is 4:53.61 per km: 5 seconds per km faster than goal pace.

The relationship is exact and general. A deficit of 10 seconds per km held for the first third of a race has to be repaid over the remaining two thirds, so it costs 5 seconds per km for the rest. A deficit of 10 seconds per km held for the first half costs the full 10 seconds per km afterwards.

This is the reason a fast start is so expensive. Every second per km spent ahead of plan in the first third has to be found twice over in the last two thirds, and the money is not there at the end of a race when it was not there at the start.

Also try these free tools:

• Pace Calculator
• VO2 Max Calculator
• Calories Burned Calculator