What Is a Good Average Cycling Speed? A Question With Three Honest Answers

Few questions in cycling are asked more and answered worse than ‘what is a good average speed?’ The internet replies with a single number, usually somewhere near 25 km/h, and thousands of riders on heavy hybrids in headwinds conclude something is wrong with them. Nothing is. Average speed is a property of the whole system — rider, bike, route, weather — and this article separates those parts so you can judge your number against the right comparison.

One more framing before the numbers: average speed answers ‘how fast did the system go?’ and almost nothing else. It does not answer ‘how fit am I?’ — for that, the cycling world uses power and heart rate — nor ‘was that a good ride?’, which is a question about weather, company and cake that no calculator should touch.

The system, not the cyclist

Air resistance dominates cycling physics above about 15 km/h, and it grows with the square of speed: doubling speed takes roughly eight times the power. That single fact explains most speed differences between setups. An upright hybrid with baggy clothing presents a sail to the wind; a road bike with a tucked rider presents a knife. Same legs, same fitness, easily 5–8 km/h apart on the flat. Add gradients — where gravity taxes every kilogram — luggage, knobbly tyres and a headwind, and identical riders can average 14 or 32 km/h on different days without anyone getting fitter or slower.

Benchmarks, honestly fenced

With those caveats nailed down, rough orientation for solo riding on flattish routes in calm conditions: new riders on hybrids commonly average 15–20 km/h; regular leisure riders on road bikes, 22–27; trained club riders, 28–34; strong racers hold 35–40+ in events, helped by drafting, which at speed can cut the power needed by a third. Mountain biking lives in another universe — 10–18 km/h on trails is normal and says nothing about fitness, because the resistance is terrain, not air.

Drafting: the speed that isn’t yours

Riding behind another cyclist at speed can cut the power you need by a quarter to a third, which is why group averages run so far ahead of solo ones and why comparing them is meaningless. Racing exploits this to the full — the peloton is an energy-sharing cooperative with occasional betrayals — but the effect operates on any friendly wheel. If your club’s Saturday average is your benchmark, train to the solo numbers and let the group be a pleasant surprise. If your benchmark is a solo commute, the relevant comparison is last month’s same route, same hour, similar wind — a private league table of one, which is the only table whose every entry you can trust.

Time trials exist precisely to isolate the rider: no drafting, same course, honest averages. If you ever want to know your number, that is the format that tells you.

Climbing speed: the other honest metric

On gradients, speed stops being about air and becomes a scale: power per kilogram, displayed as vertical speed. Cyclists track VAM — metres climbed per hour — because it transfers between mountains in a way road speed never can. A recreational rider might climb at 600–800 VAM; a strong amateur at 900–1,100; professionals exceed 1,500 on famous ascents. You can estimate your own from any climb: altitude gained divided by hours. It pairs naturally with this site’s gearing article, because the speed a climb demands at your gear is what decides whether VAM is a statistic or a wish.

Between flat average speed and VAM, you own two dialects of cycling honesty: one for the plains, one for the hills, and neither owes the other an apology.

Speed on the clock versus speed in the legs

There is one more seduction to name: chasing average speed corrupts rides. The rider who glances at the average and speeds up into headwinds to defend it, who skips the café the group planned, who treats every descent as a deposit and every climb as theft, is optimising a statistic at the expense of the riding. Training science is unimpressed — fitness responds to time at intensity, not to averages — and companions are unimpressed faster. Use the average the way this site’s calculator frames it: retrospectively, on benchmark loops, as a diary entry. The moment it starts steering the ride, it has stopped describing fitness and started describing anxiety.

The healthiest relationship with the number is seasonal: check the same loop monthly, note the trend in the same notebook as your weight and resting heart rate, and let three honest diaries corroborate each other. Fitness that is real shows up in all of them at once.

A closing rule of thumb

If you take one sentence from this article, take this: compare yourself with yourself, on the same loop, in the same season, and let the rest of the internet’s averages be weather reports from other climates. Your number, trended honestly, is the only benchmark that has ever coached anybody.

Speed’s place in the diary

Record the number, by all means — cyclists have kept ride diaries for a century, and the average has earned its line in them. Just file it where it belongs: beneath the date, the route and the weather, as one witness among several. Read back across a season, those lines tell a story no single ride can — fitness arriving in spring, holding through summer, the honest fade of autumn. The average was never the point of the ride. Across a year of rides, it becomes the plot.

The 10 km block test

Averages hide the story of a ride; block times tell it. Our cycling speed calculator reports your time per 10 km alongside the average, because comparing 10 km blocks across a ride exposes fading, fuelling problems and wind shifts that a single number smooths away. For tracking fitness, pick one loop, ride it monthly in similar conditions, and compare the average honestly. A 1 km/h gain on the same loop in the same season is a substantial improvement — treat it with the respect the physics says it deserves.

Common mistakes

• Comparing your solo average with a group ride’s
• Aiming training at a headline speed instead of at power or effort
• Calling a ride slow when the wind report explains it completely

Questions this raises

Related reading