Pace Calculator

Calculate running pace, projected finish time, or required distance. Convert between min/km and min/mile. Plan race splits, set training pace zones, and project finish times for 5K through marathon distances.

km
hrs
min
sec

Enter your values above to see the results.

Tips & Notes

  • For race planning, calculate your required pace first (time goal ÷ distance), then run your first training sessions at that pace to assess how it feels — adjust the goal if it is clearly too ambitious or too conservative.
  • GPS watches typically measure distance within 1–3% accuracy on open roads; accuracy drops in cities with tall buildings and on trails. For pace accuracy over a 10K, a 2% GPS error translates to 6 seconds per km.
  • A negative split strategy — running second half 1–3% faster than first half — is statistically associated with better race performances across all distances from 5K to marathon.
  • Easy training run pace should feel genuinely easy — 90 to 120 seconds per km slower than your 5K race pace. If you cannot hold a full conversation, you are running too fast for an easy day.
  • Heat slows pace by approximately 2–8 seconds per km for every 5°C above 15°C. Do not compare race times run in very different temperatures without accounting for heat adjustment.

Common Mistakes

  • Starting a race too fast — the most common pacing error. Going out 10–15 seconds per km faster than goal pace in the first kilometre feels easy due to adrenaline but significantly increases the probability of blowing up in the second half.
  • Using race pace for easy training runs — easy runs should be genuinely comfortable and conversational, not a moderate effort. Many recreational runners run easy days 30–60 seconds per km faster than they should.
  • Ignoring elevation when setting pace targets — running up 5% grade slows pace by approximately 45–60 seconds per km compared to flat; targeting flat-equivalent pace on a hilly course leads to going out too hard on uphills.
  • Treating GPS pace as exact — wrist GPS pace displays have 5–10 second per km noise even in good conditions. Rely on average pace over 1+ km splits rather than instantaneous pace display.
  • Not accounting for wind — a strong headwind can slow pace by 15–30 seconds per km at the same effort level. Running into a headwind and comparing pace to a calm-day run is a misleading comparison.

Pace Calculator Overview

Pace calculation is the bridge between the effort you feel during a run and the performance you produce on race day. Getting it right means no more blowing up at kilometer 8 or leaving time on the table.

Pace, speed, and time conversion formulas:

Core pace relationships: Pace (min/km) = Time (minutes) ÷ Distance (km) Time = Pace × Distance Distance = Time ÷ Pace Speed (km/h) = 60 ÷ Pace (min/km) Pace (min/km) = 60 ÷ Speed (km/h)
EX: Runner completes 10 km in 52 minutes 30 seconds (52.5 minutes) Pace = 52.5 ÷ 10 = 5:15 per km (5 minutes 15 seconds per km) Speed = 60 ÷ 5.25 = 11.43 km/h Pace in min/mile: 5.25 × 1.60934 = 8:27 per mile Goal: Run half marathon (21.1 km) in under 1:50:00 (110 minutes) Required pace = 110 ÷ 21.1 = 5:13 per km — 2 seconds faster per km than current 10K pace At 10K fitness, 5:13/km for 21.1 km is achievable with proper pacing and training.

Calculating finish time from pace:

Race distance conversion reference: 5K = 5.0 km = 3.107 miles 10K = 10.0 km = 6.214 miles Half marathon = 21.097 km = 13.109 miles Marathon = 42.195 km = 26.219 miles
EX: Marathon goal time 3:45:00 (225 minutes) Required pace = 225 ÷ 42.195 = 5:20 per km = 8:35 per mile First half split (even): 21.097 km × 5.32 min/km = 1:52:21 (first half slightly conservative) Second half split (negative): 21.098 km × 5.08 min/km = 1:47:38 (slightly faster second half) Negative split strategy: 5 minutes faster in second half → finish strong, less risk of blowup.

Common race distances — pace benchmarks:

Finish time5K pace (min/km)10K paceHalf marathon paceMarathon pace
Sub-20:00 (5K) / Sub-3:00 (Marathon)3:594:084:164:16
Sub-25:00 / Sub-3:454:595:145:205:20
Sub-30:00 / Sub-4:305:596:196:236:24
Sub-35:00 / Sub-5:156:597:227:277:28
Sub-40:00 / Sub-6:007:598:268:318:32

Pace, speed, and time conversion reference:

Training run typePace relative to 5K race paceHeart rate zonePurpose
Easy / long run90–120 sec/km slowerZone 1–2 (60–70% MHR)Aerobic base, recovery
Tempo / threshold10–20 sec/km slower than 5KZone 4 (80–90% MHR)Lactate threshold, race fitness
5K race pace intervals5K race paceZone 4–5 (85–95% MHR)Speed, VO2 max
Fast intervals (faster than 5K)10–30 sec/km faster than 5KZone 5 (90–100% MHR)Top-end speed, neuromuscular
Marathon pace30–40 sec/km slower than 5KZone 3–4 (75–85% MHR)Race-specific endurance

Pacing strategy determines as much as fitness on race day. Research consistently shows that negative splits — running the second half slightly faster than the first — are associated with better overall performances and more consistent results than positive splits (starting too fast). The mechanism is physiological: starting conservatively preserves glycogen and delays lactate accumulation, allowing you to push in the second half rather than survive it. A simple target: run the first half 1–3% slower than goal pace, then assess at the halfway point and decide whether to accelerate.

Frequently Asked Questions

A 30-minute 5K requires an average pace of exactly 6:00 per kilometer or 9:39 per mile. To run sub-30:00, you need to average slightly under 6:00/km — a 29:45 finish requires 5:57/km, and a 29:00 finish requires 5:48/km. In training, this means your threshold pace (tempo runs) should be around 5:45–5:55/km, and your interval pace should be around 5:30–5:45/km. Your easy runs would be around 7:00–7:30/km. A sub-30 minute 5K is an achievable milestone for most recreational runners with 3–4 months of consistent structured training.

Pace and speed express the same information from opposite perspectives. Pace tells you how long it takes to cover one unit of distance (e.g., 5:30 per kilometer). Speed tells you how much distance you cover per unit of time (e.g., 10.9 km/h). They are mathematical inverses: speed in km/h = 60 divided by pace in min/km. Running prefers pace because it allows direct comparison with distance markers (splits at each km or mile), while cycling typically uses speed. To convert: 5:00/km pace = 12.0 km/h speed; 6:00/km = 10.0 km/h; 4:30/km = 13.3 km/h.

The relationship between 5K pace and marathon finish time is not linear — the marathon requires running at roughly 20–30 seconds per km slower than 5K race pace for most recreational runners. A common estimation formula is Riegel's formula: marathon time = 5K time × (42.195 ÷ 5)^1.06. For a 25-minute 5K runner, this gives approximately 3:36 for the marathon. A simpler approximation: marathon pace is roughly your 5K pace plus 25–35 seconds per km for recreational runners. Elite runners (like sub-14:00 5K) can hold marathon pace closer to 5K pace plus 15–20 seconds per km.

GPS pace accuracy varies considerably. During a steady-state run in open conditions, modern GPS watches (Garmin, Polar, Coros) measure instantaneous pace with 5–10 second per km variation — this appears as the pace display fluctuating even at constant effort. Cumulative distance accuracy is better: typically within 1–2% over 10+ km in open terrain. In urban canyons, under tree cover, or during direction changes (as in track workouts), accuracy drops further. For accurate split pacing, use 1-km split pace averages rather than instantaneous pace, and calibrate on a measured course if race precision matters.

Training pace zones based on your current 5K race pace provide the most practical guidance. Easy runs (which should be 70–80% of total weekly volume): 5K pace plus 90–120 seconds per km — fully conversational. Long runs: 5K pace plus 60–90 seconds per km. Tempo runs: 5K pace minus 10–20 seconds per km — comfortably hard, can speak 2–3 words. 5K race pace intervals: at your 5K race pace with equal recovery. Fast intervals: 10–30 seconds per km faster than 5K pace. Most recreational runners make the mistake of running easy days too fast (closer to tempo effort), which prevents full recovery and reduces quality in hard sessions.

Heat significantly impairs running performance. Research shows that for every 5°C above approximately 10–15°C, performance declines by roughly 2–8% depending on the individual and conditions. At 25°C compared to 10°C, expect pace to slow by approximately 15–30 seconds per km at the same effort. At 35°C and high humidity, slowing by 45–60 seconds per km versus optimal conditions is common. Humidity matters because sweating provides less cooling when the air is already saturated with moisture. A practical adjustment: on hot days, run by effort or heart rate rather than pace, and do not compare hot-day times directly to performances in cool conditions.