Moving Time versus Elapsed Time

I noticed this week that my runs are showing the splits in elapsed time (1 minute stop for pics added to splits) versus moving time. I use Strava on iPhone. This is different than earlier in the month. Did I accidentally change a setting? I prefer the moving time to get a sense of the pace when I'm running.

Thanks!

0

댓글

  • Do you have the run type set to "race?" If so, turn it to something else or leave blank.  I'm having the opposite problem, I want mine in elapsed, but I have to mark every run as a race.  Strava really needs to fix this problem that people have been telling them about for years.  Starting to be irritating to pay for a service when it essentially has a built in bug that they have stated they have no plans to fix.  Just give people the damn option to calculate run splits/averages by either elapsed or moving time.  Thinking of going back to Endomondo.  

    28
    댓글 작업 고유 링크
  • Nate, thanks for this, it was the solution I also needed - To be honest he more I read the Strava Support pages the more I see that they don;t appear to actually try to solve any issue!

    3
    댓글 작업 고유 링크
  • Just completed a cycle ride in 4:46hrs and when I sync info from Polar V650 info is correct. I went to my Galaxy S6 to add pictures etc and selected Race in Edit activity and noticed my time went to 4:53hrs which is annoying as completed in same time as my colleague. Using info above I changed to workout from race and time corrected. Why. please explain. I'd like to annotate as Race but not if its going to add a random 7 minutes for 2 very short 1 minute water stops. Where does this extra time come from??

    0
    댓글 작업 고유 링크
  • Same for me, completed a ride with a moving time of 7:19 and elapsed time of 10:42. I was surprised when I edited and changed to Race that it used the elapsed time instead. I wish/hope that there would be an option/setting to configure whether moving or elapsed time will be used regardless of what type of activity. I ended up changing from Race to None.

    2
    댓글 작업 고유 링크
  • Hi, I now have this issue. It is since I launched the Strava and Garmin Connect App on a new phone. The race type is blank for me yet it's still on lapsed time. Annoying.

    0
    댓글 작업 고유 링크
  • Update: I took it off Treadmill running and changed it to long run, now it's different.

    0
    댓글 작업 고유 링크
  • I am having the same issue. Although, I cannot get Strava to show the actual moving time instead of elapsed time. The workout type is set as "run", but the time setting keeps reverting back to "elapsed".

    0
    댓글 작업 고유 링크
  • I wish I had that issue. Except for setting run type to 'Race' I can't get it to calculate on elapsed time only moving time. :(

    5
    댓글 작업 고유 링크
  • When will this be fixed? It has been identified for several years now and still not taken care of by the Strava team. All my runs show a non sense moving time as I never stop when running and still it deducts several minutes from the elapse time. Consequently the pace calculated is the one of Kilian Jornet, definitely not mine. And I cannot compare my runs anymore with the history.

    Indeed the only solution is to switch manually to race type and still the comparison with previous runs do not work.

    Please StravaTeam take all these complaints seriously once and for all.

    Thanks

    14
    댓글 작업 고유 링크
  • Thank you Erica and Nate. I find it very misleading to run a route, then Strava says I was 18 minutes faster (4:53 vs 5:11 ) This was a tough off-road hilly race. I KNOW I paused on a few hills, but elapsed time is the relevant one.

    4
    댓글 작업 고유 링크
  • One of the riders I'm following captured the ride with the Strava Android app and on the Strava IOS app on my phone shows "elapsed time" instead of "calories".  Maybe the capture device is determining how the results are displayed in the app?

    0
    댓글 작업 고유 링크
  • Strava will you please listen to the community.  For many of us the moving time data is worthless, I never want to use it.  It doesn't give a true reflection of time and effort spent out on a run.  At least make moving time or elapsed time an option, how hard can that be to implement?
    First comment on this thread over one year ago, and still no action, respect your community, anyone???

     

    10
    댓글 작업 고유 링크
  • Strava, I want to see BOTH elapsed and moving times for my commutes as BOTH are important. And let me choose which to use for comparisons. Do not ass-u-me that you know which is appropriate. Do not make me guess which goes with selections like "race" or "commute".

    7
    댓글 작업 고유 링크
  • Same issue here: On my watch (Samsung Gear Sport), I have correct time, avg speed and distance. After automatic upload to Strava, only race activity type shows approx the same data that on my watch / phone (S Health). Issue is in moving, elapsed time and distance.....

    0
    댓글 작업 고유 링크
  • Adding my vote for a choice that doesn't involve a falsehood, I want elapsed time in a run that wasn't a race, why should I have to call it something it isn't to do that?

    1
    댓글 작업 고유 링크
  • I don't care about "moving time," and whoever implemented it as the default was a dunce. I want elapsed time, and I want my average speed calculated from it, including my 0mph stops. This should not even be an issue.

    3
    댓글 작업 고유 링크
  • I have the same problem. I've been using Suunto and up until a couple of weeks ago, my Hikes has always been displayed with Elapsed time. But now they changed that and all of a sudden a tough Hike/climb that took 11h 24 min is displayed as 4h something. On hikes etc it is not even possible to use race to display elapsed time instead. This is super annoying....

    2
    댓글 작업 고유 링크
  • Strava should have both moving and elapse time displayed 

    0
    댓글 작업 고유 링크
  • I have the problem that I recorded my run using my Garmin watch, uploaded that to Strava as well, everything is fine until I change it to "race", then it adds on time and slows my pace right down.  I put it onto "Long Run" so it reflects the actual run time as shown on Garmin.  Others in my team had the same issues.  They need to sort this out.

     

    0
    댓글 작업 고유 링크
  • Similar problem here... i use the strava phone app to record and use the web app for viewing. Moving time is often grossly inaccurate.

    Had some luck tho. I found that understanding pauses is the key. Somewhere in the Strava help text i came accross a sentence "... As long as your device is recording conventional pauses, Strava will respect any pauses recorded in the file whether your device pauses automatically or you manually hit the pause button. ...". If no pauses detected in the track, it insists on calculating moving time anyway based on type, usually poorly. No way to explicitly turn this off.

    Also, for 'run' activities, strava app uses the the accelerometer to detect pauses. For 'ride' activities, it uses gps position.

    For me, for hiking, where i do stop regularly, this works well for me...
    Record Activity/ Settings/Auto Pause/Run Auto-pause - Checked
    Note: helps to shake the phone once in a while to make sure its unpaused.

    For walks where i want moving time to be = elapsed time...
    Record Activity/ Settings/Auto Pause/Run Auto-pause - Un-Checked
    AND do at least one Stop/Resume

     

     

    1
    댓글 작업 고유 링크
  • Forgot to mention... if you manually upload a gpx, or edit a track (crop, split, change type, etc), it seems to have lost all pause info and always does the inaccurate moving time calculation.

    0
    댓글 작업 고유 링크
  • Something has changed recently and through reading these posts I would suggest that it's a difference between Android v's iPhone. For example, my partner and I have just done the same run today for me my Moving time = 2:54:35, Elapsed = 3:35:45, for her Moving time = 3:35:34, Elapsed = 3:35:44. We have the same watch Suunto Baro 9 (ALL same settings), only difference is I sync through Suunto App on Android, she syncs via Suunto App on iPhone. 

    IF I change to race, then of course Moving marries up to Elapsed, but why should I have to change all my training runs to a Race to reflect correct pace and splits? 

    Suunto App shows the correct elapsed time as per my watch.

    Final Surge shows the incorrect moving time which is fed from Strava, pointing the finger squarely at Strava. 

    It seems that this has only changed recently but I cannot tell you when. 

    WHAT HAVE YOU DONE STRAVA

    4
    댓글 작업 고유 링크
  • Even if Moving time was really interesting for someone, it's still absolutely random.

    I run non-stop with the same pace for 1:07 hours. Strava bites 8 minutes off from those and states that I was moving for 0:59. 12% error. That really looks like a deep analysis, doesn't it?

    But the craziest things happen when you hike. Even if you walk for 7 out of 8 hours, Strava can say that your moving time was like 50 minutes.

    Once I had a thought to buy a subscription. Now I think maybe to stop using it at all. In any case, the data is useless for comparison.

    Please, let the users choose which time to use for calculations (elapsed or moving). And then take a look what real runners will choose.

    7
    댓글 작업 고유 링크
  • Strava (on the off chance you read this). Thank you for allowing us to see both elapsed pace and moving pace under pace analysis.   It would be even better if we could choose which pace displayed on the main activity page. One of the things I love about Strava is the ability to share runs with friends.  However, it feels deceptive to default to moving pace without noting it as such, since that is not a true reflection of your physical abilities over the given distance.

    4
    댓글 작업 고유 링크
  • I don’t want anyone or me seeing My elapsed time, do you know how to get rid of it, I find it annoying because I go on warm downs after runs so my elapsed time builds up??

    -2
    댓글 작업 고유 링크
  • Wow. Amazing to see zero/0 response from Strava. Nice going.
    If there is an answer elsewhere could you point us to it?
    I am now having the same issue with Garmin. Suunto took so long to sync and process the run that it seemed to keep correct moving time.

    2
    댓글 작업 고유 링크
  • Freddie

    Two ways,
    1. if you don't want to track the warm down just pause or stop the activity during the warm down.
    2. if you want to track the warm down separately, you can stop the primary run and start a new activity for the warm down or split the activity in strava.

    Splitting is similar to cropping, Go to "Actions" (the three dots next to the edit pencil) - "Split"

    0
    댓글 작업 고유 링크
  • H E L L O. S T R A V A are you there? At the very least please reply to this thread a it is a real problem for many people.

    2
    댓글 작업 고유 링크
  • Hello Strava, did you analyze this issue at all? I would like to suggest you to resolve basic issues before going forward. Even if I consider buying any of pack you are advertising, do I have guarantee that this issue will be resolved?

    1
    댓글 작업 고유 링크

댓글을 남기려면 로그인하세요.

원하는 것을 찾지 못하셨나요?

새 게시물