Cycling Speed Calculator
Calculate average cycling speed by dividing distance covered by time elapsed. Use it for tracking ride performance, comparing routes, and benchmarking against fitness milestones across road, mountain, and gravel cycling.
Last updated: May 2026
Compare with similar
About this calculator
The formula is: average speed = distance ÷ time. With distance in kilometers and time in hours, the result is km/h; with miles and hours, it's mph (multiply km/h by 0.621371 to convert). Edge cases: zero time produces division by zero; very short rides (under 5 km) produce unstable average speeds dominated by traffic stops or acceleration phases. Average speed is the standard metric for ride performance but it masks important detail — the same 20 km/h average could come from steady 20 km/h flat riding, mixed 30 km/h descents and 12 km/h climbs, or extended periods at 25 km/h interrupted by 0 km/h traffic stops. For training analysis, use moving average (excludes time stopped) rather than overall average. Speed benchmarks vary dramatically by terrain, equipment, fitness, and conditions. Road cycling on flat terrain at moderate effort: recreational rider 15–22 km/h (9–14 mph); fit amateur 22–28 km/h (14–17 mph); strong amateur racer 28–35 km/h (17–22 mph); pro touring stage average 40+ km/h (25+ mph); pro time-trial 50+ km/h (31+ mph). Mountain biking is dramatically slower due to terrain — recreational MTB ride averages 10–15 km/h, technical singletrack 8–12 km/h. Gravel sits between road and MTB at 18–25 km/h on rolling terrain. Major speed factors beyond fitness: wind (a 20 km/h headwind can drop pace by 30%+), gradient (climbing at 8% slows pace to 1/3 of flat speed for the same power), drafting (riding in a pack reduces individual effort by 30%+, allowing higher pack speeds), road surface, traffic, equipment (aero road vs. comfort tourer differ by 10%+ at same power).
How to use
Example 1 — Saturday road ride. You covered 65 km in 2 hours 30 minutes. Convert time to hours: 2.5 hours. Enter 65 for Distance and 2.5 for Time. Result: 26.0 km/h. Verify: 65 / 2.5 = 26.0. ✓ A 26 km/h (16.2 mph) average on a 65 km road ride is solid recreational performance — fit amateur cyclists typically average 25–30 km/h on flat to rolling terrain in good conditions. Example 2 — Hilly weekend ride. 80 km in 3 hours 45 minutes on mixed terrain with 1500m elevation gain. Time = 3.75 hours. Enter 80 and 3.75. Result: 21.3 km/h. Verify: 80 / 3.75 ≈ 21.33. ✓ A 21.3 km/h average on a hilly 80 km ride is good amateur performance — the elevation gain (1500m over 80 km = ~1.9% average grade) significantly impacts achievable average speed. For comparison, the same fitness on a flat 80 km ride would yield 25–28 km/h. When sharing or comparing ride data, always include elevation gain and total elevation profile because raw speed without terrain context is meaningless.
Frequently asked questions
How does wind affect average cycling speed?
Significantly more than most cyclists expect. At cycling speeds, aerodynamic drag is the dominant resistance — roughly 70-80% of total energy at speeds above 25 km/h goes to pushing air. A 20 km/h headwind effectively makes the apparent wind speed 40+ km/h, requiring 2-3× more power to maintain the same ground speed. The result: a 30 km/h pace in calm conditions might drop to 18-22 km/h in a 15 km/h headwind for the same effort. Tailwinds help less than headwinds hurt because aerodynamic drag scales with the square of velocity. Crosswinds also impact speed (about 20-40% slowdown for the same effort) and require steering corrections that consume additional energy. For training analysis and route comparisons, normalize for wind direction whenever possible — using normalized power (NP) from a power meter is the gold standard for effort-based comparison across windy and calm rides. Strava's "weighted average pace" attempts similar normalization but is far less accurate than actual power data.
How does gradient affect cycling speed?
Massively. Climbing at sustained gradient drops pace to roughly 1/3 of flat-terrain speed at the same effort. Example: a rider averaging 30 km/h on flat at 220 watts will average roughly 12-15 km/h up a 6% climb at the same wattage. The math: at flat-terrain speeds, most power goes to aerodynamic drag; on climbs, most power goes to lifting the rider+bike mass against gravity. The shift in dominant resistance means the same power produces different speeds. Speed-vs-gradient rule of thumb: each 1% of gradient drops speed by roughly 3-4 km/h for amateur cyclists at constant power. Descents return the favor: a moderate descent can boost speed to 50-60 km/h with minimal pedaling, but maximum safe descent speed is limited by bike control, road conditions, and braking ability. For ride comparisons, always include elevation gain — flat 50 km at 28 km/h is very different from hilly 50 km at 22 km/h, and the latter often represents more total effort despite the lower average speed.
How much faster does drafting make you?
In a 2-rider pace line, the rider drafting saves 25-30% of effort vs. solo riding at the same speed. In a 4-6 rider group with proper rotation, the average effort per rider drops 30-35%. In a 20+ rider peloton with no rotation needed (pure drafting), riders deep in the pack save 40-50% of effort. This is why pro cycling pelotons average 40+ km/h while individual time-trial pace for the same riders is 50+ km/h — the group dynamic dramatically reduces aerodynamic drag for everyone except the leader at the front. For amateur group rides, even casual drafting at the back of a 4-rider rotation makes a 25 km/h pace feel like 19-20 km/h solo effort. Skill at drafting (maintaining position, smoothness, predicting moves) is a major performance factor in road racing beyond raw fitness. For solo training rides, draft savings don't apply — speed and effort are 1:1, and your average speed is a direct reflection of your individual power output and aerodynamics.
What are the most common mistakes people make tracking cycling speed?
The biggest is comparing rides without normalizing for wind, gradient, and route — a 30 km/h average on a flat sheltered course is very different from a 30 km/h average on a hilly windy one. The second is using overall average (including stopped time) instead of moving average, which makes urban rides with traffic stops look much slower than they actually were on the road. The third is comparing your speed to others on Strava without considering they may have drafted in a group, had perfect conditions, or used aerodynamic equipment. The fourth is over-relying on average speed instead of power data; a power meter reveals actual effort independent of conditions. The fifth is focusing on speed when training instead of structured intervals; many recreational cyclists ride the same medium effort every ride and plateau — varied intensity (long easy rides, threshold intervals, VO2 max intervals) produces faster gains. The sixth is buying expensive aero gear hoping for big speed gains; a $2,000 aero bike upgrade might add 0.5-1 km/h on flat solo riding at most, while a $200 watt-targeted training plan can add 3-5 km/h to sustained pace.
When should I not use average speed as a training metric?
Skip it as the primary metric for structured training; power data (from a power meter) and heart rate are more reliable indicators of effort independent of conditions. It is the wrong tool for comparing rides across different terrain — a hilly ride at 22 km/h often represents more total effort than a flat ride at 28 km/h. Do not use it as the primary metric for mountain biking, where technical difficulty matters far more than raw speed; use moving time, elevation gain, and Strava segment performance instead. For long endurance rides (3+ hours), pace tends to decline naturally due to fatigue and fueling needs — comparing average across the full duration vs. fresh-condition pace is misleading. In races and group rides, your individual speed is not a fair comparison to others' because of drafting effects. And for indoor training (Zwift, smart trainer), virtual world physics are simplified and pace is often artificially fast compared to outdoor riding at the same effort. For meaningful training metrics, use power-based zones, heart-rate zones, or rate of perceived exertion — average speed is mostly useful for ride-to-ride comparisons of the same loop in similar conditions.