I Ate 500 More Calories in the Heat — And Still Lost Weight. Here's Why.

It's been 100°F in Philadelphia. The humidity has been brutal.

Same training. Same mileage. But this week I ate +12.5% more calories than last week... and still lost weight (-0.7 lbs avg).

Here's the data:

• Calories Consumed (avg/day): 4,055 → 4,561 (+12.5%)

• Calories Burned (avg/day): 4,035 → 4,316 (+7.0%)

• Body Weight (avg): 158.7 lbs → 158.0 lbs (-0.7 lbs)

More fuel in. More burn out. Weight still dropped.

Heat doesn't just make runs feel harder — it changes your metabolic demand. Your body burns more energy regulating core temp: sweating, elevated heart rate, blood flow to the skin to cool down. At the same time, heat drives appetite and fluid/electrolyte replacement up, so you eat more without trying to.

The problem is these two things don't move at the same rate. My burn went up 7%. My intake went up 12.5%. And I still lost weight. That gap is the story.

A fixed daily calorie number assumes every day carries the same demand. It doesn't. Heat, mileage, terrain, life stress — they all shift what your body needs in real time. Force a static number into a week like this, and you show up underfueled, recover worse, and leave fitness on the table.

One more thing worth understanding: a big drop on the scale is not automatically a win. Sometimes that's depletion — real body fat doesn't disappear overnight. A big jump on the scale after a huge re-feed is the actual win: glycogen refilling, hydration restored, body ready to train hard again. Getting this backwards is what wrecks people mentally mid-training block.

You don't fuel to a number. You fuel to the demand.

Want a coaching system built around your real data, not a generic number? [Link to consult/Base Camp]