Running Pace Calculator

About this tool

Target time → pace + splits

Compute running pace from target time + distance. Outputs pace per km, pace per mile, speed in km/h + mph, plus km-by-km split table for race-day pacing.

RT-HLT-013 · Health & Fitness

Distance (km)

Target time (h : m : s)

: :

Quick set:

Pace / kilometre

—

Pace / mile

—

Speed

—

Speed (mph)

—

Split	Pace	Cumulative time
Enter target time + distance to see splits

Set target time + distance to compute pace + splits

How to use the Running Pace Calculator

Pick your race distance

Use the Quick Set buttons for standard distances (5K, 10K, 15K, half, marathon, 50K, 100K) or type a custom distance in km. The default is 42.195 km (full marathon). Race distance drives the pace calculation + the split table.

Set your target time

Enter the goal time as hours : minutes : seconds. Be realistic — use Race Time Predictor (RT-HLT-012) if you don\'t know what time is achievable. Pace calculators don\'t check whether the goal is feasible; they just compute the required pace.

Read pace per km / per mile

The headline shows your required pace per kilometre and per mile (depending on which unit you prefer). Speed in km/h and mph is shown below. Use these for race-day pacing wristbands, watch programming, or training-pace prescriptions.

Use the split table for race-day pacing

The split table shows km-by-km expected pace + cumulative time. Print it or photograph it for race-day reference. For marathons, the cumulative time at each 5K mark is the critical checkpoint — use it to course-correct if you\'re ahead or behind pace.

Pace planning — the difference between hitting your time and blowing up

Pace calculation is fundamental endurance-sport math: target time divided by target distance equals required pace. Simple arithmetic. The complexity lies in executing the pace — actually running consistently at the calculated rate when adrenaline, terrain, weather, fatigue, and other runners all conspire to push you off plan. Roughly 70-80% of amateur marathoners "blow up" (slow significantly after mile 18) due to pacing errors in the first half — usually going out too fast on adrenaline. A reliable pace plan + the discipline to execute it is the single biggest factor separating finishers from PR-setters.

Three pacing strategies — even, negative, positive

Even splits: same pace every km from start to finish. Easiest to plan, hardest to execute (most runners drift from the plan). Works best for shorter races (5K, 10K) where mental load is manageable. Negative splits: second half faster than first. Optimal race strategy for trained athletes — preserves glycogen, allows physical warm-up, mentally rewarding to pass tiring competitors in the back half. The vast majority of world-record marathon performances are run with slight negative splits. Positive splits: first half faster than second. The most common amateur pattern — adrenaline pushes a fast start, then the wall arrives at mile 18-22. Suboptimal but understandable. Recommended for amateurs: target slight negative splits — run the first half 1-2% slower than goal pace; aim for goal-pace or slightly faster in the second half. This builds in a margin for inevitable mile-20 slowdowns.

70-80% of amateur marathoners blow up due to pacing errors in the first half — usually going out 5-15 seconds per km faster than their target. The discipline to run "boringly even" early is the entire game.

Heart-rate vs pace-based pacing

Two approaches to pacing, each with strengths. Pace-based: target a specific time per km. Pros: simple, watch-friendly, race-time-friendly. Cons: ignores changing conditions — heat, hills, headwind all change the effort cost of the same pace. Heart-rate-based: target a specific HR zone. Pros: adapts to conditions automatically, prevents over-effort, ideal for trained athletes who know their zones. Cons: HR drifts up over time even at constant effort (cardiac drift), so HR-based pacing requires nuance. For ASEAN races (tropical heat): HR-based often beats pace-based — heat accelerates HR for same effort, so running by HR keeps physiological effort constant even as pace slows. Many sub-elite ASEAN marathoners race by HR rather than time, accepting slower times in exchange for not blowing up. For cool-weather races: pace-based works fine since conditions match training.

The ASEAN tropical pacing reality

Tropical heat + humidity dominates pace strategy across ASEAN races. Heat penalty: ~3-5% pace decline per 5°C above 18°C. At Singapore Marathon\'s typical 25-28°C start, expect 5-10% slower than ideal cool-weather pace. At KL Marathon\'s 28-32°C, expect 10-15% slower. Humidity adds another penalty: at 80%+ humidity, evaporative cooling fails, core temperature rises faster, pace must slow further. Practical race-day strategy for ASEAN heat: (1) start 5-10s/km slower than cool-weather goal pace; (2) carry electrolytes + drink early (don\'t wait until thirsty); (3) pour water on head + neck at every aid station for evaporative cooling; (4) use HR or RPE (rate of perceived exertion) rather than pace if conditions are extreme. Cooler ASEAN race windows: Singapore Sundown (overnight, 2am start), Penang Bridge (December, cooler), Mount Faber early-morning, Bali Marathon (cooler microclimate). Plan PR attempts around cool conditions; treat hot races as training + finish events.

10 Things to Know About Race Pace

Pace = time / distance. Simple math; the challenge is executing the calculated pace consistently for the full race.

70-80% of amateur marathoners blow up due to first-half pacing errors. Disciplined even/negative splits prevent the wall.

Negative splits (faster second half) are optimal. Most marathon world records run with slight negative splits.

Sub-3 marathon = 4:16/km pace. Sub-4 = 5:41/km. Sub-5 = 7:06/km. Sub-6 = 8:31/km.

Sub-2 marathon barrier (4:43/mi pace) broken by Eliud Kipchoge in 2019 Vienna under non-record conditions; not yet officially.

HR-based pacing adapts to conditions; pace-based pacing ignores heat + headwind. ASEAN races often run by HR.

Cardiac drift: HR rises ~5-10% over 2+ hours at constant pace. Plan HR ranges accordingly.

Tropical heat penalty: ~3-5% pace decline per 5°C above 18°C. ASEAN marathons run measurably slower than equivalent cool races.

Most amateurs go out 5-15 seconds/km too fast in marathons. The mental discipline to run slow early is the hardest part.

Race-day pacing wristbands (printed split sheets) are cheap insurance against errors. Print + bring to every race.

Frequently Asked Questions

Negative splits are objectively optimal but mentally hardest. For amateur runners targeting PRs, slight negative split (first half 1-2% slower than goal pace, second half on/under) builds in margin for unexpected slowdowns and maximises chance of hitting goal time. Even splits work for shorter races (5K, 10K). Positive splits should be avoided — the all-too-common amateur pattern.
Depends on conditions vs training. If race conditions match training (similar temperature, terrain, elevation): pace-based works fine. If conditions differ significantly (tropical race after cool-weather training, hot day after months of indoor treadmill): HR-based prevents over-effort. Hybrid approach: target pace but cap HR — if HR exceeds zone-cap, slow down regardless of pace. Used by most experienced marathoners.
Rough rule: 3-5% slower per 5°C above 18°C ideal. At 25°C: ~5-8% slower. At 30°C: ~10-15% slower. At 32°C+: 15-20%+ slower. Humidity adds further penalty (80%+ humidity ~5% additional). Practical: Singapore Marathon ~25-28°C + high humidity = subtract 10-15 minutes from cool-weather marathon goal. KL Marathon ~28-32°C = subtract 15-25 minutes. Adjust expectations accordingly.
Watch + wrist-band backup. Modern GPS watches (Garmin, COROS, Suunto) display per-km pace in real-time; some can auto-lap at km markers. Wrist-band: print this tool\'s split table on a paper wristband as backup if your watch dies or GPS drifts. Wrist-bands are mandatory for races without clear km markings. For pacing groups (3:30, 4:00 marathon pace groups), trust the pacer\'s discipline rather than your own watch.
Different paces for different workouts. Easy / long runs: 60-90s/km slower than marathon goal pace (or HR Zone 2). Marathon-pace runs: exact marathon goal pace, 8-16km segments. Tempo / threshold: 10-20s/km faster than marathon goal pace. Intervals (5K-10K pace): ~30-50s/km faster than marathon pace. VO2 max intervals (mile pace): 60-90s/km faster than marathon pace. Daniels Running Formula has detailed pace tables tied to VDOT (race fitness).
Yes, slightly. GPS measures distance via satellite positions and accumulates small errors per second. On a marathon, watch-measured distance is typically 0.5-2% LONGER than actual course (curve approximation + signal noise). Implication: your watch may show 42.5km when the course measures exactly 42.195km. Your watch pace will read slightly slower than your actual pace. For accurate splits: trust km markers + race timing mats over watch GPS. Use watch for instantaneous pace + auto-laps, but cross-check at official km markers.
Sub-3 marathon = 4:16/km = 6:51/mi. Effort is hard but not all-out — sustainable for ~3 hours with proper training. Talking is difficult; brief words OK. Heart rate ~85-88% max. Glycogen burns at ~1g/min; gels needed every 30-40 min. What it requires: ~70-90km/week training base, 16-20mi long runs, regular marathon-pace tempo work, and 1-2 years of consistent training for most natural-talent recreational runners. Sub-3 is achievable for ~5-10% of male marathon finishers; ~1-2% of female.
The math is exact — pace = time / distance. The challenge is executing the calculated pace consistently. Real race performance differs from the math due to: (1) pacing discipline; (2) conditions (heat, wind, hills); (3) fitness level; (4) fueling + hydration. Use the calculator for planning; trust race-day execution + conditions for actual outcomes.
No. All calculations run in your browser via JavaScript. Open DevTools → Network and confirm zero outbound requests. Distance + target time stay on your device. Safe for personal race planning.
Pair with: VO2 Max Calculator (RT-HLT-011) for fitness benchmarks; Race Time Predictor (RT-HLT-012) to validate your target time; Sweat Rate Calculator (RT-HLT-014) for race-day hydration; Heart Rate Calculator (RT-HLT-009) for HR zones. External: Garmin Connect / Strava / COROS for training tracking; TrainingPeaks for structured plans; Daniels Running Formula book for evidence-based training prescription.

Running Pace Calculator