Back in the day I taught class on expedition mountaineering. I emphasized that extended trips into remote mountain ranges are as much (if not more so) mental as they are physical and technical. I stressed the need to find “some kind of peace.” If you’re continually fighting your gear, the weather, the mountain, your partners you’re going to, sooner rather than later, end up exhausting your will to continue, and once that will to continue is gone well buddy pack it up and go home.
In the mountains I was good at finding that peace. I was happy to be away from computers, phones and the other diversions of modern living. I embraced the simple rhythm of moving up a mountain. On the bike, however, I’m not so Zen.
I typically don’t ride with a computer, the numbers frustrate me: time goes by too fast and the miles too slow. Power? Don’t even get me started. If you want to suck the joy out of cycling get a power meter. But hey that’s just me. My tactic for long distance riding is to leave the watch at home and only use my bike computer for navigation: I pay no attention to miles and time. I worry that this strategy might not work on the XL.
If I look at the 2024 results I see that my buddy Jan finished in 27:24 at an average pace of 12.85 mph. Jan is a lot faster than I am. I mean a lot faster. So no way am I going to beat 28 hours – let’s just be realistic about this. The max allotted time is 36 hours. Now let’s stop and think about this, the race starts at 3:00 PM on Friday. I’ll probably be awake at 6:00 AM Friday. This means that at the time of the first pedal stroke I’ll have been awake for nine hours. If I do a Jan time I’ll have been awake for 37 hours. If I straggle in just before the cut-off I’ll have been awake for 45 hours. That’s essentially two days, and close to impossible without either a nap or methamphetamine.
Before I start jumping into what’s possible and what’s impossible let’s go back and review my resume:
A number of years ago I did a 24-hour mountain bike race that started and ended at noon. When I crossed the finish line I’d been awake for a bit over 30 hours.
A few years back two buddies and I rode the Festive 500 (500 Km) in just over 27 hours elapsed time. We broke the ride into two segments with a six-hour sleep break in the middle. So that’s a total of 33 hours for 313 miles. So that’s an average speed of 9.5 mph. Coincidentally, this is the slowest possible speed one can ride to finish the XL in the allotted 36 hours.
Two years ago, in preparation for the Unbound 200 my buddy Mykenna and I rode a 300km brevet with the Seattle International Randonneurs which ended up being 252 miles in just under 22 hours for an average speed of 11.5 mph. Push that out to 350 miles yields a finish time of 30.6 hours. Okay this is reasonable.
Assuming that there will be minimal stop lights and stop signs to deal with on course, an average speed of 11.5 mph will require an “on bike” speed of approximately 13 mph in order to compensate for stoppage, which is always longer than one originally plans for. Now back to the original question: can I ride 13 mph without being paced by a bike computer? Maybe. I’m not sure.
So here is the paradox: if I ride with a computer I risk getting stressed, chucking my bike in the ditch and calling my brother for a pick-up, if I ride without a computer I risk fumbling around too long and missing the cut-off.
I think the solution might be to do my long rides in the 13 mph sweet spot to get a feel for the pace. I think that during the XL I will occasionally have to check my pace to see how I’m doing, but if I can find the relative perceived exertion (RPE) required for 13 mph I won’t have to suffer having the numbers continually flashing in my face.