Skip to main content

Anyone else noticed this recent change on the webpage?

I have just noticed that under 'Profile' and ‘My Stats’ activities are now being displayed  showing the activity total time rather than the moving time of the activity.

I'm sure most people would much rather see their efforts recorded showing moving or effort time, rather than a total time that may include all manner of stops!

Any advice on how to change back would be very welcome.

Strava ‘support’ were no help BTW.

Hi ​@GaryL,

do you mean elapsed vs. moving time? For me it has been distinguished as long as I remember - races and best efforts would use the elapsed time, training runs would mainly use moving time (but elapsed time is still available in the activity details).

Here's how it works:

https://support.strava.com/hc/en-us/articles/115001188684-Moving-Time-Speed-and-Pace-Calculations
 

If you see something different, it would help if you include e.g. some links to sample activities.

 


@GaryL  I can’t confirm that for riding, it’s exactly the sum of all moving times showing there for me.


Hi ​@GaryL,

do you mean elapsed vs. moving time? For me it has been distinguished as long as I remember - races and best efforts would use the elapsed time, training runs would mainly use moving time (but elapsed time is still available in the activity details).

Here's how it works:

https://support.strava.com/hc/en-us/articles/115001188684-Moving-Time-Speed-and-Pace-Calculations
 

If you see something different, it would help if you include e.g. some links to sample activities.

 

@Jan_Mantau 

Hi, thanks for the response. 

Yes,  elapsed vs. moving time.

I’ve added an attachment to demonstrate. 

Up until my last ride (yesterday) these numbers showed the moving time and not the elapsed time. 

For example my last 100 mile ride was appox’ 7hr 20mins and now it’s displayed as the elapsed time, attached. 

The individual efforts remain accurate. Only under ‘Profile’ > ‘My Stats’ > ‘Best Efforts’ shows this change. 

As a result all ‘best efforts’ are now displayed as elapsed time and not moving time. 

Hope this makes sense! 


Well yes - best efforts have always been elapsed time. Best effort = PR. I can run short intervals fairly fast (so if I combine many intervals moving time AND exclude all breaks, it would look quite impressive), but obviously won't be able keep that pace for a marathon. If only the “moving time” counted for best efforts, it would be wildly inaccurate and would make me look like a much better runner than I actually am 😃


Exactly, the best efforts always were for the elapsed time.


Well yes - best efforts have always been elapsed time. Best effort = PR. I can run short intervals fairly fast (so if I combine many intervals moving time AND exclude all breaks, it would look quite impressive), but obviously won't be able keep that pace for a marathon. If only the “moving time” counted for best efforts, it would be wildly inaccurate and would make me look like a much better runner than I actually am 😃

@Jana_S Well I must have had a bad mushroom, because I’m sure the time for my longest ride was displayed in moving time and not elapsed time. 

Elapsed time can take into account cafe stops etc. 


“Longest ride” might have yet another special rule… ​@Jan_Mantau is a cyclist so he might confirm 🙂


“Longest ride” might have yet another special rule… ​@Jan_Mantau is a cyclist so he might confirm 🙂

The “Longest ride” means the longest distance, a time is not displayed for it in the profile stats.


“Longest ride” might have yet another special rule… ​@Jan_Mantau is a cyclist so he might confirm 🙂

The “Longest ride” means the longest distance, a time is not displayed for it in the profile stats.

 

Apologies, yes. Longest ride is displayed in distance.

I should have said, best effort 100 miles. Previously this was displayed as moving time and not elapsed time. Although I’m beginning to doubt my sanity as everyone is telling me I’m mistaken! 😵


I don’t rule out that there was the moving time displayed in some cases, but then it would have been a bug that is fixed now.