Pace/Split times seem to good to be true!

[UrbanCurbStompr]

I ran 6.8 miles on Sunday and my Fitbit calculated all my mile splits under 10 minutes each. This does not seem right to me as I usually slow down towards the end of my runs, not maintain pace. Any info?

[Rich_Laue]

@UrbanCurbStompr, you say that you ran 6.8 miles. Was this distance calculated by the Blaze, or do you know from another means that this is the true distance?

The pace is calculated off of tge distance that is calculated by the Blaze.

[UrbanCurbStompr]

I use my phone for GPS since the Blaze does not have its own GPS. I'm thinking it may also be the phone? But yes this is the true distance. Total time was said to be 1h3m ish.

[Rich_Laue]

Ok, then lets look at the mile points on the map, do they liok accurate? 

While the Blaze does not have it's own GPS, it is able to connect to your phones GPS while connected through bluetooth with your phone.

So yes you can start recording  the run from your wrist or from the Fitbit App, either way it will use the phones GPS.

[UrbanCurbStompr]

I agree and that is how I tracked this run. I also got an alert for every mile passed so it seemed accurate enough.? I have just never held a pace like that before, so I am not sure it was entirely accurate.

[Rich_Laue]

I'm at a loss as to what it might be, that is, unless your endurance and speed are being built up.

[UrbanCurbStompr]

These are my numbers from that day.

Lap Time Distance (miles) Pace  

Scroll Up

1	0:08:48	1.00	8'48"	0%
2	0:09:00	1.00	8'59"	17%
3	0:09:00	1.00	8'59"	17%
4	0:09:21	1.00	9'23"	54%
5	0:09:45	1.00	9'45"	88%
6	0:09:54	1.00	9'52"	100%
7	0:07:52	0.80	9'38"	78%

Scroll Down

Distance (miles) Pace  

Scroll Up

1	8'48"	0%
2	8'59"	17%
3	8'59"	17%
4	9'23"	54%
5	9'45"	88%
6	9'52"	100%
0.81	9'38"	78%

[AlejandraFitbit]

A warm welcome to the Community @UrbanCurbStompr and @Rich_Laue thanks for stopping by.

I just want to ask one question here, are you saying that your tracker is being accurate enough and want to make sure that the information that it registered is correct? 

Hope to hear from you soon. 

[UrbanCurbStompr]

Hello, what I am saying is that I have never kept a pace like that before. My first mile is usually in the mid 8s and usually my pace after that steadily declines from there on. The further I go the longer my pace becomes. So the fact that my miles consistently stayed under 10 makes mewonder if this run is accurate. I'm just trying to get everything dialed in. 😊

[DKH123]

Hi,

It's because the Blaze is innacurate, even when connected to GPS.  There are a lot of threads on here about it, but FItbit refuse to acknowledge the fault.  It appears when travelling east/west the data is out by about 20%.  North south is accurate.  

I ran on the weekend with the blaze on one arm and a garmin on the other.  Garmin said 12km, and Blaze said 14km.  The result is that the blaze thought I ran at about 4:00/km, rather than the real 4:40/km, which is why it appears your pace is so good.    

Other threads talking about the issue:  

https://community.fitbit.com/t5/Blaze/Blaze-Inaccurate-Distance-Even-W-GPS/td-p/1422134

https://community.fitbit.com/t5/Blaze/GPS-Inaccurate-after-Blaze-update/td-p/1911771

Fitbit's recommended solution is to reboot your mobile device which is absolute BS.  I imagine if they admit it is a problem, and they can't fix it with software, they will have to recall all devices, so I don't think theres any chance of getting assistance from them.  

[UrbanCurbStompr]

Thank you. My run was a South to North run on the beach which I know in South Florida we have issues with GPS the closer we get to the beach. 20% inaccuracy seems about right from what I see in my usual runs. I'll keep that in mind from here on out. Thank you all for your help.

-M