I "lost" calories overnight?

kaclever
kaclever Posts: 14 Member
edited November 2024 in Social Groups
Hi everyone,

I got my Zip a couple of days ago and am trying to figure everything out. :) I've read the stickies, but I still can't figure out what happened with my calorie total last night.

I have my activity level conservatively set to "sedentary." I'm trying to hit a 250 calorie/day deficit. I had the day off yesterday and didn't walk as much as usual, though I did take the dog for a stroll and do housework. I synced a ton throughout the day because, hey, it's a new toy. :)

MFP said I was over my calorie allotment by 117 when I synced everything right before going to bed last night at 11:00 PM. The Zip sat on the dresser all night.

This morning, when I logged in to MFP to close out yesterday's record, my 117 calorie overage had somehow turned into 300!

I'm confused. I didn't even have the negative adjustments enabled, and anyway, how much activity could FB expect me to do between 11:00 and midnight?

These kind of calculations are not my strong suit, so I appreciate any insight anyone can provide. :) Thanks!

Replies

  • editorgrrl
    editorgrrl Posts: 7,060 Member
    If you disable negative calorie adjustments, then you'll never eat at a true deficit on days you burn fewer calories than your activity level. Enable them! http://www.myfitnesspal.com/account/diary_settings

    My adjustments got better & better, as if MFP was "learning" my routine. Give it a week or so.
  • kaclever
    kaclever Posts: 14 Member
    Okay, thanks! I did go enable the negative adjustments this morning. I'll try to just let it be for a few days and see how smart the algorithms are. It doesn't surprise me that they are probably smarter than I am.
  • editorgrrl
    editorgrrl Posts: 7,060 Member
    You can click on any adjustment to see the math MFP used to calculate it.
  • heybales
    heybales Posts: 18,842 Member
    Read the 2nd half of the FAQ in the stickies as to how those calories for end of day are calculated - it may or may not be Fitbit's estimate that is off - depends on another option you may have enabled.
This discussion has been closed.