Why does a bike ride show pace instead of speed?

Pace and speed are the same number, flipped

Pace is time divided by distance: how many minutes it took to cover one kilometre or one mile. Speed is distance divided by time: how many kilometres or miles you cover in one hour. They are reciprocals of each other, scaled by sixty, so neither one is more correct — they are just two ways of answering the same question about the same walk or ride.

On foot the two rarely get confused, because a walking or hiking pace naturally lands somewhere between about ten and twenty minutes per kilometre, a range where "minutes per kilometre" reads intuitively. A bicycle changes the numbers enough that the same convention stops feeling natural.

Why pace is the default in the first place

Pace comes from running and hiking, where it has been the standard unit for long enough that most GPS apps report every activity the same way rather than switching conventions per activity type. A single stat — pace per kilometre or mile — also lets one app cover many kinds of outings without maintaining two separate reporting systems, one for feet and one for wheels.

The tradeoff is that a unit built around walking speeds does not scale up comfortably. A ten-minute kilometre is an easy number to picture. A three-minute kilometre, which is an unremarkable pace on a bike, takes a moment of mental math before it means anything.

Where it stops feeling intuitive

The core problem is direction: pace gets smaller as you go faster, and speed gets bigger as you go faster. On a ride that feels quick, a pace figure drops toward two or three minutes per kilometre, which does not carry the same instinctive sense of speed that a bigger, more familiar number like twenty or thirty kilometres per hour does. Nothing has gone wrong with the recording — the ride was measured correctly — it is only the direction of the number that is unfamiliar.

Converting one to the other

The conversion is one division, in either direction: speed in kilometres per hour is 60 divided by pace in minutes per kilometre, and pace in minutes per kilometre is 60 divided by speed in kilometres per hour. The same formula works for miles and mph — just keep the units consistent on both sides.

• 6 min/km ≈ 10 km/h — an easy, conversational pace
• 4 min/km ≈ 15 km/h — a steady, moderate ride
• 3 min/km ≈ 20 km/h — a brisk pace on flat ground
• 2 min/km ≈ 30 km/h — fast, or a tailwind doing some of the work
• 5 min/mile ≈ 12 mph
• 4 min/mile ≈ 15 mph
• 3 min/mile ≈ 20 mph

None of this changes what was actually recorded. Distance and duration are the two numbers everything else is built from, so a route that shows a pace figure that does not click intuitively still has an accurate distance and moving time sitting behind it — the pace stat is just one particular way of presenting the same underlying data.

What TrailCam does

TrailCam reports pace per kilometre or mile for every recorded route, whichever unit you prefer, alongside distance, moving time and elevation gain — the same four numbers regardless of which of its activity types you picked, hiking, cycling or otherwise. Spoken pace announcements during a ride use the same figure. It is free to download.