Running Pace Calculator

Divide your total goal time in seconds by race distance in kilometers to get pace in seconds per kilometer. For example, a 50-minute 10K goal is 3,000 seconds ÷ 10 km = 300 sec/km = 5:00 per km. This calculator does that automatically — enter your goal time and distance and it shows the required pace instantly.

Multiply your pace in seconds per kilometer by the race distance. A 5:30/km pace over a 21.1 km half-marathon gives 5:30 × 60 = 330 sec/km × 21.1 = 6,963 seconds = approximately 1:56:03. Use the 'Finish time from pace' mode and the calculator handles this instantly alongside projections for other popular race distances.

Research and race data consistently support negative splits — running the second half slightly faster than the first — as the optimal strategy for most distances from 5K to marathon. Starting 5–10 seconds per kilometer slower than goal pace in the first third of a race keeps lactate levels manageable and allows a genuine acceleration in the final kilometers. Positive splitting (going out too fast) is the most common cause of a disappointing finish time for recreational runners.

Several factors elevate race-day physiological stress independent of pace: pre-race adrenaline and nerves elevate resting HR going in, race-course crowds and excitement encourage early over-pacing, heat and humidity raise the cardiovascular cost of any given pace, and the cumulative fatigue of the taper and travel disrupts routines. Accounting for a 5–15 second/km adjustment in warm or hilly conditions is common advice from coaches working with recreational athletes.

The most reliable predictor is a recent race result at a shorter distance. Using the Riegel formula (T2 = T1 × (D2/D1)^1.06) or a VDOT equivalency table translates a 10K time to a predicted half-marathon or marathon time. If no recent race data exists, use your threshold training pace (the pace you can sustain for 20–25 minutes when working hard but controlled) as a starting point for predicting 10K–15K race pace.

Climbing significantly slows running pace relative to flat road effort. A common rule of thumb is to add 6 seconds per kilometer for every 10 m of net elevation gain per kilometer of course. Downhill partially offsets this, but steep downhills cause muscle damage that slows the later stages of a race. Race calculators that ignore elevation profile will always overestimate performance on hilly courses. Always check course profiles before committing to a pace target.

Yes for flat road projections, but ultramarathons and trail races require significant additional adjustments. Technical terrain, cumulative elevation, aid-station stops, forced walking on steep sections, and fatigue from distance all make constant-pace assumptions unrealistic beyond 50 km. A common ultramarathon approach is to plan by effort and time-on-feet sections rather than targeting a specific per-kilometer pace.

Pace (min/km or min/mile) is the time it takes to cover a unit of distance. Speed (km/h or mph) is the distance covered per unit of time. They describe the same effort from different perspectives. Runners almost universally use pace because it tells you directly whether you are on schedule for a goal time — if your goal requires 5:00/km, you check your watch and immediately know whether you are on track. Speed is more common in cycling and casual fitness contexts.

The physiological cost of longer races means sustainable pace decreases with distance. Using the Riegel formula, a runner who covers 5K in 25:00 (5:00/km) would project to approximately 55:00 for 10K (5:30/km), 1:58 for a half-marathon (5:35/km), and 4:06 for a marathon (5:49/km). The pace difference between 5K and marathon pace for a given athlete is typically 45 to 75 seconds per kilometer depending on training background and aerobic development.