HandyBench

Running Pace Calculator

Pace per km/mile, speed and race predictions.

5:00
Pace / km
8:03
Pace / mile
12.00
Speed (km/h)
7.46
Speed (mph)
25:00
5K
50:00
10K
1:45:29
Half marathon
3:30:59
Marathon

Predicted race times assume you hold the same even pace; real finish times drift on longer distances.

How to use the Running Pace Calculator

  1. 1 Enter the distance and choose kilometres or miles.
  2. 2 Enter the time taken in hours, minutes and seconds.
  3. 3 Read your pace per km and per mile, speed, and predicted race times.

The arithmetic behind pace

Pace is time per unit distance, so the calculator converts your hours, minutes and seconds into total seconds and divides by the distance in kilometres (miles are first multiplied by 1.609344). That gives seconds per km, which is formatted as M:SS. Pace per mile is seconds per km × 1.609344. Speed is the reverse ratio: kilometres divided by hours for km/h, and km/h ÷ 1.609344 for mph.

Worked example

10 km in 50:00 is 3,000 seconds ÷ 10 = 300 seconds per km, so 5:00 per km. Per mile that is 300 × 1.609344 = 482.8 seconds, shown as 8:03 per mile. Speed is 10 ÷ 0.8333 h = 12.00 km/h (7.46 mph). Holding 5:00/km, the finish-time panel gives:

RaceDistance usedPredicted time
5K5 km25:00
10K10 km50:00
Half marathon21.0975 km1:45:29
Marathon42.195 km3:30:59

Why predictions are optimistic

The race times are simple multiplication: pace × distance. They assume you could hold the same pace at every distance, which almost nobody can. The jump from a 10K effort to a marathon typically costs a lot of pace through glycogen depletion and muscle fatigue, so a 3:31 marathon forecast from a 50-minute 10K should be read as an upper bound. The page does not apply an endurance model such as Riegel's formula, so it will not adjust for the fall-off.

Common mistakes

  • Entering 90 in the minutes field. Minutes and seconds are capped at 59. For 1 hour 30 minutes, put 1 in hours and 30 in minutes.
  • Mixing the unit. If your watch recorded 6.2 miles, set the unit to miles. A 10 in the distance box with kilometres selected is a very different run.
  • Using GPS distance for track times. A 5K road race may be measured slightly long by a watch because of corners, so your calculated pace can look faster or slower than the official result.
  • Reading pace and speed as interchangeable. A pace of 5:00/km is 12 km/h. Treadmill displays often show speed, so use km/h or mph as a cross-check against the speed boxes here.

Pace targets pair naturally with fuelling: the TDEE calculator estimates daily calories, and training dates can be counted with the date difference calculator.

Examples

  • ▸ 10 km in 50:00 = 5:00 / km (8:03 / mile) and predicts a ~3:31 marathon at that pace.

Frequently asked questions

How is running pace calculated?

Pace = total time ÷ distance. This tool converts your time into seconds, divides by distance, and formats the result as minutes and seconds per km and per mile.

How accurate are the predicted race times?

They assume you hold the same even pace at every distance. In reality pace usually slows over longer races, so treat longer predictions as a best-case target.

How do I convert min/km to min/mile?

Multiply the pace in seconds per kilometre by 1.609344. A 5:00 per km pace is 300 seconds, which is about 483 seconds, or 8:03 per mile. The calculator shows both at once.

What pace do I need for a sub-4-hour marathon?

Four hours over 42.195 km works out to about 5:41 per km, or about 9:09 per mile. Enter 42.195 km and 4:00:00 to see it, then check the other speeds in the results.

Related guides