Press play.
An hour of original IronCommit music — no ads, no gaps, free. Start it and forget the phone.
Why 70.3 is its own problem
A sprint is short enough to suffer through. A full Ironman is long enough that everyone accepts it is a survival exercise. The 70.3 sits between: four to seven hours, fast enough to feel like racing, long enough that a bad decision in hour two is still being paid for in hour five.
Almost every blown half Ironman has the same shape. The bike felt comfortable, so the athlete rode a little harder than planned, and the run turned into a walk somewhere after mile six. The race is decided on the bike and revealed on the run.
The three legs, honestly
Swim — 1.2 miles. The leg with the least to gain and the most to lose. Saving three minutes here is worth far less than arriving at the bike calm. Start wide if the swim start frightens you; the time cost is trivial.
Bike — 56 miles. The discipline that determines your race. Hold back deliberately for the first third. Eat and drink on a schedule rather than by feel, because by the time you feel hungry at this distance it is too late to fix.
Run — 13.1 miles. This is not a standalone half marathon and will not feel like one. Expect to be slower than your open time by a wide margin and plan for it, rather than discovering it at mile three and panicking.
What training for it actually looks like
Most age-groupers get there on eight to twelve hours a week across twelve to sixteen weeks, with consistency mattering more than any individual session. The non-negotiables are a weekly long ride, a weekly long run, and regular bricks — that last one is where the run off the bike stops being a shock.
Where the music goes
Headphones are prohibited on course in most 70.3 events, so none of this is race-day music. It is for the twelve weeks before: the long trainer rides, the dark early starts, the brick sessions nobody looks forward to. Those are the sessions that decide the race, and they are the ones most likely to be skipped.
Questions people actually ask
How far is a 70.3 half Ironman?
A 1.2-mile swim, a 56-mile bike and a 13.1-mile run — 70.3 miles in total. Most age-groupers finish somewhere between four and seven hours.
What is the hardest part of a 70.3?
Pacing the bike. Almost every blown half Ironman follows the same pattern: the bike felt comfortable so the athlete rode slightly harder than planned, and the run fell apart after mile six.
How long should I train for a 70.3?
Twelve to sixteen weeks at eight to twelve hours a week suits most age-groupers. Consistency matters more than any single session; the non-negotiables are a weekly long ride, a weekly long run and regular bricks.
Can I wear headphones in a 70.3?
Usually not. Most 70.3 events prohibit headphones on course for safety. Music belongs in the training block and on race morning before the start.
Training and race information here is general and not coaching or medical advice. Race rules differ by event and change — always check your own race’s athlete guide. IronCommit is not affiliated with IRONMAN® or the World Triathlon Corporation.
More guides
Ironman motivation musicTriathlon motivation musicRunning motivation musicCycling motivation musicGym motivation musicMarathon music5am workout motivationRace day motivation1 hour motivation musicMusic for long runs180 BPM running music160 BPM running musicSwim workout musicBrick workout musicKona Ironman motivationMotivational speech musicIndoor cycling music
New songs before anyone else.
Get every new IronCommit release, training mixes, and race-week playlists by email. No spam. Leave anytime.
By joining you agree to receive emails from IronCommit about new music. Unsubscribe anytime.