Health FIELD NOTES · 4 MIN READ
How Running Pace Works
Pace is time over distance: converting km and mile paces, predicting finish times from a target pace, and how running speed feeds the MET calorie formula.
Runners never say "I ran at 11.5 km/h." They say "I ran 5:15 per kilometer." Pace — time per unit distance — is just speed turned upside down, but the flipped form is genuinely more useful: it turns directly into finish-time predictions, lap splits, and the minutes you feel in your legs. The whole system is two numbers and one conversion factor.
Pace and speed: two reciprocals
Speed is distance over time; pace is time over distance. Both describe the same run:
pace (seconds per km) = total seconds / distance in km
speed (km/h) = distance / (total seconds / 3600)
Because they are reciprocals, fast paces are small numbers and slow paces are large ones — 4:00/km is elite, 7:30/km is a relaxed jog. There is a quick mental conversion between the two: divide 60 by the pace in decimal minutes to get km/h. A 5:00/km pace is 5.0 minutes, and 60 ÷ 5 = 12 km/h. Watch the units: pace uses minutes plus seconds (5:12 means 5.2 minutes, not 5.12), which is why letting a calculator do it is safer than mental arithmetic.
Converting between kilometer and mile paces
One mile is 1.609344 km exactly, so mile pace is kilometer pace multiplied by it:
pace per mile = pace per km × 1.609344
A runner at 5:00/km covers each mile in 300 s × 1.609344 ≈ 483 s = 8:03 per mile. Popular rules of thumb fall out of this: "add 20–30 seconds to convert" works near easy-jog paces, while race-pace conversions in the 4–6 min/km range add roughly 60%. The direction reverses for mile-to-km (divide instead), and treadmill users should remember the belt is often calibrated in mph — 6.0 mph is 9:39 per mile, or about 5:59/km.
A full worked example: 10 km in 52:30
Take a 10 km run finished in 52 minutes 30 seconds — 3,150 seconds. The calculator reduces every question to division:
pace per km: 3,150 / 10 = 315 s = 5:15/km
pace per mile: 3,150 / 6.2137 = 507 s ≈ 8:27/mi
speed: 10 km / 0.875 h = 11.43 km/h (7.10 mph)
Check the reciprocal shortcut: 5:15 is 5.25 decimal minutes, and 60 ÷ 5.25 = 11.43 km/h — it matches exactly. The shortcut is exact whenever you remember that 5:15 means 5.25, not 5.15; treating a colon as a decimal point is the single most common pace-arithmetic mistake, which is why the calculator works in raw seconds and rounds only the display.
The reverse problem: predicting a finish time
Flip the division and pace becomes a race predictor. Finish time = pace × distance, so a runner targeting 5:30/km on the marathon distance (42.195 km) gets:
finish = 5.5 min/km × 42.195 km = 232.07 min ≈ 3:52:04
That is how race calculators translate a goal into a wrist-check time, and how pace bands convert it into splits at every kilometer marker. The same logic works in reverse for planning training: if you want 400 m repeats in 90 seconds, that is 3:45/km — a pace you should be able to hold for one lap, not for an hour. For adding up segment times across a route — warm-up, intervals, cooldown — a duration tool that handles hours, minutes, and seconds without decimal confusion does the bookkeeping.
Where pace meets calories
Speed is also the main input to energy expenditure, through the MET (metabolic equivalent) system: calories = MET × weight in kg × hours. One MET is quiet sitting; the calculator's table lists running at 9.8 METs and walking at 3.5. A 70 kg runner out for 45 minutes burns 9.8 × 70 × 0.75 ≈ 515 kcal. Notice what is not in that formula: distance. Two runners covering the same route at the same pace burn nearly the same energy regardless of fitness, because the work is moving the same mass over the same ground — the faster runner just finishes sooner. Pace sets the rate of burning; time and body weight set the total.
Pacing in the real world
Formula pace is a clean average; real runs are messy. Hills, wind, heat, and GPS drift all bend the numbers, and even-split races are rarely optimal — most well-paced races are slightly negative splits (second half faster) because starting conservatively delays fatigue. Treat computed pace as the plan and the watch as the feedback loop: if your average 5:12/km includes two minutes lost to a hill, your flat-ground pace is better than the headline number suggests.
Try it yourself
Enter any distance and time in the Pace Calculator — it returns pace per km and per mile, plus both speeds, simultaneously. The Calories Burned Calculator applies the MET formula above to running, walking, cycling, swimming, and a dozen other activities. And the Time Duration Calculator subtracts one clock time from another and breaks the result into days, hours, minutes, and seconds — handy for turning wall-clock start and finish times into the raw seconds the pace math needs.