Skip to content

Time and ride logs

What's the difference between moving time and total time?

The short answer

Moving time counts only the minutes you were actually rolling. Stopped time is every pause while the clock was running. Total time, often called elapsed time, runs from start to finish, so it's the other two added together. Apps disagree because each one decides differently when slow riding counts as stopped, how it handles pauses and how it cleans up GPS noise. Use moving time to compare riding, and total time to plan your day.

Updated November 14, 2026

Rider in a helmet sitting on his parked motorcycle, looking across a lake towards the hills
Photo: Cameron Kirby ckirby · CC0 · Wikimedia Commons · edited (cropped, logo added; previews with headline)

Three clocks for one ride

A ride summary usually shows more than one time, and they measure different things. Here's what each one means.

TermAlso calledWhat it measuresUse it for
Moving timeriding timetime spent in motioncomparing riding between rides
Stopped timepause timestanding still while the clock runsseeing how long your breaks really are
Total timeelapsed timestart to finish, everything includedplanning your day and daylight
Estimated riding timeplanner timea forecast of moving time, no breaksthe starting point of a plan

Total time is simply moving time plus stopped time. Strava describes elapsed time as the span from hitting start to finishing the activity, stops included. The fourth row is the one that causes the most confusion: the time a route planner shows before you leave is a prediction of moving time only. Comparing it with the total time of a finished ride will always make the plan look badly wrong. Turning that forecast into a realistic total is what estimating how long a ride will take is about.

Why two apps rarely show the same numbers

Record the same ride with two apps, or with an app and a GPS unit, and the times will differ. Usually that's not an error. Each device makes its own decisions:

  • When "slow" becomes "stopped": Apps separate moving from resting with a speed threshold, and each picks its own. Crawling in traffic may count as moving in one app and as stopped in another.
  • Auto-pause versus manual pause: Some recordings pause automatically, some only when you tap pause. Strava, for example, respects pauses stored in the file and otherwise calculates moving time from the GPS data. Pause by hand and forget to resume, and part of the ride disappears.
  • GPS noise at a standstill: At a café table your position drifts by a few feet, which can look like very slow movement. Tunnels and deep valleys cut the signal and create gaps.
  • Device switched off at stops: Garmin's zūmo manual advises leaving the unit on during frequent stops so it can measure elapsed time accurately. Turn it off for lunch and the lunch break may simply vanish from the total.
  • Different distances: Apps smooth the recorded points differently, so mileage varies a little, and so does every average built on it.

The practical rule: compare rides only within the same app with the same settings.

Which number to use for what

  • Planning tomorrow's ride: your typical moving time on similar roads, plus your typical stopped time.
  • Getting home before dark: total time, always.
  • Comparing two routes: moving time, recorded the same way both times.
  • Judging fatigue: total time in the saddle and between breaks tells you more than any average.
  • Logging a ride by hand: departure and return times give total time without any app at all.

Averages are a by-product of these numbers, not a goal. They mostly reflect the roads you chose and how often you stopped.

Your stop share: the number planners don't show

Most riders underestimate how much of a day goes to stops. You can measure it from a few of your own rides: divide total time by moving time. Suppose, purely as an example, that your rides keep landing around one and a half. Then a ride with three hours of riding fills about four and a half hours of your day. That ratio is personal. It depends on how you like to ride, on group or solo, and on season. Once you know it, plans stop surprising you. How to make breaks worth the time is the subject of coffee and scenic stops on a motorcycle ride.

Logging time consistently

Whatever you use, pick one method and stick to it. In a hand-written or digital ride log, the most reliable entries are departure time, return time and a riding time from your trip computer or app, if you have one. The motorcycle ride log guide covers which other fields are worth keeping, and recording motorcycle rides compares logs with GPS tracking.

RoadDex today: In RoadDex you enter either a duration or start and end times by hand, next to date, bike and distance. RoadDex has no timer and records no GPS, so it doesn't split moving and stopped time for you. For routes in Germany, the Salomoto route planner's riding time, shown without breaks, is the estimate to compare it with.

Common questions

Why is my moving time longer than the planner's estimated riding time?

Usually for three reasons. You ride at your own pace, not the planner's assumptions. Slow stretches in towns, traffic and road work count as moving as long as you're crawling forward. And detours or wrong turns add miles the plan never had. Compare a few rides and you'll see whether the gap is steady; if it is, that's your personal factor for future plans.

Should I pause the recording at every stop?

Usually not. Most apps either pause automatically or work out stopped time from the GPS data afterward. Pausing by hand only helps if you do it every time; forget once and that stop gets counted as part of your ride, or you forget to resume and lose a stretch of road. Starting at home and stopping when you're back is the simplest habit.

Why did my app count a traffic jam as moving time?

Because you were moving, just slowly. Apps decide what counts as stopped with a speed threshold, and creeping along in stop-and-go traffic often stays above it. A long red light may count as stopped, while the crawl to reach it counts as moving. That's not a bug; it's simply why moving time on a busy day says little about how the roads felt.

Is a high average speed a sign of a good ride?

No. Average speed depends mostly on the roads you picked and how often you stopped, and chasing it pushes you toward riding faster than conditions allow. A slow average on a twisty, scenic loop can be the best ride of the year. Use averages only to plan the next ride more honestly, never as a score.

Sources

  1. Moving Time, Speed and Pace Calculations · Strava Support
  2. Viewing the Trip Information Page (zūmo 595) · Garmin

Sources accessed November 14, 2026. Traffic laws, road closures and app features change; check current conditions with the responsible agency or the app's provider before you ride.

Planning a trip to Germany?

Lay out the route in Salomoto's route planner, check distance and riding time, and take it along as a GPX file.

Learn about the route planner

Free, no account needed. The planner currently covers routes within Germany only. A free account lets you save and share routes and log rides in RoadDex.