Elapsed time: STOP versus SAVE

~o√ 1 month ago

Hello,

I would like to share my experience regarding the "issue" related to the elapsed time showed in Garmin Connect (Web or Mobile).
My asumption is that the elapsed time cover the time between the press of the "Start" button and the press of the "Save" button.
That does not sound relevant to me.
The elapsed time should consider the period between "Start" and (last) "Stop" before "Save".

That is my 2-cent contribution

Top Replies

~o√ 1 month ago in reply to e7andy +1

Hello e7andy
No I do not use the elapsed time in Garmin Connect.
Nevertheless, Strava uses this data to compute an average pace; in this case it is not reliable/irrelevant.
Regarding the delay between Stop…
~o√ 1 month ago in reply to trux +1

Hello trux
That is not correct; Strava uses both "Moving time" and "Elapsed time" in the detailed view of the activity.
For Swim and Run activities, under the Pace graph there are the…
~o√ 1 month ago in reply to trux +1

Unfortunately I am not able to upload my screenshots.

But I confirm that in my Strava mobile app (Android) there are both but it looks like the average based on elapsed time is not present in the web app…

All Replies

0 ~o√ 1 month ago in reply to trux

Hello trux

I am sharing the info of a run activity.

* Garmin connect web app

Distance: 8.03 km
Time: 40:42
Moving time: 40:41
Elapsed time: 43:01
Average pace: 5:04
Average moving pace: 5:04

* Garmin connect mobile app

Distance: 8.03 km
Time: 40:42
Moving time: 40:41
Elapsed time: 43:01
Average pace: 5:04
Average moving pace: 5:04

* Strava web app

Distance: 8.03 km
Time: n/a
Moving time: 40:42
Elapsed time: 43:01
Average pace: n/a
Average moving pace: 5:04

* Strava mobile app

Distance: 8.03 km
Time: n/a
Moving time: 40:42
Elapsed time: 43:01
Average pace: n/a
Average moving pace: 5:04
Average elapsed pace: 5:22

I guess there is no point to go further with this thread.
But I still think that the elapsed time must not include the delay between the last STOP and SAVE.