How this instrument works
Cyclists usually think in speed — miles per hour — but the same time-and-distance numbers also convert the other way, into pace: minutes per mile. Pace is the more useful figure whenever you know a route's mileage and want to work out how long a stretch will take, since it multiplies directly against distance to give an estimated time.
This instrument divides the ride time you enter, in minutes, by the distance covered, in miles. It's the same underlying arithmetic runners use for running pace, applied to cycling: a commuter checking how long an 8-mile ride to work will take, a randonneur estimating whether a control-point cutoff is realistic, or a tourer planning a multi-day route all lean on exactly this division.
Because pace scales linearly with distance, once a pace figure is known for one stretch of a ride, it can be multiplied by the mileage of any other stretch at the same effort to estimate a split — which is why this page is framed around minutes per mile rather than the headline average-speed figure this site's bike-speed instrument reports.
- Enter Ride time (minutes) — the time taken to cover the distance below.
- Enter Ride distance (miles) — the distance covered in that time; this can be a full ride or just one leg of a longer route.
- Read Pace (min per mile) — the average pace for that stretch, ready to multiply against any other distance at a similar effort.
- Multiply the pace by a different mileage to estimate a split for another leg of the same route, assuming similar effort and terrain.
- Distance must be greater than zero — the instrument will prompt you if it is left at zero or blank.
Worked example — 5 miles in 30 minutes
Enter 30 into Ride time (minutes) and 5 into Ride distance (miles) — a 5-mile commute or local training loop finished in half an hour. Pace reads 6.00, meaning 6 minutes per mile.
That figure is useful for route planning: if the next stretch of a longer ride is 8 miles and the rider holds a similar effort, multiplying 6.00 by 8 gives an expected 48-minute split — handy for estimating an arrival time, or for checking a randonneuring control-point cutoff that's stated as an allowed time over a fixed distance.
Questions
What's a typical cycling pace in minutes per mile?
A relaxed recreational pace often sits around 5-6 minutes per mile (roughly 10-12 mph), a brisk club ride closer to 3-4 minutes per mile (15-20 mph), and a strong racer well under 3 minutes per mile. Terrain, wind and group drafting all shift these figures substantially, so treat them as rough reference points rather than targets.
What's the difference between this and the bike-speed instrument on this site?
Both use the same time and distance you enter — this page reports pace in minutes per mile, bike-speed reports the equivalent as average speed in miles per hour. Pace is often more useful for route and split planning, since it multiplies directly against a known distance to estimate time; speed is the more familiar headline figure for describing overall ride performance.
Is this the same formula as a running pace calculator?
Yes, exactly — pace is time divided by distance regardless of the sport. This site's running-focused pace instruments use the identical division; what changes between cycling and running pages is the realistic range of numbers you'd expect to see and the context the page is written for, not the underlying maths.
How do I use pace to plan an arrival time on a multi-leg route?
Work out your pace for one already-completed or well-known stretch, then multiply that pace by the mileage of the next leg to get an estimated time, assuming similar effort and terrain. Add that estimate to your current clock time for a rough arrival time — useful for touring, commuting to a fixed schedule, or checking against event cutoffs.
Does wind or hills affect the pace this calculator gives me?
No — this instrument only divides the time and distance you provide; it doesn't model wind, gradient or drafting. A pace calculated on a flat, calm ride won't automatically transfer to a hilly or windy one, so it's most reliable for estimating splits between legs of a route with broadly similar conditions.