Display name
Stored only on this device — no account.
Pace and speed from any run you just did.
Ran 5K in 27:30 and wondering what that means? Enter the distance and your time to get your pace per kilometer and average speed. It's the simplest way to track progress — when the pace drops at the same effort, you're getting fitter.
Running pace is the time it takes to cover a unit of distance — minutes per kilometer or minutes per mile — and it is the language runners actually train in. While speed (kilometers per hour) is the physicist's measure, pace tells a runner what they need to know mid-stride: 'I am running 5:30 per kilometer, so this 10K will take about 55 minutes.' Every training plan, from couch-to-5K to marathon programs, prescribes workouts in pace because it translates effort directly into the clock. Pace zones structure training: easy runs, tempo runs, intervals, and race pace each occupy a different band, and knowing your current race pace lets a plan set the others.
The arithmetic is simple: pace equals total time divided by distance. A 30-minute 5K is 30 / 5 = 6 minutes per kilometer. To go the other direction, multiply pace by distance: holding 5:00/km for a half marathon (21.0975 km) predicts 21.0975 x 5 = 105.5 minutes, or 1:45:30. For predicting times at new distances, the Riegel formula is the classic tool: predicted time = current time x (new distance / old distance)^1.06, which captures how pace fades as distance grows. A 25-minute 5K runner, for instance, would be predicted at 25 x (10/5)^1.06 = 25 x 2.084 = 52.1 minutes for 10K — slightly slower per kilometer than the 5K, exactly as experience suggests.
Two cautions keep pace math honest. First, race-day pace assumes even pacing, which beginners rarely achieve — most go out too fast and fade, so a predicted time is a ceiling to aim for with disciplined splits, not a guarantee. Second, hills, heat, altitude, and trail surfaces all slow real-world pace versus a flat, cool road calculation; adjust expectations by 10 to 30 seconds per kilometer on tough courses. Use this calculator to convert between pace, speed, distance, and finish time when planning training and race strategy.
Pace = total minutes ÷ kilometers, shown as mm:ss per km; average speed = distance ÷ hours.
Divide time by distance: 30 minutes / 5 km = 6 minutes per kilometer, or 6:00/km. In miles, 5K is 3.10686 miles, so 30 / 3.10686 = 9.656 minutes per mile — 0.656 x 60 = 39.4 seconds, giving 9:39 per mile. Equivalent speed: 5 km in 0.5 hours = 10 km/h. This is the classic beginner milestone: breaking 30 minutes for 5K means holding 6:00/km, and the natural next target, a 28-minute 5K, requires 28 / 5 = 5:36/km — a concrete number to aim for in interval sessions.
Take a half marathon best of 1:50:00 (110 minutes) for 21.0975 km. First find the pace: 110 / 21.0975 = 5.214 minutes per km, or 5:13/km. A naive doubling gives 3:40:00 for the marathon, but the Riegel formula corrects for fade: 110 x (42.195/21.0975)^1.06 = 110 x 2^1.06 = 110 x 2.085 = 229.4 minutes, or 3:49:24. The equivalent pace is 229.4 / 42.195 = 5.437 min/km, or 5:26/km — about 13 seconds per kilometer slower than half-marathon pace. That 13-second fade is the number to respect in training: marathon plans build the long runs specifically to shrink it.
There's no universal 'good' — a 6:00/km jog is a solid start for beginners, while trained runners hold 4:00–5:00/km comfortably. Compare against your own past runs, not strangers'.
Runners usually think in pace (minutes per km) because it maps directly to race goals; speed (km/h) is more intuitive for treadmill settings. This calculator gives you both.
Mostly by running more easy kilometers, plus one harder session a week. Watch your average pace trend over months — fitness compounds like interest.