This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Dont understand difference between Time/Moving Time/Elapsed Time

Former Member over 13 years ago

I have my 800 setup so that it automatically pauses as speeds of less than 3mph, and I dont understand why there are such large differences between the times on this activity:

http://connect.garmin.com/activity/142721040

Time is 47.36
Moving Time is 47.03
Elapsed Time is 50.47

I expected Time and Moving Time to be pretty much the same, as they dont include pauses, whereas Elapsed Time does. I didnt press the Stop button till the activity was finished.

Can anyone explain?

Top Replies

Nighthawk700 over 8 years ago +1

So they sent me two parts to the answer. The first is just the cookie cutter definition, and the second basically says "yeah, it's going to be wrong." I had suggested that if the moving time was within…

All Replies

0 Inksove over 8 years ago

Hi, does someone has these problems and how to solve them - with shown identical time/moving time/elapsed time on GC and GCM activity - all the three times are shown identical in the activity, though in the ride they are tracked differently and as it should be and I can see this in the data fields while riding. This happens to me with uploaded rides, tracked with Fenix 3 HR and Edge 820.
Here you can see it in the last several rides:
https://connect.garmin.com/modern/profile/Inksove
When the are uploaded to Strava, there the elapsed time is shown as real data.
Is this a bug to my profiles or what...? I had till now edge 810 and no such problems with it.

0 Former Member over 8 years ago

Moving time and elapsed time have reset

My 520 was happily showing a lower moving time than total elapsed time until I applied the latest update on Sunday (23/10/16). Now moving time has reset and all three times are now identical - this has reset the average speed for all rides stored on my device. Anyone know how to roll back the last update?

0 mattdwyerva over 8 years ago

Another anecdote:

Using my Edge 705 the other day and had it set to the screen that shows a huge compass with arrow. As I plodded along, I noticed that sometimes the arrow pointed momentarily backwards, as if I had suddenly reversed course. I had not, so I laughed and changed screens. I assume that was gps error, and I wonder if that if the data shows that same error but I have not combed thru it carefully. Anyway, this might appear as if I had stopped when I had not. Web site cheerfully changed my 52 minute time elapsed to a 44 minute moving time. I wish the 44 min time was accurate, but definitely wrong.

I was riding at a steady pace (never doing intervals).

FYIO

0 DaveBrillhart over 3 years ago in reply to Former Member

Thanks! The only correction is that Elasped Time is calculated by the Device. No backend analysis. It is the Device's Finish Time minus the Device's Start Time. Garmin doesn't do any undocumented time manipulation for Elapsed Time, as it does for "Moving Time". For Moving Time, for example, we don't know the trigger point it uses to effectively create a virtual "auto-pause" (seems to be less than 3mph, but it is probably more than 0mph).