Discrepancies in distance with runs

[MellieAnne]

I've been having a recent issue (maybe for the past couple months, not before that though) where I'm getting 2 different distances for runs. See below: 

The correct distance should be the higher number (3.15) which is what I see on my watch, but for some reason it syncs to the app with the lower number. And even more confusing is that both are displayed in the activity section on fitbit. I looked back at my runs from a couple months back and there wasn't a discrepancy at all...both numbers were always the same.

[lmartin72]

I reached out to fitbit support due to the same issue with my Versa. I use 2 apps, fitbit, along with another on my phone and they display significantly different distances. I know how far I am going, and for a 3.5 mile run as an example, fitbit only shows about 2.7. What I learned today was that the connected GPS is not used to measure the distance. fitbit ONLY uses your step count and the stride length you've entered to calculate distance. Not good in my opinion. This means I can't rely on fitbit to give an accurate measure of the distance ran. Hopefully, this will generate some updates to the fitbit app, and the fact that it is connected to the GPS on your device to provide a consistently measured, accurate distance. Apparently the only value of the connected GPS is to see the route you covered on a map. I'll keep using my other app as it has been reliable in recording GPS based distance. 

[MellieAnne]

Thanks! What's most annoying honestly is that when I glance at the Versa itself during the run, the higher number is what shows, so I'll stop the run at 3.15mi...BUT when it eventually syncs to the app, a lower number is what seems to take. It used to be much more reliable I feel like...after one update or another, the accuracy hasn't been the same for me. I sync to Strava and have been relying on the "correct distance" feature which luckily adjusts it to the correct number, but its annoying to do each time.

[JoanaEsteves]

I have the same problem on my ionic.

Every time I run more than 10km.

When my watch reflected the 10km, I stop. The resume of the race shows 10km, however when I export the run to my app, it shows two different distances. In the main menu appear 10km but when i open the details shows 9,88km on the top but in map is still 10km.

Do you have your problem solved?

Thank you

[MellieAnne]

Thanks! Sounds like the same thing that's happening with mine (different numbers on the map and in the details). Unfortunately I haven't figured out a fix yet. My last run was 2.33mi, but is synced as 2.28mi. Not a huge difference but I don't understand why there's one at all. I'm even having issues where it looks like it completely stops tracking me for a second various times throughout the run (e.g it'll have my pace at 8'00" or something and then all of a sudden it drops to 23'00" and then back up, as if I had stopped)...this happened a few times in my last run which sucks because it effects the overall average. I never had any issues with my versa until recently so its a shame 😞 

[lmartin72]

I've noticed this also. It seems like the connectivity between the fitbit and my phone drops, which doesn't really make sense either, since it's through Bluetooth and well within the range of the signal.