Showing posts with label Ironman Bike Course. Show all posts
Showing posts with label Ironman Bike Course. Show all posts

Ironman Kona 2017 Results Analysis: Finish Times, Splits, by Age Group, vs Previous Years

Ironman Kona 2017 saw a record 2235 athletes cover the grueling 140.6 mile course, finishing in an overall average time of 11:39.
  • It was tougher than the average 11:31 finish time spanning the 16-year period 2002 to 2017, 
  • A near-record 132 athletes did not finish, more than 80 qualifiers did not start  
  • Average splits indicate athletes suffered most on the run -- 1:11 swim, 5:49 bike, 4:27 run
  • Things could have been worse -- a far cry from 2004 finishers' 12:06 experience in the wind-laced, blast-furnace heat, 
  • But it was a long way from what would be considered fast, a full 25 minutes slower than the wind-aided 11:06 average time turned in by finishers in 2013. 
We dove into details of the 2017 race, overall, by split, by division, and did side-by-side comparisons across each dimension going as far back as 2002. For extra credit, we conducted a bike vs run correlation analysis, illustrating the degree to which bike speed strategy impacted run splits for each athlete.















For more, see our Comprehensive Historical Ironman Kona Coverage.

Toughest/Easiest Ironman Bike Course: Comparing 25 Ironman Races




What's the easiest Ironman triathlon bike course? Which is the hardest? From the most recent race data, St. George, UK and Lanzarote are easily toughest, followed by Cozumel, Lake Placid and Wisconsin. Austria, Arizona and Florida are among the fastest courses. 

Note that outside factors, such as weather, wind, or ability of athletes in the field will influence average times. Kona is harder than most, but qualifiers will, naturally, ride faster than most.  We think that the Austria time is probably deceptively fast. Unless the course was short or featured tailwinds, having ridden all four, we'd say it's harder than Arizona and Florida, and equivalent to New Zealand.


Ironman Chattanooga 2016 Results Analysis by Division, by Split, DNS, DNF, Compared to 2014 and more

Quite an astonishing day at Ironman Chattanooga 2016. Relentlessly harsh heat led to a 13:59 average finish time for 1688 triathletes, and an exceptionally high 19% DNF rate, considering all finishers under the typical 17 hour Ironman cutoff time.

But, wait: the official cutoff time, it turned out, was determined to be 16 hours 15 minutes (I have no idea why). That meant another 50 or so athletes who happily finished under 17 hours but after 16 hours 15 minutes got the staggering news they would not be considered Ironman finishers, but instead were classified DNF.

My analysis and charts reveal how brutal it was out there for all Ironman Chattanooga 2016 triathletes. And it's based on results for all who finished under 17 hours.














Ironman 70.3 2015 Rio Results Analysis

Ironman has added several new 70.3 events since our most recent detailed and comparative analysis of half Ironman Rankings.

We'll be catching up as time permits, here's a summary of 2015's Ironman Rio 70.3. At a 5:56 average finish time, it's slightly faster than average, the number of finishers, at 797, is on the low end.

Here's our Analysis of the Rio 70.3 event in 2015.







Ironman Lake Placid Bike Course: What to Expect

By Raymond Britt

The Ironman Lake Placid Bike course is one of the most beautiful, but also one of the toughest 112-mile Ironman rides you’ll ever experience. While the course features exceptional scenery and some very generous downhill sections, the course can demoralize and defeat riders on the last 10 miles of each lap. [see how IM LP bike splits compare: Ironman Bike Course Split Comparisons]

In short, you can have a great ride on the first three sections, but you’ll give it all back on your way past Whiteface Mountain to transition. So pay attention -- this is what a 5:36:12 Ironman Lake Placid bike split looks like:

Lap 1  Distance Split Time/mile mph
Keene  14.0 0:34:30 0:02:28  24.3
Hasleton  15.0 0:44:00 0:02:56  20.5
Out/back  14.0 0:38:30 0:02:45  21.8
T2  13.0 0:47:00 0:03:37  16.6
 56.0 2:44:00 0:02:56  20.5
Lap 2  Distance Split Time/mile mph
Keene  14.0 0:36:14 0:02:35  23.2
Hasleton  15.0 0:45:09 0:03:01  19.9
Out/back  14.0 0:41:29 0:02:58  20.2
T2  13.0 0:49:21 0:03:48  15.8
 56.0 2:52:12 0:03:05  19.5
Total  112.0 5:36:12 0:03:00  20.0

With a carefully constructed riding strategy, you can ride with strength through the roughest sections, complete the course with a solid bike split, and be ready to begin your marathon with energy to spare.  

That’s what’s presented here, in the form of a 5:36:12 bike split I rode in one of my six races at Ironman Lake Placid. I’ll break the course down into sections, describe what you can expect in each one, and provide actual splits to help guide your riding strategy.

So let’s get down to business.  Here’s everything you need to know about the Ironman Lake Placid Bike course. [For reference: Ironman Lake Placid Bike Course Map]

For starters, the key thing is to break the course down into manageable sections. In each lap, there are four clearly defined segments to consider (distances are approximate):

1.     From T1 to Keene: 14 miles
2.     From Keene to Jay to Wilmington: 15 miles
3.     The Haselton Road out-and-back: 14 miles
4.     Whiteface Mountain climb to transition: 13 miles

As we go through these segments, it’s important to consider the parameters: my complete split was 5:36:12, or about 20 miles per hour overall.  I covered the first 56-mile lap in 2:44:00, or 20.5 mph. I slowed on the second lap to 2:52:12, or 19.5 mph. 

The data examples, e.g., noting that it takes 20 minutes to climb from miles 3 to 8, are in this context. These are my actual times; yours may well vary. So view my data as a relative benchmark. If you hope to ride a 6-hour split, for example, adjust my data to meet your expectations.

Segment 1: Transition to Keene – 14 miles

This first segment on the bike course is a mixed bag of uphills and downhills, with an emphasis on the downhill: a screaming descent to Keene.  This segment is best seen as an additional four sections.

Miles 1 to 2 -- T1 to Ski Jumps. Walk your bike through the transition area and do not mount it until you cross the official line in the parking lot on the south side of Lake Placid High School.

Once you clip into the pedals, you’ll immediately roll down a steep decline from School St. to Colden Ave. You’ll be excited to start, but be very careful here. There’s a sharp left turn at the base of Colden, taking you onto Route 73. Go too fast at the start, and you’ll wind up crashing into hay bales before you’ve gone 200 meters.

As you get going on Route 73, take some time to make sure you’re set on the bike. Nutrition in place, pull up arm warmers if you’ve got them, straighten the sunglasses, just settle in. Without trying to, you’ll ride fast.

It’s less than six minutes out of town, at 21.8 mph, and then you reach the ski jumps. 

Miles 3 to 7– High Peaks These miles are a series of steady, manageable ascents of 150 meters or so,  overall. Don’t push the pace here. Find a steady rhythm in a good gear, and plan on riding for 18 minutes or so.  This climb is actually a good thing to settle all riders down. Few feel like passing, and you shouldn’t  either.

You’ll know this section is almost over when you see a sign for the Mt. Van Hovenberg Recreation Area on your right. Just ahead will be one gentler incline. Consider this segment of 5 miles as a warm-up. And not a fast one -- I finish it at an average speed of 15mph.

Miles 8 to 10 – Cascade Lakes. At about the 8-mile point, you’ll enter a two-mile section of slight rollers that pass the scenic Upper Cascade Lakes on your right. 

Now’s the time to hammer a little. Let gravity work for you -- pedal hard on the slight downhill grades and you can pick up speed and start passing riders. I cover this part in 5 minutes at 24.0mph.

When you reach Lower Cascade Lake, also to your right, you, yourself, are about to cascade downhill at a frightening rate.

Miles 10 to 14 – The Screaming Descent. These are the miles you’ve been hearing about and looking forward to: the screaming descent to Keene. It’s the fastest 6 minutes you’ll ever experience on an Ironman course, and that equates to 40mph.

And I ride this part cautiously. Riders will pass you going even faster.  I don’t see the risks of riding 50mph as worth saving a few seconds.

If the weather is wet and/or windy, be careful, stay under control. Accidents on this stretch could be very nasty, what with all the downward momentum.

Sometimes riders experience a shaking of the front wheel, at high speed, and it's hard to control. To avoid this, try to keep your bike stable by hugging the frame with your knees on the way down.

Be realistic in knowing that this descent will not make much of a difference in your overall bike split. If you ride it 80mph, you save only three minutes. So be safe, enjoy it, and it’s on to the next major segment.

Adding it up from the start, I cover these first 14 miles at 24.3 mph overall, without working too hard.

Segment 2: Keene to Wilmington – 15 miles

Segment 2 includes the relatively flat and fast 10 miles from Keene through Upper Jay to the adjacent town of Jay, followed by a generally uphill stretch of five miles from Jay to Wilmington.

Miles 15 to 24 --  Keene to Jay. This segment of eleven miles may be the longest, easiest stretch on the course , but you have to work a little. You can start riding at speed here, but, again, don’t hammer. We’re trying to be smart, and you need to keep yourself in check.

You’ll enjoy the scenery of rocky streams for much of your ride from Keene to the town of Jay, as the course meanders gently right and left, through dense wooded passages and wide open spaces.

Road signs will give you a sense of where you are: you’ll reach Upper Jay after about the 20 mile marker, and four more miles to Jay.

Ride these miles fast, feel free to push it a little. A little. Even while not hammering much, I ride these 10 miles to Jay at around 22 miles per hour.

Miles 25 to 29 -- Jay to Wilmington. When you enter Jay, you’ll take a hard right turn onto Route 86 toward Wilmington. From there it’s a 5 mile trip to Haselton Road. As you approach the turn, get into an easy gear, because you’ll need it for the 1-mile climb. Like the initial climb on the course, settle in here, and just spin.

Once over the top of this 1-mile climb, the next four miles are rolling and fun, but still challenging. On balance, you’ll be mostly climbing as Whiteface Mountain begins to come into view on the horizon, to your left.

I complete these 5 miles in 17 minutes, 17.6 mph.  It seems slow, but others will be riding slower. You can use these miles to your advantage.

Make sure to get the most of the declines. Begin to pedal hard as you crest the hills here, and hammer on the way down. You’ll pass many riders this way. They’ll coast; you’ll pass easily without working too much harder. Make the hills work for you.

And my totals for this second segment – Keene to Jay to Haselton Road -- 14 miles, 21.6mph. Remember: the overall speed on this segment could be slower, unless you take advantage of the declines on the last few miles.

Average speed from the start through 29 miles: about 22mph. Fast, but still in control.

Arriving in Wilmington, you’ll be zooming at a fast clip toward the hard right turn onto Haselton Road. You’ll have to be careful on the turn because you’ll only have one lane; the other lane is occupied by riders coming the other way. Accidents do happen at this turn. Sit up, apply the brakes, and be careful.

Segment 3: Haselton Road Out-and-Back  -- 14 miles

The next fourteen miles are, generally, a fast and fun ride. It’s also unique from the rest of the bike course, with nearly the entire distance under the share of tall trees. I remember this whole section as being the greenest part of the course. Really nice, visually.

Miles 30 to 36. This can be another fast segment. The miles are gently rolling, for the most part. Again, get the most out of the rollers by pedaling over the top and hammering down the other side.

Make gravity work for you. That’s how you’ll continue to ride faster here, and elsewhere on the course. Take the forward momentum, lock into a big gear and go.  This tactic may make the difference between getting a Kona slot or not. Seriously.

The course elevation map says otherwise, but I always feel the outbound portion declines overall.  At least it seems to favor speed most of the time. But things to change in the last mile before the turnaround, when you do climb about 150 meters.

You’ll know you’re approaching the turnaround as the volume of riders heading the other way will grow. It may seem like hundreds pass you on their way back, and it may feel very frustrating. Don’t let it get to you.

If you’re riding smart, you’ll probably pass one or two hundred on the second lap. Seriously. Let them crush the first lap; many of them will suffer for it on the next 56 miles. You won’t.

Miles 37 to 43. When you get to the turnaround, load up on nutrition and liquids.  While heading back on the return 7 miles, you want to be fueling and preparing for the last 10 miles of the first lap. 

Also, soon after you pass the 40-mile marker, you’ll have a very taxing climb, perhaps the steepest on the course. When you get there, you’ll know it. Don’t panic. Get in your easiest gear, and just pedal smoothly and consistently.

I ride the 14 mile out-and-back on Haselton Road in 38 minutes, an average speed of 22mph. I’m usually pretty consistent: 19 minutes out, 19 minutes back.  Again, the difference is how I work the descents. A little extra effort pays dividends with a lot of speed.

At this point on the course, roughly 43 miles have gone by in about 2 hours, at an average speed of 21.8mph.

What was I saying earlier about Lake Placid being the toughest course? Seems pretty easy through 43 miles.  That’s because . . .

Segment 4: to Whiteface Mountain and T2 – 13 miles

The large orange ‘Road Closed’ sign is marks the beginning of the end. Everything changes when you pass the orange sign. Buckle up, time to face the beast.

Mile 44. Mercifully, the first mile or so is relatively flat, giving you time to hydrate, relax, and get ready to climb.

If there’s any good news to share, it’s that the 300 meter overall elevation gain is spread out over the next 10 miles, and therefore doesn’t slam you too hard at any one place.

You will work your way upwards, but it’ll have a sort of switchback feel, without switching back. It’s more like a ½ mile incline, ¼ slight descent, and the like.  Over and over. 

You will see your average speed plunge. It just will. You’ll have to be mentally ready to give back a lot of the speed you had through 43 miles. But so will everyone else. And those who ride these final miles strategically will be that much closer to a great bike split.

Miles 45 to 48. You may be hardest hit in the beginning. I ride miles 45 to 48 at an average of 15mph. You just don’t want to fight it too much. It’s too early. Sit up in the saddle, get out of the aero bars, try to relax and just spin as consistently as you can.

Miles 49 to 52. Things should get better for you here. You’re still working hard, but you’ll have gotten used to the grind. I gain speed here, riding it a couple notches better, at 17mph.

Miles 53 to 56. You’ve heard about the Bears, no doubt. Baby, Mama and Papa Bear. These are the names given the final, challenging climbs to face before the lap is over. Unless time has worn away the paint, you’ll spot the name of the next Bear before you get there. You will see it because you will be looking down much of the time, at that point. You’ll be digging for everything you’ve got as you slowly spin toward the finish.

The lesson you’ve hopefully learned by now is that going uphill offers a significant opportunity to gain speed and pass people on the other side. The Bears each make you work long and hard, but when you crest the top, each time, pedal hard and hammer down the other side.

Everyone else will be gliding. You’ll want to glide. Don’t. This is easy speed, easy chances to move yourself higher in the race standings.

Still, you will be gasping for air one way or the other when you make what will be an extremely slow right turn from Route 86 onto Northwood Rd. You’ve made it at that point, really. The next mile back into town is a fast one as the adrenaline kicks in.

I ride miles 53 to 56 at an average of about 18 miles per hour. These miles are perhaps the most daunting in terms of work as well as how late in the race they hit you.  But you can hit back, and you can ride well. Getting to 18.5 proves it.  That’s the difference a well-constructed riding strategy can make.

You’ll know you’ve made it through one of the toughest Ironman Bike courses in the world. You’ll hear the cheer of the crowd as you near the transition area, and it will bring a smile.

Except for one thing: you’ve got to do it again.

At the end of lap 1, with 56 miles complete, I was at 2:44:00, an average of 20.5mph.  A good start, but I’ve never found it easy to repeat it.

Twice the Fun: Lap 2

Lap 2 for me was twelve minutes longer, 2:56:12, averaging 19.5 mph. Shoot for that. Map a strategy for lap 2 that has you riding about 5% slower. Total for 112 miles: 5:36:12, just about 20mph.

The second lap feels relentless, especially the final 13 miles. It’s these last 13 miles that makes Ironman Lake Placid one of the toughest out there. 

When you’re at 100 miles complete, and you’re climbing, you’ll know what it’s like in the Tour de France: not the least bit easy, but worth it in the end.

It’s a fantastic feeling to finish 112 miles in Lake Placid, and you’ll feel the rush of excitement as you head into T2 to drop off your bike.

If you’ve ridden well, according to your race strategy, you’ll have plenty left over to run a sub-4 marathon. Yes, you will.


Ironman Wisconsin Triathlon Bike Course: 5:54 Bike Split

Excerpt from the book "Racing Ironman Wisconsin: Everything You Need to Know"

To many triathletes, the Ironman Wisconsin bike course has appeared relatively easier than other north American courses such as Ironman USA Lake Placid and Ironman Canada, at least when considering course maps. But when triathletes arrive to race Ironman Wisconsin, they are inevitably surprised at the difficulty they face on the bike course.[for proof, see Ironman Bike Course Average Times]

While the elevation changes on paper are quite more significant in Lake Placid, the tricky subtleties in Wisconsin make it such that an overall bike split on both courses can be very similar.

What the Ironman Wisconsin bike course lacks in vertical elevation challenges, it more than compensates with the challenge of never letting up; the course chips away at you with a continuous series of slight gains, turns, and technical challenges that constantly serve to damper hopes for a bike course PR.

What It's Like

On September 9, 2007, I returned to complete my fifth Ironman Wisconsin, my 29th Ironman race since July 1997.  

This time, I wanted to do something different. Experience the Ironman in a unique way. And I did: I shot photos on the bike course, and I tracked the entire 112-mile ride with a Garmin 405 GPS Watch. 

As a result, the 2007 experience presented here gets to the nuts and bolts of the bike course, perhaps Ironman Wisconsin’s most daunting feature.

Personal Race Data Summary

My overall bike split in Ironman Wisconsin 2007 was 5 hours, 53 minutes and 57 seconds, about 19mph.
  • Overall Splits: First 56 miles: 2:52:49 riding time, 19.44 mph; Second 56 miles: 3:01:08 riding time, 18.68 mph. 
  • Equipment: Softride Rocket 650TT, Zipp 909 wheels, Sidi shoes, Look pedals, 2 bottle cages and 2 pouches. 
  • Fueling: 4 PowerBars and 8 GU packets on bike; bananas every other aid station; water/Gatorade every aid station. 
  • Hammer Factor: limited; I rode comfortably; never pushed it too hard, never bonked, never suffered. But I also did not hold back; it was a solid ride for my fitness at the time.
Ironman Wisconsin 112-Mile Bike Course: Rider’s Perspective



The 112 mile Ironman Wisconsin bike course starts fun and fast, then gradually eats away at you over the miles. It throws no serious difficulty your way, but it refuses to yield over most of the course. Go out too fast, and you can suffer later.

With that as a sort of warning, the first 16 or so miles, out to the two-loop section, are a good warm-up, taking riders to the west of Madison, from the small city toward classic Midwestern farmland. Some small rollers stretch your leg muscles, and a couple of pretty steep but short downhills will give you a speed boost, but also provide warning that they may hurt you a little on the way back. Here’s my data from those first miles:

Reaching the 39-mile loop section, you’ll continue west on relatively tame terrain until you approach the town of Mt. Horeb. Approaching mile 30, you’ll be faced with about a 1⁄2 mile long climb that veers to the left then right, where you’ll be greeted by aid station volunteers. Get what you need, then prepare for five miles of work.

Miles 30 to 35 (and 70 to 75 on the return trip) take riders through relentless up-down riding that I like to call The Rollercoasters of Witte Road and Garfoot Road. Passing between and through farms, these miles toss it all at you: fast declines followed immediately by sharp uphills again and again, with short stretches of reasonably flat road connecting the little challenges.

At first, it’s fun. Then getting over the next hill gets tougher each time. You’ll think you’re done, then there’s more. You’ll see when you get there. You don’t want to be bonking the second time you ride this section. It’s a bad place to be on the rocks.

Next up is a slightly dangerous fast, swerving downhill on northern Garfoot Road. You’ll wish you can take it at full-speed, but only the most expert of riders can do it. It’s too easy to lose control on the sharp turns here. Sacrifice a few seconds for better control.

The course flattens out on the top half, east-bound road for a few miles, allowing you to relax a little. You’ll need the break, because when you make a right turn at Country Road KP to begin a southward path toward the start of loop two, the course’s most challenging climbs await.

The climbs – at Old Sauk Pass and on Timber Lane – aren’t very long, but they can be quite taxing. When you arrive there, settle into your easiest gear, sit back, and pedal as efficiently as you can.

Stay steady for the next few miles until you reach the town of Verona, where you'll be greeted by a cheering crowd that treats you as if you are a Tour de France rider. Savor the moments, smile at spectators and enjoy your short time there. Because after it's over, you get to do it all again on lap 2.

You'll finish lap 2 at about 95 miles, with 17 more to go. Depending on the heat, wind and your nutrition and hydration at that point, those last miles may be relatively breezy or can be very challenging.

Don't let the apparent downhill back to town on the race website course map fool you. It's more work that you'll expect. Be prepared mentally and physically at that point, and you'll do fine.

For more, return to our Ironman Wisconsin coverage.

Ironman Wisconsin Bike Course: How to Ride a 5:54:37 Bike Split

The Ironman Wisconsin bike course is every bit as deceptively challenging as you have heard. But the confusing part: the course elevation chart looks so tame, so flat relative to Ironman Canada, Lake Placid and many others. Why is it so hard?

See chart below, actual mile-by-mile speed, maximum speed and cumulative average speed. It's not steep hills that get you; it's the constant choppy turbulence of the course that wears you down.

This is how to ride a 5:54:37 bike split at Ironman Wisconsin. For video of this ride and more, see Ironman Wisconsin: 5:54 Bike Split, Live.





Ironman St. George 2011: Correlation Between Bike and Run Splits

With an average marathon of 5:10 and bike split of 6:41, Ironman St. George 2011 is at the top of RunTri's Toughest/Easiest Ironman list.

When it comes to balancing the bike (x, and 50% of total race time) and run (y = 77% of x), our analysis of IM StG 2011 highlights four groups: 1. Fast and Balanced; 2. Energy to Spare for a fast run; 3. Left it on the Bike Course; 4. Smooth and Steady for a slow bike and slow run.


You want to be #1 or #4.  In comparison to similar analyses of other Ironman races, the finishers at Ironman St. George seem to have struck a clear, if conservative balance between bike and run. Translation: it appears fewer blew up on the run after riding too hard on the bike course.

As the R^2 is .45, the correlation is low overall, but in an Ironman, all that really matters is reaching the finish line. For more see Ironman St. George and RunTri's Race Analysis Index.

Half Ironman 70.3 Bike Times as Percent of Finish Time: The 50% Rule

As you prepare your training plans and consider your racing schedule, if you've got a half Ironman race on the calendar, you're trying to decide how much time to spend swimming, biking and running during the year.


One of the factors that should influence your thinking is this: your half Ironman bike time may very well end up being 50% of your total finish time. Of course, as shown in the chart, there is some variation by race (Brazil, Germany, Mooseman and UK) but for the most part, the 50% rule holds. Same is true for full Ironman races: 50%.

Ironman Bike Split: The 50% Rule

As you prepare your training plans and consider your racing schedule, if you've got an Ironman race on the calendar, you're trying to decide how much time to spend swimming, biking and running during the year.


One of the factors that should influence your thinking is this: your Ironman bike split may very well end up being 50% of your total finish time. Half your Ironman race will be on your bike; be ready! Of course, as shown in the chart, there is some variation by race, but for the most part, the 50% rule holds. Same is true for half Ironman 70.3 races, too: 50%.

Ironman Lake Placid 2010 Bike Course Changes

RunTri believes the course detour -- details below -- will lead to faster bike splits at this year's Ironman Lake Placid. I'd expect it will reduce pro bike splits by 10 minutes. Reason: Route 9N is the flattest and most consistently fast section of the bike course. How fast? Ironman Arizona and Ironman Florida fast.

"Ford Ironman Lake Placid will be required to make alterations to the bike course for this year's race due to road contruction. Changes to bike course of Ford Ironman Lake Placid triathlon scheduled for Sunday, July 25 will impact residents of Jay and Ausable Forks. Due to the bridge project over the Ausable River on Haselton Road in Wilmington, Route 9N from Jay to Ausable Forks will now comprise a 10.2 mile portion of the 56 mile bike circuit that racers will travel twice. Both lanes of Route 9N will be closed to non-essential vehicle traffic on race day between 8 am and 4:30 pm." -- from www.ironmanusa.com July 18, 2010

Benchmarks: Easiest and Toughest Ironman Bike Courses by Age Division

The 112-mile bike courses at Ironman Lake Placid, Ironman Wisconsin and Ironman Canada are among the most challenging routes on the Ironman Circuit, as the average bike splits from seven 2009 Ironman races indicate. Having raced on all course, I can confirm these averages are accurate.

What bike split might you expect in your next Ironman? See averages below by race and age division for Ironman 2009 events in Lake Placid, Wisconsin, Canada, New Zealand, Arizona, Florida and Kona.

For more, see Comparison of 15 Ironman Bike Course Average Times.

Toughest/Easiest Ironman Triathlon Bike Courses

By Raymond Britt

Riding 112 miles anywhere, any time, especially after a 2.4 mile swim and before a 26.2 mile marathon, is no small task. In that light, there really is no such thing as an easy Ironman bike course. They’re all hard. For at least 6 hours, on average. Of course, there are notable differences, when you look at the averages. Here’s how bike splits at seven of the more popular Ironman races compare, overall:


[For more detail, see Average Ironman Bike Course Splits by Race and Age Division]

The Ironman Lake Placid Bike course is one of the most beautiful, but also one of the toughest 112-mile Ironman rides you’ll ever experience. Everything you’ve heard about Ironman Wisconsin is true: it’s much harder than you expect. Ironman Canada is also considered to have one of the toughest bike courses in the world.

If you’re looking for a faster bike split, New Zealand, Arizona and Florida are the places to race. But there are some challenges to consider. In New Zealand, your cycling challenges are more likely to be weather related. In Arizona, you’re likely to deal with head winds half the time. And in Florida, you’ll be riding under the blazing sun for most of your 112-mile ride.

Personally, I rate Lake Placid and Wisconsin courses as tied for toughest bike course, having ridden nearly identical bike splits in both races, year-by-year. And of course, the extremely fast Kona average is skewed by an elite field of extremely fast triathletes.

I consider Kona’s degree of difficulty akin to Ironman Wisconsin; both courses are far more challenging than they appear on any elevation chart. In Wisconsin, the never-ending undulation gets the best of many riders; in Kona, it’s the headwinds on the last 30 to 40 miles that can crack the spirit.

As for the 'fast' courses like Ironman Arizona and Ironman Florida, consider this: an Ironman bike split record has never been set on either course.

Finally, there's also the consideration of the individual rider. I've ridden nearly identical bike splits on several courses, regardless of the degree of difficulty,  during what I call my Ironman 'Finisher' and 'Kona Qualifier' phases.

In my first Ironman races, the 'Finisher' phase, I rode roughly 6:15 splits in Canada, Germany, Lake Placid. During the years I qualified for Kona, I was riding 5:25 to 5:35 bike splits on the tough courses like Lake Placid and Wisconsin, but also in Austria, Florida and Arizona.

In my case, 112 miles was 112 miles, hard no matter where they were. My training and strategy put me in a position where I was going to ride a 5:35, no matter the course. The same may be true for you.