Tracking the trackers: Garmin, Fitbit, Runkeeper, Moves

(Update: Scroll to the bottom for more results)  I have long been mad for tracking pretty much anything, so when I started jogging, it was quite obvious I would be tracking my runs as well. I started with Moves ( an iOS/Android app that tracks your steps all day long, but also can recognise running and cycling. Later on, I added RunKeeper ( which allowed me to schedule runs and set goals.

This January I was… upgraded with a Fitbit Force (, a wristband tracker with tracks steps, climbs, calories (through a calculation) and also your sleep. Finally, this week I’ve reached a final (?) level by getting a Garmin Forerunner 210 (, GPS watch that also connects with a heart rate monitor.

So today was the first time I used the Garmin. After getting the Fitbit Force I was only paying attention to the numbers it was giving me, ignoring the other apps. Since Fitbit is a dedicated tracker I never questioned if it would be better than an iOS app. Today though it struck to do a comparison between all three methods: Garmin, Fitbit and iOS apps.

Without further bubbling these are the results (Moves data gathered via Moves Export (

I’m mainly surprised by two things: Fitbit getting the distance wrong and Moves getting the calories quite right. Garmin is for sure the best way to calculate the calories since it takes into account the heart rate. It’s also interesting to note the big difference in the step count between Fitbit and Moves.

Here is also a comparison between the pace charts (Moves doesn’t track pace)

Here Garmin really shines by providing more accuracy while RunKeeper and Fitbit just round up numbers.

In conclusion, if you’re not into tracking your heart rate and improving your calorie burn though that, the free Moves app might be just fine for you. Fitbit might seem like a waste of money there, but it has other benefits like tracking your sleep and also doing a good job calculating how much calorie intake to do depending on your activity during the day. Of course this was only the first test, so (as all good reports note) more research is required. :)

If you have any experience with similar comparisons, drop them in the comments!

Update 14/4: Here are two more comparisons

On this one, RunKeeper got the calories right and Fitbit and Moves were way off

RunKeeper and Fitbit were close but Moves was again off on the calories count

So, my enthusiasm for Moves seemed to be premature. Will come back in a few days with more data :)

Update 23/4: Probably the final update, two more comparisons, with the addition of Strava.

This includes Strava, which was also running and recording at the same time as the other apps

Here RunKeeper and Strava did not record anything, but instead the Garmin data was imported.

In the last one, there was a glitch in Garmin’s data and the last point was marked way off the actual position. Apparently, RunKeeper ignores that total distance recorded in the Garmin file and just calculated the distance on it’s own.

Conclusion: Each device/app will use it’s own algorithms to record data and calculate pace and calories. Even when you supposedly use the same base data, the end result is different. So, before you go crazy comparing stuff (like I did :), you might be better off to chose method and monitor your status.

Tags: , , , , , ,