Calories Burned Running Calculator
Estimate calories burned during a run from body weight, duration, and average speed. A quick first-pass for runners tracking energy expenditure; uses the 1 kcal per kg per km running rule (about 1 MET per km/h of speed).
Last updated: September 2026
Formula below · 3 sources (pubmed.ncbi.nlm.nih.gov, WHO, nhs.uk) · Updated Sep 2026
Compare with similar
About this calculator
This calculator uses the running rule of thumb that the energy cost of running is about 1 kcal per kg of body weight per km, which is the same as saying running at a given speed in km/h costs roughly that many METs: calories = weight_kg × speed_km/h × (time_min ÷ 60). Distance (speed × hours) drives the result, so pace matters much less than how far you go. Variables: weight in kilograms; time in minutes; speed in km/h. The Compendium of Physical Activities lists running at 8 km/h at about 8.3 METs, 9.7 km/h at 9.8 METs, 12 km/h at about 11.5 METs and 16 km/h at about 14.5 METs, so the 1-MET-per-km/h approximation is close across normal running speeds (one MET ≈ 1 kcal/kg/hour). So a 70 kg runner at 10 km/h for 30 minutes burns ≈ 70 × 10 × 0.5 = 350 kcal. Edge cases: below about 6-7 km/h most people walk, and walking costs less per km than running, so the result overstates walking; at very high speeds (above about 16 km/h) the Compendium values fall slightly below the rule, so the result runs a little high. The MET method is what most fitness trackers and apps use, with personal corrections (heart rate, stride length, age) layered on top. Real running energy expenditure varies by 10–25% between individuals of identical weight and speed due to running economy, terrain (hills add cost), wind, surface (sand or trail vs. road), and shoes. The figure is gross energy (it includes the ~1 kcal/kg/hour you would burn at rest anyway). Treat the calculator output as a starting estimate and validate against your own actual experience over multiple runs.
How to use
Example 1 — Morning jog. You weigh 70 kg and run for 30 minutes at 10 km/h (a 6 min/km pace, comfortable jog). Enter Weight = 70, Time = 30, Speed = 10. Calories = 70 × 10 × (30 ÷ 60) = 350 kcal. ✓ That matches the MET check (about 10 METs × 70 kg × 0.5 hours) and the 1 kcal per kg per km rule (70 kg × 5 km). It may still be 10–20% high for an economical runner. Example 2 — Heavier runner, longer slower effort. An 85 kg runner does 45 minutes at 8 km/h (a relaxed pace). Enter Weight = 85, Time = 45, Speed = 8. Calories = 85 × 8 × 0.75 = 510 kcal. ✓ Larger runners burn more calories at any given pace because there is more body mass to move; slower paces are also more sustainable for longer, so total per-session calorie burn can exceed shorter, faster efforts.
Frequently asked questions
How accurate is this calculator vs a heart-rate-based estimate?
Simple formulas like this one (or MET-based equations) typically have ±15–25% error at the individual level. Heart-rate-based estimates from wearables can be more accurate because they reflect your actual exertion in real time, but they're sensitive to your maximum heart rate estimate (often miscalculated as 220 − age, which has ~10–15 bpm individual variation), and they assume a linear HR-to-VO2 relationship that breaks down at very low or very high intensities. The most accurate consumer method is a wrist-based optical HR monitor combined with a personal VO2 max measurement and known body weight; even then, you're looking at ~10% error compared to gold-standard indirect calorimetry. The honest answer: any single-run calorie estimate is approximate; trust the trend over weeks rather than any single number. For fat-loss planning, assume your actual burn is 15–20% less than what calculators report — that helps you avoid the "earned the cookie" trap of over-eating because you "burned 500 calories on a run".
Does running really burn more calories than walking?
Per minute: yes, dramatically — running at 10 km/h burns ~3× the calories per minute of walking at 5 km/h. Per kilometre: surprisingly, only modestly more — running 1 km burns roughly 30% more calories than walking 1 km for the same person, regardless of pace within a wide range. So if you have limited time, running burns more total calories; if you have limited distance, walking burns nearly as much per kilometre. The classic rule of thumb is about 1 kcal per kg of body weight per km, so roughly 70 kcal per km for a 70 kg person (actual values range from about 60 to 90 depending on terrain, economy, and individual). For weight management, the daily distance walked or run matters more than pace; total movement throughout the day (NEAT) often dwarfs structured exercise calories in the overall energy budget.
Why do hills and uneven terrain matter so much?
Running uphill increases caloric cost roughly 10% per 1% grade — a 5% incline adds ~50% to flat-ground burn, an 8% grade can nearly double it. Downhill running also costs more than flat running because of the eccentric muscle work absorbing impact (though the cost increases less dramatically than uphill). Trail running, sand, and very soft surfaces also raise caloric cost by 10–30% compared to road running because of reduced running economy and additional stabiliser muscle work. This calculator uses a flat-road assumption; for hill or trail running, multiply the output by 1.2–1.5 depending on the terrain. Conversely, treadmill running at 0% incline burns ~5% fewer calories than equivalent outdoor running because there's no wind resistance and the belt slightly assists turnover; setting the treadmill to 1% incline approximates outdoor effort.
What are the most common mistakes people make estimating running calories?
The first is over-trusting the number — single-run calorie estimates are ±20%, so a "350 kcal" run could really be 280 or 420 depending on individual factors. The second is using calorie estimates to justify eating extra after the run (the "I earned it" effect); studies repeatedly show people overestimate calories burned and underestimate calories eaten, so post-run snacks often exceed the workout's energy cost. The third is comparing your wrist tracker's calorie estimate to a friend's on a different device; brand-to-brand differences of 30–50% on the same run are common. The fourth is ignoring weekly totals in favour of single-workout obsession; for body composition change, weekly volume and consistency matter far more than any single day. The fifth is forgetting that EPOC (excess post-exercise oxygen consumption — the "afterburn") is real but small — typically 5–10% of workout calories for moderate runs, not the "burn calories for 24 hours" claims of HIIT marketing.
When should I not use this calculator?
Skip it for non-running activities — swimming, cycling, weight training all have different energy-cost relationships and need their own MET tables. Don't use it for very low intensities (walking under 5 km/h) or very high intensities (sprinting above 15 km/h); the linear approximation breaks down at both ends. It's the wrong tool when you need accurate calorie counts for medical purposes (bariatric surgery recovery, strict diet protocols, athlete weight-cutting) — those need either lab-measured VO2 or careful tracking against actual weight change over weeks. Avoid it for trail or hill running without applying a terrain multiplier; flat-road formulas understate the cost substantially. Finally, don't use single-session calorie burn as your main metric; daily total movement (NEAT plus structured exercise) and consistent caloric intake matter far more than any single workout's headline number.