We are pleased to announce that on March 4, 2025, an updated Rich Text Editor will be introduced in the MyFitnessPal Community. To learn more about the upcoming changes, please click here. We look forward to sharing this new feature with you!

Polar HRM and polar personal trainer webside

nymphis
nymphis Posts: 59 Member
edited November 2024 in Fitness and Exercise
I have recently received a polar ft7 for my birthday. I started using it along with the polarpersonaltrainer.com. I noticed yesterday when I manually added my data onto the website that the number of calories burnt was different than my watch. My data was as follows:

Duration: 59.13 mins
Calories: 639
Avg: 170
Maximum: 191

According to polarpersonaltrainer website the calories burnt would have been 939. My question is who is wrong? I safely assume it's the website, but why such discrepancy between figures?

Replies

  • PriceK01
    PriceK01 Posts: 834 Member
    I know this post is really old, but was wondering if anyone else is having the same issue and/or knows the answer?
  • jaz050465
    jaz050465 Posts: 3,508 Member
    Sorry- cant help. Maybe you should contact Polar.
  • AllonsYtotheTardis
    AllonsYtotheTardis Posts: 16,947 Member
    I would contact them... I have the flowlink for my FT7, so it down loads all the data for me (all I have to manually enter is my kilometres...) I haven't noticed any issues with the data not matching the watch
  • EvgeniZyntx
    EvgeniZyntx Posts: 24,208 Member
    Check profile: weight and gender.
  • PriceK01
    PriceK01 Posts: 834 Member
    Check profile: weight and gender.

    Thank you! While height, weight, and gender all matched up between FT4 and PPT, other settings did not. RHR, MHR, and aerobic/anearobic thresholds did not.
  • PriceK01
    PriceK01 Posts: 834 Member
    Nope, that didn't change it. All settings are identical, yet PPT still tries to autocomplete calories burned with a different number than I get from the FT4. Not a big deal, but it can be changed to my number, but still curious.
This discussion has been closed.