🏃 Running Calorie Calculator

How to Use This Running Calorie Calculator

Running has the simplest calorie rule in all of exercise science: about 1 kilocalorie per kilogram of body weight per kilometer. Enter your weight, distance, and whether you ran or walked, and the calculator applies the rule.

The 1 kcal/kg/km Rule

Decades of lab studies converge on roughly 1 kcal per kg per km for running, remarkably independent of speed: running faster burns more per minute but you finish sooner, so per-kilometer cost stays nearly flat. Walking costs about 0.53 kcal/kg/km at typical speeds. A 70 kg runner covering 5K burns 1.0 x 70 x 5 = 350 calories; walking it burns 185. Hills raise the cost (about 10 percent per 100 m climbed per km is a rough guide), and the rule slightly overstates for very efficient elites and understates for beginners.

Worked Example

Enter 160 lb, 5 km, running. Convert: 160/2.20462 = 72.57 kg. Calories = 1.0 x 72.57 x 5 = 362.9. Per mile: 5 km = 3.1069 mi, so 362.9/3.1069 = 116.8 cal/mi. Switch to walking: 0.53 x 72.57 x 5 = 192.3 calories. A 70 kg marathon (42.195 km): 1.0 x 70 x 42.195 = 2,953.7 calories, which is why marathoners hit the wall when glycogen (about 2,000 stored calories) runs out. Verify each figure in the calculator.

Speed, Hills, and Accuracy

Speed barely changes per-km cost between 8 and 16 km/h; the rule holds across that whole range. Hills are the big modifier: climbing costs roughly 8 to 10 times flat running per vertical meter, so hilly routes can run 15 to 30 percent above the formula. Wind, soft surfaces, and extra weight (vests, packs) add more. Body composition matters a little: the rule uses total weight, and two runners at 70 kg with different body fat burn nearly the same. For food budgeting, the rule is accurate within about 10 percent on flat roads, which beats most watch estimates.

Running for Weight Management

The numbers explain both the promise and the limit of running for fat loss. Five kilometers burns 300 to 400 calories, a meaningful chunk of a daily deficit, but one large muffin erases it. Consistency beats heroics: 25 km a week at 70 kg burns about 1,750 calories weekly, roughly half a pound of fat. Do not "eat back" the full estimate if losing weight is the goal; appetite rises with mileage and the math gets slippery. Protect the habit first, count the calories second, and let the scale judge over weeks, not days.

Second worked example: 200 lb, 10K run

Enter 200 lb, 10 km, running. Convert: 200 / 2.20462 = 90.72 kg. Calories = 1.0 x 90.72 x 10 = 907.2. Per mile: 10 km = 6.2137 mi, so 907.2/6.2137 = 146.0 cal/mi. Per km: 90.7. Switch to walking: 0.53 x 90.72 x 10 = 480.8 calories. Compare with the first example: the 160 lb runner burned 362.9 for 5K, while this 200 lb runner burns 907.2 for 10K. Double the distance and 25 percent more weight gives almost exactly 2.5 times the burn, 907.2/362.9 = 2.50, which shows the formula's clean linearity. Enter both in the calculator and confirm the ratio.

Gross vs net calories

The 1 kcal/kg/km rule gives gross calories: everything burned during the run, including what you would have burned sitting on the couch. Net calories subtract resting metabolism for the same period. A 70 kg runner with a resting burn of about 1 kcal/min runs a 5K in 30 minutes: gross = 350, resting for 30 min = 30, net = 320. The difference is about 9 percent, small enough that most runners ignore it, but it matters in two cases. First, comparing running to sitting: the true extra cost of the run is the net figure. Second, very slow running and walking: at 12 min/km walking pace, gross and net differ by nearly 20 percent because resting burn fills a bigger share of a long, easy hour. Food labels and fitness apps usually speak gross; weight-loss math is slightly more honest with net. Either way, pick one convention and stay consistent.

Common running-calorie mistakes

Mistake one is eating back the full estimate. Appetite rises with mileage and the formula runs about 10 percent high on downhills and soft surfaces; crediting yourself the gross number stalls fat loss. Eat back half at most. Mistake two is treadmill trust: treadmills estimate from speed and a default weight, often 150 to 180 lb, so a 200 lb runner's display reads low and a 130 lb runner's reads high. Enter your real weight or use this calculator. Mistake three is double counting: wearing a watch that estimates from heart rate while also logging the run in an app that applies the 1 kcal rule, then adding both. One source per workout, or the numbers are fiction.

For informational purposes only, not medical advice. Consult a healthcare professional.

A Second Worked Example: The 150-Pound 5K Runner

Take a 150-pound runner finishing a 5K in 24 minutes. Convert weight: 150 divided by 2.20462 is 68.0 kg. The 1 kcal/kg/km rule says 68.0 times 5 is 340 kcal gross. Now net it out: subtract the basal burn for 24 minutes. Basal for a 150-pound adult runs about 1.1 kcal per minute at rest, so 24 minutes is roughly 26 kcal. Net exercise calories: about 314.

Compare with the heavier runner to see weight's role. A 200-pound runner at the same pace: 90.7 kg times 5 km is 454 gross, minus the same 26 basal, is 428 net. The 50-pound difference costs 114 extra kcal for the identical run, which is why heavier runners lose weight faster at first: every mile is more work. It is also why pace-based calorie charts without a weight input are decoration, not data.

The 1 kcal/kg/km Rule: Where It Comes From

The rule is not a guess; it falls out of the measured energy cost of running, about 1 kcal per kilogram per kilometer, which exercise physiologists have confirmed across decades of lab studies. It holds because running is essentially a series of small jumps, and the energy of lifting your mass against gravity scales linearly with mass and distance. Walk the same 5K and the cost drops to about 0.5 kcal/kg/km; the flight phase is what makes running expensive.

The rule's limits are speed and slope. Above about 90 percent of max effort, efficiency drops and the cost rises toward 1.1 or 1.2. Uphill, add roughly 10 percent per 1 percent of grade; a 5K with 100 meters of climbing costs about 8 percent more than a flat one. Downhill gives some back but not all, because braking is work too. For flat training runs at normal effort, though, 1.0 is honest to within 5 percent, which beats every fitness tracker estimate you have ever seen.

Gross vs Net: The Number That Matters

Gross calories include what you would have burned lying on the couch; net counts only the exercise premium. For a 30-minute run at 300 gross kcal, the net is about 270 after subtracting basal. Dieters should use net: the couch calories were never available for creating a deficit, since you burn them regardless. Using gross double-counts your resting metabolism and makes the deficit look bigger than it is.

The practical effect is small per run but large per month. Over 20 runs, the gross-net gap is about 600 kcal, nearly a full day's deficit at aggressive dieting rates. Fitness apps almost always report gross, because bigger numbers feel better. The calculator reports both so you can log honestly; when the app says 400 and the calculator says 360 net, the calculator is the one telling the truth.

Hills, Heat, and the Accuracy Killers

Three things break the simple rule, in order of damage. Hills first: that 10-percent-per-grade cost means a hilly 10K can run 15 to 20 percent above the flat estimate. If your route has real climbing, multiply by 1.15 and stop wondering why hilly weeks leave you ravenous. Heat second: running in 90-degree weather raises the cost 5 to 10 percent as your heart works to cool you, and the extra sweat loss masks it on the scale.

Wind is third and the sneakiest, because it is invisible in the data. A 10-mph headwind raises energy cost about 5 percent; a full out-and-back in wind costs more than a calm run because the headwind leg hurts more than the tailwind leg helps. And weight changes everything continuously: lose 10 pounds and the same run costs 7 percent less, which is why weight loss slows even when training stays constant. Recalculate monthly, not yearly.