how many hours to train for an ironman
Triathlon Training Hours Calculator
Pick your race and enter the hours you can give it each week. You get the peak weekly training load the distance demands, the hours needed to absorb it, the realistic week-to-week hour range, and a straight verdict on whether your schedule is enough.
Verdict
Tight
Peak build needs about 10 h/week
Peak weekly load
650
race-ready load
Peak hours needed
10 h
hardest week
Typical hours range
7–13 h
base to build
Your hours buy
450 Load
at base intensity
Typical plan range
On the meter your hours sit in the amber band — inside 80% of the ~10 h peak, just short of the green. You'd finish, but you're training with no spare capacity, and the outlined band shows where a typical week should already be landing.
How to use it
- 1
Pick your race: sprint, Olympic, 70.3, or Ironman — or a standalone 5K, 10K, half, or marathon.
- 2
Enter the hours per week you can realistically train, counting swim, bike, run, and strength together.
- 3
Read the verdict and the peak hours the distance needs at the hardest point of the build.
- 4
Compare the peak weekly load and the typical hour range against what your schedule holds.
- 5
If the gap is large, drop to a shorter distance or free up hours — then re-check.
Hours are the constraint, not motivation
Every distance has a peak weekly training load a prepared athlete trends toward — about 650 for a 70.3 and 850 for an Ironman. Aerobic base training converts roughly 50 load per hour, and race-specific peak weeks run harder at about 65. This calculator turns that load into the hours your schedule actually has to find. If the peak week needs 13 hours and you have 8, the gap is arithmetic, not willpower.
A planning sanity check, not a go/no-go gate
This calculator turns a distance-level peak-load assumption into a simple time-budget check. The product planner does not accept or reject a season from this one verdict: it also considers your history, current capacity, timeline, available days, and recovery constraints. Use the result to start a realistic calendar conversation.
Know the number before you sign up
Most athletes pick a race first and discover the hours later. Reverse it. The typical hour range here spans your easier base weeks to your hardest build weeks, so you see the real week-in, week-out commitment — and decide between an Ironman and a 70.3 from your calendar instead of your ego.
Common questions
How many hours a week to train for an Ironman?
An Ironman trends toward roughly 850 peak weekly load, which lands at about 13 hours a week at the peak of the build. Across the whole plan the typical range is about 9 to 17 hours, lighter in base weeks and heaviest in the final build. Below about 10 hours a week the math gets tight, and a first-timer on a low hour budget finishes more comfortably by targeting a 70.3 instead.
Can I do a 70.3 on limited hours?
Yes, within reason. A 70.3 trends toward about 650 peak weekly load, which is roughly 10 hours a week at peak and a typical range of about 7 to 13 hours. Around 8 hours a week is the tight-but-doable floor to cross the line trained rather than survived; below that the calculator tells you to raise the hours or pick a shorter race, because every session has to be near-perfect to close the gap.
Related tools
Keep going
Next step
Turn these numbers into an adaptive plan.
PaceBeats combines the relevant calculations with your training history, constraints, and deterministic checks to build and adapt your week.