Thank you!! I am 6' tall and have extremely long legs (38" inseam), so I have been having some definite issues with my fitbit's accuracy. So nice to have the math done for me!

Marking for later. Definitely need to do this, since my Fitbit told me I walked nearly 6 miles one morning when it was actually only 4.

I am having the same problem.

Ran 1.8 miles this morning. Burned 181 calories according to iFit Live.
Fitbit had me running 2.13 miles and burning 247 calories.

I spent all week doing this, lol! This was after the fitbit told me I walked 50 miles in one week...I knew something had to be wrong.I couldn't find a place where it said what the "default" stride was so I just went to the old H.S. track behind my house for three nights in a row and, using the timer on the FitBit, timed a walking mile. The first "mile" calculated at 1.5 miles with the default value. I finally got my stride correct at 27.1" and now the mile is .99. Those fitbit badges will actually mean something now.

Did you just keep updating it on your Fitbit profile until you found the number that matched? I callibrated on my treadmill last night, and that clearly was a flop! I will head out to the track tomorrow to test it out!

Thanks for the link! I'll have to calibrate mine soon too...

Sorry for the double post!

Thanks for this info! I'll have to do this soon and make mine is accurate

I didn't actually count my steps as I walked/jogged. I let the fitbit count them for me. It is usually spot on for the actual counting of steps while you are walking and running. I wrote down the start count and the stop count for each one (walking and running) on a piece of paper as I started and stopped each exercise.

Another good point. I didn't count or write down my steps either. I used the fitbit timer to do that for me so I could just do the workout and I did the calibration at home. When you use the timer, it creates an activity record that you can later view on your fitbit account under "activity log". That activity record contains the fitbit data on what you did in that time, it includes: the start time, duration, total steps, total floors, distance the fitbit detected, calorie burn estimate, and average pace. It also has a minute by minute breakdown of the calories per minute, steps per minute, floors per minute, and speed and pace per minute.

In this case, I just use the step count the fitbit gives me since that is what I want to calibrate. In the future I want a walk with that number of steps to match the actual distance covered. Or a run with that number of steps to match the actual distance covered. The ting to be careful of is to not add extra steps to it so be careful to not start until the timer is going and to stop until after the timer is off (though a few extra steps probably won't matter too much, but on flat ground it is easy enough to avoid adding them).

I suppose counting them is a good mental memory exercise and can be a way to test how well the fitbit picks up on your actual steps. But for this purpose even if it is wrong, the fitbit steps are the number you want to use assuming you are wearing your fibit the same way as you usually do during a walking or running workout.

There are of course a few ways to do this. But just saying it doesn't have to be a memory and math workout unless you want it to be. I find it easier to focus on the physical part at the track, then do the math when I get home. :-)

I have to recalibrate my fitbit too when I realised that the steps are inaccurate.

The default stride length does not apply to me.

After experimenting, I realised that the type of shoes you wear also affect your stride length. High heel shoes tend to throw the fitbit off. So I average the stride length after trying out different pair of shoes.

I also find out that the placement of the fitbit also affect how fitbit count the steps. When I put the fitbit on my upper body (bra or pocket), it gives the most accurate count. If it is pockets in your pants/dress, a deep pocket may throw your fitbit slightly off. If you put your fitbit in your bag, it is preferable to put it in a bag where you can carry by your shoulder and not hand carry the bag. If you hand carry your bag with your fitbit, the 'swing' in the bag when you walk tends to throw fitbit off, especially when it comes to counting of stairs.

And lastly - just a speculation why the fitbit default stride length did not work for me. For my height and weight, I have very small feet - size 4. The average shoe size for my height/weight is 6-7. So my stride length is shorter than most people my height/weight.

Stupid question... I'm going to do this tomorrow as I have noticed that my miles are way off compared to GPS. When changing the settings, it wants feet and inches (similar to height). Are you converting the inches to feet and inches or just simply entering the total inches in the inches spot? Told you it was a stupid question.

Thanks!

Great info!

I initially entered a stride length too short. I'm 4'11" tall. I just calculated some adjustments, using the formula
.413 x 59 inches = 28 inches, or 2'4" stride length.

I thought WOW, that's a huge change from what I'd been using. But then I paced it out, divided distance by # of steps, and lo and behold, I got 2'3". But, truthfully this is my "southern/leisurely pace", such as when I walk during the day in the office, I'm just sauntering about at this slower pace.

When I walk alone with intent to get someplace, I use my "NYC pace" which is a faster, longer stride. I paced this out out, again divided distance by # of steps, and got a 2'9" stride length.

Looking ahead, I expect FitBit will tell me I'm doing fewer steps, but expect the distance may increase due to the stride length. I think.

I'm going to adjust my walking stride to 2'4", and my "running" to 2'9" since when I "run" I'm basically in race-walking mode, with an occasional jog for a few minutes tossed in here and there.

It sounds logical to me, so we'll see how it goes.

Gerry

I initially entered a stride length too short. I'm 4'11" tall. I just calculated some adjustments, using the formula
.413 x 59 inches = 28 inches, or 2'4" stride length.

I thought WOW, that's a huge change from what I'd been using. But then I paced it out, divided distance by # of steps, and lo and behold, I got 2'3". But, truthfully this is my "southern/leisurely pace", such as when I walk during the day in the office, I'm just sauntering about at this slower pace.

When I walk alone with intent to get someplace, I use my "NYC pace" which is a faster, longer stride. I paced this out out, again divided distance by # of steps, and got a 2'9" stride length.

Looking ahead, I expect FitBit will tell me I'm doing fewer steps, but expect the distance may increase due to the stride length. I think.

I'm going to adjust my walking stride to 2'4", and my "running" to 2'9" since when I "run" I'm basically in race-walking mode, with an occasional jog for a few minutes tossed in here and there.

It sounds logical to me, so we'll see how it goes.

Gerry

.413 x 59 = 24.367 not 28 btw

m0ll3pprz wrote: »

Bump. For future use

There is a much better method in the FAQ for the group if you have access to a treadmill, plus some comments on the pace that should be used for all day best estimate, not just during a 1 hr workout say.

I had to adjust my stride as well. I am 5'7" and my stride was much more than the defaults. Since adjusting my numbers have been right on and I have started losing.