Input

Results

Enter weight, distance, and pace to estimate calories burned.

Calorie estimates are approximate. Actual burn varies with terrain, weather, fitness level, and running efficiency.

How It Works

This calculator estimates running energy cost from body weight, distance, and pace. Pace determines speed, speed maps to a MET value, and the formula combines MET with body weight and run duration to estimate total kilocalories.

Output includes total calories, calories per kilometer, and estimated duration so you can compare short hard runs against longer easy sessions. It is especially useful for planning weekly volume and fueling strategy alongside your aerobic work in the Zone 2 Calculator.

Expert Note

Use calorie numbers to guide trends over multiple weeks, not to "earn" or remove food after a single run. Consistent fueling improves recovery and training quality.

Accuracy & Limitations

Like all running calorie tools, this is an estimate. MET-based models are solid for planning, but real expenditure shifts with terrain, weather, biomechanics, and sensor quality.

Garmin and Apple Watch calorie readouts may differ from this result because wearables combine heart rate, movement, and proprietary algorithms. In steady outdoor runs, watch values and MET estimates are often close, but interval sessions, trails, and wrist-sensor lag can widen the gap.

Real-World Examples

10K easy run: A 70 kg runner at 6:00/km typically lands around the mid-700 kcal range. This is useful for long-run fueling and post-run meal planning.

5K tempo vs easy: Over the same 5K, a faster effort usually burns only moderately more total calories than easy pace, but creates more recovery cost and fatigue.

Wearable comparison: If Garmin reports 610 kcal and this calculator shows 580 kcal for the same run, treat both as reasonable bounds and track your rolling weekly average instead of chasing single-run precision.

FAQ

Why is my Apple Watch calorie number different?

Apple Watch uses heart rate and motion signals in addition to pace, while this tool uses a MET model from pace, distance, and body weight. Different inputs produce different estimates, especially on hilly or stop-start runs.

Does pace matter less than distance for calorie burn?

For most steady runs, yes. Over fixed distance, faster pace raises calorie burn somewhat, but body weight and distance usually explain most of the total calorie difference.

Should I use this for weight-loss targets?

Use it as a planning reference, then evaluate progress with body-weight trends, training quality, and recovery markers over several weeks. Daily calorie estimates are too noisy to be a standalone target.