Can Fitbit do basic math?

[Tresy]

Look at this readout from yesterday’s jog. I’m sorry, but running 3km in 20 minutes does not work out to 32+ minutes per km. To put it mildly. This math illiteracy is pretty astounding. Am I the only one who is experiencing it? When is it going to be fixed?

[vincentml]

I'm seeing the same, on my "walk" this morning, 5.03 Km in 29 minutes is apparently 10.31 min/km !

I say walk because despite setting exercise to run, fitbit records it as a walk, a bug reported 6 months ago that isn't fixed although the community post is marked as solved because apparently acknowledging it's broken counts as Solved. 

Don't expect a solution anytime soon as Google continues to run fitbit into the ground but i'm sure this topic will soon get "solved" !

[mikey_pdx]

I track my rec soccer games as "Run". Last one was 3.38 miles in 77 minutes, saying my average pace was 45'03"/mi, which sounds like the same problem you're describing - should be more like 22'48"/mile. 

However, I looked at my Run settings on the device and I had forgotten I had set laps at 2 minutes to show someone else it could be done. Since I failed to clear that setting, it shows 38 laps and some of them are at a 200-minute pace (presumably when I was standing on the sideline while subbed off), so maybe it's averaging those (I didn't go through and do the math). 

The game before, I hadn't messed with the lap settings, so it broke the laps down by mile as usual and it actually makes more sense - 2.94 miles in 79 minutes, saying 26'48"/mi. 

[Tresy]

I frankly don’t even know where I’d set a 2 minute lap, but this problem is erratic: some runs are accurately recorded and others aren’t.
A theory I’m entertaining is that walk auto-detect is kicking in either before or after my run and getting appended to the run data, destroying the average pace figure for my run. This problem is intermittent, so presumably there’s a variable that is not being captured. That might be it. 
Even if there’s an “explanation,” there’s no excuse for summary stats that explicitly report nonsense like 30/5=17.