Cycling Pace per km

How cycling pace per km works

In cycling, pace is how long you take to ride 1 km. Flip it around and you get speed in km/h instead: pace = total_time / distance_km and speed = distance_km / total_time_h. On the road you'll see roughly cycle touring 15–25 km/h, amateur road 25–35 km/h, and a pro Tour ~40 km/h average. What you're really fighting on the flats is wind, gradient and how aero you sit. And once the road tilts up, raw speed stops telling the story. Power-to-weight (W/kg) does. A rider at 4 W/kg goes up a 6% climb much faster than a heavier rider pushing the same absolute watts.

Example: 40 km in 1:30:00 → 1.5 / 40 = 0.0375 h/km = 2:15 / km (26.7 km/h).

Applications

Garmin Edge and Wahoo bike computers. Strava segments. Working out Audax brevet cutoffs (200/300/400/600 km), timing Brasil Ride stages, guessing your Ironman bike split, setting FTP-based training zones.

FAQ

Pace or speed? Most cyclists think in km/h, but pace per km lets you line your numbers up directly against running and triathlon splits.

Why is W/kg better than speed? Speed is at the mercy of terrain, wind and who you're drafting behind. W/kg is the rider's own engine, and that's what wins the climbs.

Flat vs hilly average? Put the same effort into a hilly course and your average can land 5–8 km/h below the flat equivalent. You lose time climbing that the descents never quite give back.