b2KIT

Running Pace Calculator

Calculate running pace, finish time, or distance from any two of the three values with split tables.

Tested tool guide Tested browser tools Checked August 16, 2026

What Running Pace Calculator does, with a checked example

This calculator handles the three quantities that define any run: distance, time, and pace. Enter any two and it returns the third, along with a split table showing cumulative elapsed time at each mile or kilometer. The same relation works in all directions: pace is time divided by distance, so the arithmetic is one formula looked at three ways. The common mistake is units, not formula: pace is minutes per mile or kilometer, not speed, so 5:00 is faster than 6:00, and entering distance in one unit while thinking in another corrupts every result.

Worked example

A concrete input and expected output from the current implementation.

Input

Distance 10 km, time 50:00

Expected output

Pace 5:00 per kilometer (50 minutes / 10 km). Split table, cumulative at each kilometer: 5:00, 10:00, 15:00, 20:00, 25:00, 30:00, 35:00, 40:00, 45:00, 50:00.

Each kilometer adds exactly one pace increment, so ten 5:00 splits accumulate to 50:00, matching the entered time. The final split always equals the finish time when the pace is held evenly.

How the result is produced

1

One formula, three directions

With distance and time known, pace = time / distance, reported as minutes and seconds per mile or kilometer. Give pace and distance, and finish time = pace x distance. Give pace and time, and distance = time / pace, expressed as a decimal of the unit chosen. All three rearrange the same statement, so an implausible result usually means a value landed in the wrong field.

2

Split tables

A split table is the pace applied repeatedly: cumulative time at the end of each mile or kilometer, growing by exactly one pace increment per row. The first row is one unit at the given pace; the last row equals the total time from the main calculation. Splits are even by construction, so they form a pacing plan rather than a prediction of what actually happens.

Good uses

  • Race planning: enter the official distance and a goal finish time, get the pace to hold, and use the split table to check each mile or kilometer as you pass it.
  • Post-run logging: enter elapsed time and the distance your watch or a measured course reported, and the tool returns the pace to record and compare against earlier sessions.
  • Time budgeting: enter a pace and the minutes available, get the distance you can cover, or enter pace and distance to see what time a route should finish.

Limits and checks

  • Units are load-bearing. A pace is meaningless without its unit: 5:00 per kilometer and 5:00 per mile are very different efforts. If you train in kilometers and the page is set to miles, or the reverse, the pace and every split are wrong.
  • The result assumes even pacing across the whole distance. Hills, wind, stops, and fatigue push actual time past the straight-line estimate, and a fast start does not buy time back later.
  • Input format errors produce plausible garbage. Entering hours where minutes belong, or decimal minutes where minutes and seconds are expected, shifts results by factors of 60. If a pace looks too fast or too slow, recheck what was typed before trusting it.

Common questions

Why does the pace disagree with my GPS watch?

Usually distance, not math. A watch measures the path actually covered, which drifts with turns and GPS noise, while a race or route distance is a fixed number. Over 10 km, a 0.2 km difference moves the pace by a few seconds per kilometer, so small gaps between watch and calculator are normal: the two are measuring different distances.

Does it account for hills or walking breaks?

No. This is pure arithmetic: pace, distance, and time are related with no terrain, elevation, or effort in the model. Uphill sections and stops add time the formula cannot see, so the split table is only accurate for even effort on flat ground. On hilly routes, treat the result as a target, not a guarantee.

References and verification

The example and behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.

Related Tools