Let users specify whether moving time or elapsed time is relevant to that activity

When runs or rides are uploaded to Strava, time spent stationary or with very little movement is ignored when evaluating the whole average pace of the activity.  So for example, a run last night where I had to stop for 50s to tie some shoe laces ignores those 50s when calculating the average pace.

For running, I think this gives a misleading impression of pace.  I can run 5min/miles for a mile, providing I run for 15s, stop, run for 15s, stop, run for 15s, stop, etc etc etc.  And if I recorded such an activity on Strava, that's what the activity would show.  

I would like to suggest a toggle switch for an activity - "Elapsed time or moving time" - which can be specified on run by run basis so that if I want to see my pace based on total elapsed time, I can; and vice versa.

I strongly suspect that this would be a feature only desireable for runners.

311

Comments

218 comments
  • Please fix this no one wants moving time 

    3
    Comment actions Permalink
  • All Strava statistics need to support elapsed time including splits and comparison with other segments and activities, against others and yourself. I had Strava saying my previous run was faster, though it was the opposite. This because Strava shaves off random minutes you never know what you will end up with. My runs gets totally random times. It cannot be that hard to show elapsed time, can it? If my run took 48 minutes, it actually took 48 minutes.

    3
    Comment actions Permalink
  • I also agree with this. On personal routes with no public segments it is quite a chore to have to browse through all the data to find the elapsed time and compare it to different efforts. 

    2
    Comment actions Permalink
  • This change is essential. Maybe it's OK for interval sessions, or repeats, but anything else is fooling yourself.

    If your "moving time" for a marathon shows 3:30, but you actually took 4:30 because you stopped to stretch, chat to friends at aid stations, or ducked into the shops to go to the toilet, then Strava will report a number that is totally unrealistic for you.

    On long rides/runs/hikes, stopped time is recovery time, and should be included by default.

    3
    Comment actions Permalink
  • All, please open and report individual bug tickets about this. We need some change in this regards. It's ridiculous how long it takes for such a simple and fundamental feature.

    3
    Comment actions Permalink
  • @Ron, of course you're welcome to submit support tickets to us, however it would be more helpful to us to recruit your friends to vote and comment here. Thanks! 

    1
    Comment actions Permalink
  • Completely agree with what has been mentioned before. We need to have a switch or the capability to switch the time for calculation.

    During a run, i lost the GPS for 1min, the distance was right but the elapsed time was 1 min wrong so the achievement is overcalculated. Given a wrong achievement which will be challenging.

    1
    Comment actions Permalink
  • I would just like to pile on here.  I'm also very surprised that this isn't an option.  I can't think of any reason why I wouldn't want my pace to reflect the fact that I couldn't handle my pace!

    1
    Comment actions Permalink
  • Totally agree.  It is MADNESS that there is a difference between 'elapsed time' and 'moving time' (when auto-pause is off).  I'm sure that this has only recently changed.  When I stop the clock and it says '40:23', I expect the time displayed to be '40:23', not a figure less than that!?

    How is it possible that only 32 people have voted for this?  To me it seems like a serious bug that needs to be fixed... Not a feature request.

    2
    Comment actions Permalink
  • ***If you tag your run as 'Race', it will display the Elapsed Time, rather than moving time*** as per this blog post.  

    Seems madness to me, but anyway, that's the solution for now :-)

    "Elapsed Time: For all runs that are NOT tagged as “Races”, we now filter resting time out of both pace analysis and the overview chart. “Races” will continue to show all elapsed time including resting, since races are a competitive effort. Segment efforts will also continue to display elapsed time."

    http://blog.strava.com/run-activity-page-updates-and-improvements-6500/

     

     

    3
    Comment actions Permalink
  • Looks like this has been resolved. Go for a run and check it out!

    0
    Comment actions Permalink
  • I just uploaded a new run and it still using moving time. I see nowhere to change to elapsed.

    1
    Comment actions Permalink
  • And the moving time is still really bad. I ran for 55 minutes and it shows my moving time as 53 minutes. I never stopped!

    2
    Comment actions Permalink
  • +1 vote for killing Moving Time.

    Agree with all these comments. For running, and trail running in particular with steep slow climbs, moving time is a useless stat. 

    Kill Moving Time or make it optional in user settings.

    I and others want to be held accountable for the time we stop and gasp or hold our bellies and puke. It's the only way to accurately track training progress and to track competitive ability.

     

    3
    Comment actions Permalink
  • I totally agree! Patrick wrote an alternative solution but we cannot distinguish race and training in this case.  As you said, it sounds like a small change, please fix ASAP.

    1
    Comment actions Permalink
  • This would also solve the problem with stationary workouts that ignore HR when not moving

    0
    Comment actions Permalink
  • Is anyone from Strava even listening here? Nice that we all agree, but...where's Strava?

    3
    Comment actions Permalink
  • I'd like to weigh in too.  I hike/approach and indoor bike.  Hikers need elapsed time for training hikes.  For example  this one https://www.strava.com/activities/571093248

    It took me really about 2:18:00 to get to the top.  All the moving times for hikes don't work with your Moving Time.  Besides the really fast types want to show off their car-to-car times for epic climbs, etc.

    1
    Comment actions Permalink
  • It should be an option.

    Personally, I run in an semi-urban environment with a lot of places where I have to stop due to intersections, etc.  Why would I want that time calculated into my pace in that circumstance.  

    The fact that I am stopping has nothing to do with needing a break, taking a rest, etc.  So a mile I am running at a 7:30 pace, now looks like a 9:00 pace due to having to stop for traffic. How is that accurately reflecting how fast I am running.  It is just bad luck that I caught traffic at a bad time.

    When I am out on a training run, I never walk or stop for any other reason other than to avoid getting run over by a car.  I would like my pace to show how fast I am running, not how much car traffic I encountered.

    Maybe there should be two pace figures for both overall and splits .. moving pace and elapsed pace?

    I totally agree that activities that are tagged as races should always be elapsed time not moving time.

    1
    Comment actions Permalink
  • Big trouble for all my uploads where I had to correct bad GPS data. I can set the elapsed time, but the moving time is still showing up wrong.

    0
    Comment actions Permalink
  • Yip, another voice in the wilderness requesting the option to get rid of moving time in favor of actual time. It makes comparing trail runs utterly useless for me on strava. I was just beginning to have fun comparing my runs and segments with friends until I became frustrated with the whole ridiculous and useless moving time calculation. Your service is the only one, and I have looked at many, where this is an issue. I really can't think what ulterior motives you have for not allowing it but there must obviously be something that I am missing...

    2
    Comment actions Permalink
  • Yeah, I think it's rooted historically in the Strava being for bike rides. For bicycles it makes a lot of sense, because moving time deducts all red traffic lights. But it doesn't translate to running very well.

    0
    Comment actions Permalink
  • I agree completely that having time recorded as Elapsed time is a must!  At least have the option to do so.  Not having that feature makes utilizing Strava virtually useless for trail/mountain running.  If I go out for a 5+ hour run I would like my data to show that I ran for 5+ hours, not the typical 4ish hours it shows now.

    I mean, all the "wow your so fast" comments I get after a long run are nice but I'd rather have data that reflects my actual ability level.  :)    

    2
    Comment actions Permalink
  • Keep voting +1 on this issue and also send individual bugs/reports about this (even though Strava couldn't care less and won't even read those). Maybe some day by 2039 Strava will catch up with the rest of the world and make their site/platform usable.

    2
    Comment actions Permalink
  • I just completed a 100 km ultra marathon where stoppages at aid stations are a natural part of the race (Elapsed time). My official race time was 12 hours 20 minutes but on Strava, it was 11 hours 41 minutes. Very misleading!

    Strava should provide an option for the user to decide which mode to use (Elapsed time or Moving time). Please implement this change ASAP! 

    1
    Comment actions Permalink
  • I'm an endurance road racer and join the Gran Fondo bike race. The elapsed time is vital since the regulation mentioned the elapsed time should be within 24 hours. In the future I may have a 24 hours ride but need to look at the elapsed time when it gets very close. This function is quite important for me. 

    1
    Comment actions Permalink
  • Please all vote +1 and submit tickets. But then Strava couldn't care less about their user base anyway. I wonder if we all shouldn't spend our time finding another web resource than Strava?!! I myself is using Garmin. It has less features, but it does support the very basics, like elapsed time! Strava is utterly useless.

    What other resources are out there? Maybe others have better recommendations? Strava will never fix or change anything anytime soon.

     

    2
    Comment actions Permalink
  • Note that you can just mark every run as a "race". For races in Strava, the clock never stops, just like in reality. :-)

    FYI, I do not know if marking everything as a race would mess up data.... but I kind of don't care. I need to know if my 8:45 mile is really 9:10, etc.

    0
    Comment actions Permalink
  • Marking an activity as race pretty much only changes the title, but all other stats, data and comparisons are still moving time.

    0
    Comment actions Permalink
  • Any update on this? There seem to be consensus that elapsed time is the preference?

    3
    Comment actions Permalink

Please sign in to leave a comment.

Didn't find what you were looking for?

New post