How to use the speed, distance and time calculator
Choose the question you want to answer before entering numbers. Average speed needs distance and time. Ride time needs distance and average speed. Distance needs average speed and time. The unused measurement disappears, so you do not have to fill in a speed you are trying to calculate.
The initial 40 km and 1 hour 20 minutes are an editable example. Replace them with measurements from your ride or with a planning scenario, then press Calculate. Results update on calculation rather than on every keystroke. Reset restores the example. Metric and imperial switches convert distance and speed together; hours, minutes and seconds stay the same.
Use the separate time fields literally. For a 90-minute ride, enter 1 hour and 30 minutes. Minutes must be between 0 and 59. You can leave optional seconds blank. A decimal hour is not accepted in the hours field: 1.5 hours should be entered as 1 hour 30 minutes.
The three formulas
Average speed is total distance divided by the time covering that distance. This follows the standard definition in OpenStax's speed and velocity reference. Rearranging the relationship gives the other two modes:
| Question | Formula | Compatible units |
|---|---|---|
| Average speed | Distance ÷ time | km ÷ hours = km/h |
| Ride time | Distance ÷ average speed | km ÷ km/h = hours |
| Distance | Average speed × time | km/h × hours = km |
The calculator converts hours, minutes and seconds to a single time value before doing the division. It uses unrounded numbers internally, then rounds the displayed speed or distance to two decimal places. Time results round to the nearest second, carrying 60 seconds into a minute and 60 minutes into an hour.
Miles use the exact international conversion of 1 mile = 1.609344 km, as documented in NIST's SI conversion guide. A change of units changes the number displayed, not the distance you are describing.
Worked examples
Average speed: 40 km in 80 minutes
Eighty minutes is 80 ÷ 60 hours, or 1⅓ hours. Divide 40 by 1⅓ to get 30.00 km/h. Enter 40 km, 1 hour and 20 minutes in Average speed mode to reproduce the result. If the 80 minutes excludes stops, this is a moving average.
Ride time: 60 km at 20 km/h
Divide 60 by 20 to get 3 hours. This is the riding time implied by maintaining a 20 km/h average over the route. A 20-minute café stop would make your elapsed outing 3 hours 20 minutes, even though the moving-time calculation remains 3 hours.
Distance and imperial examples
At an average 24 km/h for 2 hours 30 minutes, distance is 24 × 2.5 = 60.00 km. For an imperial example, 10 miles in 30 minutes gives 10 ÷ 0.5 = 20.00 mph. These are arithmetic examples rather than recommended riding targets.
Moving average versus elapsed average
Moving time counts the time classified as movement by your recording device. Elapsed time runs from the start to the finish, including pauses. Choose the time that answers your question, and use the same definition when comparing two rides.
For example, covering 40 km in 80 moving minutes but 100 elapsed minutes produces a 30 km/h moving average and a 24 km/h elapsed average. Neither result is wrong. They describe different parts of the outing. Device auto-pause thresholds can also make recorded moving times differ, particularly in slow traffic or on very slow climbs.
For an arrival-time plan, elapsed time is usually the more useful quantity. Calculate riding time first, then allow separately for planned breaks, navigation and delays. The calculator has no knowledge of your stop pattern.
What average speed leaves out
A single average compresses a whole route into one number. Two rides can return the same result even if one is steady and the other alternates slow climbs with fast descents. Road surface, wind, hills, traffic, equipment and effort affect what happens on the road; they are not inputs in this tool.
The climb gradient calculator explains one terrain measurement. The bike gear calculator shows the mechanical speed associated with gearing and cadence. Neither supplies a guaranteed average for a future ride. For power measurements, the W/kg calculator keeps rider power and body mass distinct from speed.
When reading our Tour de France statistics guide, keep official classification times and classified distances in their original context. A race total may include timing adjustments and route changes, so dividing two published totals need not reproduce an organizer's stage-speed statistic.
Frequently asked questions
Can I average the speeds shown for two sections?
Only if the sections took equal amounts of time. Otherwise, add their distances, add their times and divide the totals. For example, 10 km at 10 km/h takes an hour, while 10 km at 20 km/h takes half an hour. The combined 20 km in 1.5 hours averages 13.33 km/h, not 15 km/h.
Why does my result differ from my cycling app?
Check the time definition, auto-pause settings, distance source and rounding. Use matching distance and time from the same activity. A lap's distance with the full ride's time will produce a misleading answer.
Does Ride time account for climbing or headwinds?
No. It assumes the average speed you enter applies to the entire distance. Choose a scenario based on relevant experience and leave room for uncertainty; the calculator does not estimate resistance or rider effort.
Method and sources
This tool uses distance-time arithmetic and exact mile conversion, without a road-performance model. The OpenStax definition and NIST unit tables support the method. Explore the cycling tools hub for the other measurements used alongside average speed.