Moving time for Runs completely useless

So here's the thing. I've just run a parkrun in 19.21. Strava calculates my moving time at 18.12. I ran flat out for 19.21. Where on god's earth does Strava get 18.12 from? This feature is completely and utterly useless. Can anybody explain this to me???

28

Kommentare

33 Kommentare
  • Offizieller Kommentar

    Hi Lee, 

    You may want to check out this discussion. It's a very popular feature enhancement, and we at Strava are aware of the feedback. Currently, nothing is planned or prioritized, but it's on our radar. 

    Aktionen für Kommentare Permalink
  • It would be an enhancement if it worked. Like I say, my moving time and elapsed time were identical! According to Garmin Connect, and Mapmyrun they were! Shame because I prefer Strava. I think this really needs sorting.

     

    9
    Aktionen für Kommentare Permalink
  • There is one run I use as a benchmark and in order for Strava numbers to be valid I have to always mark it as a Race.

    Using a stopwatch I've been able to verify moving time is within seconds of actual time when the activity is set to Race.

    Owen

    3
    Aktionen für Kommentare Permalink
  • Yeh I get that. But not every run is a race! It just seems bazaar that Strava seem to accept this as a positive!

    5
    Aktionen für Kommentare Permalink
  • I have to add my plus 1 to this thread. As a premium subscriber accurate data is paramount, and It really isn't rocket science to tweak this. Come on strava, be the best...

     

    4
    Aktionen für Kommentare Permalink
  • @Lee
    Totally agree, my comment was only meant to validate a work around.

    @Andi
    Thanks for posting a reply. Keeping this topic active might generate some action Strava's part.

    @Strava
    Lets do something about this and, while you're under the hood tweaking things, add new headders to allow for designating 'rest days' and injured recovery days

    Thanks
    Owen

    1
    Aktionen für Kommentare Permalink
  • There seem to be dozens of comments on this all over the support forum and the Strava facebook page and have been for a couple of years but Strava don't seem to want to listen to their users in this case

    4
    Aktionen für Kommentare Permalink
  • Has there been any movement on this moving time issue for runs. I just ran a 50k training run that I have ran 7 times now. When I looked at the comparison to the other times I ran the route it shows up as the slowest I have ran it even though it was actually my fastest time. I, like most people, count my run time from when I start running to when I finish. Basically I start my clock at the start and stop it at the end just like I am doing a race. But Strava insists on using the moving time unless you count it as a race. If I stop to pee (just like I do in a race) it Strava seems to think that should not be counted as part of my run. You can count every run as a race but that seems crazy. You shouldn't have to call everything a race for it to show up as a realistic run. I train like every run is a race so I can actually compare them to races but I don't want to call everything a race in order for it to make sense on Strava. Just counting moving time is not realistic and gives a false impression that you are running faster than you actually are.

    Can Strava just add a field in the "Run Type" box to count a run as a "Realistic Run" and program it to count the run time from the actual elapsed time and not the moving time. There could be another field to count the run as a "Moving Time Only" run if that is what the user prefers.

    4
    Aktionen für Kommentare Permalink
  • +1

    Note that this is indirectly affecting the accuracy (and usefulness) of the recent running fitness and freshness enhancement. If a portion of the time is incorrectly counted as non-moving time, then that portion of HR data is not included in the fitness/freshness calculation. For example, I ran hills today and included some bounding and other plyo. Strava said I was not moving for over 40% of my run. I estimate that the training impulse was 50% less than it should have been.

    3
    Aktionen für Kommentare Permalink
  • Yesterday I ran a mile race with my club.

    https://www.strava.com/activities/1027174934

    I stopped my garmin watch just after the finish line at 6.10 yet strava has added an extra 4 seconds. Where has this 4 seconds come from?

    I ran a pb for both a mile and 1k and yet neither of these show in my personal bests section!!

    Any ideas?

     

    Seems I'm not alone!

    Cheers

    0
    Aktionen für Kommentare Permalink
  • This is very frustrating!  I did a hike today that was 59:16 in duration, without any stops.  The "moving time" is 48:13 on Strava, not a small difference!  When I finished the hike and was asked how long I took, I couldn't say as the 48:13 was what was showing on my Apple Watch and I certainly knew it wasn't right!

    This is also what gets saved as the exercise to Health.

    I decided to use Strava because I really like the segments feature but I now suspect all the segment times are off as well.

    Jenn

     

    2
    Aktionen für Kommentare Permalink
  • @Paul Griffiths - your issue is not related to moving time. pls move your comment to another thread. (BTW, your actual issue is likely related to your Garmin recording in "smart mode". Switch this to record every second and your GPS data will be much more accurate.

    0
    Aktionen für Kommentare Permalink
  • And what I don’t understand is why the person who did the run with has his Moving Time shown on his Strava, whereas mine shows 15mins less as an elapsed time. This is ridiculous and I am only interested in Moving Time. Is there no way to turn off elapsed time option? Let the user choose it.

    -1
    Aktionen für Kommentare Permalink
  • I know this is an old post but as I hit this problem and did a little digging today I thought I would share my findings. My GPS watch recorded my run and this then uploaded to both RunKeeper and Strava. On Strava it showed the moving time as about 1 minute less than RunKeeper. I downloaded the GPX files from both sites and found data missing from the RunKeeper system. The data missing were twofold
    1) Times where I had seemingly not moved despite not stopping
    2) ridiculous times like 100kmh
    So it seems that RunKeeper filtered these out from the GPX file and Strava just put them as not moving time. But the upshot for me is that this was down to bad GPS data being sent to Strava. It would be good though if Strava had similar logic as RunKeeper to be able to make sense of c*** data.

    0
    Aktionen für Kommentare Permalink
  • I ran 1 mile last night set Strava to RUN. Gave me 9 min mile and 8.29 moving. I dudnt stop! My official time was 8.49. If I change to RACE it adds approx. 30 secs to both times! Strava can this get sorted this year? I have friends who are thinking of using other apps now.

    2
    Aktionen für Kommentare Permalink
  • I can’t believe this is still an issue.  And it’s very frustrating there is a cloud of uncertainty on how well I’m doing.  Tonight I ran a very frequent non-stop 38 minute run and Strava decided to shave some 3+ minutes off my moving time.  Why am I paying for Premium much less using Strava at all if it’s going to distort my results like this?  Hugely frustrating.

    2
    Aktionen für Kommentare Permalink
  • I just must say I agree with all above. I have been frustrated with Strava making up better results than I am actually doing for a while, and glad I found this thread. "Moving time" is useless, and it makes Strava much less attractive - so it is a bad sign that it hasn't been fixed for two years, and that they don't even comment on this thread. A pity when most other things are nice with Strava. But for a serious runner, it is the time from start to finish that counts. Instead of buying Premium I'll now look at the alternatives.

     

    2
    Aktionen für Kommentare Permalink
  • Hey Martin,

    Basically, as my daughter pointed out, Strava is Facebook for athletes.

    If you really want meaningful data to track your progress I'd recommend Training Peaks.

    Keep Strava for social 'measuring up' and that's about it.

    Owen

     

    1
    Aktionen für Kommentare Permalink
  • I ran 1.08 in a race, and GOT 55 minutts in moving time....

    3
    Aktionen für Kommentare Permalink
  • Hi guys. When I am running a race, I set my GPS watch so that it doesn't auto pause time. I assume that would fix the issue for you? when training I prefer to go on moving time as there are busy roads to cross etc.

    -3
    Aktionen für Kommentare Permalink
  • So, moving time is inaccurate. The Official Comment by Strava touts it as a "very popular feature". Kudos to Lee for pointing out that would be legit only if it were accurate. Talk about bringing in the spin-doctor. 

    No subsequent response from Strava. It will be 2 years next week. Very sad how a companty whose business model is dependent on accurate measurement of distance/elevation and time, of which time I imagine is the easier one to measure, screws up this badly. 

    Does anyone knows Nike+ Run is better or not? Would always support the smaller guy but what I disappointed me was lack of acknowledgement of the error. 

    3
    Aktionen für Kommentare Permalink
  • I'm going back to RunKeeper. At least they don't change my pace based on completely broken algorithms to calculate a statistic that has no meaning.

    2
    Aktionen für Kommentare Permalink
  • just went for a beautiful fall run. according to my strava premium I ran 12.9 km in 34 miles with average pace 2 41. I am 60 and 3 of my km were under 1 min. I am not a horse. this string is more than 2 years old. it's time for a new app

    0
    Aktionen für Kommentare Permalink
  • Hey Folks, 

    We're happy to take a look at the files themselves. Please feel free to write to our reps so we can help determine if there are any issues. 

    If there are any general questions I can answer in this thread, please let me know. 

    Cheers. 

    0
    Aktionen für Kommentare Permalink
  • Yea Strava, this is a MAJOR disappointment. I just spent loads of time transferring all my activity from MapMyRun, and then today, went for a run who's record was total nonsense. It claimed I had run across water! I had autopause turned off, and yet three times it shows a straight line on the map. GPS issues can be discounted because during the run, the 1/2 mile cues were correct, and the pace was 8 min/mile to 10 min/mile with total run time around 54 min. Then when I got home it changed to 7 min/mile average pace, cut out three sections, and said 44 min time. What the heck!? I think I better move back to MMR, very upsetting. Glad I'm not paying for any premium subscription!!!

    1
    Aktionen für Kommentare Permalink
  • @Dylan - Shoot our team an email and we'll help you troubleshoot the issue. Cheers. 

    0
    Aktionen für Kommentare Permalink
  • This issue still doesn't seem to be resolved.

    1
    Aktionen für Kommentare Permalink
  • I've had better luck since I posted comment earlier. The really glaring problems have gone away and the program has gotten smarter.

     

    0
    Aktionen für Kommentare Permalink
  • Hi, I'm just registering the fact that I'll be deleting my account and moving to another running app as soon as Strava send me my account data, due to precisely this issue with moving/elapsed time. 

    I got a PR today, running with my boyfriend who was also using the app. The issue is our finishing times were 50 seconds apart, despite the fact we ran the entire thing together. I recognise that phones have varying abilities to track GPS accurately, but our difficulty in figuring out my actual time- and having to switch between moving and elapsed times to get any idea of my actual splits and finishing time has certainly put a damper on the PR. 

    I don't see a reason to stay with Strava given that users have clearly been reporting their frustration with moving time for years, without Strava listening. 

    3
    Aktionen für Kommentare Permalink
  • Also experiencing this issue since switching from a Garmin watch to Suunto. Logged a 1hr 03m run with no stopping, but Strava decided to cut 6 minutes out giving me a ridiculous and inaccurate pace. Marking the run as a race corrects some of the problems but I shouldn't have to mark every run as a race.

    As this issue hasn't been corrected in over 2.5 years I doubt it will be fixed anytime soon, so the only option is to switch to another platform.

    2
    Aktionen für Kommentare Permalink

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.

Sie haben nicht gefunden, wonach Sie suchten?

Neuer Post