Surge GPS inaccurate

[Rob2017]

Just repeated a run that I did in August. In August it was 6.75 miles tonight it is 6.0miles. all the mile points are in totally different places as well. What is going on?? That is a big error.

[YojanaFitbit]

Hi @Rob2017 thanks a million for posting your question here. Welcome! 

That's a really good question. If fact, your Surge uses GPS to get more accurate information. It is very interesting that the mile points are in different places. Why don't you restart it and give it a try one more time to see how it goes? Just remember to check the start time and end time, since once in a while the satellite takes a moment to connect with your Surge. Read some tips about it this post. 

Whereas GPS gives you a more accurate measure of distance than step counting alone, the actual accuracy depends on both your environment and the weather. You can read more information about accuracy in this help article: How accurate is GPS?

Now, when you're not using the GPS on your Surge, it takes the distance taking in count your steps and your stride length information. You can edit this information if you wish, you will find instructions here: How do I measure and adjust stride length for my Fitbit device? 

If this is not working as mentioned before you can try to restart your Fitbit in case that this is cause for something internal on the tracker itself.

Let me know if you have any other question! 

[Rob2017]

Thank you. According to Google maps the correct distance for the run is about 6.8 miles which tallies with the first recorded run. Don't know why  it only measured 6 the second time. I'll try restarting but won't be doing that particular run again for a while so won't be able to check.

[YojanaFitbit · Accepted solution]

Thanks for getting back @Rob2017.

I understand your point, and you're right it will very difficult to test your Fitbit as you don't do this particular run often. But thanks a million for the trying the suggested steps. Hopefully, you won't have more issues with future runs. In case that the issue persist, please keep me posted.

I'll be around.