Running Pace Calculator
Convert any running time and distance into a per-kilometre or per-mile pace, and project your finish time at that pace over standard race distances. The operational tool runners use to set treadmill speeds, design interval workouts, and avoid blowing up by going out too fast on race day.
About this calculator
Pace is the time required to cover one unit of distance, the conventional inverse of speed used in running and walking. The formula is: pace (min/km) = total time in seconds ÷ distance in km ÷ 60. For min/mile, multiply the kilometre distance by 1.609344 before dividing (1 mile = 1.609344 km). Speed in km/h = 60 ÷ pace in min/km. Pace is preferred over speed in running because it scales linearly with finish time at constant effort — projecting a marathon time from a 10K split is just 10K time × 4.2195 (under the unrealistic assumption that pace holds). The math also runs the other way: at a 5:00 min/km pace, a 10K takes 50:00, a half marathon (21.0975 km) takes 1:45:29, and a marathon (42.195 km) takes 3:30:58. Common reference benchmarks: world-record marathon pace is ~2:50 min/km for men and ~3:10 for women; a sub-3-hour marathon requires ~4:15 min/km sustained; a Boston Marathon qualifying time for a 35-year-old man (3:00:00) requires the same; a 5:00 min/km 10K is a serious recreational runner; an 8:00 min/km easy jog is a typical beginner pace. Edge cases: GPS-watch displayed pace is a real-time rolling average computed from instantaneous velocity, which can fluctuate by ±10–20 sec/km even at constant true effort — for race planning and post-run analysis, always use the total-time-over-total-distance pace (what this calculator returns), not the instantaneous reading. Grade-adjusted pace (GAP) on hilly courses adjusts for the metabolic cost of elevation changes and is meaningfully different from absolute pace; some watches compute it automatically using formulas derived from Minetti et al. (2002). Treadmill pace is usually slightly faster than overground pace at the same effort because of the absence of wind resistance and the assist from the belt — set the treadmill at 1% incline to approximately equalise.
How to use
Example 1 — 10K race time. You ran 10 km in 52 minutes and 30 seconds (0 hours, 52 minutes, 30 seconds). Convert to seconds: 52 × 60 + 30 = 3,150 s. Pace = 3,150 ÷ 10 ÷ 60 = 5.25 min/km = 5:15 min/km. ✓ Project to other distances at the same pace: 5K = 5.25 × 5 = 26:15; half marathon = 5.25 × 21.0975 ≈ 1:50:46; marathon = 5.25 × 42.195 ≈ 3:41:32 — but expect to slow 5–10% in the second half of a marathon, so a realistic projection is ~3:45–3:55 unless you have specifically trained for the distance. Example 2 — Half marathon in min/mile. You ran a half (21.0975 km) in 1 hour 45 minutes 0 seconds. Total time = 3,600 + 45 × 60 = 6,300 s. In min/km: 6,300 ÷ 21.0975 ÷ 60 ≈ 4.976 min/km ≈ 4:59 min/km. In min/mile: convert the distance to miles first. 21.0975 km ÷ 1.609344 = 13.11 miles. Pace = 6,300 ÷ 13.11 ÷ 60 ≈ 8.01 min/mile = 8:01 min/mile. ✓ A 4:59 min/km / 8:01 min/mile pace corresponds to about 12.04 km/h on a treadmill (60 ÷ 4.98) or 7.49 mph.
Frequently asked questions
How do I convert between min/km and min/mile?
To convert min/km to min/mile, multiply by 1.609344 (1 mile = 1.609344 km). A 5:00 min/km pace = 5 × 1.609344 = 8.05 min/mile = 8:03 min/mile. To go the other direction, divide by 1.609344: an 8:00 min/mile pace = 8 ÷ 1.609344 = 4.97 min/km = 4:58 min/km. To convert pace to speed in km/h, divide 60 by the pace in min/km: 5:00 min/km = 12 km/h. For mph, divide 60 by min/mile: 8:00 min/mile = 7.5 mph. Most American races and treadmills use miles; most of the rest of the world uses kilometres. International running magazines often quote both; race calculators on most watches let you toggle. Memorise one reference pace in both units (e.g., 5:00 min/km = 8:03 min/mile = 12 km/h = 7.46 mph) and you can quickly estimate the others by linear scaling.
Why does my GPS watch show a different pace than this calculator?
GPS watches calculate instantaneous or short-rolling-average pace (typically smoothed over 5–30 seconds) from successive position fixes. Small GPS positioning errors, momentary velocity changes (you slowed for a curb), tree-cover signal degradation, and accelerometer fusion algorithms all introduce noise of ±10–20 sec/km even at constant effort. This calculator uses the simpler and more accurate total-time-over-total-distance method, which gives one average pace for the whole effort. For training feedback during a run, the instantaneous pace on your watch is what you adjust to. For race planning, post-run analysis, and comparing performances, total-time-over-total-distance is the right number. If you start a watch a few seconds late or stop it a few seconds early, the watch's "average pace" can also differ from a true total-time pace; check both numbers if precision matters.
How can I use my current pace to predict a marathon time?
The simplest projection is to multiply your current per-km pace by 42.195 (or per-mile pace by 26.2). This assumes you can hold the same pace over a much longer distance, which is rarely true — most runners slow 5–15% in the second half of a marathon due to glycogen depletion, accumulated muscle damage, and pacing errors. A more accurate approach uses the Riegel formula: T2 = T1 × (D2/D1)^1.06, where T1 is your known time over distance D1 and T2 is the projected time over D2. For a 10K at 50:00 to project a marathon: 50 × (42.195/10)^1.06 = 50 × 4.6 ≈ 230 min = 3:50, which is more realistic than the naïve 50 × 4.2 = 3:30. The 1.06 exponent reflects the empirical fatigue curve across race distances. Race-specific training (long runs over 30 km, marathon-pace tempo work, fuelling practice) is what actually closes the gap between projection and reality.
What are the most common mistakes people make with pace?
Going out too fast at the start of a long race — the single most common cause of underperformance for distances longer than 5K. Aim for slightly negative splits (second half faster than first) and you will run a faster overall time than going out hot. Confusing pace and speed: pace numbers feel like "lower is better, higher is slower" while speed numbers are the opposite, and runners regularly trip up on this when converting between watch readouts. Using treadmill pace as if it equals overground pace; set the treadmill to 1% incline to approximately match outdoor effort. Comparing your pace to elite times without adjusting for age, sex, weather, and course — a 5:00 min/km tempo run for an amateur is genuinely fast; the same pace is a recovery jog for an elite. And ignoring environmental effects: every 10°C above ~12°C slows marathon pace by ~10 sec/km for most runners; humidity and altitude compound that.
When should I not use this calculator?
Skip it for trail running or any course with significant elevation change — per-km pace is meaningless when terrain dictates effort more than aerobic capacity. Use grade-adjusted pace (GAP) instead, available on Strava and most modern watches, which normalises pace to a flat-equivalent effort. Avoid using pace as the primary metric for interval training; for VO2-max or threshold work, heart rate, RPE, or power (with a footpod) better track the intended physiological zone than pace alone. Do not use it for ultra-distance projections (50K+) — the Riegel formula breaks down past the marathon because nutrition, sleep deprivation, and walking breaks dominate finish time. It is the wrong tool for predicting downhill or point-to-point race times (the Boston Marathon, for example, is net downhill and runs ~2% faster than a flat course at the same fitness). And do not use simple average pace to compare two efforts of very different durations or terrains — apples to apples means same race, same conditions, same course.