Bike Pace Calculator

Cyclists talk speed; runners talk pace; triathletes must translate mid-race; and anyone planning a ride needs both, plus the finish time hiding inside them, waiting to be planned around properly beforehand. This calculator moves freely among the three, in both unit systems, without a scratchpad: enter any distance and time — or a target speed — and it returns your speed in km/h and mph, your pace per kilometre and per mile, and predicted times for the standard ride distances at that pace, so the sportive plan stops being a guess.

Speed and Pace Are the Same Fact Twice

Speed divides distance by time; pace divides time by distance — reciprocals, each answering the question its community asks. Runners ask "how long is each kilometre costing me?" because their races split by the kilometre; cyclists, going fast enough that per-km splits blur, ask "how fast am I travelling?" and read a speedometer. The calculator prints both because events mix the dialects: a triathlete leaves the bike leg holding cycling speed and must instantly think in run pace; a sportive rider pacing by heart rate still needs per-kilometre times to judge feed-stop arithmetic. The conversion anchor worth memorising: 30 km/h is exactly 2:00 per kilometre — the defaults of this page — and the scale around it (25 km/h = 2:24/km, 32 = 1:52.5, 40 = 1:30) folds out of the same division. Any pair on that ladder, multiplied back, must return the whole ride; that is the calculator's only secret, and it is now yours.

Worked Example: 40 Kilometres in 80 Minutes

The defaults are the club-run benchmark: 40 km in 1 hour 20 — 30.0 km/h, 18.6 mph, 2:00 per km, 3:13 per mile. The predictions fan out along the pace: 20 km in 40:00, 50 km in 1:40:00, 100 km in 3:20:00, the hundred-miler in 5:21:52. Read them with the note's skepticism scheduled by distance: the 20 km projection is nearly a promise (the pace was set over twice that), the 100 km is a plan, and the 100-miler is a hope that nutrition, wind and hills will be paid from a budget the linear model doesn't carry. Honest pacing plans degrade the projection with distance — a common sportive rule sustains target speed to 100 km, then allows 5–8% decay — and this calculator supplies the optimistic baseline those adjustments start from, which is all a baseline owes you.

Using Pace Targets in Training and Events

Three jobs pace arithmetic does weekly. Interval prescription: speed targets translate workouts across bikes and days — "5 × 5 minutes at 34 km/h" is a load this page can reverse into per-km splits for the head unit's lap screen. Event cut-offs: sportives and brevets run on minimum average speeds (a 200 km brevet at the classic 15 km/h minimum average allows 13.5 hours including stops — stops being the trap, since the clock that matters includes them: your moving pace must exceed the minimum by the margin your stops consume, a margin this calculator exposes the moment you enter the total elapsed time instead of the moving time). Group-ride honesty: the advertised "28 km/h social" is a moving average; door-to-door with café stops it lives near 22 — entering your own last ride settles which dialect your club speaks.

What a Speed Number Leaves Out

Average speed is the most flattering statistic in cycling because it hides its own distribution: a ride of climbs at 12 km/h and descents at 60 averages far below the same ride flattened, since the slow segments own most of the clock — time is spent at the speeds, not distance. Two riders with identical 30 km/h averages may have ridden entirely different days. This is why serious analysis graduates to power (the sibling calculator on this hub prices the same ride in watts, indifferent to what the wind did to the speedometer) and why this page's humility note matters: pace is a planning language, not a fitness verdict. Use it to schedule, split and predict; let watts and heart rate argue about what the ride cost.

The Cost of Fading, in Minutes

Linear projections assume a metronome; legs are not metronomes, and the arithmetic of fading is worth seeing once in full. Take the 100 km projection at the defaults' pace: even-paced, it is 3:20:00. Now fade just 10% in the second half — 50 km at 30 km/h (1:40:00), then 50 km at 27 km/h (1:51:07) — and the finish becomes 3:31:07: an 11-minute penalty bought by a slowdown most riders would describe as "easing off slightly". The asymmetry is the lesson pacing strategy is built on: time lost at low speed cannot be repurchased at high speed, because the slow kilometres occupy more clock. Negative splitting (second half faster) is the same mathematics with the sign flipped and the difficulty inverted — cheap on paper, expensive in glycogen — which is why even pacing, the calculator's naive assumption, remains the professional default that real plans adjust by percentages, not hopes.

The Century's Splits, Committed to Memory

Even-paced riding has one more gift: splits simple enough to hold in your head at kilometre 80. At the example's 30 km/h, the hundred divides into five identical 20 km blocks of 40 minutes — through 20 km at 0:40, 40 at 1:20, 60 at 2:00, 80 at 2:40, done at 3:20 — a metronome a tired brain can still audit against the road signs. Choose any target pace and the same service is available: divide the distance into equal blocks, price each block once with this calculator, and ride the blocks instead of the whole. The professionals' pacing screens are fancier; the arithmetic is this arithmetic, and the discipline it supports — knowing, at every point, whether you are ahead of the ride or behind it — is most of what pacing means.

Miles In, Kilometres Out — Without Tears

The form speaks kilometres; if your riding speaks miles, one multiplication converts the whole conversation: miles × 1.609 = kilometres (a marathon's 26.2 miles is 42.2 km; a century's 100 miles is 160.9, the figure the prediction ladder already carries). Enter the converted distance and read speeds in both units from the answer line — the mph figure is printed precisely so the return journey needs no second conversion. Unit discipline is the whole trick: convert once, at the door, and let every number inside the calculation share the system.

Related Tools

More from the Sports Calculators hub: the Cycling Wattage Calculator — the physical price of this pace — and the Calories Burned Biking Calculator for what the ride spends. Cyclists converting to the run can also use this hub's pacing family built for foot speeds.

Frequently Asked Questions

What is a good average cycling speed?

Context is everything, but the population anchors: untrained riders on flat ground typically average 20–24 km/h; regular club riders 26–30; strong amateurs 30–34; professionals in races 40+. The worked example's 30 km/h sits exactly at the club-rider threshold — a speed that says fitness and practice without saying obsession. Judge your own trend, not the peloton's: the calculator's finish-time ladder is a personal progress chart when fed last month's ride and this month's.

How do I convert mph to min per mile?

Pace is 60 divided by speed: at 20 mph, 60/20 = 3:00 per mile; at 15 mph, 4:00. The km version divides 60 by km/h for minutes per kilometre. The calculator prints both paces alongside both speeds, and the inversion is why pace numbers fall as you get faster while speed numbers rise — the same improvement wearing opposite signs, a small daily confusion this page exists to end.

Does drafting change the pace maths?

Not the arithmetic — the group's speed is the group's speed — but it changes the effort behind the number entirely: riding in a peloton's slipstream can cut the power cost of the same pace by a third or more. Two identical pace printouts may therefore describe different workouts, which is the effort-blindness the section above warns about and the wattage calculator next door quantifies.

How do I find my time for a distance I haven't ridden?

Enter a recent ride's distance and time honestly (elapsed-versus-moving chosen deliberately), read the predicted time for your target distance, then apply judgment: subtract ambitions for distances far beyond the reference ride, add credit for a flatter or sheltered course. The linear projection is the correct starting point; experience is the correction factor, and it improves exactly as fast as your log of predictions-versus-results does.

Why does my bike computer's average differ from this?

Three usual causes: the computer auto-pauses (excluding stops your elapsed entry includes), its distance comes from a wheel sensor calibrated to a slightly wrong circumference, or GPS sampling rounds corners off on twisty routes. Feed the calculator the computer's own moving time and distance and they must agree to the metre — the disagreement is always in the inputs' definitions, never in the division, which is the useful diagnostic this page quietly provides.

Can I use this for running or swimming?

The arithmetic is identical (distance over time is sport-blind), and the finish-time ladder labels cycling's standard distances — but running pace conventions (min/mile over 5K–marathon) have their own dedicated calculators in this hub's family, tuned to running's distances. Use this page freely for any steady locomotion when the distance is yours to choose; it will not know you weren't on a bike.