JoseFitani
📏 Distance Tools

Cycling Distance Calculator

Estimate cycling distance and time. Assumes an average speed of 18 km/h for a recreational cyclist.

This page explains how the cycling distance calculator works, the data and formulas behind it, and how to interpret the result. Great-circle distances are the shortest path over the Earth's surface - the route aeroplanes actually follow. They are the baseline every other distance estimate starts from, and are accurate to ~0.3% of the more complex ellipsoidal (WGS84) distance. The tool is one of 329 free, open tools on JoseFitani for maps and geography. It runs in your browser with no sign-up needed. Use the search field or click the map to drop a pin - the tool uses the Haversine formula on a sphere of radius 6,371 km, plus mode-specific detour factors for driving, walking and flight-time estimates and returns the result in seconds. Below you'll find a step-by-step guide, real use cases, the methodology, FAQs, and data sources.

Important notice

Distances and durations are estimates based on the route data provided. Actual cycling distances and times may differ — allow extra time and verify your route locally before heading out.

Or click on the map: currently setting Point A
Loading map…

How to use this tool

1
Enter your input

Type your query, paste coordinates, or click on the map. The tool uses the Haversine formula on a sphere of radius 6,371 km, plus mode-specific detour factors for driving, walking and flight-time estimates to process your input locally in the browser.

2
View the result

The result appears instantly with the map showing your location. You can adjust by clicking elsewhere or searching a new place.

3
Copy or share

Click Copy to save to clipboard, or Share to send a direct link with the exact inputs.

What people use this tool for

Sizing up a training ride

Cyclists planning a weekend ride want to translate a target distance into saddle time before committing. Converting kilometres to hours at a realistic pace shows whether the loop fits the morning or swallows the whole day, including time for cafe stops.

Example: A rider in Copenhagen plans a 60 km loop and sees it is about 3 hours 20 minutes at 18 km/h, so they schedule an early start with a mid-ride coffee break.
Reality-checking a bike commute

Prospective bike commuters often overestimate how long the ride will take because they think in car or bus times. A cycling-specific estimate shows the true door-to-door time, which is frequently competitive once waiting and parking are counted.

Example: A worker in Bristol checks the 9 km ride to the office, sees roughly 30 minutes, and realises it beats the bus once waiting time is included.
Splitting a tour into day stages

Bike tourers crossing a region need to divide the total route into daily stages that match their fitness and daylight. Estimating riding time per stage keeps days balanced and ensures each evening ends at a town with accommodation rather than in the middle of nowhere.

Example: A tourer crossing the Loire Valley splits the route so each day holds about 4 to 5 hours of riding, leaving afternoons free for chateaux and long lunches.
Checking e-bike battery range

E-bike riders need to know whether the battery covers the planned round trip with margin to spare. The distance estimate lets them compare against the manufacturer's range figure, derated for hills, headwind, and assist level, before setting off.

Example: A rider in Munich estimates a 40 km round trip to the lake and confirms it sits comfortably inside the battery's real-world range even on a high assist setting.

How it's calculated

Cycling distance uses a 1.35x factor over great-circle distance, reflecting typical bike route detours.

The calculation runs in your browser - no data is sent to our servers. Map tiles come from OpenStreetMap (ODbL license), geocoding uses Nominatim (1 request/second limit), and elevation uses the Open-Elevation API backed by SRTM data. All are free, open services.

All calculations use the WGS84 datum (EPSG:4326), the same as GPS. For other datums (NAD27, NAD83, ETRS89), a separate conversion is needed. The difference is typically under 1 metre - negligible for most uses but important for survey-grade work.

The formulas match those in professional GIS software (QGIS, ArcGIS, Global Mapper), just in a browser-friendly form. For sub-metre accuracy, use professional software with ellipsoidal calculations. Results are shown in multiple units: km and miles for distance, km²/m²/hectares/acres for area, metres and feet for elevation. Conversion factors are exact (1 mile = 1.609344 km), so the only error source is input precision.

Related tools and resources

For more tools in this category, explore the related tools listed below. Each tool includes full documentation, examples and FAQs. Explore related tools in our Distance category for complementary functionality. See the Tools index for all 329 tools, or read our blog for in-depth articles on geography and maps.

Frequently asked questions

What speed is assumed?

18 km/h for a casual cyclist on flat terrain.

Does it include hills?

No - use an elevation profile tool for accurate estimates.

What cycling speed does the calculator assume?

It assumes 18 km/h, a typical recreational pace on flat ground with no strong wind. Fit regular riders hold 25 km/h or more, while loaded tourers, beginners, and headwinds drop well below 18. If you know your own average from a bike computer, scale the time estimate accordingly.

Does it account for hills?

No. Climbing slows a cyclist dramatically while descents only partly make up the time, so hilly routes take considerably longer than the flat-ground estimate. For routes with serious elevation, use a cycling planner that models gradient, or add a large margin based on the total climbing.

How is the cycling distance estimated?

The straight-line distance is multiplied by roughly 1.35 to approximate real roads and cycle paths. Dedicated greenways and riverside trails can wander longer than this, while city grids with cut-throughs can come out shorter. It is a planning figure, not a measured route.

Does it know about bike lanes, trails, or surfaces?

No. The calculator models neither cycling infrastructure nor surface quality: a smooth bike path and a potholed road with heavy traffic get the same estimate. For choosing the actual route, use a cycling-specific map such as Komoot or Strava, which know about lanes, trails, and surfaces.

How do I adjust the estimate for an e-bike?

E-bikes typically cruise around 25 km/h where legally permitted, versus the 18 km/h assumed here. Scale the time estimate down proportionally: multiply the estimated time by 18/25. Also remember that higher assist levels drain the battery faster, so check range as well as time.

Do I need a connection to use the cycling calculator?

Only for place-name search, which queries an online gazetteer to turn typed addresses into coordinates. The cycling math itself runs locally in your browser, so entering coordinates directly needs no connection at all.

Why is my GPS-recorded ride longer than the estimate?

A GPS records every wiggle of the real path, including detours, wrong turns, and weaving through traffic, while the estimate is a smoothed approximation. GPS traces also pick up small positioning errors that inflate the total slightly. The two should agree within about 10 to 15 percent on a clean ride.

Is 18 km/h realistic for a beginner?

For a reasonably fit beginner on flat roads it becomes realistic after a few rides, but very new riders often average 12 to 14 km/h at first. Start with your own comfortable pace and revise the estimate once you have a few rides logged on a bike computer or phone app.

Data sources & methodology