Why is my elapsed time wrong?

I did a cycle ride and the moving time was 25mins 38secs, (which is correct). However the elapsed time for the ride shows 7 hours, 47mins and 42seconds, which is completely incorrect.(This gives extremely long times on the segments). This discrepancy started about a month ago and now happens on every ride I do. Why is this happening? (It used to work fine).(Note:- My rides are recorded on my phone).

6

댓글

  • I'm having similar problems recording runs (elapsed time recorded by strava exceeds actual time of recording) except that my moving time is also wrong (moving time is less than actual recording even though I was moving constantly).  I'm using up to date strava app on Pixel 2 / android v10

    Here's a recent run that recorded incorrectly:

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

    The actual elapsed time on this run was 40:03 according to a stop watch. Strava shows moving time 32:57 even though I never stopped and elapsed  time of 51:27 which is totally wrong.  .gpx data downloaded from strava shows elapsed time of 51:27 but google maps timelines shows 39minutes so the phone is obviously recording the data correctly it just doesn't post correctly to strava.

    Here's another one https://www.strava.com/activities/3035189075

    actual elapsed time was 19:48 of constant running but strava shows 15:55 moving / 25:40 elapsed.  google timeline shows 21minutes.

    2
    댓글 작업 고유 링크
  • I have also some strange behaviour with some segments. total time 5:23:33. moving time 4:51:13. these values seems correct, but i have some segments with time > 6 hours. Another segment with a distance of about 2.5km with a time of more than 2 hours. if I summarize all the totaly wrong times, my journey took more than 36 hours.

    I use the Android App.

    ps: for me it seems that they have at strava not the best programmer. at first they did deactivate the heartrate sensors and now there are some bad bugs with segmenttimes.

    1
    댓글 작업 고유 링크
  • The problem I had has now gone and I believe it was a setting on the phone that was causing the problem. In the settings on my phone for date and time there is a setting that is 'automatic date and time'. I found this setting un-ticked(don't know why it was un-ticked). I ticked the box so 'automatic date and time' is now used. (there was also a software update pending on my phone which i updated at the same time.....however I believe it was the un-ticked 'automatic date and time' that caused the problem....Segment times and elapsed times now good...happy days again.

    1
    댓글 작업 고유 링크
  • Thank you Graham, I have just checked that and the box was ticked. I am willing to think it is related to a software update because as I explained, the GPS data shows wrong times. 

    1
    댓글 작업 고유 링크
  • All android phone users please strava sort it it has been going on since december2019 and still no solutions it's getting beyond a joke

    1
    댓글 작업 고유 링크
  • I’m having a problem of a similar flavour. iPhone11, recorded on an Apple Watch. All segments seem fine during run, I get the split notifications and so on. On upload to Strava app however, all of my runs are fine for distance, but have recorded no time and heart rate data for the first mile. And it’s always the first mile.
    So for example a run completed today, 5k in 23:38, has been recorded as 5k in just under 15 minutes, with a time of 0:00 for the first mile.

    1
    댓글 작업 고유 링크
  • I have had the same problem, and it is driving me crazy.  My elapsed time and moving time on most segments are different, although I do not stop during or after or right before the segment.  I have contacted Strava Support, but they have not been helpful so far. 

    1
    댓글 작업 고유 링크
  • Do  you "Finish" and "Save Activity" when you're completed your ride? -- Dan

    0
    댓글 작업 고유 링크
  • The same thing is happening to me. It started about 1 month ago. When I move faster than 20 kph, the time recordings seem to be ok, but when I move slower, the segment time is way longer than the actual time. I have just finished a recording. The recording time was 1 hour, but the elapsed time was 1 hour 30 minutes. I have just checked the GPS data and the last recording time was 30 minutes ahead the real one. How can that be possible?

    0
    댓글 작업 고유 링크
  • I have the same behavior for several weeks, I don't know how it happens, its really ennoying. Please strava correct this bug.

    0
    댓글 작업 고유 링크
  • I started seeing this situation back in November. my official time was 5:17 total time. Strava recorded it as 5:48 moving over 7 hours elapsed. i started the activity at the gun time, and ended as soon as i got off the bike. https://www.strava.com/activities/2886136618

     

    Yesterday i ran 5k. My moving time was 28 minutes with a pace of 8:39. All of my mile splits show between 10-12 minutes for the pace. All the segments and efforts have slower times as well. https://www.strava.com/activities/3039698512

    Im recording with the app directly from my phone. LG G6. my automatic date and time is already checked.

    0
    댓글 작업 고유 링크
  • I'm also an Android user and am having the same issue. Just got in from a run that took 61 minutes according to a stop watch, but my Strava activity suggests a total time of 1hr 28m and moving time of 1hr 16m: given I was running laps of a park this discrepancy alone would give me pause for thought!

    I've tried reporting/flagging the errors on multiple occasions and have deleted/reinstalled the app.

    Anyone have any other ideas, or is this just a bug to be fixed by Strava HQ?

    0
    댓글 작업 고유 링크
  • I just posted some relevant comments on this thread:

    https://support.strava.com/hc/en-us/community/posts/360056124992-Incorrect-pacing-on-Strava-on-Android?page=1#community_comment_360009063191

    I also included some links to other threads that might relate to the same underlying problem.

    0
    댓글 작업 고유 링크
  • My last run recorded with android phone is totally wrong : Elapsed time = 1h 31 min, Moving time = 1h 56 min. Obviously something messed up with software.

    0
    댓글 작업 고유 링크
  • I am having the same problem. Started a few weeks ago. Seems to be related to one of the latest app updates...?

    Today I did an activity starting at 10:11 AM. Finished around 12:50 PM. But Strava shows a total moving time of 05h:18m. So at the time I finished the activity that would be more than 2.5h in the future. Very annoying...

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

    Meanwhile I found out when I use the "Export Original" functionality for that activity and upload the according FIT file to Garmin Connect a total time of about 2h:38m is shown.

    Seem like something is going wrong while exporting an activity from the phone to the Strava website.

    0
    댓글 작업 고유 링크
  • Exactly the same problem!
    Today I started at the start of a known segment and checked the time at the end - it took 15 minutes. When I finish the run and upload it says 19 minutes.
    Realit annoyed as 15 mins is a gold for me!

    Anyone got any solutions?

    0
    댓글 작업 고유 링크
  • I've just started getting the same problem where my elapsed time is significantly longer than my Strava time. I use my phone for tracking so initially thought it was something to do with GPS on my phone. I got home at about 17.30 but when I looked at the Flyby of my run it showed me only getting home at about 18.10 which is a massive difference in a 45 minute run...

    0
    댓글 작업 고유 링크
  • Anyone got a solution for this?

    0
    댓글 작업 고유 링크
  • I've had the same issue as what people have posted above. Ran 15 miles in approx 1:41, listening to the mile audio cues which verified a 6:45-6:50/mile pace throughout. When the activity was uploaded, although the starting time and distance were correct, the moving time was supposedly 2:23, elapsed 2:40; an hour into the future. I couldn't even view it on my personal feed at first though it showed on the Following feed. I used a Samsung S8, time was already set to automatic.

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

    0
    댓글 작업 고유 링크
  • 0
    댓글 작업 고유 링크
  • I fixed this problem
    I went to my location and it said my town was in LA. (I'm uk)

    I changed my town to LA and saved.
    I changed back to my town and saved. My location was then corrected to UK.

    Problem fixed instantly

    0
    댓글 작업 고유 링크
  • Checked and made sure my date and time were correct on Iphone(what I use to track, with Strava app). My total run elapsed time was 16:51 but then I checked one of the segments that I ran and it gave me a 24:13 which was way off. I had a basic watch tracking at the same time and it gave my time on that segment around 9 minutes. How does part of my run take 24 minutes when my total run only took 16:51. Ironically, the only reason I did this run was for this particular segment that the tracking was wrong on, haha. 

    0
    댓글 작업 고유 링크
  • Ditto.  iPhone 10.  Strava app version 152.0.0.

    0
    댓글 작업 고유 링크
  • Same on iPhone 11 running 13.5.1 and watchOS 6.2.6. Times look fine during activity, but total time when saved is consistently 5-10 mins less than total elapsed time. Distance saves correctly.

    0
    댓글 작업 고유 링크
  • I’m using the Strava app on Apple Watch which showed an elapsed time of 29:20 when I stopped and saved the activity. When uploaded to Strava to view on iPhone app it says elapsed time of 28:49? Which one is correct? Distance looks OK. I have auto time zones on.

    0
    댓글 작업 고유 링크
  • On my regular commute I've noticed discrepancies between the time that Garmin 35 reports to Garmin Connect and the moving time shown on Strava. My Garmin 35 syncs to my Android phone and syncs to Strava via the app. Autopause on the Garmin is switched off. After a recent ride Garmin 35 and Garmin Connect said total time, moving time and elapsed time were all 44:01, but Strava says moving time is 45:52. I did not press pause during the ride. My Strava location was set to LA at the time, since corrected to Matlock, UK. Thinking of going back to using my Garmin Edge 500, but don't want to give up the ease of wireless syncing. Does anyone know of a fix to this issue?

    0
    댓글 작업 고유 링크
  • Something is not working properly in Strava

    Many times, in Segments, it shows different effort and moving time and for sure I did not stop. And the begining and the end of my ride are far away from the segment in order to prevent this: Resting time can be captured in a segment effort if you rest or turn around near the beginning or end of the segment.

     

    0
    댓글 작업 고유 링크
  • I did a controlled test on this last night.

    I did a running start and a running end with absolutely no stops and my moving time is 22.49 (which is the time I observed on apple watch) but elapsed time is 23:41 on strava!!
    I'm also unable to sync my cycle rides and some of my training runs this week.. so something is going on.
    0
    댓글 작업 고유 링크
  • Having the same issue. I started the run at ~18:30, finished and uploaded the run ~18:54. Strava claims my total elapsed time was 31 minutes (obviously wrong) and my moving time is ~24 minutes (which is correct).

    Exported gpx says I finished the run at 7:01. Which is wrong.

    I'm using a OnePlus 3t, and date and time settings are set to automatic.

    -1
    댓글 작업 고유 링크

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

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

새 게시물