Ironman Calculator

An Ironman triathlon is the pinnacle of endurance sport — a single-day race covering a 3.86 km open-water swim, a 180.25 km cycling leg, and a full 42.2 km marathon run. Athletes have a strict cutoff of 17 hours to complete all three disciplines plus transitions, making race-day time management as important as physical preparation.

The distances are fixed for every official full-distance event worldwide, which means an Ironman calculator can use those constants to produce highly accurate leg-time estimates based on your personal performance inputs: swim pace, bike power, run pace, and body weight. Understanding how each leg contributes to your total time — and how nutrition and pacing interact — is the foundation of a successful race plan.

This Ironman calculator uses the official distances (swim: 3.86 km, bike: 180.25 km, run: 42.2 km) together with your normalized power (NP) target, functional threshold power (FTP), and paces to project your finish time, check cutoff compliance, build a calorie and carbohydrate plan, and estimate fluid and sodium requirements for race day.

Whether you are aiming for a sub-10-hour finish or simply hoping to cross the line before midnight, accurate split projections let you train smarter and race with confidence. Use this tool alongside a structured training plan, a coach's guidance, and rehearsed nutrition protocols for best results.

The calculator breaks the race into its three main legs plus the two transitions (T1 after the swim and T2 after the bike). Each leg time is derived from a formula that reflects real-world Ironman physics and athlete data.

Swim Time

Swim time is the most straightforward leg. The swim distance is 3.86 km, which equals 3,860 metres. Your pace is entered in minutes per 100 metres, so the formula is:

Swim Time (min) = (3,860 ÷ 100) × Swim Pace (min/100 m) = 38.6 × Swim Pace

A swimmer at 2.0 min/100 m will take 38.6 × 2.0 = 77.2 minutes for the swim leg.

Bike Time

The bike leg uses a power-to-speed model that accounts for your normalized power target, body weight, and a realistic road speed formula. The effective speed (km/h) is estimated as:

Speed (km/h) = Bike NP × 0.9 ÷ Weight × 0.27 + 20

Bike time is then: Bike Time (min) = (180.25 ÷ Speed) × 60

This formula captures diminishing returns at higher powers and the impact of rider weight on real-world Ironman bike speeds.

Run Time

Run time is simply: Run Time (min) = 42.2 × Run Pace (min/km)

A pace of 6.0 min/km gives 42.2 × 6.0 = 253.2 minutes for the marathon leg.

Total Time

The total finish time adds T1 (5 minutes) and T2 (4 minutes) to the three leg times:

Total Time = Swim Time + T1 (5 min) + Bike Time + T2 (4 min) + Run Time

All times are displayed in H:MM:SS format and checked against the official cutoff times: swim at 2:20:00, combined swim+T1+bike at 10:30:00, and overall finish at 17:00:00.

Nutrition is widely described as the fourth discipline of triathlon. Getting it wrong is one of the most common reasons athletes DNF or dramatically slow during the run. The Ironman calculator estimates your caloric needs based on metabolic rate approximations for each discipline.

On the bike, the calculator uses approximately 6 calories per minute, reflecting the moderate but sustained effort typical of an Ironman bike pace. On the run the rate rises to 8 calories per minute, which reflects the higher metabolic cost of running at race intensity after hours on the bike. These rates are conservative and appropriate for most mid-pack athletes; elite athletes burning more watts will require higher intake.

Carbohydrate Needs

The calculator targets 60% of calories from carbohydrates, since carbs are the dominant fuel at Ironman intensities. Using 4 kcal per gram of carbohydrate:

Carbs (g) = (Total Calories × 0.6) ÷ 4

Carbs per hour are then divided across the total moving time from the bike start to the run finish. Sports science recommends 60–90 g of carbohydrate per hour during prolonged endurance events when mixed-sugar sources (glucose + fructose) are used.

Fluid and Sodium

The fluid estimate uses 0.75 litres per hour of combined bike and run time, which aligns with Ironman medical guidelines for moderate conditions. In hot weather, increase this toward 1.0 L/hour. Sodium is estimated at 500 mg per hour to help maintain electrolyte balance and reduce the risk of hyponatremia, a potentially dangerous low-sodium condition seen in long endurance events.

Practice your nutrition strategy in long training sessions before race day. The gut needs training just as the legs do; consuming calories under fatigue requires rehearsal to avoid GI distress.

The bike section of an Ironman is where most races are won or lost — not by going fast, but by avoiding going too hard. Two key metrics help you dial in the right effort: Intensity Factor (IF) and Training Stress Score (TSS).

Intensity Factor (IF)

IF = Normalized Power ÷ FTP

For a full Ironman, elite coaches typically recommend an IF of 0.68–0.75. The calculator displays your IF so you can confirm your NP target falls within this window. An IF above 0.80 almost always leads to a deteriorating run pace; an IF below 0.65 may leave you with unexploited fitness.

Training Stress Score (TSS)

TSS = (Bike Time in Hours) × IF² × 100

A bike TSS of 270–310 is typical for a well-paced Ironman effort. TSS values above 330 are associated with significant glycogen depletion and a slower marathon. Use your calculated bike TSS to gauge whether your target NP is sustainable given your FTP.

Target Normalized Power (72% of FTP)

The calculator also displays a recommended NP ceiling of 72% of your FTP. This is a commonly cited upper limit for maintaining run performance in a full-distance race. Compare this to your entered NP target; if your target exceeds 72% FTP, consider whether the extra speed on the bike is worth the likely cost on the run.

Power-based pacing requires a well-tested FTP value from recent testing — ideally within 4–6 weeks of your race. An outdated FTP will throw off every downstream calculation.

Every full-distance Ironman event enforces mandatory cutoff times. Missing a cutoff means disqualification, regardless of how much distance remains. The three cutoffs are:

The calculator checks all three cutoffs against your projected times and flags PASS or RISK for each. If your projections show RISK on any cutoff, you need to either improve fitness, select a more appropriate target pace, or both. Do not rely solely on improving your pace on race day — a cutoff risk detected in training signals a genuine gap that requires systematic work to close.

Athletes targeting the finish-line cutoff should build buffer time into each leg. Weather, mechanical issues, and GI problems can each cost 15–30 minutes, which can be catastrophic with no buffer remaining. A good rule of thumb is to target the bike cutoff at least 60 minutes ahead of schedule and leave the finish cutoff at least 90 minutes of buffer.

Understanding pace requirements relative to cutoffs lets you set meaningful training benchmarks throughout the season — not just in the final weeks before race day.

Pacing an Ironman correctly separates athletes who run the marathon from those who shuffle or walk it. The physics of the event reward conservative early pacing because glycogen stores, core temperature, and muscular fatigue all accumulate in ways that penalize early aggression.

The calculator shows a Run Pace Equivalent that is approximately 5% faster than your entered standalone marathon pace (dividing by 1.05). This is a rough benchmark for how fast you should expect to run the Ironman marathon given accumulated fatigue. In practice, athletes with strong run backgrounds often beat this estimate, while athletes who over-biked tend to fall well below it.

The Bike-to-Run Relationship

Studies of Ironman finisher data consistently show that athletes who ride below 75% of FTP run significantly faster marathons than those who exceed it, even when bike split times are similar. This is because riding at lower intensity conserves muscle glycogen for the run and reduces core temperature accumulation.

Run Execution

On the marathon, start conservatively — 15–20 seconds per km slower than your target pace for the first 10 km. Many athletes use a run-walk strategy on aid stations, which often produces faster overall run times than continuous running for non-elite athletes. Walking aid stations (approximately 30–45 seconds per station) costs about 3–4 minutes total but allows consistent fueling and a brief muscular recovery that sustains run pace between stations.

If you are targeting a specific finish time, work backwards from the finish cutoff using your projected leg times and build a realistic race-day schedule with specific check-in goals at each discipline exit.