Hello @Stuarthitchman1 

Thanks for posting about this.  The Strava Mobile App is not supported for recording swim activities, and may not be able to accurately estimate your moving time, leading to the issue you are reporting.

Sorry about that an apologies for any confusion.  For information on the best way to record swims on Strava, please refer to this article.  

For best results we recommend recording swims with either the Apple Watch or a Wear OS 3 supported watch.  There's also a number of third party devices that are popular.

I hope that helps.  Please let us know if you have further questions.

I have exactly the same issue. Thanks for pointing out that fix by saving it temporarily as a run. 

Hi Jane, 

Thanks for your response.

I have to say for a app that doesn't support recording open water swimming it does a very good job. It tracks my path using GPS very well. My phone is located in my safety bouy and keeps a steady connection. This probably helps.

It feels like by default the swim moving time uses something like a minimum speed of 2km/hr. Which I currently often fall under.

By saving as a run and then back to swim it seems to pick a different threshold and fix the issue. Then I get a very accurate moving time (comparable to my garmin watch, which sadly can't hold the GPS connection).

Hence the fix appears relatively simple. Adjust the default minimum speed for moving time for swim activities. Would be great if this can be fixed. For now I simply use the temporarily save as run and save back to swim work around.

Thanks

Merijn

I don't know why drawing a very detailed path on a map is not considered as 'moving' at the end of the day. My phone also records splits like 30s/100m. (carrying my phone in my safety buoy)

I have the same issue. I record my swimming activity with Polar watch. In Strava i get correct  elapsed time but much smaller moving time, and accordingly enormous pace.

It's been another year and Strava still hasn't made this seemingly easy fix. I too have to record as "run" (or walk), and then edit the activity to Swim to make it accurate.

Please pay some attention to this. A known workaround has been available for a long time already.

Yes.. today I swam 30 laps of a 300m- ish open water pond & the distance was 6.29 miles / it took me 4 hours 40 mins which is about right for my pool times but Strava said my time was 1 hour 4 mins!! Is it cuz the pond was so small maybe? 

Hello,  I tried a work around By saving as a run and then back to swim. And it doesnt workds for me. Affter few seconds after showing real pace ir recalculates and stars to show pold data.

Regards,

Ruslanas

Same issue, but I am not as good as you, although I would beat the record of Pan Zhanle.
(also carrying my phone in my safety buoy)

---

@ruslanijus wrote:

Affter few seconds after showing real pace ir recalculates and stars to show old data.

---

Same here. I recorded it on my Android phone in the buoy as "swim" after saving it and being at home I changed it to "hike" and back to "swim". As soon as I went back to "my activities" the results were wrong again.

Affter few seconds after showing real pace ir recalculates and stars to show pold data.

...

I have the same problem. Did an open water swim in the sea on Zakynthos today. Phone in my swim buoy. 1.200m in 11 minutes according to strava. I was for sure swimming for 30+ minutes. Please fix this Strava team.

Somewhere it was mentioned that the "fix" would be to record the swimming as "walk/hike activity" and later change it via settings into swimming. This works for me once. But when I open Stava next time the recorded time or my average on 100m is completely out of specs. According to Strava I would easily win the Olympics 🙂

> the "Mobile App is not supported for recording swim activities"

And yet the option to record a swim with it is there.  (Why?)

> "let us know if you have further questions."

Is this planned to be supported?

As discussed in this thread it sounds like it would be a relatively simple fix.

(The recorded GPS route is accurate and yet the "moving time" is not.)