Strava shows incorrect moving time

[Mayday_qq]

My Garmin device shows different elapsed time and moving time for my indoor activities, but Strava shows the same elapsed time and moving time. That's annoying. I'd like to have the actual moving time shown on strava. 

[Jan_Mantau]

There are clearly bugs involved in Stravas own calculation of the moving time. When the complete ride shows the same elapsed time as moving time but in specific segments Strava shows the moving time as lower than the elapsed time, Strava has contradicted itself successfully.

[Bikej]

Same problem. Since some time Strava does not respect moving time from Garmin and adds plenty of seconds which is bad for average speed for cycling activities. Every ride (since few weeks) Strava moving time is much longer than Garmin says.  It's a bug for me.

[Vaviatrix]

Totally agree, this feels like misrepresentation! I’ve only just noticed this and wonder how long it has been going on for?

[Rogier]

Makes sense that Strava recalculates moving time from the raw GPS data. If it wouldn't, you could never compare moving times calculated by different devices that all use different proprietory algorithms and speed cutoffs.

[Scout · Accepted solution]

Hey @Mayday_qq, 
Thanks for your post. We are two separate platforms with different calculations so certain aspects of your activity analysis may be different. In general, this is because Strava is more strict about resting time so we remove less of it than Garmin Connect. In other words, we're a bit more likely to consider you moving in places where Garmin considers you stopped. This means that even though the elapsed time is the same, the moving time can be a bit different, which can cause differences in average speed. Strava typically reports a bit more moving time and so a bit slower average speed.
 
We feel confident that we are accurately representing your data, but are always working on improving our calculations and appreciate your feedback. You may want to search our support site for more information and discussions on this topic.

[stravauser1]

This is not an acceptable response - Strava clearly has a bug that you are not addressing. I know the elapsed time of my workout - it is the time I was doing the workout and not paused. This shows up correctly in Garmin Connect. When the workout is uploaded to Strava, however, Strava ignores this good data and comes up with a workout duration that is SEVERAL MINUTES shorter than the actual workout, making all of my pace times way faster than they actually are. This isn't a small margin either - Strava consistently reports a duration that is a full 10-20% shorter than my actual workout. This happens for pool swims, open water swims, runs, bikes, etc. It makes the Strava app basically useless. Some of the paid features look interesting, but there's no way I'm paying for an app that is so buggy and doesn't even provide accurate data. Please recognize this as the bug it is, and at least give users an option to use correct data from the devices that are calculating properly.

[Bikej]

 There is no solution in this post. Strava modifies data received from users devices. Solutions is not doing this or at least give an option to choose if user wants Strava correct these data is not.

[Mazz]

If Strava is going to add more moving time, it should also add the untracked distance.  Plenty of times I’m late to restart my watch, so I totally understand having a higher moving time than what was recorded since my watch was stopped, but I also covered distance during that period.  Essentially, you added time but not the distance.  Please look into fixing this, or don’t alter the data at all.

[Bikej]

Totally agree!