Why distance alone lies about ride time
Every cyclist has made the same mistake: looked at a 40-kilometre route, divided by a remembered average speed, and promised to be home an hour before they actually were. Distance alone is a poor predictor of ride time because it ignores the two things that slow cyclists down most: climbing and everything else that is not pedalling. A flat 40 kilometres at 25 km/h takes 96 minutes in a perfect world. Add 500 metres of climbing, a couple of traffic lights, a headwind on the way home, and a cafe stop, and the same route takes two and a half hours. The calculator on this page handles the biggest predictable factor, elevation gain, by adding about four minutes for every 100 metres climbed. That single correction turns a fantasy estimate into a plan you can actually ride to, and it explains why hilly routes always feel longer than the map suggests.
The formula: flat time plus climbing time
Ride time in minutes equals distance divided by your flat pace, times 60, plus elevation gain divided by 100, times 4. A 40 km ride with 500 m of climbing at a 25 km/h flat pace takes 96 minutes of flat time plus 20 minutes of climbing time, or 116 minutes in total. A flat 20 km commute at 20 km/h takes exactly 60 minutes. A 60 km mountain day with 1,000 m of climbing at 30 km/h takes 120 minutes plus 40 minutes, or 160 minutes. Your flat pace is the speed you hold on level ground in calm conditions, not your fastest downhill speed and not your overall average including stops. If you do not know your flat pace, ride a flat 10 km route, time it, and use that speed: most recreational riders sit between 20 and 28 km/h, fit club riders between 28 and 35, and loaded touring riders between 15 and 22.
| Route | Distance / climbing | Flat pace | Estimated time |
|---|---|---|---|
| Flat commute | 15 km / 50 m | 20 km/h | 47 min |
| Rolling club ride | 40 km / 500 m | 25 km/h | 1h 56m |
| Hilly sportive | 60 km / 1,000 m | 28 km/h | 2h 49m |
| Mountain day | 80 km / 1,800 m | 30 km/h | 3h 52m |
| Loaded tour day | 70 km / 600 m | 18 km/h | 4h 17m |
What counts as your flat pace
Flat pace is personal, and it changes with fitness, bike, load, and road surface. A road bike on smooth tarmac is several km/h faster than a hybrid on a gravel path at the same effort. Panniers, a child seat, or a loaded bikepacking setup can cost 3 to 5 km/h. A headwind costs more than most riders expect: a 15 km/h headwind can cut your ground speed by 4 to 6 km/h at the same effort, while the tailwind on the way home rarely gives it all back, because you rarely ride the same road in reverse at the same effort. The honest way to set your pace is to look at your last few rides on a cycling app and take the moving speed on flat sections, not the overall average, which includes stops, junctions, and hills. Then be conservative for a new route: using a pace 2 km/h slower than your best protects your schedule far more than it costs you in optimism.
Climbing: why four minutes per 100 metres
Climbing costs time because gravity is indifferent to your fitness. The four-minutes-per-100-metres rule is a practical average for recreational riders: it blends the slow grinding of steep pitches with the faster rolling of gentle gradients. Strong climbers beat it, loaded tourers miss it, and very steep climbs cost more than gentle ones of the same height, because there is a minimum speed below which balance and traction suffer and walking becomes faster. If your route has one brutal 20-percent wall, budget extra time for it specifically, and remember that descending does not refund climbing time: you descend faster than you climb, but technical descents, junctions, and caution keep your average well below your flat pace. As a planning rule, a route's climbing time is roughly proportional to total ascent, not to gradient, which is why the calculator uses total gain rather than steepness.
The hidden minutes: stops, wind, and surfaces
- Traffic and junctions: urban routes lose 1 to 3 minutes per ten junctions. A city commute is rarely a pure speed calculation.
- Cafe and photo stops: budget them explicitly. A 20-minute cafe stop is not a rounding error on a two-hour ride.
- Wind: add 10 percent to your estimate on a windy day, 20 percent if the return leg is into a headwind.
- Surfaces: gravel, wet roads, and rough paths cost 2 to 4 km/h versus smooth tarmac at the same effort.
- Group riding: a group is only as fast as its slowest rider on climbs, and regrouping stops add up; add 15 minutes per hour for a social group.
- Mechanicals and navigation: a first ride on an unfamiliar route always costs time for map checks and wrong turns.
Planning the day around the ride
A ride-time estimate is only useful if it feeds the rest of the day: daylight, food, water, and transport. Work backwards from sunset or from a train home, and add a buffer of at least 20 percent for any ride over two hours. Eat before you are hungry and drink before you are thirsty; on rides over 90 minutes, carry food even if you feel fine at the start, because the bonk arrives suddenly and costs far more time than a snack stop. For commuting, run the calculation once with your honest pace and once with your tired, end-of-day pace, and use the slower figure for promises to other people. For sportives and charity rides, remember that event routes quote distance, not time: run the route profile through this calculator and you will know whether the advertised feed stations and cut-off times are comfortable or tight for you.
Getting faster versus going farther
Riders who want to go farther usually need to get a little faster first, because time, not distance, is the real budget. Adding 2 km/h to your flat pace saves about 9 minutes on a 40 km ride, while adding fitness for climbing saves a similar amount on hilly routes. The most efficient training for most recreational riders is not intervals but consistency: three rides a week, one of them longer, builds the aerobic base that raises flat pace and climbing speed together. Strength work for the core and glutes helps climbing more than leg presses do, because climbing is as much about holding position under load as raw power. And the cheapest speed of all is free: a well-inflated tyre, a clean chain, and a bike that fits properly can be worth 1 to 2 km/h with no extra fitness at all.
Electric bikes and mixed groups
E-bikes change the calculation in a specific way: they flatten small hills and raise flat pace, but their assistance typically fades above 25 km/h, so fast group rides gain less than slow ones. For an e-bike commute, use your assisted flat pace (often 23 to 25 km/h) and halve the climbing penalty, because the motor does much of the gravity work. For mixed groups of e-bikes and conventional bikes, plan to the slowest rider's numbers and agree regroup points at the top of major climbs; nothing sours a group ride faster than half the group vanishing over the horizon. The calculator still works for e-bikes if you enter honest assisted numbers: garbage in, garbage out applies to motors as well as muscles.
Using the calculator for a real route
Take the route's distance and total ascent from your mapping app (note that different apps disagree on ascent by up to 20 percent, because they sample elevation differently; use the higher figure for planning). Enter your honest flat pace, read the estimate, then add your buffers: stops, wind, group size, and unfamiliarity. Write the resulting arrival time down and tell people that time, not the optimistic one. If the ride must fit a hard deadline โ a train, sunset, a school pickup โ and the buffered estimate does not fit, shorten the route or start earlier rather than planning to ride faster than you have ever ridden. The road does not negotiate, and a plan built on your real numbers is the difference between a ride you enjoy and a ride you survive.
Distance tells you how far. Elevation tells you how hard. Pace tells you how fast. Put all three together and you get the only number that matters for planning: when you will actually get there.