Before I go forward into the desert, I think it's fair to take a look back at all the stats from the past several months.
Wanna know what it takes to train for an Ironman? Here's a very rough approximation.
(Quick notes: My training range is roughly Thanksgiving 2009 to November 17, 2010. Approximately 350 days. I began using my Garmin watch in early April, so the most accurate data actually spans seven months. And I may have deleted data inadvertently from April-June while trying to clean out my watch database. I logged workouts on Training Peaks beginning in early December 2009.)
Garmin miles logged (since April): 2,855.27
Distance from San Francisco, Calif. to Lubec, Maine: 3,452
Average combined speed (swim, bike, run): 11.9 mph
Garmin elevation logged: 124,794 feet
Mt. Everest in feet: 29,035 feet
Distance in feet from ocean level to leaving the Earth's atmosphere: 327, 360 feet
Calories burned: 90,646
Based on a 2,000 calories/day diet, equivalent days of calories burned: 45.3 days
Training Peaks Hours Logged: 608/660 (still have 14 hours of training to complete this week, including race)
Percentage completed: 92% (not including upcoming hours this week)
If I trained non-stop, the equivalent in days would be: 25.3 days
Bike: 164.3 hours (27%)
Run: 152.7 hours (25%)
Swim: 109.2 hours (18%)
Classified as "brick" hours: 79.1 hours (13%)
Race hours: 34.0 hours (6%)
"Custom" (usually yoga/strength): 42 hours (7%)
No matter how I slice it, that's a LOT of time spent training for one event.
Time to go see how that training pays off.
My next post will be in Arizona.
Four days and counting.