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. 

[Whitey10]

I’ve had the same problem for the last month now. Why not just import the data as it is from the device. Makes no sense to change it, Strava always calculates it backwards,

[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.

[ABCycler]

This is problematic for cyclers who are entering and exiting multiple intersections during their rides.  The Garmin device pauses so as not to include the time waiting around for cars to pass.  Garmin correctly subtracts that time but Strava includes a lot more of it, arguing that we are still moving at that time.  

[samadacus]

This is all well and good except you are miscalculating our performance. Yesterday I was on a ride with a friend which I led. We stopped at the exact same times for the same amount of time. We both finished with near identical stats on our devices. Yet his mph on Strava using wahoo was higher than mine using Garmin. We both use speed sensors. I would revisit your programming. The discrepancies are why I no longer subscribe to Strava. 

[EmS]

I've noticed this as well. For example I did a ride. Garmin Edge 130 Plus shows a distance of 13.98 km travelled, a total time of 34:42 with an average speed of 24.2km/hr. 

The data uploads to Strava and somehow converts to 13.97km travelled, moving time of 35:04(not to elapsed time) and an average speed of 23.9km/hr. 

Why not just take the data exactly as it uploads from Garmin(or Wahoo, Coospo, whatever)? I'm not recording directly to Strava so why should my data be different?