This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Calorie counts seriously off

Hi, I use my Garmin Forerunner 220 for all outdoor activities, running and cycling. When running, it calculates calories burned pretty accurately. When cycling, however, it wildly overestimates the calories burned. I have to go to my computer, open up the activity, zero out the calories, then tab around the different fields and a new, vastly different calorie count will appear.

Example 1: The activity title "Richmond," a 64-mile bike ride. https://connect.garmin.com/modern/activity/1175461511

When I import it from my Forerunner 220, it displays a calories burned number of 8,419. When I open the activity on the computer, zero out the calories, and tab to another field, the calories burned number changes to 3,688 -- less than half the original number.

Example 2: The activity titled "Williamsburg," a 66-mlle ride in the other direction. https://connect.garmin.com/modern/activity/1174276029

When I import it from my Forerunner 220, it displays a calories burned number of 8,720. When I open the activity on the computer, zero out the calories, and tab to another field, the calories burned number changes to 3,682 -- again less than half the original number.

Why are the calories estimates so far off? Thanks.
  • Are you using a heart rate monitor? If not that probably explains it. The watches come up with crazy calorie counts without one in my experience. Interesting if Connect is using a different algorithm though. It sounds reasonable too.....usually get at most half the calories per mile on a bike than for running.......
  • Calorie count off

    Hi, no, I'm cheap. No heart rate monitor connected. It just calculates based on the workout and my weight, I guess. Perhaps the watch calculations are set by default at running, and the website knows the difference between running and cycling.


    Are you using a heart rate monitor? If not that probably explains it. The watches come up with crazy calorie counts without one in my experience. Interesting if Connect is using a different algorithm though. It sounds reasonable too.....usually get at most half the calories per mile on a bike than for running.......