help menu

Join us on the Community Forums!

  • Community Guidelines

    The Fitbit Community is a gathering place for real people who wish to exchange ideas, solutions, tips, techniques, and insight about the Fitbit products and services they love. By joining our Community, you agree to uphold these guidelines, so please take a moment to look them over.

  • Learn the Basics

    Check out our Frequently Asked Questions page for information on Community features, and tips to make the most of your time here.

  • Join the Community!

    Join an existing conversation, or start a new thread to ask your question. Creating your account is completely free, and takes about a minute.

Not finding your answer on the Community Forums?

Cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 

How are high and low pace statistics determined?

Replies are disabled for this topic. Start a new one or visit our Help Center.

‎05-23-2022 13:09

‎05-23-2022 13:09

I've been tracking my exercise walks (using "Run" so far because I only found out today how to get "Walk" onto the tracker's menu), and on the report screen for my most recent walk, under "PACE" I see the following:

 

Low pace   193'07" longest

High pace   26'58" best

Avg pace   19'30"

 

The average pace appears to be correct based on elapsed time and distance. But the low pace makes zero sense - I start and end the exercise while moving and never get as slow as about 0.31 MPH (which is what 193'07" works out to) while in the exercise. I went back through old walks, and ALL of them have a low pace of exactly 193'07", which is absurd.

 

The high pace is similarly nonsensical. It's not mathematically possible for my best pace to be slower than my average pace. This one does vary from walk to walk, but is almost always slower than the average. One of the times it wasn't, it was listed as 8'08" which I know can't be true as that's over 7.3 MPH, but even at max effort I can barely hit 6MPH due to foot and knee issues. If the sampling period is short enough, combining it with just the right GPS location errors might explain the 8'08", but not the ones where "best" is slower than average.

 

Searching the forums shows some folks having similar issues with the Charge 4, and I didn't see any answers on those posts.

Best Answer
4 REPLIES 4

‎06-29-2022 15:29

‎06-29-2022 15:29

Over a month and no replies here... This is actually also happening on my Versa (original). I get the same 193'07", even if I start and end before I stop moving. And same that my "high pace" is worse than my average which makes no sense. Would love to see this issue fixed.

Best Answer

‎06-30-2022 02:43 - edited ‎06-30-2022 02:45

In response to moosecat

‎06-30-2022 02:43 - edited ‎06-30-2022 02:45

I do running mostly and see the low pace problem on every exercise. I see the high pace problem occasionally.

 

The number 193'07' appears to be a default 'low' value put in the app by a Fitbit developer. If you change your units to km then it becomes 120'00" a nice round number. The low pace functionality is either broken, withdrawn or has never been implemented.

 

Having watched these forums for a while I don't have any expectation that Fitbit will fix this in the foreseeable future.

 

I think this is an app problem rather than a watch problem. Out of interest, are you seeing this on Android or iPhone? I am using a Versa 3 with Android.

 

https://community.fitbit.com/t5/Android-App/Low-pace-on-exercise-map-always-shows-120-or-193-minutes... 

Best Answer
0 Votes

‎06-30-2022 03:28

In response to James291

‎06-30-2022 03:28

I don't think even Fitbit knows what the low pace is. It makes no sense. I have never seen the "low pace". I believe it's the slowest pace so you have the lowest, average, and highest pace but the problem with the slowest pace is that it makes no sense at all. It's always (for km)  120'00" (with the word "longest" which confuses me even more). The colors on the map however just indicate green - faster than average, blue - slower than average pace.

Best Answer
0 Votes

‎06-30-2022 05:52

In response to t.parker

‎06-30-2022 05:52

I agree that giving a value for low pace is probably meaningless. Maybe there is a statistical way of calculating it after removing stationary periods. I don't know.

 

I do like the colours on the map indicating higher and lower paces, but I think Fitbit should remove the '120/193 longest' label because it's just plain confusing.

Best Answer