Running calories burned calculator

How running calories are calculated

Running sits near the top of the MET scale for everyday exercise, which is why it burns more per minute than almost anything else in this calculator family. Each pace carries its own MET value, and the calculator turns that into calories with your weight and time.

The formula is calories burned equals MET times 3.5, times your weight in kilograms, divided by 200, times the number of minutes. At 8.0 km/h the MET is 8.3. Push the pace to 14.5 km/h, a fast 9 mph run, and the MET climbs to 12.8, roughly 55 percent higher.

Worked example

An 80 kg runner at 9.7 km/h (6.0 mph) for 40 minutes burns 9.8 times 3.5 times 80, divided by 200, times 40, which comes to 549 kcal. The same runner covering the same 40 minutes at the faster 12.9 km/h pace burns about 661 kcal, because the higher MET outweighs the shorter time it actually takes to cover any given distance.

Running by pace or by distance: which is more accurate

This calculator works on pace and time, which is the more accurate method for a run at a fairly steady speed. Distance based estimates, often quoted as a flat "100 kcal per mile" rule, are a simpler approximation.

The 100 kcal per mile rule

It is a decent rough guide for a mid weight runner at a moderate pace, but it ignores body weight, which the MET formula accounts for directly. A 60 kg runner and a 100 kg runner covering the same mile do not burn the same total, even though the rule of thumb treats them the same.

Why pace based is better here

Because MET values rise with speed, a fast 5K burns more per minute than a slow one, and pace based calculation captures that. Distance based estimates are still useful for quick mental maths on a long run when you know your average pace is fairly constant.

Terrain and treadmill incline

These MET values assume level, firm outdoor ground. Hills, sand, trail terrain and treadmill incline all raise the true cost above what the calculator shows, sometimes substantially on a steep incline.

Trail and technical terrain

Trail running, especially with technical footing, roots or loose rock, tends to sit above the equivalent road pace in energy cost even when your watch reports a similar average speed, because more of the effort goes into stabilising and adjusting stride rather than pure forward motion. Treat a trail run at a given pace as closer to the next speed band up in this calculator, particularly on hilly or technical routes.

Running calories at a glance

Calories burned in 30 minutes of running at each pace, for a 70 kg adult. The 9.7 km/h row is highlighted as a common, sustainable training pace for a recreational runner.

Calories burned by common race distances

Distance events roughly fix the time you spend running once you set a pace, which makes it easy to estimate a whole race rather than just 30 minutes. These figures assume a 70 kg runner at a steady 9.7 km/h training pace throughout.

Race day totals in practice usually run a little higher than a training estimate at the same distance, since race pace is typically faster than an everyday training pace and nerves, crowd energy and taper freshness often combine to produce a quicker finish than a solo training run at the same perceived effort.

Running calories by body weight

Body weight changes the total in direct proportion in the MET formula, so a heavier runner burns noticeably more than a lighter one at the identical pace and time. The table below shows a steady 30 minute run at 9.7 km/h across a range of body weights.

Why two runners at the same pace can burn different amounts

MET values describe an average across the population they were measured on, but individual running economy, how efficiently someone converts oxygen into forward motion at a given pace, genuinely varies. Trained runners tend to be more economical than untrained ones at the same speed, meaning the true energy cost for an experienced runner can sit a little below the compendium estimate, and a beginner's a little above it. Years of consistent training, stride mechanics and even shoe choice all contribute to this variation, which is why elite runners can sustain paces that would exhaust a recreational runner at what feels, to them, like a comfortable effort.

Body composition plays a role too. Running is a weight bearing activity, so the formula already scales with total body weight regardless of whether that weight is muscle or fat, which is the correct approach for energy cost even though body composition affects other things like pace and injury risk that this calculator does not attempt to capture.

How to use the number

For a runner tracking weekly training load, the total across all sessions in a week matters more than any single run, and the number here is a reasonable way to sum that up.

Fuel around long runs, not after every session

Runs under 60 minutes rarely need mid session fuelling, and the calories burned mostly come out of your existing daily intake rather than requiring an immediate top up. Longer runs are a different case: the protein calculator and your usual meal pattern still apply either way.

Do not let a hard run justify a bad week

A single long run can burn 800 to 1,000 kcal or more, which makes it tempting to treat it as licence for extra food across the following days. Spread over a week, that swing is smaller than it feels in the moment.

Marathon and half marathon training blocks

Weekly mileage often climbs sharply during a training block, sometimes doubling from a base level over 8 to 12 weeks, and the energy cost climbs with it. Recalculate your expected weekly running burn every few weeks as mileage builds, rather than using a figure from week one of the plan for the peak week.

Carbohydrate needs on long runs

The calorie total here measures energy expended, not what needs replacing during the run itself, and those are different questions once a session pushes past roughly 90 minutes. At that point glycogen stores start to matter, and treating carbohydrate as something to plan around a long run, practised in training the same way pace and gear are, tends to work better than improvising it mid session or trying to eat back the exact calorie total afterwards. Marathon and half marathon plans usually introduce race-pace long runs with a rehearsed fuelling routine well before race day for exactly this reason: a fuelling plan that has never been tested is one more variable to go wrong alongside pace and weather on race day itself.

Running compared to other cardio for the same time

Minute for minute, running at even an easy pace generally sits above brisk walking, moderate cycling and swimming in calories burned, because its MET values start higher and climb faster with pace than most other common cardio options. That makes it an efficient option when time is the limiting factor.

The trade off is impact. Running loads the joints with each footstrike in a way cycling and swimming do not, which is part of why many training plans pair it with a lower impact option like cycling on recovery days, rather than running every session at the same volume.

Against short, very high intensity intervals or stair climbing, running at a steady pace generally burns less per minute at the peak of the hardest interval, but those formats are rarely sustained for anywhere near as long as a typical run, so total session calories often end up in a similar range once duration is accounted for.

Run-walk intervals

Building volume through structured run-walk intervals, a common approach for beginners and for anyone returning from injury, does not meaningfully change the total calorie estimate compared with covering the same distance at one steady pace. This calculator assumes a single continuous MET value, so the simplest way to estimate a run-walk session is to average the overall pace across the whole session rather than treat each segment separately. For a more careful estimate, split the session into its running minutes and its walking minutes, price each block with the matching calculator on this site, the walking calories burned calculator for the walk portions, and add the two totals together. Either approach lands close enough for practical training purposes, since the point of a run-walk plan is building tolerance to volume and time on feet, not tracking every interval to the minute.

Common mistakes

Assuming a faster pace than you actually held. Average pace over a run with stops, traffic lights or a warm up mile is usually slower than your best segment.

Ignoring hills. A hilly route at the same average pace as a flat one burns noticeably more, since uphill effort costs more than the flat MET value assumes.

Using flat per mile rules for every runner. A rule of thumb like 100 kcal per mile ignores body weight, which changes the true number by 30 percent or more between a light and heavy runner.

Double counting a watch estimate and this calculator. Pick one method for a given run and use it consistently, rather than adding two different estimates together.

Overfuelling after short, easy runs. A 20 minute easy jog rarely burns enough to need dedicated recovery nutrition beyond a normal meal.

Running calories at a glance by duration

Calories scale linearly with time once pace is fixed, so a table by duration is a quick way to size up a run before you set out, without needing to know the exact distance in advance. The figures below use the steady 9.7 km/h pace, for a 70 kg runner, across four common training lengths.

Gait, footwear and surface, briefly

None of these change the MET value the calculator uses, but they are common questions, so it is worth covering why they are left out. Running form, forefoot versus heel strike, cadence, arm carriage, has a real but small effect on running economy at a given pace, generally a few percent at most between two reasonably competent runners, well inside the normal error band of a MET based estimate.

Shoe type

Modern carbon plated racing shoes have been shown in several studies to modestly improve running economy at race pace for many runners, meaning slightly less true energy cost for the same speed than an older shoe design would produce. The effect is real but is not large enough, and not consistent enough across individual runners, to justify a separate MET value in this calculator, so treat the number here as a reasonable average regardless of shoe.

Road, track and treadmill belt surfaces

A rubberised track returns a small amount of energy with each stride compared with asphalt or concrete, which some research links to a marginally lower energy cost at the same pace, though the difference is small next to the effect of pace itself. A treadmill belt, similarly, removes a small amount of the propulsive work outdoor running requires, which is part of why a slight incline is commonly used to bring treadmill effort closer to an equivalent outdoor pace.

Barefoot and minimalist running

Barefoot or minimalist running tends to shift stride and landing pattern for most people used to cushioned shoes, and the calorie effect of that shift is not well separated from the effect of the accompanying change in cadence and stride length in the available research. Treat the standard MET values here as the default for any footwear unless you have a specific reason to expect a meaningfully different gait.

Heat, cold and altitude

Running in hot, humid conditions raises heart rate and perceived effort at a given pace, largely through the extra cardiovascular work of dissipating heat, and most runners naturally slow down to compensate, which lowers the MET value for the pace they actually end up holding rather than raising it for a fixed speed. The net effect on calories at a truly fixed pace is small, but the practical effect of a hot run is usually a slower pace and a harder feeling effort for the same or a slightly lower total.

Cold weather

Cold air adds a small metabolic cost through shivering thermogenesis at rest, but during active running the body generates enough heat that this effect is minor, and heavy cold weather layers add a small load similar to carrying extra weight rather than meaningfully changing the running MET itself. The bigger practical factor in cold weather is often a more cautious pace on icy or unfamiliar footing.

Altitude

At meaningful altitude, roughly above 1,500 to 2,000 metres, reduced oxygen availability makes the same pace feel harder and typically forces a slower actual speed, similar to the pattern seen in heat. Controlled research on whether the true energy cost of a given pace rises at altitude is mixed, so treat an altitude run mainly as a pace adjustment problem: pick the speed band that matches how hard the run genuinely felt, rather than the pace you would hold at sea level.

How coaches use a running calories calculator

For a coach programming a training block, weekly running volume translates into an energy cost that has to be accounted for somewhere in a client's nutrition, especially during marathon or half marathon build phases where mileage climbs fast.

A practical approach: estimate the week's running burn once from planned mileage and pace, adjust the client's activity level or calorie target accordingly, then use weekly weight and performance trends to fine tune rather than recalculating after every run.

This matters most during taper and peak weeks, where mileage swings sharply in opposite directions over a short span, and a calorie target left unchanged from the middle of a block can leave a client under fuelled during peak weeks or unnecessarily restricted during a taper.

Scraler keeps planned workouts and nutrition targets in one place, so a change in weekly mileage is easy to reflect in a client's calorie target without rebuilding the plan from scratch.