Singletrack's forums are sponsored by...

Forum sponsored by Saracen

Strava Elapsed/Movi...
 

[Closed] Strava Elapsed/Moving Times don't Match Garmin Connect Mystery.

1 Posts
2 Users
0 Reactions
26 Views
Offline  outofbreath
Free Member
Topic starter
 
Share this post

Run recorded on Garmin 35, and synced to Strava from Garmin Connect. I ran non-stop with no pauses of any kind. I started the watch the moment I started to run and I stopped the watch the moment I stopped. (But I may have 'saved' a few seconds after stopping IYSWIM.)

Garmin Connect:
Elapsed time: 34:27
Moving time: 34:27

Strava:
Elapsed time: 35.32
Moving time: 33.37

Pace data is not identical between the two.

Strava appears to have added time to the Elapsed time, and generally makes no sense. How can my Elapsed time possibly be longer than the Garmin thinks the watch itself was timing?

On the face of it either Strava is completely mangling the timing or Connect is feeding Strava duff data for competitive advantage...

 
Posted : 29/04/2020 10:14 am
Offline  scotroutes
Full Member
 
Share this post

Download the GPX file from each and open them in a text editor. You'll be able to see all the timestamps. Might give you clue.

 
Posted : 29/04/2020 10:19 am

Secret Diary Of Benjamin Haworth Age 47 3/4

Last Minute Tuscany

Digital Detox

singletrack issue 159 cover image

Issue 159