Skip to content

Free training tool

Running pace calculator

Convert distance and time into pace per kilometre or mile and generate a splits table for workouts and race planning.

Updated Oct 17, 2026

Loading pace calculator…

Example presets

Prefill with a realistic scenario

Pick an example to prefill the calculator, then tweak inputs for your own training week.

Tool

What you enter and what you get

Enter a few details to get your result. The guide below explains how to use it.

You enter

  • • Distance (km/mi)
  • • Finish time (hh:mm:ss)
  • • Split every (km/mi) (optional)

You get

  • • Pace per km
  • • Pace per mile
  • • Split table

Calculate pace, time or distance

Running pace is elapsed time divided by distance. Enter a distance and finish time to get an average pace and checkpoint splits. Use kilometres or miles consistently: one mile is 1.609344 km.

What you knowCalculationExample
Time and distancePace = time ÷ distance50 minutes ÷ 10 km = 5:00/km
Pace and distanceTime = pace × distance5:30/km × 10 km = 55:00
Time and paceDistance = time ÷ pace60 minutes ÷ 6 min/km = 10 km

Worked 10K example

For a 50-minute 10K, enter 10 km and 00:50:00. The average is 5:00/km, or approximately 8:03/mile. At an even average, the 2 km, 5 km and 8 km checkpoints are 10:00, 25:00 and 40:00. These are cumulative elapsed times, not the time for each separate segment.

Changing the split interval changes the checkpoint spacing, not the finish time. A final partial interval should cover only the remaining distance. Rounding each displayed split can create a small difference if you add rounded values manually.

Pace is not speed

Minutes per kilometre gets smaller as you run faster; kilometres per hour gets larger. A pace of 5:00/km equals 12 km/h. Convert minutes and seconds before dividing: 5:30 is 5.5 minutes, not 5.30 minutes.

Use elapsed time for a race plan

Pausing a watch at an aid station may improve the displayed moving pace, but the official race clock continues. Use elapsed time for finish planning and account for any stops. GPS error, weaving, the measured course line and rounded distance can also make watch pace differ from official splits.

This calculator performs arithmetic. It does not measure fitness, select a sustainable effort or adjust for hills, heat, wind or fatigue. Use the race-time predictor to explore a different distance with explicit assumptions, and the marathon pacing guide to plan execution. Easy training should still reflect an appropriate effort rather than a calculator target.

Assumptions

What this tool assumes

  • • You run at a steady average pace (real races have pacing variation).
  • • Splits are calculated on flat ground with no wind/terrain adjustments.

Limitations

When this estimate may be less reliable

  • • Does not adjust for heat, hills, wind, crowding, or fatigue drift.
  • • Race-day execution is effort-driven; use splits as a planning guide, not a rigid script.

Adaptive AI coach for iPhone

Meet your adaptive AI coach.

Tell your coach what you are training for. It builds the plan, follows the work you complete, and adapts upcoming training when recovery, your schedule, or real life changes.

FAQs

Should I pace evenly or negative split?

For most runners, a gentle negative split works best: start controlled, settle, then accelerate only if effort stays stable after 30K.

What pace should I use in training?

Train by effort zones and purpose: easy runs easy, workouts controlled, long runs mostly easy. Use this tool to translate goals into splits.

Why do my race splits drift?

Heat, hills, crowding, and fatigue drift all compound. Plan with splits, execute by effort and hydration/fueling.

Your path

Perform on the day

The decision this page helps you make

Use pace as a visible planning anchor, then adjust it for terrain, conditions, fatigue, and the evidence from training.

Keep going

Sources