Running Calories Calculator

Two runners cover the same 10 km at the same pace and burn measurably different amounts of energy. Body mass is the reason. Running costs roughly one kilocalorie per kilogram per kilometre, so a 90 kg runner spends about 50% more than a 60 kg runner over identical ground. That single relationship explains most of the variation between people, and it is why a calorie figure quoted without a body weight attached is close to meaningless.

This calculator works from MET values, the standard measure of how much energy an activity costs relative to sitting still. Running at 10 km/h sits around 10 METs; at 14 km/h it is closer to 15. Multiply the MET value by your body weight and the time you spent running and you have an estimate grounded in published research rather than a proprietary guess.

Your watch will usually disagree, and often by a lot. Wrist-based devices infer energy expenditure from heart rate, and heart rate drifts upward through a long run as you dehydrate and warm up, even when your pace and effort have not changed. That drift gets read as extra work. Neither figure is the truth; both are estimates. The one that helps you is whichever you use consistently.

Body mass and pace pull in opposite directions here, which is worth sitting with before you decide what to do about it. Carrying less weight lowers the energy cost of every kilometre, and how your weight impacts running pace works through what the data supports and where the returns stop.

A total burn figure is a poor guide to what to eat during a run, because your body cannot absorb carbohydrate anywhere near as fast as running spends it. Most runners can take in 60 to 90 g of carbohydrate per hour, roughly 240 to 360 kcal, while running a marathon at four hours' effort spends closer to 600 to 800 kcal an hour. The gap is covered by stored glycogen and fat, and the point of fuelling is to slow the rate at which glycogen runs out, not to match the burn.

That distinction is what separates a run that finishes strong from one that falls apart at 30 km. How much a marathon actually costs in calories puts numbers on the deficit, and how marathon runners fuel during a run covers the practical side: what to carry, how often to take it, and how to practise it in training rather than discovering it on race day.

For runs under about an hour, none of this applies. You have enough stored glycogen to cover the distance, and eating during the run makes no measurable difference to how it goes. Fuelling becomes a real decision somewhere past 90 minutes, and a decisive one past two and a half hours.

The meal before a run matters more than most runners expect, and mainly in the negative sense: there is little you can eat the night before that will make you faster, and a fair amount that will make you slower. What not to eat the night before a race is the shorter and more useful half of that question.

Use the figure this calculator returns as a planning input rather than a target to eat back. Runners who treat estimated burn as a licence tend to overshoot, because the estimate includes the energy they would have spent existing for that hour anyway.