Cycling time estimates

Estimate your cycling ride time.

Planning a weekend ride, gran fondo or long-distance route? Start with your route and power reference points. Compare moving time, average speed and arrival time for the effort and stops you choose.

  • 01
    Start with a real routeImport a GPX, TCX or FIT file, or draw your route on the map.
  • 02
    Describe your effortEnter your FTP, bike and, if you have one, your personal power curve.
  • 03
    Compare three time estimatesCautious, likely and ambitious scenarios with moving time, average speed and elevation profile.
  • 04
    Plan your stopsAdd stops to the ride plan to update waypoint and arrival times.
Example result for the real Grenoble, Uriage and Vizille GPX loop: scenarios, average speed, map and arrival.
Example on the Grenoble–Uriage–Vizille loop, routed with BRouter on OpenStreetMap. Times depend on your settings. Download the example GPX

For every cycling plan

One time to plan, three ways to ride.

Distance divided by average speed misses climbs and stops. The estimate starts with your route and planned effort, then separates time on the bike from time stopped.

The chamois plans a cycling route on a map before setting off.

Estimate a cycling ride

Your weekend route has its own terrain. Compare a cautious pace with a harder one, then check whether your return time is realistic.

The chamois rides towards a feed stop on a mountain road.

Plan a gran fondo

Estimate key waypoint and arrival times using the elevation profile, your power strategy and planned feed-stop times. Leave a margin for the event day.

The chamois rides at dawn with a light on a long-distance route.

Plan a long-distance ride

On an ultra-cycling route, stops matter as much as pace. Mark your stopping points and treat times as reference points, not guarantees.

Where does the estimate come from?

Your route meets your watts.

Working Out divides the route into segments, then estimates speed on each from the gradient, resistances and target power. You can inspect the assumptions instead of receiving an unexplained number.

01

Route and elevation

The GPX provides distance and elevation. Check the route and profile: incorrect elevation can change the estimate.

02

FTP and the power curve

Your functional threshold power (FTP) guides your strategy. An imported personal power-duration curve bounds planned efforts; otherwise, the simulator identifies its estimated curve.

03

Bike and conditions

Your weight, bike, position, rolling resistance and wind change the calculated speed. These settings remain visible and adjustable.

04

The full-day time

The result separates moving time from chosen stops. The displayed average is for riding; total time determines waypoint and arrival times.

Read the method and its limitations
Result screenshot with three scenarios, moving average, map, elevation profile and times.
Result screenshot using the Grenoble–Uriage–Vizille example GPX.

Read the result, adjust the plan

Three scenarios. An arrival time to put in context.

The cautious, likely and ambitious scenarios change the effort level. Compare moving times, average speeds and margins against your power curve. An overly demanding scenario is flagged: the fastest is not automatically the wisest.

Then add the stops you actually plan. The ride plan recalculates waypoint and arrival times without confusing a stop with slower riding. You can save the plan in your account and take a PDF with the map and profile.

See what the simulator cannot predict

Once your account is created

A few reference points and you can get started.

Add your FTP, weight and bike in your welcome space. Then you can import or draw a track and prepare your ride plan.

Explore training too

Ready for your next route?

Estimate your ride time for free.

Create your account, enter your starting details and import your route. No payment or card required.

Create my free account