Four laps of a 25 mile loop through the McDowell Mountains, a hundred miles of desert singletrack with the start and finish as your pit every lap. Below is the day the way the model rides it: your finish at three paces, where a fast rider gains on you, the climb you meet four times, and a fuel plan for thirteen hours of cutoff.
No card. No account needed to try it.
Aravaipa's event page lists 100 miles and 3,708 ft, 25 miles and 927 ft a loop, through McDowell Mountain Regional Park. The figures above are the model's own reading of a Strava route of the 25 mile loop, with elevation read from AWS Terrain Tiles (it agrees with the file's own to within 1%). Their own 15 mile relay loop is listed at 1,026 ft, more than the 25 mile loop, and a Strava file of the loop measures the same as the terrain does, so the listed figure looks low. Start 6:00 AM, cutoff 13 hours, aid at the start and finish, plus a fully stocked station at Granite Tank on the Pemberton Trail. The same day runs a 50 (two loops), a 25, a 15, an 8 and a 9 hour relay on a 15 mile loop.
The rider the app opens with, 185 lb, 280 W FTP, 20 kJ reserve, at the app's three pace settings, beside a fast rider. Your own numbers move all of it.
Riding it steady costs 1 hour 3 minutes against moderate; riding it aggressive saves 32 minutes and leaves your anaerobic reserve about where moderate does. Each loop takes about 2:16.
150 lb, 350 W FTP, 28 kJ reserve, aggressive
6:41258 W average, 15.7 mph
185 lb, 280 W FTP, 20 kJ reserve, moderate
9:03180 W average, 11.6 mph
The deficit grows fastest from mile 27 to mile 45, 29 minutes of it in 18 miles. It takes in climb 1 on the second loop: watts buy the most time where gravity is what you are paying, and on the flat and the descents the gap barely moves.
| Where | Climb | Grade | Time | Power | |
|---|---|---|---|---|---|
| 1 | 16.1 to 18.1 mi of each loop | 331 ft | 3.1% | 14:25 | 213 W |
For the guest rider at moderate pace. Ranked by what each one costs as a share of the ride, not by how tall it looks, then listed in the order you reach them.
About 77 g an hour at moderate pace. Each feed goes in about 20 minutes before the model says you need it, on an easier stretch rather than on a climb, and none in the last 20 minutes, where it could not be absorbed before the line.
| Feed | Mile | Into the ride | Carbohydrate |
|---|---|---|---|
| 1 | 5.2 mi | 0:27 | 15 g |
| 2 | 19.3 mi | 1:46 | 66 g |
| 3 | 26.8 mi | 2:19 | 54 g |
| 4 | 31.5 mi | 2:43 | 40 g |
| 5 | 35.8 mi | 3:10 | 46 g |
| 6 | 41.2 mi | 3:38 | 46 g |
| 7 | 49.8 mi | 4:18 | 67 g |
| 8 | 57.7 mi | 4:58 | 67 g |
| 9 | 62.1 mi | 5:26 | 67 g |
| 10 | 67.4 mi | 5:54 | 75 g |
| 11 | 76.0 mi | 6:34 | 75 g |
| 12 | 84.0 mi | 7:14 | 75 g |
From the burn the model puts on this course: work along the route, carbohydrate share from the pace, what your glycogen holds for your weight, and 400 kcal an hour through the gut for a glucose and fructose mix. Move the feeds to the aid stations you will actually use; the plan updates.
Set a goal time for the Frenzy 100 and the app reads your recent rides against this course: a likely finish range, its middle, and your goal marked likely, possible, a stretch or unlikely. With a power meter from measured watts; without one, from your speed on your own ground.
What your best riding of each week would finish in on this route, so you can see whether the training is moving the number, not just adding miles.
Each of the climbs above, checked against what you actually ride: covered, mostly covered, thin or not ridden, so the next session goes where the race will hurt.
The route is cut into short segments and each is solved for the speed your power holds against gravity, rolling resistance for the surface, and air, thinner at altitude. On twisting trail your speed is capped by how fast you can corner, and on the far side of a climb you keep the speed you carried in. The time on each segment is added up, the reserve you spend above threshold and win back below it is tracked the whole way, and the carbohydrate is burned where the work is done. It is fitted against recorded races: on a Chequamegon 40 validation ride it predicted 2:24:28 against an actual 2:24:20.
For the guest rider the app opens with (185 lb, 280 W FTP, 20 kJ reserve), the model puts it at 9:03 at moderate pace, 10:07 riding steady and 8:31 riding aggressive. A fast rider at 150 lb, 350 W FTP, 28 kJ reserve is around 6:41. The cutoff is 13 hours. Put your own weight and fitness in and it forecasts yours.
Aravaipa's event page lists 3,708 ft for the Frenzy 100. The route file the model rode measures 6,362 ft over 105.0 miles, 1,591 ft a loop, between 1,576 and 2,472 ft. Their own 15 mile relay loop is listed at 1,026 ft, more than the 25 mile loop, and a Strava file of the loop measures the same as the terrain does, so the listed figure looks low.
Climb 1 on the chart, 16.1 miles into the loop: 331 ft at 3.1%, 14:25 at 213 W for the guest rider at moderate pace, and you ride it four times.
At moderate pace the plan is 693 g of carbohydrate over the ride, about 77 g an hour, in 12 feeds. Each goes in about 20 minutes before the model says you need it, on an easier stretch, and the last is at mile 84 so it is absorbed before the line.
The model rode it as singletrack throughout, the app's starting assumption. The organizer describes wider rolling desert terrain, a sandy wash and some rock gardens. Surface is worth 13 to 17% of a finish time, so tag the sections in the app and the forecast follows.
Yes. Load the route and run the whole plan as a guest, no account. Pro ($9 a month, or $59 a year) adds saved routes and plans, a saved athlete profile and the head unit export.
Same model, one page per course.
Same course, your weight, your fitness, your pace. Two minutes of setup now.