Running burns roughly 80 to 140 calories per mile for most people, with your body weight being the single biggest factor. A 160-pound runner burns about 125 calories per mile at a 10-minute pace, while a 220-pound runner covers that same mile for about 172 calories. Over a typical 30-minute run, that adds up to 300 to 500 calories depending on your size and speed.
Calories Burned Per Mile by Weight
Your body weight drives calorie burn more than anything else during a run. Heavier bodies require more energy to move across the same distance. Here’s what the numbers look like at a common 10-minute-per-mile pace (6 mph):
- 130 lbs: ~101 calories per mile
- 160 lbs: ~125 calories per mile
- 190 lbs: ~148 calories per mile
- 220 lbs: ~172 calories per mile
A simple rule of thumb: multiply your weight in pounds by 0.75 to get a rough per-mile estimate at a moderate pace. It won’t be exact, but it gets you in the right neighborhood without a calculator or fitness tracker.
Does Running Faster Burn More Calories?
This is where things get counterintuitive. On flat ground, the energy cost of running per mile stays remarkably stable across a wide range of speeds. Classic exercise physiology research published in the Journal of Applied Physiology found that net calories burned per kilogram per kilometer are essentially independent of speed on level terrain. In other words, running a mile at an 8-minute pace and a 10-minute pace costs your body about the same amount of energy for that distance.
The calorie data supports this. A 160-pound runner burns about 125 calories per mile at a 10-minute pace and roughly 119 calories per mile at an 8.5-minute pace. The numbers barely budge. What changes dramatically is calories burned per minute. Running faster covers more ground in less time, so you burn more total calories in a 30-minute session simply because you’ve covered more miles. A 160-pound person running for 30 minutes at a 10-minute pace covers 3 miles and burns about 375 calories. That same person running 8-minute miles covers 3.75 miles and burns around 440 calories in the same half hour.
At very high speeds (above 10 mph), the calorie cost per mile does start climbing because biomechanical efficiency decreases. A 160-pound runner burns about 190 calories per mile at 10 mph compared to 125 at 6 mph. But most recreational runners won’t hit those speeds, so the practical takeaway is straightforward: if you want to burn more calories, run more miles. Speed is secondary.
The Extra Burn After You Stop
Your body doesn’t snap back to its resting state the moment you finish a run. It continues burning calories at an elevated rate as it repairs muscle tissue, replenishes energy stores, and returns to its baseline temperature and heart rate. This is sometimes called the “afterburn effect.”
How long this lasts varies widely. Estimates range from 15 minutes to 48 hours depending on workout intensity. For a typical 30-minute run, the afterburn adds roughly 6% to 15% to your total calorie expenditure. If your run burned 300 calories, you can expect an additional 18 to 45 calories afterward. It’s a real effect, but not a large one for moderate-effort runs. High-intensity interval sessions and long, hard efforts produce a bigger afterburn than easy jogs.
Gross Calories vs. Net Calories
Most calorie calculators and fitness trackers report gross calories, which is the total energy your body used during the time you were running. But your body would have burned some calories during that time anyway, even if you’d been sitting on the couch. The extra calories you burned specifically because you ran, rather than rested, are your net calories.
For most people, resting metabolism burns about 1 to 1.5 calories per minute. Over a 30-minute run, that’s 30 to 45 calories you would have burned regardless. So if your watch says you burned 400 calories during a run, the running itself was responsible for roughly 355 to 370 of those. This distinction matters most if you’re using calorie burn to guide how much you eat. Treating the gross number as “extra” calories you’ve earned can lead to slightly overeating, which adds up over weeks.
How Accurate Is Your Watch?
Fitness trackers are convenient, but their calorie estimates carry meaningful error. A 2025 review of Apple Watch studies found that calorie burn readings were off by about 18% on average. A 2022 study comparing the Apple Watch, Fitbit Sense, and Polar Vantage V rated every device as “poor accuracy” across all activities, with error rates ranging from 15% to 30%.
These devices use your heart rate, movement data, and personal stats to estimate energy expenditure, but they can’t directly measure how many calories your muscles are actually using. They tend to overestimate for some people and underestimate for others, and the error can shift depending on running speed, terrain, and even how snugly the watch sits on your wrist. Use your tracker’s calorie number as a rough guide, not a precise measurement. If it says 400 calories, the real number could reasonably fall anywhere between 280 and 520.
Hills, Heat, and Other Variables
Running uphill increases calorie burn significantly because you’re lifting your body weight against gravity with every stride. The same research that found flat-ground energy cost to be independent of speed showed that incline is the variable that actually moves the needle on per-mile calorie expenditure. A moderate hill can increase your burn by 30% or more compared to flat ground. Running downhill, conversely, costs less energy than running on a level surface.
Other factors that shift your calorie burn include temperature (your body works harder to cool itself in heat, adding a modest calorie cost), wind resistance (running into a headwind increases effort), and running surface (trails and sand demand more energy than pavement). Your fitness level also plays a role. Experienced runners develop more efficient form over time, meaning they burn slightly fewer calories per mile than a beginner of the same weight. This is your body getting better at the task, not a reason to worry about diminishing returns.
Putting the Numbers to Use
If you’re running for weight management, the most reliable lever you have is distance. Adding one extra mile to your run burns roughly 100 additional calories for a 160-pound person, regardless of how fast you cover it. Over a week of five runs, that’s an extra 500 calories, or about a pound of fat loss every seven weeks from that single added mile alone.
For a quick estimate without any device, multiply your body weight by 0.75 and then multiply by the number of miles you ran. A 180-pound person running 4 miles would calculate 180 × 0.75 × 4 = 540 calories. Subtract about 50 calories for what you’d have burned at rest during that time, and you’re looking at roughly 490 net calories from the run. That’s a more honest number than what most apps will show you, and it’s close enough for practical decisions about nutrition and training.