• Route planner
  • My activities
  • Blog
  • FAQ
Instagram Buy me a coffee
Connect with Strava
All posts

Plan your ride by time, not distance

12 November 2026

Also available in: Deutsch · Français · Nederlands

Most of us don't plan rides in kilometres. We plan them in time. "I have two hours before dinner." "I need to be back by noon." "The kids are at practice for three hours."

Then we open a route planner, and it asks for a distance. So you guess: two hours is maybe 50 km? Then the route has more climbing than you expected, and you're late. Or you guess low, and you're home after 80 minutes wondering why you didn't ride longer.

That's why RouteCycle can build a route from a ride time instead of a distance.

How it works

Instead of a distance, you pick Time and set how long you want to ride, for example 1.5 hours or 3 hours. RouteCycle then builds a route that should take about that long for you, including the climbing.

The important part is "for you". A 2-hour ride is 45 km for one rider and 70 km for another, and a flat 60 km is not the same ride as a hilly 60 km. So the estimate needs two things: your pace, and the profile of the route.

Where your pace comes from

There are two ways:

  • With Strava connected, RouteCycle looks at your own past rides to estimate how fast you actually ride, not a generic average. Riders who average 22 km/h and riders who average 30 km/h get very different routes for the same 2 hours.
  • Without Strava, you pick a fitness level yourself, and the planner uses a sensible default speed for it.

Climbing is taken into account as well. An hour with 600 m of ascent covers less ground than an hour on the flat, so a hilly route for the same time comes out shorter.

Capping the climbing

Time alone wasn't enough. Ask for 3 hours, and the planner could happily drag you over every hill in the area. Sometimes you have the time but not the legs, or you're on a heavy bike, or you just want an easy recovery ride.

So time mode has an elevation slider. You can ask for "3 hours, but keep it under about 400 m of climbing", and the planner looks for a route that fits both the time and the ascent you're up for.

Time for one-way routes too

Time works for A-to-B routes as well. Normally a one-way route between two places is the most direct pleasant route. With a ride time set, you can say "I have 3 hours to get from A to B", and RouteCycle builds a longer, more scenic route between them that fills that time instead of the shortest one.

This is great for rides like "train out, ride home" or meeting friends in the next town without arriving an hour early.

Every route shows a ride time

Even when you plan by distance, every route now shows an estimated ride time next to the distance. So "60 km" also tells you "about 3 hours". If you're logged in with Strava it uses your own pace, otherwise a default.

How accurate is it?

For most riders on most routes, it lands close. The estimate is based on your average pace, though, so it's not a promise. Wind, stops, traffic lights in town, a long café stop: none of that is known in advance. My advice is to treat the number as "riding time" and add your own buffer for coffee.

If the estimates feel consistently off for you, I'd really like to hear about it. That's exactly the kind of feedback that helps me tune them.

Try it on the route planner: choose Time instead of distance, set your hours, and ride.

Read next

  • How hard is this ride? Reading the climb chart
  • Why generating a loop is much harder than routing from A to B
  • From route planner to Garmin in one click

Want a quiet ride from your door? Pick a start and a distance, and RouteCycle builds the loop.

Open the route planner
FAQBlogRoutesTerms & ConditionsPrivacy Policy