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. 

[DanielRios549]

It still not working correctly. I use my Galaxy Watch5 to record my rides that are not training, on Samsung Health it shows the duration was 23 minutes, the average speed was 17.6km/h and the maximum was 33.3km/h, but when uploaded to Strava, it shows the duration was 13 minutes, the average speed was 30km/h and a maximum of 70km/h, this is absolute nonsense. What I noticed, is that the GPS of this wearable is not too good, so it could lose connection during the activity, it looks like Strava doesn't count the time I'm riding while the GPS connection gets lost, but it counts the distance.

[MatB]

Had a short ride yesterday with multiple stops at intersections. Finished at an avg of 27.6km/h with a moving time of 31:05 and a distance of 14:32km, with a Polar Vantage M. Surprisingly, Strava gave me the same distance but added 1:01 to my moving time, which is pretty longer than what I actually rode on a so short distance.

Strava usually gives me the right moving time, sometimes adding or withdrawing seconds, causing no noticeable impact on my speed average. However, this one was hard to miss! Been a user for years, this is the first time I see such a discrepancy.

As for I, I won’t complain that much since I do not have a paid subscription. Though, that recalculation of moving time thing is odd in my opinion.

To Strava: maybe it would be great to listen to users who claim that something’s wrong instead of simply arguing that you are confident in your own product? 😉

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

[JodiO2L]

I will also have to agree with all others here. Two weeks ago, my run included periods of rest. None were counted when my garmin activity synced to Strava. Today, Strava counted them all. Garmin shows this accurately on both runs but Strava does not. I pay for a subscription and I am happy to share any details about both these activities to assist in troubleshooting as there is clearly a bug in the sync.