Skip to content
Calculator Collection

Cycling Speed Calculator

Calculates average cycling speed from distance and elapsed time. Use it to evaluate ride pace, set training targets, or compare GPS-tracked rides across similar routes.

Last updated: May 2026

Compare with similar

About this calculator

Average speed is the simple ratio of distance traveled to time elapsed: Speed (km/h) = Distance (km) / Time (hours). Variables: Distance is total route length (use your bike computer's odometer or GPS-track total distance, not Strava 'distance moved' which trims short pauses differently); Time is total elapsed time including all stops, signals, and short breaks (use 'total time' not 'moving time' for honest pace measurement). Edge cases: 'elapsed' versus 'moving' time differs by 10-30% on urban or stop-and-go rides; a 50 km commute with 3 minutes at each of 15 stoplights adds 45 minutes of stationary time, dropping average speed from 28 km/h moving-time to ~21 km/h elapsed. Headwinds reduce sustainable speed by 3-8 km/h depending on rider position; tailwinds add 2-5 km/h. Elevation profile dominates on hilly routes — a 5% sustained climb cuts speed 30-50% versus flat terrain for an average rider. For benchmarking: recreational riders average 18-25 km/h on flat road; touring riders with loaded panniers 13-18 km/h; mountain bike singletrack 8-15 km/h; competitive amateurs in flat road races 32-38 km/h sustained; UCI WorldTour stages average 40-46 km/h. For training-pace decisions, prefer power-based metrics (W/kg, normalized power) over raw speed because power isolates rider effort from wind, gradient, and road surface.

How to use

Example 1 — Weekend loop ride. You complete a 60 km loop in 2 hours 30 minutes elapsed (2.5 hours). 60 / 2.5 = 24 km/h. Verify ✓. This is a brisk recreational pace for moderately rolling terrain. Example 2 — Long touring day. You ride 85 km loaded with panniers in 5 hours 40 minutes including a 30-minute lunch stop (5.67 hours total elapsed). 85 / 5.67 = 15 km/h. Verify ✓. Slow average but realistic for fully-loaded touring on rolling terrain. If you instead use 'moving time' from your bike computer (5 hours 10 min = 5.17 h), you get 16.4 km/h — same ride, but a more flattering number that ignores the stop.

Frequently asked questions

What's the difference between average speed, moving speed, and normalized speed?

Average speed (this calculator) divides total distance by total elapsed time including all stops. Moving speed (Strava 'avg moving speed', Garmin 'moving average') divides distance by 'moving time' only — time when the bike is actually rolling above a low threshold (typically 1-2 km/h). The difference can be 10-30% on urban rides. Normalized speed is a power-equivalent metric that weights faster segments higher to reflect the metabolic cost of variable-intensity riding, but it's mostly used in racing analytics and isn't generated by basic bike computers. For training honesty, use elapsed time; for comparison against others' Strava segments, use moving time; for race pacing, use normalized power instead of any speed metric.

Why does my average speed look slower than the speedometer on my bike showed?

Bike computers display instantaneous speed, which spikes upward on descents (sometimes 50+ km/h) and during sprints. Your average across a whole ride is dominated by moderate cruising speeds (15-25 km/h for most riders), which is much lower than the peaks you remember. Hills matter asymmetrically — you spend 2-3× as long climbing at 8 km/h as descending at 50 km/h, so the slow climbing minutes dominate the average. Headwinds, traffic stops, and route choice all pull the average down further. If your average feels low, log a flat-route ride on a still day for a clearer baseline of your sustainable cruising speed.

What is a typical or 'good' average speed for cycling?

Depends on the rider, terrain, and ride length. Casual riders on flat paths average 13-18 km/h; recreational fitness riders 18-22 km/h; experienced enthusiasts 22-28 km/h on flat road; competitive amateurs in flat group rides 28-35 km/h; racers in flat road races 35-45 km/h sustained; UCI WorldTour stages 40-46 km/h. Subtract 3-5 km/h for moderate hills, 5-10 km/h for steep mountain stages, 5-15 km/h for off-road or singletrack. Bike type matters too — a road bike is 3-5 km/h faster than a hybrid, and 5-8 km/h faster than a mountain bike on the same paved route. Aerodynamics dominate above 25 km/h; a triathlon position or TT bike adds 2-4 km/h at the same effort.

Does wind affect average speed?

Yes, significantly. A 15 km/h headwind cuts cruising speed by roughly 4-7 km/h for an average rider holding the same effort, while a 15 km/h tailwind adds 3-5 km/h. The asymmetry is because aerodynamic drag scales with the square of relative wind speed: doubling the wind doesn't double the resistance, it quadruples it. On out-and-back routes the slowdown going into the wind is not fully recovered on the return, so total ride time always increases on windy days. For consistent ride-to-ride comparisons, log wind speed alongside your average speed, or stick to indoor trainers and stationary bikes when you want fully controlled benchmark conditions. Apps like Bestbikesplit and Wahoo SYSTM use power and wind models to predict actual ride time, which is more honest than speed alone.

When should I not use this calculator?

Skip it for training-load tracking — average speed conflates effort with environment (wind, hills, traffic), making it a poor proxy for fitness or training stress. Use power data (W/kg, TSS, normalized power) or heart rate zones for training prescription. Do not use it for race pacing if the course is hilly or windy; power-based pacing via Bestbikesplit or PowerAgent is more accurate. Skip it for comparing different rides unless the routes are nearly identical — comparing a flat ride at 28 km/h average to a hilly ride at 22 km/h average doesn't tell you who is fitter. For triathlon bike-leg pacing, use a target power (or perceived effort) rather than a target speed; the actual speed will depend on conditions and is a result, not a control variable.

Sources & references