Surge Free Run - not recording correct distance

[SunsetRunner]

I have completed the 5Kms parkrun for the last 10 saturdays and the distance recorded is nealry always 4.7kms.  How can it be so far out??

[SantiR]

@SunsetRunner Thanks for stopping by! For your tracker to be more accurate I will recommend to adjust your stride length. Also, perform a restart on your tracker. It should give you more accurate data afterwards. 

As another tip, check the dominant hand setting for increased accuracy!

Let me know how it goes! 

[SunsetRunner]

Thanks - I have my device set as non-dominant hand, do you think I should change it to dominant? 

I reset my device last week and this hasn't made any difference.

Also, I thought on Free Run it calculated distance using GPS, not number of strides?

[shipo]

---

@SunsetRunner wrote:

I have completed the 5Kms parkrun for the last 10 saturdays and the distance recorded is nealry always 4.7kms.  How can it be so far out??

---

Assumption: you have a Fitbit Surge.

If the above assumption is correct, setting your stride length won't do didly when you're in Free Run mode with GPS tracking enabled.

When I read your post I hear you saying you're running a measured and certified 5 kilometer course but your Surge is always reporting 4.7 kilometers.  Yes, no?

If the course isn't certified at the 5K distance, I'm inclined to believe the Surge over the alleged length of the course.

FWIW, while my Surge is definitely wrong on occasion, there is no way it is even wrong two out of ten times much less ten out of ten times.

[SunsetRunner]

Thanks for your reply. It is a certified Park Run that I complete each Saturday along with approx 300 other runners.  I have other friends that use different devices ie Garmin/Strava and their runs come up as 5kms. I don't mind the odd fluctuation on distance, but I'd have thought calculating 300 mts short all the time is a bit of an error??