Distance discrepancy between Fitbit and Strava

[kaisaannikki]

I simultaneously track my runs on my Blaze and the Strava app, because the latter gives more detailed info. However, I've noticed that there is a significant discrepancy in the distance measured every time. This strikes me as odd because both trackers use the same GPS on my phone.

I create my running routes on the Strava app to fit a specific distance I want to run (so I have 5k, 10k, 20k routes etc. ready-made). I look at the maps in quite a lot of detail and think the distances on the Strava map are accurate. However, my Blaze always gives a much lower distance, which is getting a bit annoying. For example, this morning I did a 5.2km route, which I had created online looking at the map. The Strava app gave me exactly this distance. Meanwhile, my Fitbit app says I only ran 3.9km (!), much lower. When I look at the map automatically created in the Fitbit app, the route looks exactly the same, but somehow a whole kilometre has been lost somewhere. My running pace is also registered as much slower. 

Can anyone explain why this discrepancy occurs and if there is anything I could do to fix it? I don't know which app is more accurate, but I feel like the Strava routes should be, because I have created them while measuring distances on a map. 

Moderator edit: Updated subject for clarity

[FerdinandFitbit]

Hi there @kaisaannikki, great to see you in the Community Forums! 🙂

I'm sorry to hear that Fitbit seems not to be keeping an accurate track of your distance. I'm not really sure what could be causing this but I'd like to help you out!

Now, I'd like to know, when you're going out for a run, do you take your phone with you or do you only measure it with your Blaze? Also, I'm not completely familiar with Strava, but just to make sure, this means that you create your run routes with Strava and then go out for the run and the distance that Fitbit tracks is different or do you also take your phone to measure the activity from Strava at the same time that you track it with Fitbit?

When it comes to distance tracking, your Blaze will determine your distance based on your stride length (both for running and walking) so for routine tracking, that should work. Now, for more accurate distance tracking when running or walking, you can use MobileRun, which will use your phone GPS to give you a more accurate distance (you can do this from the Fitbit app by going to the Exercise tile, tap on the stop watch at the top right corner and then make sure you're on the Track tab and then choose either walk, run or hike and start the activity from your phone).

Also, you can do this from your tracker  by going to the exercise shortcuts. Then choose Run and wait for your tracker to connect to your phone. Once it says it's connected, you can start your run and as long as your tracker keeps connected to your phone, the distance tracking should be more accurate.

Hope you find this helpful  and anything else you may need, I'm here to help!

[kaisaannikki]

Hi Ferdin,

thanks for the response. 

When I run I simultaneously measure it with Blaze and my phone/Strava app. I always carry my phone with me since it has GPS and I need it to listen to music. I also get more accurate running data on from my phone via Strava. Blaze hasn't been that good with running so I mainly just use it to get an idea of my heartbeat now, but it would be nice if it could be a bit more accurate. 

I always use the Run function on exercise shortcuts on my Blaze (just as you described), and it seems wildly inaccurate every time. I haven't used the Mobile Run function though. Is it possible it would be more accurate than tracking through the shortcut, or is it the same? 

[FerdinandFitbit]

Thanks for getting back @kaisaannikki! 🙂

In theory, Mobile Run and tracking your exercise from the exercise shortcuts on your Blaze while making sure it's connected to your phone should be virtually the same thing. Now, just as a test, you could track your run just using Mobile Run and see if there's any difference doing it that way.

If you get to test it, please, let me know how it goes!

[Shelthomas1]

I have this same issue. I always take my phone, I turn on the app and select run from the watch. Fitbit is way short on distance. 

Shel 

[Skipper1995]

Hi - also noticing this discrepancie with my fitbit versa. Any route i take is 15-20% short of the actual distance. Haven't tried this mobilerun feature but given my phone too is being inaccurate with gps im unable to get accurate real time data. Waste of £200.

[GGxGG]

Came here for the same question and am disappointed that fitbit still hasn’t provided an answer.... I am using Strava and a Charge 2 HR Fitbit.

[howlandster]

Fitbit stopped supporting heart rate reporting with MobileRun at the end of July. They seem really focused on delivering subpar, overpriced products.

[nonstopchops]

I am having the same issue with the Versa and it’s a pretty severe discrepancy! Today I ran a marathon (26.2 miles) and I know that’s the accurate distance. I tracked it on strava and was told I ran a 8’43” pace. I also tracked the Tun using the exercise shortcut on my versa (I wanted heart rate data which is why I tracked it on both) ... and my versa tells me I only ran 24.5 miles at a 9’38” pace. Is there a fix yet?

[Tbrisk]

I’m also having the same issue.  Logged a bike ride in Strava and selected bike ride in my FB Charge 2 yesterday.  Brought my phone with me for the entire ride and was connected to GPS and Bluetooth to the charge 2.   The map for each ride is identical but the Strava distance is 16.8 miles while the FB distance is 14.8 miles.  I really like the HR, calorie, and distance/speed info on my wrist but will likely be moving away from for FitBit towards another HR platform unless this is fixed soon.  The discrepancy is just too big.  

FitBit, please provide a fix for this soon as I use the distances for specific training info and planning. 

[TwinkleStarr]

I've been having the same problem for about 6 weeks. Today I did a 5 k park run and my fitbit blaze says I ran 3.9k. Others have had the same problem . Previously it was recorded at 5 k. My fitness levels have apparently plummeted. If I go out and do a casual run , I have no idea how far i'm running with fitbit. Very fustrating

[Rubensdm]

Same here, using fitbit integrated with strava... When using only strava, 20% dfifrence for runs, less for bike.. And it started out of nowhere the last month or so, I used to run the same route sometime ago with no problem 

[huttjames]

Having exactly the same problem when I start runs on my Charge HR3. Started a couple of months ago and doesn't seem to be caused by battery saving modes on my phone. Please solve this Fitbit! 

[AndEd]

This is ridiculous! Distance is 20% off on average. Ask FB to create a simple algorithm to tally the distance with Google Maps when using GPS. Now that Google bought FB this should be a straightforward solution.

My best!

[StuMackin]

Having same issue - using strava on phone and the (exercise --- run) function on versa watch. Versa is under reporting distance on 5k park runs and showing slower pace.

The GPS on my phone is being used by the watch as I can see a map of the route i took in the dashboard. 
Are you saying the watch is calculating distance by steps x stride length and disregarding the GPS data? 

[Jell6]

Same here, Fitbit Versa 2, Strava  today  4.06km @ 6.52.

Fitbit  3.48km @ 8.15!!!!

I previously had a versa lite that was more or less in sync with Strava.

I am choosing to ignore it, use my Strava app as usual,  and use the Fitbit for it's other functions.  I can't use Garmin  as they are too huge:(

[AndEd]

Hi, actually is the opposite. When the GPS is on the watch, the steps x distance is disregarded and the distance will be wrong as discussed. So, to get the distance correct, you have to run with the GPS off and make sure you stride x steps gives you the correct distance. I  increased substantially my stride length manually to make sure I get the correct total distance during my runs. However, I will not get the map in the Fitbit app since GPS is off, but my speed and average heart rate will be ok.

I parallel  I activate the Strava app during my runs.  Once my runs are completed Strava should take the heart rate measurements from the watch and the GPS distance should be accurate from its own calculation. In the end, all the correct data should be in the Strava.

[Jell6]

Thanks for the reply,  I  can't even get  Fitbit to connect to Strava,  it won't accept the authorization.  Grrr!

[Benlg81]

I'm also getting discrepancies which seem to be getting worse. Always run with watch connected to phone gps and still under state my runs compared to strava and also from measuring the route in a car 

Have fitbit solved this yet 

[rsvrmillie]

I have the same problem but use endomondo on my phone o track the distance and  show the route I took I have done 10k's half marathaon's and a few marathons all accurately measured out courses and the fitbit is always short on the distance like others I am mainly using it for heart rate now and keeping my phone with me for the accurate measurement 

Gav