Pace Calculator

Running/cycling pace (min/km) and speed (km/h) from distance and time

Running or cycling pace (minutes per kilometre) and speed (kilometres per hour) are inversely related measures of the same underlying performance — pace is time-per-distance, speed is distance-per-time — and converting between them, or calculating either from a known distance and time, requires keeping that inverse relationship straight.

Why pace and speed are inverses, not the same measure scaled differently

Pace expresses effort as time required to cover a fixed distance unit (minutes per kilometre) — a lower pace number means faster movement, since less time is needed per kilometre. Speed expresses the same underlying performance as distance covered per fixed time unit (kilometres per hour) — a higher speed number means faster movement, the opposite direction from pace. Because they're inverses of each other rather than the same measure on a different scale, a faster performance shows up as a smaller pace number but a larger speed number — mixing this up (assuming both figures move in the same direction as performance improves) is a straightforward but common source of confusion when comparing training data across sources that report one measure versus the other.

A worked example

A runner who improves their performance will see their pace figure decrease (less time needed per kilometre) while their speed figure simultaneously increases (more kilometres covered per hour) — both changes represent the identical underlying improvement, just expressed through two measures that move in opposite numerical directions, which is exactly why comparing "my pace went up" against "my speed went up" requires knowing which specific measure actually improved.

How this connects to your other fitness calculations

Pace and speed feed into broader training and calorie-burn calculations — the Calories Burned Calculator uses activity intensity (which correlates with pace/speed) as part of its MET-based calorie estimate, connecting this calculator's output to broader energy-expenditure tracking.

Common mistakes

Assuming pace and speed move in the same numerical direction as performance changes — expecting both to increase together, for instance — is a common source of confusion, since they're inverse measures; pace decreases as performance improves while speed increases, and keeping that inverse relationship straight avoids misreading training data when it's reported in whichever of the two measures a specific source happens to use.