Inaccurate splits after importing?

I typically log my runs on my Apple Watch with the built in Activity app. Then I use HealthFit to import it into Strava.  All year, this has worked completely fine, and if there was ever any difference in pace/splits/etc it was super minor and negligible.

In the past month or two, any time I import a run into Strava that I had paused in, it shows the correct average pace...but the splits are off.  It always shows one split at like 5 minutes slower than what it actually was.  It's weird because this only just started happening.  Does anyone know how to fix this?

1

댓글

  • I am having the same issue. Obviously overall average pace of my run was accurate, but per KM splits pace was not accurate. There are splits where I was ridiculously fast and splits that I was ridiculously slow.

    This screw up my Strava's Estimated Best Efforts of 1KM and 1 Mile.

     

    1
    댓글 작업 고유 링크
  • This happens to me, too! Still don't have a solution.

    1
    댓글 작업 고유 링크
  • Sometimes my mile split is recorded in the app incorrectly (1 minute faster than it should be). This only happens for mile 1 split, but it makes my average mile pace faster than it should be.
    Does anyone have a solution?

    0
    댓글 작업 고유 링크
  • My splits were fine until about 1 month ago now they are all over the place. The KM announcements are fine when I'm running but in my activities they all totally different, by minutes sometimes. Can anyone tell me why?

    1
    댓글 작업 고유 링크
  • Same here, last 3 runs the pace is around my usual, the shout outs are also in line with most runs but the splits bear no resemblance.
    Examples.
    Last shout out 6.34. Split recorded as 7.58.
    If I add up all the splits I would have been running for 4.5 minutes longer than I actually ran for. Seems that they can alter time!
    Most annoying is that they keep pestering to upgrade, try free trials, and yet you cannot contact them to discuss something as basic as this.

    1
    댓글 작업 고유 링크
  • I have this issue as well. Pace display during the run is accurate. After the upload overall time and distance is accurate but the km split times are way too slow. About 1-2 minutes per km more. The track on the map looks fine as well. It has to be the processing on stravas end.

    Example activity: https://www.strava.com/activities/2956918325

    The frustrating thing is, that the broken times count towards segments. I ran my ass off to do a 4:00 pace on a segment and now I'm on the leaderboard with 6:30 something.

    1
    댓글 작업 고유 링크
  • Nothing wrong with Strava. Found it was the gpx file on my phone that was suspect. Uninstalled Strava, rebooted phone and reinstalled and all is fine now.

    0
    댓글 작업 고유 링크
  • I'm having this issue as well.
    Just done a run with an average mile pace of 8:31 over 5.7 miles, yet the fastest mile pace according to the splits is 9:23!
    I restarted the phone before the run but still happened.
    Anyone know why this is?

    1
    댓글 작업 고유 링크
  • I have had the exact same issue since mid December.
    I deleted the app, rebooted my phone and reinstalled, however no improvement.
    It is very frustrating and surely must be a Strava issue if other people are having the same problem.
    Any solutions would be appreciated.

    2
    댓글 작업 고유 링크
  • Very frustrating isn't it.
    I've tried everything possible now, even turned the auto pause off and turned location on the phone off and on.
    Contacted Strava who basically said there isn't a lot they can do about it. Weirdly tonight it has made my run look faster than I've actually ran, but when I finished my run, I looked at the time and it said 29 minutes. Uploaded the activity and it said a moving time of 25 minutes.
    What device are you using to record your activities mate out of interest?

    0
    댓글 작업 고유 링크
  • My fix above worked only temporarily. Have used Kamoot to record last couple of runs and am now back to my 5:20ish pace rather than 7:30. But of a faff exporting and importing gpx files. Will do next run with both Strava and Kamoot running at same time for comparison.

    0
    댓글 작업 고유 링크
  • I am using my iPhone. Admittedly it is an old iPhone 6S.
    I am now wondering if maybe it is the phone itself.
    I will try using another device to see if it works and post again.

    0
    댓글 작업 고유 링크
  • Having the same problem, started in mid Dec 2019.  Pace display during the run is accurate. It shows the correct average pace...but the splits are off.  They are showing me running faster than I actually am by a good minute per KM.  I have shut down and rebooted  the phone but the problem still exists. I am on version 133.12 (1211701).

    0
    댓글 작업 고유 링크
  • Used the same device tonight to record the same run simultaneously

    Strava 6.06km 33:30 (started before and stopped after Kamoot)

    Split times: 5:51, 6:36, 6:55, 6:41, 5:54, 6:17 (totalling 38:14 if my maths is right)

    Kamoot 6.03km 32:24

    Split times: 5:11, 5:17, 5:26, 5:33, 5:25, 5:22 (totalling 32:14)

    This has been going on since mid December for me as well in Strava and I would love to know how to fix it especially before I get back to cycling in the spring. For me I know the issue is not my device. it's just what is being recorded within the Strava app itself.

    Any ideas anyone?

    1
    댓글 작업 고유 링크
  • Just done a run this morning - ran for 7.4 miles, my moving time was 1 hour and 4 minutes (didn't pause the run once and auto pause is off), however, I looked at my phone just before finishing the run and it was showing that I'd been running for 1 hour and 9 minutes?! Why the 5 minute variance?

    Also, just looked at my run online and for some bizarre reason the elapsed time is saying 1 hour and 20 minutes. The app wasn't even on for that long!

    Any suggestions welcome as I am completely confused and getting annoyed by this now.

    Lewi

    0
    댓글 작업 고유 링크
  • Same issue here. BUT

    What's interesting for me is I used the Strava app on the phone while running (NOT IMPORTING, although I also ran it simultaneously on my Garmin watch to verify I wasn't going crazy.) Over the Bluetooth headset the Strava app gave me 1/2 mile pace updates, all that were accurate and matched the watch

    After completing the run I get correct totals: 32 minutes, 4.1 miles, 7:48 min/mile pace.  However ALL the splits are over 8:14 min/mile.  Adding them up would be almost 34 minutes.

    tldr: mid-run splits were displayed on the Strava app correctly, and changed once hitting Finish

    1
    댓글 작업 고유 링크
  • I may have found a solution to this issue.

    Upload your run as a race. Strava will not perform post-processing on the data. Then change it back to type "none".

    Worked for me. Splits are fine now.

    1
    댓글 작업 고유 링크
  • I tried what Martin suggested, and afraid it didn't help me. splits up to 3 minutes longer than the audio cue times, and it even managed to add 8 minutes to my run time!!!.

    1
    댓글 작업 고유 링크
  • same here, it all started last month. splits are way too slow...if we have the same issues, probably there's something wrong with Strava. 

    1
    댓글 작업 고유 링크
  • Same here. All my runs this year are all over the place, segments are taking hours(!) My split miles are reading at about twice the speed I'm actually going. Very annoying, got in touch with strava and they said turn location on/off uninstall and retry.
    No change though. 🤷‍♂️

    1
    댓글 작업 고유 링크
  • I am having the same issue. Splits are all over the place which is effecting my "achievements"! Let's hope someone has a solution soon. 

    1
    댓글 작업 고유 링크
  • Same problem, at least since last month, maybe longer. I initially thought it was me going crazy so I'm happy to have found this thread! The audio cues give the correct times as I'm running, but then when the activity saves, they're totally different, despite the total elapsed time and average pace being correct. It makes no sense - I could understand if it was a recording problem, but the app clearly had the right data at one point. Surely it just shouldn't be possible for the sum of the individual splits to exceed the total time?

    0
    댓글 작업 고유 링크
  • SAME!!! Its so annoying because its messing up my PRs and I don't like that. boooooo. Also, I tried to change the run type but that didn't help. I also removed the apps and rebooted my phone. Nothing 

    0
    댓글 작업 고유 링크
  • Same issue. This morning's Fastest Split: 4:44 / mi. Avg. Pace looked about right: 7:33 / mi. Unfortunately it looks like it's time to find a new app to record runs.

    0
    댓글 작업 고유 링크
  • Same for me...started in december. Audio split times were fine but when uploaded to the app completely wrong. Each km showing about a minute longer!!..Total running time was fine though.
    However...tonight...now the running time is wrong aswell....audio correctly told me 5km in 27minutes...i then ran another 0.4km but total running time 32 minutes!! I must have crawled that last bit!!!
    Looking back in the comments do Strava ever actually reply to anyone???
    I've hit the REPORT DATA button many times recently but is there any point???

    0
    댓글 작업 고유 링크
  • Same issue here. Fastest 1km split is over 6 minutes /km, yet for the run overall pace is 5:30 per km (which is closer to correct though still wrong). Some km splits are as slow as 9 minutes which is definitely wrong. Segment times are all way slower than they should be and give my pace as 7:30 per km for example, when they should have been closer to 5:30. Really frustrating.

    0
    댓글 작업 고유 링크
  • I've been digging into this and I've found that it's not Strava itself, but the GPS data provided by a device.

    A run last night had my moving time at 24:30. The GPX data recorded over 30 minutes. It's like the GPS clock is running fast.

    When Strava calculates the distance and time, it comes up with an accurate average pace, because that's easy to calculate. The route is also accurate, because the GPS coordinates are correct, but the time is wrong. 

    I don't have an answer yet, but I'm now understanding the issue better.

     

    0
    댓글 작업 고유 링크
  • This issue is still there....

    I did the following run the other day:

    Distance 12.75km,

    Moving time 1:11:29

    Pace: 5:36/km

     

    KM1: 4:20

    KM2: 4:17

    KM3: 4:04

    KM4: 3:50

    KM5: 3:39

    KM6: 3:35

    KM7: 4:40

    KM8: 4:12

    KM9: 3:55

    KM10: 4:29

    KM11: 4:30

    KM12: 4:46

    KM13: 4:22

     

    As you can see from this my pace / splits are way off....I have never run a KM in 3:35!!!

     

    I use Strava on my Android Phone, I do not have any other App on the phone, I have had no issues until December last year...

      

    0
    댓글 작업 고유 링크
  • I wouldn't mind so much if mine was telling me I'm faster than I really am, but it's always the opposite!

    I presume other people may have done so too, but FYI I raised a support ticket with Strava a week or so ago and ultimately got this response:

    "We appreciate your continued patience while our engineers actively work on resolving the issue. We are recording all reports we receive from our athletes about this so you can be assured that the bug has been logged and tracked.

    We hope to have this resolved soon but at this moment in time I cannot offer a timeframe for when the update will be released. Please check back on future application updates."

    0
    댓글 작업 고유 링크
  • @Martin Schwarz has posted the correct (temporary) solution.
    Here's a link to Martin's comment:
    https://support.strava.com/hc/en-us/community/posts/360048456012/comments/360009148771?mobile_site=true

    Strava needs to allow the users to choose between elapsed time vs actual running time.

    Here's more details on the same topic.

    https://support.strava.com/hc/en-us/community/posts/208848057-Let-users-specify-whether-moving-time-or-elapsed-time-is-relevant-to-that-activity?mobile_site=true&page=8#comments

    another article explaining this Strava "feature"

    https://medium.com/@meghanstevensonbooks/your-strava-pace-is-incorrect-db3a3b35cb54

    Hope this helps!

    0
    댓글 작업 고유 링크

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

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

새 게시물