05-18-2018
21:00
- last edited on
05-24-2018
06:33
by
FerdinandFitbit
05-18-2018
21:00
- last edited on
05-24-2018
06:33
by
FerdinandFitbit
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
08-05-2020 16:11 - edited 08-05-2020 16:12
08-05-2020 16:11 - edited 08-05-2020 16:12
Fitbit Ionic also does this. I went in and change my stride thinking it would help. It didn't. It has stopped synching with strava after a Fitbit update so I started using Strava on the phone as a backup and Fitbit had my pace two minutes slower and was off by 2.4 miles on what Strava registered as an 8.7 mile run. That's a big discrepancy. I did part of the route in the car and there is a turn at .85 miles. Fitbit had it at .69. It's frustrating when you are training for a race and cannot get past an 11 minute mile and then do the same pace at a race and get a 9.30 mile. At least it makes you work harder!
08-05-2020 16:21
08-05-2020 16:21
Yeah, Im pretty sure I'm going to move away from Fitbit and start using an Apple watch. I'm on my third watch anyway. Mainly because the **ahem** things only work for a year, then they have to be replaced.
01-16-2021 10:24
01-16-2021 10:24
That’s funny my discrepancy is the opposite my Fitbit says I go at least a half mile further than my Strava. Time is also off by about a minute I feel like that’s a large discrepancy.
01-20-2021 18:48
01-20-2021 18:48
I recently noticed this on my Versa 3. I had taken about a month and a half off running and got back to running 4x a week. It was logging as 11 minute mile sometimes more. I was previously at 9:30. So I began using Strava because I didn’t think I lost that much fitness and iStravs was tracking at 9:45-10 minute mile. Which is much closer to the pace I felt, it also tracks longer mileage on Strava. I just got this Versa and am disappointed that it is not accurate. I used to be very loyal to Fitbit products and have been using them for years. Now I’m not sure I will continue. I will be tracking my runs on Strava now.
01-20-2021 19:44
01-20-2021 19:44
I have Ionic, with it's own onboard GPS. I've been doing the reset ritual before running, almost as a rule. Something I noticed, is with the latest Fitbit app update, the exercise/run reporting no longer displays minutes and seconds. It rounds up to the next minute. With that alone, it's harder to note time discrepancies. I've also noticed that my Strava seems to record (data ported over from Fitbit) virtually the same distance, but the time is noticeably less. F/I, if my Ionic reported 3.1 miles and 1:00:00, when it ports to the Fitbit app it displays 3.11 miles and 1h:1m. Then, when it ports to Strava, it's 3.1 mi and 58m:18s. Yes, it was a walk, but the numbers between the Fitbit watch, the Fitbit app and Strava are still 3 different things. It's frustrating. I don't know how good or bad it would be if I didn't reset everything before each run, and I don't independently track my runs on Strava simultaneously as Fitbit. I didn't consider my phone's GPS to be very accurate. A while back I walked a 10K. Ionic reported 6.21mi @2h:15m:59s. Fitbit app reported 6.1mi@ 2h:30m. Strava reported 6.1mi @ 2h:06m:12s. The distances were not tight, across the board and the times were all over the place. It's frustrating! Something's really amiss somewhere, Fitbit!
01-21-2021 17:02
01-21-2021 17:02
01-22-2021 08:42
01-22-2021 08:42
I'm not ready to upgrade to a pay account, if Fitbit can't perform accurately on a free account. Disregarding Strava for a minute, the Ionic tracker (watch with built in GPS) is reporting differently than the Fitbit app. That's all in-house, to Fitbit, and doesn't reflect well on them.
01-22-2021 08:57
01-22-2021 08:57
I have the ionic too. I noticed a lot of difference over the first lockdown in March. Strava and fitbit were a bit off. Last few months though its been much more accurate and I dont pay for premium account. Its still not 100% though. I have to say, I think ill be converting to Garmin later in the year...
01-23-2021
00:16
- last edited on
07-01-2021
11:05
by
DavideFitbit
01-23-2021
00:16
- last edited on
07-01-2021
11:05
by
DavideFitbit
I also recently began the free trial, and the stats between Fitbit and Strava are now pretty close. It never occurred to me that there might be a connection. I need to check my recent runs to see if that is part of the issue.
---------------------------------------------------
If Garmin weren't so cheap looking, but not cheap I would consider one.
Also they are big. I did see a similar looking one to the Versa, but the reviews weren't good.
01-23-2021 08:30
01-23-2021 08:30
Fitbit upgrade or Strava upgrade?
01-27-2021 16:36
01-27-2021 16:36
I too have the same problem with Strava and my Charge 3.
The charge 3 (connected to my phone’s GPS) consistently records further distance (and therefore better pace) than Strava on the same phone, for the same run.
I often run with my children who track just on Strava and our distances according to Strava (across 3 different phones) are never more than 0.1KM out over a 5K run. But the Fitbit records at least 0.5K more.
it’s very frustrating and I’ve switched to tracking just on Strava
02-05-2021 03:42
02-05-2021 03:42
Same issue as previous commenters. Did 10 km. Strava 10.5 km Versa 3 10 km. How this can be fixed?
02-05-2021 04:07
02-05-2021 04:07
If I've read this thread correctly (and there's a fair amount to read), most people have the situation where Strava is logging more distance than their Fitbit device, whereas I consistently have the opposite problem. Over a 5KM run my Fitbit Charge 3 is normally records at least 1/2K more - Am I alone in this or do others have the same issue? - It's really frustrating as I like getting the heart rate data from Fitbit into my runs but have had to stop due to the inaccuracy.
04-23-2021 05:52
04-23-2021 05:52
It’s a bit discouraging to see that after three years, Fitbit still hasn’t been able to resolve this issue, and it’s happened across pretty much all of the Fitbit models. I have the same problem with my Versa 3. Just this morning I went for a run and Strava recorded it as 2.71 miles (10:17/mi), while my Versa 3 told me I only ran 2.45 miles, at a rate of 11:26/mi. Strava used the GPS on my phone, while my Versa 3 used its own built in GPS. Both were with me the entire time. I shouldn’t have to depend on a separate *free* app to give me a more accurate picture of my run, after spending several hundred dollars for a device whose sole job is to do just that.
04-26-2021 06:47
04-26-2021 06:47
It is discouraging, but I've found the GPS on my Ionic to be more accurate than my phone using Strava. I go through pains to get Fitbit data to align with Strava, uploading the former to the latter, and it's close but never perfect.
04-26-2021 07:00
04-26-2021 07:00
I gave up and ended up using a Galaxy watch active that came with a phone upgrade. Admittedly I prefer the Fitbit app and accessories, but the Galaxy watch active is consistently accurate so far less angst.
06-22-2021 06:06
06-22-2021 06:06
I'm having the same issue between Strava and bike rides recorded on Fitbit Charge 4 watch. Did a 20.05km ride today, showing up on Fitbit app as 18.85km.
10-20-2021 09:06
10-20-2021 09:06
I am having the same problem. i just bough a charge 4 and its measuring around 15-20% short on distance, it is also off on time, I think its a bit much to have to pay for premium to get accurate measurements, its as if they are deliberately giving us false info to try to get us to subscribe