About the Cycling Speed
The Cycling Speed Calculator turns a ride's distance and total time into an average speed, giving cyclists a quick way to gauge pace across training rides, commutes, or races without doing the division by hand. It is built for simple after-ride math, not GPS-file analysis, so it works from just two numbers: how far you rode and how long it took.
How It Works
You enter distance in miles and ride time in minutes. The tool converts minutes into hours, divides distance by that time to get average speed in mph, then also reports the equivalent in km/h and the pace expressed as minutes per mile. Because it only uses total distance and total time, it reflects your overall average, including stops at lights or rest breaks, not your moving-only speed.
Formula & Methodology
Start by converting ride time to hours: divide minutes by 60. Then divide distance by that hour figure to get mph. For example, 75 minutes is 1.25 hours; a 20-mile ride divided by 1.25 hours gives 16 mph. To get pace instead of speed, divide total minutes by total miles directly, which gives minutes per mile in the fmtMinutes format (minutes and seconds).
Examples
Steady club ride
A rider covers 20 miles in 75 minutes. Dividing 20 by 1.25 hours gives an average speed of 16.00 mph (25.75 km/h), with a pace of 3:45 per mile.
Short commute
A commuter rides 6.5 miles in 28 minutes (0.4667 hours), for an average speed of about 13.93 mph and a pace of roughly 4:18 per mile.
Advantages
- Converts raw ride numbers into both mph and km/h in one step, useful for riders who train with different unit preferences
- Reports pace per mile alongside speed, which is handy for comparing against interval or time-trial targets
- Works from just two inputs, so it is fast to use immediately after a ride without needing a GPS file
Common Mistakes
- Entering ride time in hours instead of minutes, which produces a wildly inflated speed
- Including long stops (café breaks, mechanical fixes) in the total time, which understates true riding speed
- Mixing up distance units by entering kilometers while the calculator expects miles
Edge Cases to Watch For
- If ride time is entered as zero or a negative number, the calculator returns an error instead of a result, since dividing by zero or a negative duration has no meaningful speed.
- The result is a whole-ride average, so it does not separate out coasting, climbing, or stopped time the way a bike computer's moving-average function would.
- Speed is only as accurate as the distance entered - GPS-tracked mileage and cue-sheet or odometer mileage can differ slightly, which will shift the computed mph.
Common Use Cases
- Recreational cyclists tracking how their average speed changes over a training season
- Commuters comparing route or day-to-day variation in average speed
- Coaches or riders converting a ride's average speed to km/h for comparison with metric-based training plans