How Many Calories Does a Triathlon Burn? A By-Distance Estimate

As a starting point, here are typical ballpark figures for a roughly 70 kg (154 lb) age-group athlete — useful for orientation, not as precise numbers for you:

• Sprint (750 m / 20 km / 5 km): ~600-1,200 kcal in about 1:00-1:45
• Olympic (1.5 km / 40 km / 10 km): ~1,400-2,400 kcal in about 2:15-3:30
• 70.3 half (1.9 km / 90 km / 21.1 km): ~3,500-5,500 kcal in about 4:30-8:00
• Full Ironman (3.8 km / 180 km / 42.2 km): ~7,000-11,000 kcal in about 9:00-16:00

As a rough adjustment, add or subtract on the order of 10% for every 10 kg you are above or below 70 kg. Notice how wide each range already is — that is the honest reality of energy expenditure, and the next section explains why a single 'calories for an Ironman' figure can never be more than a ballpark.

It is tempting to treat a distance-based total as a fact, but four variables move it so much that two athletes finishing the same race can differ by thousands of calories.

• Body weight. Heavier athletes move more mass and burn more, roughly in proportion — this is usually the biggest single factor.
• Duration. A 16-hour Ironman finisher is working for far longer than a 9-hour one, so time on course often matters more than raw speed.
• Intensity and efficiency. Fitter, more economical athletes use less energy at a given pace; a stronger cyclist covers 180 km for fewer calories than a beginner grinding the same distance.
• Terrain, conditions and gear. Hills, wind, heat, drafting rules and even position all change the cost of the same distance.

Because of all this, energy expenditure is genuinely estimated rather than measured outside a lab. Treat every number in this guide — and on your watch — as a reasonable ballpark for planning, not a figure to act on to the calorie.

Within a race, the split between the three sports is fairly consistent, and it surprises people.

Swimming: roughly 8-12 kcal/min, but the leg is short (about 11-60 min), so total swim energy is modest across all distances.

Cycling: roughly 9-15 kcal/min at endurance pace and more at race pace. Because the bike leg is by far the longest, it typically supplies most of the total race energy in anything beyond a sprint — which is also why the bike is where you do most of your fuelling.

Running: the highest rate per minute, but the run leg is shorter than the bike, so it lands as a smaller share of the total than its intensity suggests.

The practical takeaway is that the bike leg dominates both your energy use and your fuelling opportunity. Use the pace calculator to estimate your leg durations, which matter more to the total than pace alone.

For a personal ballpark, a simple formula works better than a distance chart because it uses your own weight and time:

Total kcal ≈ (race duration in hours) × (body weight in kg) × (MET value)

MET values are standardised estimates of activity intensity; for typical triathlon efforts, rough values are around 10 for hard sprint-pace work, ~9 at Olympic pace, ~7.5 at 70.3 pace and ~6 at the steadier Ironman pace. For example, an 80 kg athlete racing a 12-hour Ironman: 12 × 80 × 6 ≈ 5,760 kcal.

Treat the result as an order-of-magnitude estimate. MET tables are population averages, your true intensity varies through the race, and the formula ignores terrain and conditions — so it will not match your watch, and neither is 'correct'. It is enough to plan around, which is all it needs to be.

Here is the part that reframes the whole topic: you cannot refuel anywhere near what you burn, and you are not supposed to.

Your gut can absorb only about 60-90 g of carbohydrate per hour — very roughly 240-360 kcal/hr — and even well-trained athletes practising gut training reach only somewhat higher. So the arithmetic is stark. Across a ~5-hour 70.3 you might burn in the region of 4,500 kcal but take in perhaps 1,500-1,800, and across a ~12-hour Ironman you might burn ~9,000 while absorbing ~3,000-3,600.

That leaves a large deficit on any long race — and this is completely normal. Your body draws on its own substantial fat and glycogen stores to cover the gap; that is how endurance works. The goal during a race is not to match your burn but to take in enough carbohydrate per hour to keep working well, which is the subject of fuelling during training and racing and race fuelling, and to plan it with a tool like the fuelling planner.

The single most important message of this guide is that your energy expenditure is not an eating target. Knowing you 'burned 9,000 calories' can tempt two mistakes, and both are worth avoiding.

The first is trying to eat back the deficit during the race, which the gut cannot do and which causes stomach distress — you fuel to a per-hour carbohydrate range that keeps you moving, not to your burn. The second, more chronic mistake is under-fuelling training day after day because you are watching a calorie figure. Persistently taking in far less energy than you expend — often called low energy availability, which can lead to RED-S (relative energy deficiency in sport) — undermines adaptation, recovery, hormones, bone health and immunity, and it is a genuine risk for endurance athletes, not a shortcut. Fuel the work in front of you and your recovery, eat enough to train consistently, and if you find yourself anxious about calories or deliberately restricting, treat that as a reason to speak to a qualified sports dietitian or clinician rather than to push the number lower.

After a long race your body has real jobs to do — restock glycogen, repair muscle, rehydrate and replace electrolytes — and it does them best with steady, ordinary eating rather than one heroic meal.

General, evidence-based starting points rather than strict prescriptions: prioritise carbohydrate in the first few hours to refill glycogen (something on the order of ~1 g/kg/hr is a common guideline), include protein across the day to support repair (roughly 20-40 g per feeding, repeated), rehydrate steadily and replace electrolytes to match losses, and return to normal balanced meals with fruit and vegetables over the following day. Spread it across several smaller meals rather than forcing thousands of calories at once. Notably, many age-group triathletes under-eat after racing and feel worse for it, so the practical goal is to eat enough, comfortably, over 24 hours — see the recovery nutrition guide and race-week nutrition. Individual needs vary, so adjust to appetite and how you feel.

People often reach this topic while wondering about weight, so it is worth addressing carefully and without hype. Triathlon training does increase energy expenditure, and some people do change body composition over a season — but the picture is not as simple as 'big burn equals easy weight loss'. Appetite tends to rise with training, high-volume weeks demand substantial fuelling, and using race-day burn figures to justify a large everyday deficit is a route to under-fuelling rather than to performance.

If a body-composition change is a genuine goal, the sustainable approach is a modest adjustment made mostly in lower-volume periods, with enough fuel around key sessions to keep training and recovery intact — never a steep deficit stacked on heavy training, which risks the low-energy-availability problems described above. Because weight and health are individual and sometimes medically sensitive, this is an area to approach with a qualified sports dietitian rather than a calorie chart; weight management during Ironman training discusses it in more depth.

If your device disagrees with this guide's estimates, neither is wrong — both are estimates made different ways.

Wrist devices infer calories from heart rate, pace and personal data, not from direct measurement, and they tend to run around 10-20% high, especially in heat or when heart rate is elevated for non-metabolic reasons. Cycling power data is the most reliable proxy available to age-groupers: the kilojoules of mechanical work recorded by a power meter happen to be numerically close to the kilocalories burned, because human cycling efficiency sits near a quarter — a convenient coincidence that makes a power file the best 'calorie' estimate you will get outside a lab. Swimming and running have no equally clean proxy. The sensible habit is to pick one method, use it consistently to compare efforts over time, and never treat the exact figure as truth.

Energy-expenditure estimates are genuinely useful — for planning, not for calorie-counting. Three good uses:

• Plan your in-race fuelling by the hour. Since you cannot match your burn, work from a target carbohydrate range per hour for your race duration and rehearse it in training; the burn figure just tells you the scale of the effort.
• Plan recovery. Knowing a long race leaves a big deficit is your cue to eat properly and consistently afterwards rather than skipping meals because you feel wiped out.
• Sense-check training fuelling. If big weeks leave you constantly depleted, the answer is usually more fuel, not less.

What these numbers are not is a scoreboard to eat back or a licence to under-fuel. Use them to fuel the work, protect your recovery, and keep training sustainable — and hand the precise per-hour and per-session detail to the fuelling and recovery guides built for it.