The cycling pace calculator above solves the standard speed, distance and time relationship in the units cyclists actually use. Give it any two of the three and it returns the third, reports average speed simultaneously in kilometres per hour and miles per hour, and breaks the ride into segment splits per 10 km and per 10 miles. It never expresses a result in minutes per kilometre or minutes per mile, because those are running units and this is not a running tool.
That boundary is deliberate and it is worth stating in the first paragraph rather than burying it. Arb Digital publishes separate tools for separate jobs, and pace in the running sense — minutes and seconds to cover a fixed unit of distance — is handled by our running pace calculator, by the training pace calculator for effort-based running paces, and by the pace converter for moving between pace units. This page speaks cycling: km/h and mph, over ride distances, for riders comparing efforts and planning arrival times.
What This Cycling Pace Calculator Does
Cyclists describe effort in speed, not in inverted pace. Nobody says they rode a four-minute kilometre; they say they averaged twenty-four. The unit convention is not an accident either — a cyclist's speed varies enormously with gradient, wind and draft within a single ride, so a headline average speed with segment splits is more informative than a single inverted pace figure that hides all of it.
The calculator therefore does three things. It solves for whichever of speed, time or distance you leave to be computed. It reports the speed in both metric and imperial units at once, so a ride logged in one system can be discussed in the other without a second conversion step. And it gives segment splits — how long 10 km takes at that average, and how long 10 miles takes — which are the practical numbers when you are checking whether you will make a ferry, a café stop, or a group ride start.
Alongside it, our speed, distance and time calculator handles the same relationship in a general form for any moving object, the mph to km/h converter handles unit conversion alone, and the cycling power calculator answers a different question entirely: how many watts a given speed on a given gradient demands.
How to Use It
- Choose what to solve for. Average speed from a completed ride, ride time from a planned route and target speed, or distance from a time and a speed.
- Enter the ride distance and its unit. Kilometres or miles; the calculator converts internally and reports both regardless.
- Enter the time in hours, minutes and seconds. Keep it consistent with the speed you are describing — elapsed time and moving time are different numbers and produce different averages.
- Enter the average speed and its unit if you are solving for time or distance.
- Read the splits. Time per 10 km and per 10 miles give a practical check on arrival time at the same steady average.
The Formula
The arithmetic is the elementary kinematic relationship: speed = distance ÷ time, rearranged to time = distance ÷ speed or distance = speed × time. Everything else is unit handling. The calculator converts every distance to kilometres internally, works in decimal hours, and converts back for display, so mixing a distance in miles with a target speed in km/h is safe.
The conversion factors are exact by definition: one mile is 1.609344 kilometres, one kilometre is 0.621371 miles. The National Institute of Standards and Technology's guidance on unit conversion makes the point that matters most here — do not round at intermediate steps, only at the final result. Rounding a mileage to one decimal before dividing by a time is exactly how a computed speed ends up disagreeing with a head unit by a tenth or two.
Why Cycling Uses Speed and Running Uses Pace
This is not a stylistic quirk, and understanding it explains why the two calculators cannot be merged. A runner's speed sits in a narrow band and is dominated by their own effort, so inverting it into minutes per kilometre gives a number with useful resolution: the difference between 5:00 and 5:10 per kilometre is meaningful and easy to hold in your head mid-race. A cyclist on the same road might do 45 km/h downhill and 9 km/h up the other side. Inverted, that is 1:20 per kilometre against 6:40 per kilometre — a range so wide that the average is close to meaningless as a target.
Speed also maps directly onto the physics that governs cycling. Aerodynamic drag rises with roughly the square of speed, and the power to overcome it with roughly the cube, so a rider thinking in km/h is thinking in the same currency as the resistance they are fighting. A runner has no equivalent relationship at ordinary speeds. That is the real reason the sports settled on different units, and it is why converting a cycling average into min/km produces a technically correct number that no cyclist would ever use.
Moving Time Against Elapsed Time
The most common reason two people compute different averages for the same ride is that one used moving time and the other used elapsed time. Head units usually pause automatically when the wheels stop, so moving average excludes traffic lights, punctures, and the twenty minutes spent at a café. Elapsed average includes all of it. On a quiet 100 km route the two might differ by half a km/h. On an urban ride with thirty junctions, moving average can be several km/h higher, and on a long day with real stops the gap can be enormous.
Neither figure is wrong; they answer different questions. Moving average describes how fast you rode. Elapsed average describes when you got there. If you are planning an arrival time, elapsed is the one that matters, and it is the one that catches people out on long routes where the stops are the difference between arriving in daylight and arriving in the dark.
Why Your Average Speed Is Not a Fitness Score
Average speed compares badly across rides and compares terribly across riders, because it absorbs everything the road and the weather did. Gradient is the obvious one: a route with 1,500 metres of climbing will produce a lower average than a flat route at identical effort, and there is no adjustment that meaningfully fixes that. Wind is the underrated one, because an out-and-back into a headwind does not average out — you spend far longer riding into it than with it, so the slow half dominates the total time.
Group riding changes the picture again. Sitting in a bunch cuts aerodynamic drag substantially, so a rider can hold a much higher average in a group than alone at the same effort. Surface matters too; gravel and wet roads cost speed that never appears in a distance figure. If you want a measure that survives these differences, power is the one that does, which is why our cycling power calculator exists alongside this one and why the cycling power zone calculator works from threshold power rather than from speed.
Planning a Route Rather Than Reviewing One
Solving for time is where this tool earns its keep on the planning side. Enter a route distance and a realistic average, and you get a ride duration you can put against a start time. The word doing the work there is realistic. Most riders overestimate the average they will hold on an unfamiliar route, usually by anchoring on a recent flat ride and forgetting the climbing.
A useful sanity check comes from the published data on ordinary riding rather than racing. A study in PLoS One estimating duration-distance relations in cycle commuting in Greater Stockholm reported cycling velocities of about 20.8 km/h for male and 16.1 km/h for female cycle commuters, and adjusted those downward by roughly a quarter to represent the general population rather than habitual commuters. Those are real-world numbers over real routes with real junctions, and they are a long way below what a rider tends to assume when planning from memory of a good day.
Arb Digital builds fast, dependency-free interactive tools that earn links and rank on their own merits. Browse the free library to see the standard, or tell us what you need built.
Browse All Free Tools Talk to Arb DigitalCommon Mistakes to Avoid
- Comparing a moving average to an elapsed average. They measure different things and the gap grows with every stop on the route.
- Mixing units mid-calculation. A distance in miles with a speed in km/h is fine here because the tool converts, but doing it by hand is the classic source of a nonsense answer.
- Treating average speed as a fitness measure. Gradient, wind, surface and group riding move it far more than form does.
- Planning from a personal best. A route duration built on the fastest average you have ever held will be wrong on every ordinary day.
- Converting cycling speed into running pace units. The number is arithmetically valid and practically useless; use the running tools for running.
Related Free Tools From Arb Digital
For running, use the running pace calculator, the training pace calculator or the pace converter. For cycling, the cycling power calculator covers watts from speed and gradient, the cycling calorie calculator covers energy expenditure, the bike gear ratio calculator covers gearing, and the e-bike range calculator covers assisted riding. The speed, distance and time calculator and the mph to km/h converter handle the general cases, and the free online tools hub lists everything.
Frequently Asked Questions
Divide the ride distance by the ride time. Sixty kilometres in two and a half hours is 60 divided by 2.5, or 24 km/h. The calculator does the unit handling so you can mix a distance in miles with a time in hours and minutes.
No. Running pace is expressed as minutes and seconds per kilometre or per mile; cycling is expressed as speed in km/h or mph. This tool never outputs a running pace. For minutes per kilometre, use the running pace calculator, the training pace calculator, or the pace converter.
A cyclist's speed varies far more within a ride than a runner's does, so an inverted pace figure has little practical resolution. Speed also maps directly onto aerodynamic drag, which rises with roughly the square of speed and dominates cycling at anything above a gentle pace.
Moving time excludes stops and describes how fast you rode. Elapsed time includes everything and describes when you arrived. Use elapsed time when you are planning an arrival, and be sure you know which one a reported average was based on before comparing it to anything.
It depends entirely on terrain, wind, surface and whether you were riding in a group. As a real-world reference point, a PLoS One study of cycle commuting in Greater Stockholm reported about 20.8 km/h for men and 16.1 km/h for women, adjusted downward by roughly a quarter for the general population.
Because you spend far more time on the climbs than on the descents, so the slow sections dominate the total. This is the same reason an out-and-back ride into a headwind averages slower than a still day, even though half the distance is with the wind.
They convert an average speed into how long a fixed 10 km or 10 mile block takes at that speed, which is the practical figure when you are checking whether you will reach a point on the route by a particular time.
Figures produced by this tool are planning estimates only. Actual ride times depend on gradient, wind, surface, traffic, stops and group dynamics, none of which a distance and a target speed can capture.
