Running Pace Calculator

Share:

Compute running pace from target time and distance: pace per km and per mile (1 mi = 1,609.344 m), speed in km/h and mph, and a km-by-km split table for race-day pacing. Standard distances follow World Athletics rules.

RT-HLT-013 · Health & Fitness

Running Pace Calculator

⚠ Disclaimer: FOR FITNESS AND EDUCATIONAL PURPOSES ONLY. NOT MEDICAL ADVICE. These calculations are based on population-average formulas and may not reflect your individual physiology. Consult a physician before beginning any exercise programme, especially if you have cardiovascular conditions, pregnancy, or other medical concerns. Heart rate, body composition, and metabolic estimates from this tool are not substitutes for direct medical measurement.
: :
Quick set:
Pace / kilometre
Pace / mile
Speed
Speed (mph)
SplitPaceCumulative time
Enter target time + distance to see splits
Set target time + distance to compute pace + splits
📅 Research current as of 13 Sep 2026 · Sources: World Athletics standard distances (marathon 42.195 km, half marathon 21.0975 km); NIST SP 811 mile = 1,609.344 m; Ely et al. 2007 for the heat effect
Standards, published formulas, and reference data are revised over time — check against a current authoritative source before relying on these figures.
Advertisement
After results · AD-W1Responsive · Post-tool — peak engagement

How to use the Running Pace Calculator

Pick your race distance

Use the Quick Set buttons for standard distances or type a custom distance in km. The half marathon (21.0975 km) and marathon (42.195 km) are the distances defined in World Athletics Technical Rules; the default is the 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 our Race Time Predictor 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, using the international mile of 1,609.344 m (NIST SP 811); the tool applies the reciprocal 0.621371 mi/km, which agrees with the exact figure to better than one part in a million. 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.

Advertisement
After how-to · AD-W2Responsive

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

Pace calculation is fundamental endurance-sport arithmetic: target time divided by distance equals required pace. The complexity lies in executing it — holding the calculated rate when adrenaline, terrain, weather, fatigue and other runners all push you off plan. The common amateur error is starting faster than goal pace and slowing badly in the last third; a split table you have actually read before the start is the cheapest defence against it.

Three pacing strategies — even, negative, positive

Even splits: the same pace every kilometre. Easiest to plan, hardest to execute. Negative splits: second half faster than the first — the pattern most coaches recommend for a goal race because it protects against the early over-pace that ends in a slow final third. Positive splits: first half faster than the second, the most common amateur pattern and usually the unintended one. A practical target: run the first half a percent or two slower than goal pace and aim for goal pace or slightly faster in the second half, which builds a margin for the inevitable late slowdown. This tool's split table assumes even pacing; adjust the early splits by hand if you plan a negative split.

The split table is only useful if the early kilometres in it feel too slow. Adrenaline at the start line makes goal pace feel easy; the table is there to overrule that feeling.

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 tropical races: heart-rate or perceived-effort pacing has an advantage, because heat raises heart rate at a given pace and a fixed pace target then means a rising effort. For cool-weather races: pace-based pacing works well when conditions match training.

The ASEAN tropical pacing reality

Tropical heat and humidity dominate pace strategy across Southeast Asian races. Ely and colleagues analysed marathon results against wet-bulb globe temperature and found performance slowing progressively as WBGT rose, with slower runners penalised more than the leaders (Ely et al., Med Sci Sports Exerc 2007;39(3):487-493). Humidity is the multiplier: when evaporative cooling fails, core temperature rises faster and pace must fall further. Practical race-day strategy for the heat: (1) start slower than your cool-weather goal pace and let the second half decide; (2) drink early and carry electrolytes rather than waiting for thirst; (3) use water on head and neck at aid stations; (4) race by heart rate or perceived effort rather than pace if conditions are extreme. Plan personal-best attempts around the cooler windows — overnight starts and the cooler months — and treat hot races as training and finishing events.

Pace arithmetic, standard distances and why heat rewrites the plan

01

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

02

One mile is exactly 1,609.344 m (NIST SP 811), so pace per mile = pace per km × 1.609344. This tool converts through the rounded reciprocal 0.621371 mi/km — within a millionth of the exact figure.

03

Marathon = 42.195 km and half marathon = 21.0975 km under World Athletics Technical Rules — the exact figures behind the Quick Set buttons.

04

Sub-3 marathon = 4:16/km pace. Sub-4 = 5:41/km. Sub-5 = 7:07/km. Sub-6 = 8:32/km (each is the goal time ÷ 42.195, rounded to the second).

05

Eliud Kipchoge's 1:59:40 in Vienna (2019) is 2:50/km — run under paced conditions that World Athletics does not ratify as a record.

06

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

07

Cardiovascular drift: over a long effort heart rate rises at a constant pace, more so in heat and with dehydration (ACSM 2007) — plan HR ranges, not a single number.

08

Marathon times slow progressively as wet-bulb globe temperature rises, and slower runners lose more than the leaders (Ely et al. 2007).

09

The common amateur error is starting faster than goal pace; the discipline to run the early kilometres "boringly" on the table is the hardest part.

10

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

Frequently Asked Questions

  • A slight negative split is the safer plan for a goal race: run the first half a percent or two slower than goal pace and the second half on or under it, which builds a margin for the late slowdown. Even splits are realistic for shorter races (5K, 10K). Positive splits — fast start, slow finish — are the common unintended pattern. Note that this tool's split table assumes even pacing.

  • 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.

  • Measurably, and more the slower you are. Ely and colleagues' analysis of marathon results against wet-bulb globe temperature (Med Sci Sports Exerc 2007;39(3):487-493) found times slowing progressively as WBGT rose, with the penalty larger for slower finishers than for the leaders. High humidity compounds it because evaporative cooling fails. The honest answer for a Singapore or Kuala Lumpur marathon is to set the goal from a hot training run, not from a cool-weather race.

  • Watch plus a printed backup. GPS watches show real-time pace and can auto-lap at kilometre markers; a paper wristband printed from this tool's split table survives a dead battery or a GPS drift. Where a pacing group runs your goal time, its pacer's discipline is usually more reliable than your own early-race judgement.

  • Coaches structure training paces relative to goal race pace, and the schemes differ in detail. A common one: easy and long runs clearly slower than marathon pace (heart-rate Zone 2 if you train by HR); marathon-pace segments at exactly goal pace; tempo runs a little faster; intervals at roughly 5K–10K race pace. Jack Daniels' Daniels' Running Formula tabulates paces against a fitness index (VDOT). Treat any published table as a starting point to adjust against your own races.

  • Yes, slightly. GPS accumulates small positional errors and cuts curves differently from the measured line, so watch distance on a certified course is commonly a little longer than the official distance, and watch pace correspondingly reads slower than your real pace. For splits, trust the course's kilometre markers and timing mats; use the watch for instantaneous pace and auto-laps, and cross-check at the markers.

  • Sub-3 is 4:16/km or 6:52 per mile. It is a hard but not all-out effort sustained for three hours: talking is difficult, brief words are possible. Fuel matters at this duration — most runners take carbohydrate at regular intervals. It typically demands a substantial weekly mileage base, regular marathon-pace work and years of consistent training; whether it is realistic for you is a question for your recent race results and our Race Time Predictor, not for a pace table.

  • The arithmetic is exact — pace equals time divided by distance, and the mile conversion uses 0.621371 mi/km, the reciprocal of the exact 1,609.344 m mile to six significant figures. Everything else is execution: pacing discipline, heat, wind, hills, fitness and fuelling all separate the plan from the result. Use the calculator for planning and the splits as checkpoints.

  • No. All calculations run in your browser via JavaScript; distance and target time stay on your device and nothing is sent to our servers.

  • Pair it with our VO2 Max Calculator for fitness benchmarks, the Race Time Predictor to sanity-check the target time, the Sweat Rate Calculator for race-day hydration, and the Heart Rate Zones Calculator if you race by heart rate rather than pace.

Related News

You may be interested in these recent stories from our newsroom.

View all news →

Method & sources

How it computes

Pace per km = target time ÷ distance; pace per mile and mph use the international mile of 1,609.344 m (NIST SP 811); the split table repeats the even pace for each kilometre and the final partial kilometre. Quick-set distances follow World Athletics: half marathon 21.0975 km, marathon 42.195 km. Planning arithmetic, not coaching or medical advice.

What this tool implements

  • Even-split table: every kilometre at the same pace; negative and positive splits are described in prose, not computed
  • Mile = 1,609.344 m exactly (NIST SP 811 Appendix B.9); the page converts through the rounded reciprocal 0.621371 mi/km, within one part per million
  • Standard distances per World Athletics: 5 km, 10 km, half marathon 21.0975 km, marathon 42.195 km; the 15 km, 50 km and 100 km quick-set buttons are common race distances
  • Heat guidance cites Ely et al. 2007 (marathon slowing with WBGT) and is presented as qualitative planning advice, not a computed correction

Sources

What can make this go out of date

  • None at runtime — the distances and the mile are fixed definitions.
Advertisement
Pre-footer · AD-W3 728 × 90