Home Blog Page 17

Zwift Camp: Build – Stage 5 Walkthrough

Zwift Camp: Build – Stage 5 Walkthrough

Zwift Camp: Build is underway: a 5-stage route-based workout series, with each stage lasting one week and focusing on developing power over a specific time interval.

My plan is to do each of the five workouts before their weeks begin, so I can write a post unpacking the workout and delivering some tips along the way. This post covers Stage 5’s workout on Watopia’s Road to Sky route, which takes you up the massive Alpe du Zwift KOM. Let’s roll!

Stage 5 Intro: Summit Challenge

The fifth and final stage of Zwift Camp: Build is focused on “One 60-minute showdown,” according to the event description. We’re climbing Alpe du Zwift, a 12.2km, 8.5% climb modeled after France’s infamous Alpe d’Huez.

This is by far the longest effort in Zwift Camp: Build. We began this Camp with short sprints in Stage 1, went to longer sprints in Stage 2, then (sort of) VO2 power in Stage 3, followed by 10-20 minute power in Stage 4. Stage 5, for many riders, will be around a 1-hour interval, making it a true threshold effort.

Apart from the mental and physical challenge of a long threshold effort, the only tricky part here is pacing. You’ll do best if you know the wattage you’re aiming to hold on the climb, and this will also let you pick a pace partner to ride with.

The RoboPacers each have their own pens, with the faster bots leaving first. While everyone is visible on course, chances are very few riders from the slower groups will catch the faster ones ahead.

Here are the RoboPacer options:

  • A – 50 Minutes: 4 W/kg
  • B – 60 Minutes: 3.3 W/kg
  • C – 70 Minutes: 2.8 W/kg
  • D – 90 Minutes: 2.1 W/kg
  • E – 115 Minutes: 1.7 W/kg

The stage is built around Watopia’s Road to Sky route, which begins with an easy descent into the Mayan Jungle.

The bots go much slower during this warmup portion, so be sure to stay with your bot (it’ll be easy) if you want to start the Alpe climb next to them.

The route ends atop the Alpe, but you can keep pedaling and descend back to ground level afterward. You earned the distance!

Stage 5 Walkthrough

Once again, I was going into this ride with legs that were less than fresh. Luckily, Zwift had set up the RoboPacers in such a way that the B bot was perfect for what I could do in terms of a longer effort!

The B bot’s 60-minute climb pace, at 3.3 W/kg, seemed like it would pace me nicely on the early part of the climb. Then I figured I’d have a bit more left on the upper slopes, so I could push a bit harder, drop the bot, and negative split things overall.

After 9 minutes of easy warmup spining through the Jungle, we crossed the start line for Alpe du Zwift, the bot kicked up the effort, and we got to work:

I settled into my target pace, finding the best gear and staying close to the bot.

After climbing for several minutes, I realized that this setup was working out really nicely. While the Sector Stats HUD on the left let me easily see my average power for each of the 21 sectors, the green bot and its big ol’ beacon made it easy to see if I was holding my target pace.

A warning, though: these bots are relentless, and if you ease up, you’ll get dropped!

Hairpin Note

The spot where you’ll notice the relentless nature of the RoboPacers the most is on the flatter gradients that often occur on the hairpins at the end of some sectors. When the road flattens, your power will naturally drop as trainer resistance drops. But the RoboPacer won’t change its output!

I found myself losing several meters to the bot on each flat section, until I began to consciously increase my power when I felt resistance ease.

Doing the Work

I stayed just a few meters ahead of the B bot for the first 15 sectors. I also opted not to steer, as the pace I was holding felt good and I didn’t need to gain further advantage on the unsuspecting robot. (Note: steering can reduce the overall length by around 500 meters, so it’s no small thing!) If you’re struggling to keep up with the bot, though, a few cut corners may be just the trick you need.

Nearing the finish, 40 seconds ahead of the bot

My heart rate had risen steadily from 140 at the bottom of the Alpe to 160 with 6 sectors to go. That’s when I decided to bump up my effort, drop the green robot, and sail to victory!

I went from averaging ~270W to ~280-285W, and began putting time into the bot. I kept pushing, getting my heart rate up to 170bpm as I crossed the finish line. My final climb time was 58:21, and the bot finished about 40 seconds behind me. (So it’s worth mentioning that the bot climb times are estimates only, probably accurate within a minute or so.)

Watch My Video

Results!

I received an automated email after finishing this stage, which included a link to a web-based results dashboard: zwift.com/zwift-camp-build/dashboard

Good to see Zwift getting this launched, even if it came a bit late.

Suggestion Box

I’ve been offering improvement suggestions to Zwift for each of these stages, and my suggestions for stage 5 would be the same as stage 4: add messaging, and improve the event description (read those suggestions in more detail here).

Apart from that, I want to take a moment to talk about the overall Zwift Camp: Build experience now that I’ve finished the final stage.

Overall, I’d say Zwift Camp: Build offers some good sessions for riders looking to challenge themselves with maximal efforts across particular time intervals. Three stages do this well:

  • Stage 1 with its 4 neuromuscular sprints on Glasgow’s Champion’s Sprint
  • Stage 4 for a suprathreshold effort on The Grade KOM
  • Stage 5 for a maximal threshold effort, assuming you can complete the Alpe in ~60 minutes or less

The other two stages fell short of what could have been. To be precise:

  • Stage 2 talked about targeting 1-minute power, but since the on-screen instructions had you sprinting every sprint segment (9 of them!), your 1-minute efforts were blunted.
  • Stage 3, on the cover, was about VO2 max efforts. But it had you do 3 back-to-back hard laps of the Volcano Circuit, which meant you couldn’t actually hold VO2 max power for more than perhaps 1 lap. It was actually more like a pacing exercise for stage 4.

Like I said in the intro to stage 1, this isn’t meant to be a workout program for an intermediate or experienced rider, and it won’t offer the periodized training of a true program.

It is, however, an easy way for beginners, or those new to structured training, to dip their toes into more structured approaches. Route-based workouts are a great way to do this, as they offer a welcome and needed alternative to the rigid structure of ERG workouts. So it’s good that Zwift is pushing in this direction.

As Zwift’s first serious foray into a route-based workout series, I’d say overall, Zwift Camp: Build feels like a step in the right direction.

But these workouts, and the overall program, could be much better. I’ve already written all my suggestions in previous posts, but I’ll summarize them by saying Zwift should:

  1. Find routes that dial in the interval lengths more precisely;
  2. Use the HUD effectively to aid the workout, and also;
  3. Communicate clearly what each workout is about through the event titles, description text, and other marketing comms.

There’s a lot more to be said about the potential of route-based workouts in Zwift, but I’ll save that for an upcoming Pondering the Possibilities post.

Sign Up For Stage 5

Sign up for stage 5 events in-game, in the Companion app, or go to zwift.com/events/tag/zwiftcampbuild2025wo5.

Questions or Comments?

Have you done this workout yet? Did you do the entire Camp? Share your thoughts below, or any questions you may have heading into the workout.


Notable Zwift Events for the Weekend of December 6-7

0

This weekend we feature three very different race events, a ride for a cause, and a training ride for crazy people. See our picks below!

Top view of three cyclists in yellow and blue jerseys with the word FEAR riding on a road; the word FEAR is displayed large on the left side of the image.

✅ Women Only  ✅ Popular  ✅ Unique Event

Now in its ninth year, this race can be called a true Zwift December classic! Over 260 women are already registered, but organizers expect that number to more than double by race day.

Read more about this event >

This year’s race is on France’s Knights of the Roundabout route, with different route lengths based on rider category. Cat D/E will be finishing at 36km at the Ballon Sprint arch, while A/B/C will finish at 44km after descending from the Petit KOM.

Saturday, December 6 @ 7:30pm UTC/2:30pm ET/11:30am PT
Sign up at flammerougeracing.com/fearless/

✅ Endurance Challenge  ✅ vEveresting  ✅ Crazy

Interesting in completing a virtual Everesting? This is a training ride for global vEveresting Day on December 29th.

Read more about Global vEveresting Day >

The event has riders on Oh Hill No for 20 laps. “Enjoy!”

Sunday, December 7 @ 1:30pm UTC/8:30am ET/5:30am PT
Sign up at zwift.com/events/view/5091167

✅ Good Cause  ✅ Beginner Friendly

Picked this because it’s a cause that’s near and dear to us. Ride organizers say, “We ride to support Ukraine and to remember that freedom has a cost. The war is still real — let’s keep Ukraine in the world’s heart and mind.”

Sunday, December 7 @ 8:45am UTC/3:45am ET/12:45am PT
Sign up at zwift.com/events/view/5250083

✅ Popular  ✅ Long Race  ✅ Age-Based ✅ Unique Event

Team Foudre’s weekly “medio fondo” is proving quite popular, with its age-based groupings and a women-only category.

This weekend’s race is on 2 laps of New York’s Everything Bagel route (68.6km, 1090m).

Sunday, December 7 @ 8:45am UTC/3:45am ET/12:45am PT
Sign up at zwift.com/events/view/5106424

✅ Popular  ✅ Race of Truth

Cycling Time Trials (CTT) – the national governing body for time trials in England, Scotland, and Wales – continues to evolve their popular time trial series (read about the launch here).

Saturday is your last chance to complete week 4’s race on Innsbruck’s hilly 2018 UCI Worlds Course Short Lap (23.9km, 494m). Note: there are now dedicated events for men and women.

Multiple timeslots Saturday, December 6
Sign up at zwift.com/events/tag/cyclingtimetrials

How We Make Our Picks

We choose each weekend’s Notable Events based on a variety of factors including:

  • Is the event unique/innovative in some way?
  • Are celebrities (pro riders, etc) attending/leading?
  • Are signup counts already high, meaning the event is extra-popular?
  • Does the ride include desirable unlocks or prizes?
  • Does the event appeal to ladies on Zwift? (We like to support this under-represented group!)
  • Is it for a good cause?
  • Is it just plain crazy (extra long races, world record attempts, etc)?
  • Is it a long-running, popular weekly event with a dedicated leader who deserves a shout out?

In the end, we want to call attention to events that are extra-special and therefore extra-appealing to Zwifters. If you think your event qualifies, comment below with a link/details and we may just include it in an upcoming post!

Tiny Race Series – December 6 Routes – Rollercoaster Tour

0

Tiny Race Series – December 6 Routes – Rollercoaster Tour

See zwiftinsider.com/tiny for current Tiny Race details.


How the (Team) Race Was Won: Burning Matches in Glasgow

5

How the (Team) Race Was Won: Burning Matches in Glasgow

This week, we all visited Glasgow for a tough points race in the penultimate event of Zwift Racing League 2025/26, Round 2. With so many points segments, no one rider could contest them all. How would teams play this, and could we grab enough points to win?

Read on to see how my team’s race unfolded in the B1 Development Lime division…

Race Planning

As usual, my Coalition Delusion teammates and I were chatting on Discord in the days leading up to the race, trying to figure out how best to ride the course.

It was going to hurt no matter what we did: 10 laps of Glasgow Crit Circuit, with the Clyde Kicker KOM and Champion’s Sprint as points segments each and every lap. Along with a sprint on the lead-in, that meant 21 hard efforts would be required just to stay in the front pack.

Because of all those hard efforts, we figured this would be an attritional race. Therefore, staying in the front pack wasn’t important so much for the finishing position as it was for the segment points you would earn every lap as you beat the riders who had fallen off the back.

But of course, if we wanted to score big points and actually win overall, we would have to put in some max efforts on the points segments. How do you decide which segments to go all-in on, and which ones to conserve on? Nobody can produce 21 max sprints in a 40-minute race.

I decided my best approach was to target the Champion’s Sprint, since I would perform better there than on the Clyde Kicker, being stronger in terms of pure watts than W/kg. So I would go all-in for as many reps of the Champion’s Sprint as I could, while doing the minimum amount of work necessary to hang onto the front for the rest of the race.

Warmup

Prepping to get on the bike, I used all the supplement tricks at my disposal: PR Lotion to my legs, 300mg of caffeine thanks to MEG gum + dirty chai, a Nomio shot (still not sold on this), and some beta-alanine, for the tingles.

Then it was off to Watopia to spin up the legs for ~25 minutes, putting in a few good efforts to get the heart rate up to 160bpm. A full warmup was especially important this week, because we would be going all-out for the first 40 seconds of the race.

A Hard Start

The race begins with a short lead-in to the start of lap 1, and that lead-in includes the Champion’s Sprint. So straight out of the gate we were sprinting, then holding that high power for around 45 seconds!

It was a tough start, and the pack stretched out quickly. I was near the front, but when riders really poured on the power in the final stretch of the sprint, my legs just didn’t have the power to hold their wheels. I came across in 14th place, and Sauce for Zwift showed the first selection had been made: 44 front riders from the original group of 51.

The pack didn’t ease much as we made our way to the Clyde Kicker, but I made my way toward the front, activated my feather powerup, then pushed just hard enough to stay in the pack while drifting backward up the climb (the classic “sagging” strategy). Even with all my tricks, it still took a hard effort to stay in touch with the group.

Down the other side, the pack eased considerably. I certainly wasn’t going to complain. I tried to spin the pedals as easily as possible, breathe deeply, knowing another sprint was just up the road.

It arrived quickly, as riders started jumping off the front and popping their aero powerups just after we turned onto the sprint straightaway. I followed the wheels, pushed hard, and came across the line in 6th.

One lap down. Nine to go. This was going to hurt.

A sea of aero powerups on every sprint…

The Middle: Attrition + Efficiency

I went all-in for the sprint at the end of lap 2 as well, coming across the line in 2nd for my best segment result of the day. And that’s when I decided not to sprint the next time. There was no way I could sprint hard 8 more times!

So I settled into a rhythm of sprinting every other lap, and essentially just trying to stay in the front group with as little effort as possible apart from those sprints. That meant keeping my avatar’s nose out of the wind, sagging the Clyde Kicker, and even sagging the sprints I wasn’t contesting.

The front group’s behavior became quite predictable, and I felt like each lap I was learning to ride more efficiently. That little kicker after the first descent from the Clyde Kicker? You can almost coast over that. Going all-in on the Champion’s Sprint? I could coast for several seconds after that as well. And in between the segments, the group simply wasn’t pushing hard. Nobody had the legs to get away.

You can see how this unfolded in my Ride Report chart. This is what a book of burned matches looks like! (Yellow arrows are max Champion’s Sprint efforts):

After 5 laps, most of the attrition had occurred. The front group contained just 23 riders, and Coalition Delusion had 4 riders in that group (including myself), with 2 behind in the chase.

The Finish

I took it easy on the penultimate sprint, wanting to have the freshest legs possible for the final sprint, since it essentially counted for double points (sprint points + finish points).

Coming around to the final Clyde Kicker, I expected some riders to attack hard, so I pushed a bit harder to make sure I didn’t get gapped off the back. The group didn’t surge as much as I’d expected, though, and I came across in 4th, grabbing some unexpected extra points!

A couple of riders tried to go long off the front with less than a 1km to go, and things were confused as we were about to lap a rider as well. (Where are the race officials when you need them?)

It started popping off 400m from the line, well before the final straightaway, but I didn’t think I had the legs to follow those wheels from that far out. So I upped the power but stayed seated, trying to surf the draft so I could stay near the front without blowing up early.

I triggered my aero a bit earlier than usual, then downshifted and got out of the saddle for one final sprint to the line. I looked up just in time to see my avatar passing a few riders (who had probably gone a bit early), and I came across in 9th.

See my ride on Strava >

Watch the Video

Results and Takeaways

Heading over to the WTRL website, we were elated to discover we’d won the race!

Team leader Dave Thompson had turned in a particularly impressive performance, coming in 2nd over the line and leading our team in points. He scored plenty of points on both segments, which shows he’s quite a balanced rider.

Our finishing points were also strong, because we had 4 riders in the front group of ~20, and all of us finished in the top 10.

Here are my segment results on the day. You can definitely see which Champion’s Sprint efforts were all-in, and which were conservative:

It’s interesting to see how my placings on the Clyde Kicker improved in the back half of the race. I’m not sure how to explain that, except to say perhaps those with punchy W/kg were getting tired.

Could I have scored more points if I’d raced this differently? I’m not sure there is much I would change, actually. I think I did about as well as I could, given my relative fitness and the day’s race course.

This was a really strong result for us, and we are now tied overall for first place with team TSE heading into next week’s final race of the round:

Taking home an overall win will be far from easy for Coalition Delusion: we excel in flat/rolling TTTs and flatter races overall, and next week’s race finishes on the NY KOM (see the race guide). But we’ll give it our best!

I’ll close with our traditional team Discord shot:

What about you?

How was your race #5? Share your story below!


Zwift Racing League Week 6 Guide: Empire Elevation (Scratch Race)

25

The sixth and final race of Zwift Racing League 2025/26 Round 2 happens Tuesday, December 9, and we’re back in NYC for a scratch race on the Empire Elevation course. This new route has some sneaky climbs, escalator intrigue, and a very spicy finish.

There’s much to discuss, including crucial course segments, powerups, bike decisions, and strategic options. Let’s dive in!

Looking at the Route

Empire Elevation is a 26km long point-to-point route with 266m of elevation gain from start to finish. This is a new, event-only route created just for ZRL, which means many riders haven’t yet completed it, although most will be familiar with the New York roads it covers. All categories will be racing the whole route:

Clearly, the finishing climb up the NY KOM is the big feature of this route. But there are a few slight warmup climbs before we get there:

  • Climb up from Peristyle Sprint @ 3.8km (900 meters at 2.4%): the first climb on the day, even if it’s a small one.
  • The Hill KOM @ 5.9km (500 meters at 3.7%): another short one, but a bit steeper than the first.
  • Manhattan Bridge @ 10.8km (1km at 2.6%): a draggy but draftable climb up to the mid-bridge Sprint banner.

Let’s Talk Escalators

Riders will take three downramps into subways during the course of the race… and also three escalators up and out of the subways. The downramps will certainly speed things up, but it’s the escalators that may make things truly interesting, if lighter riders choose to take advantage of what they offer.

You may recall, in preparing week 4’s race guide, I did some bot testing on the new NYC escalators. I ran bots of various weights up one of the longer escalators on the route (the final escalator you’ll hit, in fact). Each bot’s power was set so they would all have approximately the same escalator entry speed (~46 kph), and that power remained steady as they went up and over the top of the escalator. Here’s how much each bot slowed between entering and exiting the escalator:

  • 50kg bot @261W: slowed 3.2 kph
  • 75kg bot @339W: slowed 11 kph
  • 100kg bot @390W: slowed 16.1 kph

It appears as if Zwift is adding a flat power boost to all riders on the escalators. (In the comments section of the week 4 post, astute ZI readers Carl and Tom used some climbing speed calculators to estimate it at 1200-1400W.) If instead Zwift had given the same w/kg boost for all riders, the speed gap would be minimal. But 1200W is a huge number for a lightweight rider (20 W/kg for a 60kg rider) while being comparatively tame for a larger rider (12 W/kg for a 100kg rider), which is why the bot tests show what they show.

Zwift has acknowledged this is a problem, and they’ll roll out a fix soon. But it won’t be out before Tuesday’s race, as far as I know.

If I were a light rider, I might take advantage of this and attack on the escalators to soften the legs of heavier rivals. I could also just soft pedal up the escalator to conserve my energy! Think about it: assuming Zwift is indeed adding 1200W, a 60kg rider could coast up the escalator while a 100kg rider puts in a solid 8 W/kg dig, and both would have the same effective W/kg:

  • 60kg at 1200W=20 W/kg
  • 100kg at 800W+1200W=20 W/kg

Watch for escalators at 10km, 15.8km, and 21.7km.

NY KOM Finish @ 24km

The official KOM segment (shown above) is 1.4km, averaging 6.3%. But the actual climb is 1.8km long, averaging 6.2%. This will be a legit VO2 max effort: expect the full climb to take just under 4 minutes for top riders, almost 5 minutes for B category, and 5-6+ minutes for C category and below.

This is a fairly steep climb, so drafting will offer a minimal advantage, except on the three short flat bits. And the final 200 meters are the steepest part, so it’ll be a fiery finish for Round 2!

Read more about the Empire Elevation route >

PowerUp Notes

Powerups will be awarded at each segment arch, including Power Segment arches in the subways, which means we’ll have 8 powerup opportunities on this route. You have an equal chance of getting a feather, van, or helmet powerup at each arch.

Lightweight (feather): reduces your weight by 10% for 30 seconds. Save one for the final climb, since it’s the most important section. You may also want to use them on the escalators if you’re a heavier rider.

Draft Boost (van): increases the draft effect you are experiencing for 40 seconds.
Use at higher speeds (flats and descents) when you are already drafting off another rider (since this powerup only helps when you are drafting.)

A simple white helmet with a visor, shown in profile with three lines behind it to indicate speed, centered on a turquoise circle with a gray and white border.

Aero Boost (helmet): makes you more aerodynamic (reduces your CdA by 25%) for 15 seconds.
Use at higher speeds (flats and descents), especially when no draft is available (although it is still useful when drafting.)

Bike Recommendations

This race’s steep finishing climb definitely makes me steer away from pure aero setups and look at climbing bikes and all-arounders instead. While a more aero setup would have a time advantage on a solo effort of the whole course, what you’re really looking for is maximum advantage on the finishing climb.

My recommendation, then, is to use the new ENVE SES 4.5 PRO wheels paired with one of these bikes:

Of course, your frame’s upgrade status should impact your decision. A fully upgraded Aethos will outclimb the other four frames, but that’s not the case when comparing un-upgraded versions.

Related: All About Zwift’s New “Bike Upgrades” Functionality >

See Speed Tests: Tron Bike vs Top Performers for more nerd-level detail on frame and wheel performance.

More Route Recons

Lots of recon events are scheduled on upcoming ZRL routes, led by various teams. This is a new route on fresh roads, so many riders will find recons particularly helpful this week. See upcoming ZRL recons for this race at zwift.com/events/tag/zrlrecon.

Additionally, riders in the Zwift community do a great job every week creating recon videos that preview the courses and offer tips to help you perform your best on the day. Here are the recons I’ve found (comment if you find another!)

John Rice

J Dirom

Nathan Krake

Beccah Niesen

Strategic Options

How will the race unfold, and what strategies will riders employ to bring home a team win on Empire Elevation? Here’s what I predict:

  • Escalator pandemonium: Expect some lighter riders to attack on the escalators, as explained above. This becomes more likely as the race progresses.
  • Escalator and chill: Expect some lighter riders to simply coast on the escalators, as explained above.
  • Going long: Teams with pure-power riders who don’t fancy their chances in a W/kg slugfest may attack on the flats to get up the road and boost their chance at a high finishing position.
  • Save it for the climb: Most riders will do this. Simple conserve, conserve, conserve for the first 24km, then “give it the beans” for the final 4-6 minutes and hope for the best.

Your Thoughts

Any insights or further thoughts on this race? Share below!

All About Global vEveresting Day – December 29

42

All About Global vEveresting Day – December 29

The Torturefest Club, in collaboration with Everesting.com, are holding a virtual Everesting event on Zwift on December 29, 2025. On that day, riders around the world will take on Zwift’s infamous The Grade segment to push together through a Quarter, Half, or Full Everesting.

Read on to learn a bit about vEveresting, and details of the events planned around Global vEveresting Day!

What Is vEveresting?

Everesting, named after the highest mountain on Earth, is a grueling challenge for cyclists. The mission is simple, but the task is brutally difficult: find a climb and keep riding your bike up and down until you’ve climbed the height of Mount Everest (29,032 feet/8,848 meters). The challenge often takes riders 12-24 hours to complete, depending on gradient and fitness level.

Do this on Zwift (or any other virtual cycling platform) and it’s called virtual Everesting, or “vEveresting.” Frank Garcia became the first-ever vEverester in 2015. He rode a Strava segment on Zwift called “Watopia Wall” – the first piece of the Hilly KOM– 315 times in 24 hours!

There are rules, of course. The climbing must be done on one hill. 100% Trainer Difficulty is required. And the challenge must be completed in one attempt, with no sleep. See complete vEveresting rules >

Training Rides

New to Everesting? Join the Torturefest Club’s prep sessions, which have already been running for the past several weeks. You will learn about pacing, nutrition, and the importance of team camaraderie as you prepare your body and mind. 7.3 laps is a Quarter vEveresting, and 14.6 laps is a Half Everesting (all of which can be uploaded to the Everesting hall of fame).

Events do not allow Coffee Breaks, and 100% Trainer Difficulty is enforced. But you do get a feather at every banner.

vEveresting Day Events

The Torturefest Club is hosting eight dedicated rides across every major timezone, so you can climb with a global community and tackle the full 8,848 m together. All riders on course will be visible, so these events are structured to give you pacing support, motivation, and camaraderie along the way.

  • vEveresting Day: Australia/New Zealand
  • vEveresting Day: Asia
  • vEveresting Day: Middle East
  • vEveresting Day: Europe (East)
  • vEveresting Day: Europe (West)
  • vEveresting Day: United Kingdom
  • vEveresting Day: USA (ET/CT)
  • vEveresting Day: USA (MT/PT)

Questions or Comments?

Check out the event page on everesting.com for more info. Got questions or comments? Share below!


Zwift Update Version 1.103 (156100) Released

27

Zwift version 1.103 begins its phased rollout today. This is a minor update containing visual improvements and bug fixes.

Release Notes

  • Improved drafting behavior on steep gradients – the steeper the climb or descent, the more the change will be noticeable. Note: This was actually rolled out last week… read Zwift Insider post for more details >
  • Various visual improvements in New York.
  • macOS: Fixed an issue that caused Ultra graphics to not be enabled for devices with Apple M3 chips.
  • Fixed a crash that could potentially occur when joining an event while in worlds without intersections, e.g. Paris.

Discuss this update in Zwift’s forum >

Questions or Comments?

If you spotted any other changes or bugs in the update, please comment below!

Team Fearless 9th Annual Women’s Team Championships – December 6

0

Team Fearless 9th Annual Women’s Team Championships – December 6

Team Fearless has announced the details of this year’s Annual Women’s Team Championships, held in partnership with Flamme Rouge Racing (FRR).

Now in its ninth year, this race can be called a true Zwift December classic! Over 220 women are already registered, but organizers expect that number to more than double by race day.

Meant to test resilience and endurance with a longer distance than the average Zwift race, the AWTC is one of a kind. First, it’s a team-based competition, but without limits on team size. Even better: each category gets to crown its own champions, so this race is for all ability levels. Read on for details…

Date and Time

The race happens Saturday, December 6 at 7:30 PM UTC/2:30pm ET/11:30am PT).

Race Format and Categories

Riders are grouped into categories based on Zwift Racing Score:

  • Dancer (450+)
  • Blitzen (350–450)
  • Comet (250–350)
  • Donner (175–250)
  • Rudolph (0–175)

This is a team competition, with winning teams determined using a custom points system. Points are scored in two ways:

  • Finish Points: based on your position across the finish line
  • Segment Points: based on your segment time (Fastest Through Segment) on each segment of the race course

Finish and Segment Points start at 100 and drop by 1 point each place down to the 41st position. Then from 46th to 100th position, points drop by 5 every 5 places, with every rider earning at least 1 point for their effort. For example:

  • 46th to 50th places will earn 55 points
  • 51st to 55th places will earn 50 points

Team competitions will be held across all five pens and overall. The Club with the highest average points score will win the day. This way, clubs are not restricted in the number of riders who can enter, and also, there is no minimum number of Club riders.

For more info, see the Rules page >

Route Details

This year’s race will be held on France’s Knights of the Roundabout route, with different route lengths based on rider category.

Animated “Knights of the Roundabout” Route Details (France) Map
Animated map provided by ZwiftHacks

Cat D/E will be finishing at 36km at the Ballon Sprint arch, while A/B/C will finish at 44km after descending from the Petit KOM.

Sign Up

This is a team event. Riders can register until the race begins, but the race pace link is private, so registration is required at https://flammerougeracing.com/fearless/.

To compete, you must meet these minimum requirements for accounts and equipment:

  • Riders must be OPTED IN to share their race data with ZwiftPower from their Zwift Profile Connections
  • Riders must have created and connected a ZwiftPower account – full instructions on this can be found here
  • Riders must have an FRR account to allow Team Managers to select them for a Club Team and have registered for the Fearless event, to do this simply follow these instructions:
    • Simply visit the FRR Home page and Login or Register a New account – once in, click on your name to open your Profile options
      • New accounts must first complete their basic Profile Information when they first log in – just select Profile and complete the fields presented not forgetting to SAVE at the end
    • To register for the event click on Event Admin and then select Register from the 3 tabs shown
      • The page details the 3 simple steps to follow to complete event registration
      • Race BIO confirmation is important to us as we look to improve rider responsibility for their virtual profile, since these define how our virtual self competes
  • Riders are advised to have completed at least 3 Zwift race events prior to racing to ensure your ZRS value is reflective of you as a rider

Once registration is completed you will appear on the Registered list of riders and you will receive a welcome email to confirm along with some helpful details about the event.

You can email Team Fearless at [email protected] for support, email FRR race control at [email protected], or join the Fearless Discord server.

Watch the Live Stream

The race will be live-streamed on FRR’s YouTube channel, with Nathan Krake commentating.

Final Details

Go to the race homepage and click “Roadbook” for detailed rules and other info.


Zwift Camp: Build – Stage 4 Walkthrough

Zwift Camp: Build – Stage 4 Walkthrough

Zwift Camp: Build is underway: a 5-stage route-based workout series, with each stage lasting one week and focusing on developing power over a specific time interval.

My plan is to do each of the five workouts before their weeks begin, so I can write a post unpacking the workout and delivering some tips along the way. This post covers Stage 4’s workout on Watopia’s Hilltop Hustle route, which takes you up The Grade KOM. Let’s roll!

Stage 4 Intro: Find Your Pace

The fourth stage of Zwift Camp: Build is focused on “One 20-minute attempt,” according to the event description. That may be a bit of an over-simplification, but it’s close: all we’re doing is hitting The Grade KOM for a single max effort, which means you’ll be riding at just over your threshold (FTP) power.

The only tricky part here is knowing ahead how long the climb will take you, so you can pace yourself accordingly. When I tested The Grade with Nathan and Gabi Guerra just before it was released, Nathan finished the segment in 10:37, Gabi in 11:46, and I in 14:02. So this won’t be a “20-minute attempt” for many riders.

If you’ve never done a max effort up The Grade, here are a few metrics from bot tests with a 75kg, 183cm rider on the Tron bike that give you some idea of how long it may take you to finish the climb at your pace:

  • 150W (2 W/kg): 27:46, 146W FTP (97.3% of average)
  • 225W (3 W/kg): 18:47, 210W FTP (93.3% of average)
  • 300W (4 W/kg): 14:22, 267W FTP (89% of average)
  • 375W (5 W/kg): 11:44, 328W FTP (87.5% of average)
  • 450W (6 W/kg): 10:04, 388W FTP (86.2% of average)
  • 525W (7 W/kg): 8:49, 449W FTP (85.5% of average)
  • 600W (8 W/kg): 7:54 (not FTP detected for efforts below 8 minutes)

The stage is built around the Hilltop Hustle route in Watopia, which begins in the Southern Coast start pens, taking riders out to the Sasquatch Sprint turnaround for a flat warmup, up The Grade KOM for your big effort, then down the hill and out to the Sasquatch Sprint for the finish.

Animated “Hilltop Hustle” Route Details (Watopia) Map
Animated map provided by ZwiftHacks

Differences from Previous Stages

Apart from the single power interval you’re targeting, this stage’s setup differs from stages 1-3 in other ways:

  1. RoboPacers! When you sign up to do the stage as an event, you pick a RoboPacer group to join. (Note: All bots and riders will be visible in your event, so you can actually chase whatever bots or Zwifters you’d like.)
  2. No script: there are no on-screen instructions like the previous stages. You’re expected to know when to begin and end you The Grade KOM effort.
  3. No Splits or Ride Stats HUD: Instead of these elements, The Grade HUD is shown, which shows your stats for each of the The Grade’s 10 segments.

Stage 4 Walkthrough

Once again, I came into this workout with legs that weren’t primed and ready for a 100% effort. (I had actually done Stage 3 the day before, simply because it was the only way to fit these rides into my schedule.) So I decided to target sweet spot-level power (~275W) for the first portion of the climb (up to the flat spot), which would keep me basically even with my B RoboPacer at 3.2 W/kg. Then I would increase the power for the second portion if my legs would allow it!

The route begins with a flat 6km warmup. Use these ~10 minutes to spin up your legs, put in a couple of short efforts at high cadence to blow out the cobwebs, and raise your heart rate so you’re properly warmed up for The Grade.

RoboPacer Details

If you do stage 4 as an event, you’ll have RoboPacers riding with you. If you do it as an on-demand ride, there are no RoboPacers.

If you care about using the RoboPacer to pace you up The Grade, you’ll want to be careful not to lose your target RoboPacer during the warmup! The nice thing is, the bots ride at a much lower pace during the warmup than they do on the climbs.

Here’s a chart showing each of the available RoboPacers, their climb paces, and their (approximate) warmup pace:

Bot LetterBot NameClimb PaceWarmup Pace
A14 Minutes4.22.8
B18 Minutes3.21.9
C22 Minutes2.61.7
D26 Minutes2.21.5
E30 Minutes1.91.3

I knew I wasn’t up for holding the A RoboPacer’s pace, but I figured I could beat the B RoboPacer. So I decided I would target that B bot, starting The Grade with the bot then making sure I beat it across the line at the top!

I found it really easy to stay ahead of the B RoboPacer during the warmup, and had to ease up before starting The Grade so the bot could catch me and we could start it together:

Once we crossed the line to start The Grade, it was “on like Donkey Kong,” as the great Dave Towle likes to say. That RoboPacer wasn’t going to beat me to the top, even if my legs were a bit tired!

After quickly putting ~35 meters into the B bot, I basically held that gap up to the flat section, holding a similar W/kg as the bot. But I knew something the bot didn’t know: the bot was programmed to drop its power on flat roads. This was my chance to keep the power high and put more time into the bot! So I did just that, extending my lead further as that lazy bot sat up on the flats.

The second portion of the climb is the tougher bit. It feels steeper, it’s definitely longer than the first part, and your legs are starting to feel the effort. I bumped up my effort from ~275W to ~300W, and began steadily putting more time into B bot. 25 seconds, then 30, then 35…

The Sector Stats HUD on the left is handy when it comes to pacing yourself, as it shows your average power and HR across the 10 equidistant sectors of the climb, along with your overall progress. When I saw my average power drop a bit on one sector, I increased it to keep pushing the pace.

I gave one last hard push up the final bit of the climb and went under the banner at the 16:26 mark. Nothing to write home about in terms of my personal performance, and the FTP it detected for me (261W) is certainly lower than my actual FTP! But it was a good little 16-minute interval that warmed me up nicely and sapped the legs a bit, so I was ready for an easier-paced ride outside with friends immediately following.

After finishing the hard climb, you’ll quickly turn around and come down The Grade. Keep your legs spinning to clear the lactate and safely lower your HR, wave at the alpacas, throw in a cheeky supertuck (take that, UCI!), and finish out the route.

Watch My Video

More On Threshold Power

Functional Threshold Power, often just called “threshold power” or FTP, is an approximation of your maximal lactate steady state. It is “the cycling power you produce when your lactate production has risen, leveled off, and then closely matches your body’s ability to remove lactate,” according to this helpful TrainerRoad post. A few interesting things about threshold power:

  • It’s the most popular metric in cycling because it helps you determine both race ability and workout pacing. That is, structured workout intervals are usually based on a percentage of your FTP.
  • When operating at FTP, you are essentially riding on the balance point between your aerobic and anaerobic energy systems.
  • TSS – or “Stress Points,” as Zwift calls it is a common metric for measuring the difficulty of a given workout or training week. This is calculated based on your FTP, so it’s vital you set your FTP accurately so you can track your training load accurately. Read more about TSS here >
  • While pros may go to a lab to be tested for a precise FTP reading, most training platforms, including Zwift, automatically look at your power numbers and estimate FTP fairly accurately. Still, you may want to do an actual FTP test on Zwift to help you put in your best effort. For more info, read How (and Why) to Take an FTP Test on Zwift >

FTP Training Tips

Unlike training other systems (such as VO2 max), workouts to increase your FTP can take a variety of forms.

The most fundamental “FTP boosting” workouts are simple aerobic work. This is your base, and if it isn’t well developed, you really can’t progress meaningfully as a cyclist. Longer zone 2 endurance rides and shorter “sweet spot” intervals at 88-94% of FTP are both effective ways to build your aerobic base.

Beyond simple aerobic work, two other high-intensity workout styles are popular for boosting FTP:

  • VO2 Max: Short repeats at your VO2 Max can deliver big improvements in both aerobic and anaerobic power
  • Over-Unders: Pyramid workouts with steps going from 95% to 100% to 105% of your FTP (then down again) help train your body to deal with the metabolic byproducts of riding above FTP.

Suggestion Box

The fourth workout of Zwift Camp: Build felt the most “ordinary” of the stages I’ve done so far, because it was really just a ride up The Grade, with a bot to keep me company. That said, an all-out attack of The Grade is a solid workout and fitness test any day of the week!

After finishing stage 4, I’d say there are two things Zwift could improve:

  • Messaging: It’s odd that the first three stages had on-screen messaging to coach you, but this stage did not. That feels like a miss, especially because messaging could be helpful in guiding people to pace optimally on the longish effort up The Grade.
  • Improve the event description: I already mentioned this for earlier stages, but once again, a simple line or two in the event description would clarify what people are signing up for. As explained above, the current description for this workout (“Target Effort: One 20-minute attempt”) really isn’t accurate for many.

Sign Up For Stage 4

Sign up for stage 4 events in-game, in the Companion app, or go to zwift.com/events/tag/zwiftcampbuild2025wo4.

Questions or Comments?

Have you done this workout yet? Share your thoughts below, or any questions you may have heading into the workout.


How the Race Was Won: Escalator Pandemonium In the ZRL TTT

9

How the Race Was Won: Escalator Pandemonium In the ZRL TTT

This week, we took on the new Watts the Limit route in NYC for the second TTT of Zwift Racing League 2025/26. It was a bit of a wild route due to the crazy ramps in and out of the subway, and I didn’t make things any smoother by accidentally sapping my legs in a heat training session the day before.

But I’m getting ahead of myself. Read on to see how our race unfolded!

Heat Training vs Recovery

Let’s start this story a day before the race, when I decided to do a heat training use the CORE sensor. You can watch the whole session here, but I’ll summarize it by saying it turned into a harder effort than I’d planned. But by the time I realized I was probably overdoing it, I was nearly done with Off the MAAP stage 1, and didn’t want to pull the plug. Because I’m not DNFer!

My mistake was confirmed when I pulled up the CORE app and saw this in my activity summary:

Still, I didn’t feel particularly tired after the effort. I’d only ridden zone 2 power after all. So I just tried to make sure I rehydrated and got rest heading into ZRL day.

Planning Our Race

Heading into the race, my team (Coalition Delusion) was chatting about all things course and strategy as usual. Since these were fairly new roads in New York, none of us had raced them as a TTT yet. Captain Neil had our pull order worked out, with a bit of help from the Zwift TTT Calculator:

The big question for everyone was the escalators. I had already done some testing to confirm that going up the escalators would prove tricky for teams of varying weights, since the escalators slow heavy riders much more than light riders.

Then Zwift made things even more interesting by releasing a drafting fix the day before the race, which particularly affected the ride experience on steep inclines and declines. How would this change the escalators? There really wasn’t time to try it out. We would learn as we went!

The Race

We took off from the Central Park start pens, and quickly got into formation. Like most TTT squads, our goal is to “line it out” – to hold a 6-rider formation, rotating pulls on the front. It’s absolutely the most efficient way to race a team time trial, and it really is a cool feeling when your whole squad is dialed in and riding as one.

As each rider finished their planned pulls, they would announce on Discord that they were pulling off. Then the next rider would call out how long they’re going, and the on-deck rider would acknowledge that they knew they were there next. We were doing our best to communicate clearly, since we didn’t have a dedicated (non-riding) DS to direct us today.

Calling an Audible

I was supposed to take 60-second pulls, but after my first one (3 minutes into the race) I was already questioning whether that would be possible! It’s not hard to do the math: this would be a ~41-minute race, and the team of 6 would race through in just under 4 minutes. That meant I had at least 10 pulls to make, and possibly more if we lost a rider or two.

I decided I would need to do some shorter pulls to ensure I didn’t blow up on the back half of the course.

Escalator Madness

We hit our first downramp into the subways as I was dropping back from taking my first pull, and I didn’t time things well at all. First, the team flew past me faster than I’d anticipated, which left me a 3 meters off the back as we hit the ramp. I stopped pedaling at the ramp, figuring I would get sucked back into the team via the new, stronger draft… but instead, they rocketed ahead, and I soon found myself 20-30 meters off the back!

Nobody wants to see this view in a TTT:

My teammates were quite animated in Discord, surprised by the high speeds and churn caused by the downramp. It was pandemonium, but I hammered to get back in the wheels – you have to react quickly in these situations – and we slid back into formation.

A couple of minutes later, we had our first escalator up and out of the subway. We handled this one much better, with everyone lifting their efforts and our team at least staying tightly packed over the top.

Hammer up the escalator, keep the power high to accelerate once it flattens out, then return to formation. That would be our general approach on the next 5 escalators.

Feeling Weak, Feeling Strong

On my next pull, I only did a 30-second effort. Pushing at what I felt was the typical VO2 max power (~370W) where I take my pulls, the numbers on screen showed 30-40W below my target. Yikes. Clearly, yesterday’s heat session had sapped me.

At the same time, I wasn’t on my limit. This is thanks to being on a B development squad, which means we’re all mid-pack B riders and not a bunch of super-B’s! So I could still contribute to the team in a meaningful way, despite not being on top form. The race began to feel like a tug-of-war between me struggling to pull at my target power, and me feeling strong and perfectly capable in the draft.

At the 9:15 mark, I noticed a gap forming between the two front riders and the four of us behind. (This sort of thing happens to some extent in pretty much every TTT race, and it’s usually triggered by a rider who is dropping back after taking their pull. If that rider drops back too slowly, and someone ends up getting stuck behind that rider, a gap will quickly open up.)

I saw such a gap forming, so I announced I was heading forward to full the gap, and for Robert, the rider whose wheel I would normally sit on in our formation, to let me know when he wanted to come around me to get back into formation. It worked just as planned: the gap was closed quickly, with just a bit of extra work on my part. Let’s roll!

Logging the Miles

The course continued to unfold before us, and we worked together to keep speeds high and ride efficiently. This was far from a flat, steady route! Instead, it was rather polarized, thanks to the six escalators, six steep downramps, and two crossings of the Manhattan Bridge. In between these dramatic sections the course was quite flat, so we were repeatedly transitioning from easy flat roads to major pitch changes and back.

But we were moving well, and Sauce showed us a few seconds up on the teams visible to us: two ahead and one behind – as we made the turnaround at Grand Army Plaza.

No HR

At 16.1km, I noticed my heart rate wasn’t showing in the HUD anymore. Crap. I tried pushing the button to turn it on again, but that didn’t work. It never does, with the Schosche monitor. When it’s dead, it’s dead! Should have charged it beforehand. I just hoped I’d been showing HR long enough that WTRL wouldn’t DQ my effort for the event.

Chris Skips

At 19.1km, Chris said he would need to skip a pull. As a C-cat rider who had been sick in the day leading up to the race, we wouldn’t begrudge him sitting in the wheels for a while! So he slid to the back of the formation, becoming the “bookend” of the group as we started the return climb to the Manhattan Bridge sprint arch.

Back to 1-Minute Pulls

With 8.7km left in the race, I rotated to the front and called out a 1-minute pull. The race wasn’t easy by any measure, but I also felt like I had the legs to do a few hard 60-second efforts before it ended, and the team could use the extra break with Chris unable to pull for now.

(I should mention Fabian here, our strongest rider, who took consistent and strong 1-minute pulls throughout the race. Every team needs a Fabian!)

We hit the downramp into City Hall Station while I was on the front, and while I sort of automatically eased up on the power due to the drop in resistance, the rest of my team slingshotted from my draft and came around me as we hit the flat road at the bottom! We would then have to quickly reorganize into formation while speeds were still high.

This is how the downramps seemed to unfold each time. It may not have been the fastest possible way to attack these ramps, but it was efficient, and we were still putting time into the other teams. The front rider seemingly couldn’t push hard enough to stay ahead on these downramps, as the chasing riders were still putting out power and the newly strengthened draft wanted to slingshot everyone ahead. It was all a bit chaotic, but at least it was fast chaos.

The Finish

We hammered up the final escalator, the longest of the course, and now just 3km were left in the race. The formation was getting a bit jumbled, as often happens near the end of these races.

Chris was still holding on like a boss and volunteered to take a suicide pull to make one last contribution to the team. “Let’s go,” he said with 700 meters left. And he hammered on the front, emptying his tank as we hit the little kicker heading into the finishing sprint.

I hammered up that sprint and tried to keep the power up, as I saw I was the front rider. That always pushes me to give it all, as I know everyone behind is behind helped by my draft!

We finished in 41:37.247, for the win!

See my ride on Strava >

Watch the Video

Results and Takeaways

We won by a good margin, beating the next-best team by over 26 seconds:

The problem is, we didn’t do well in races 2 and 3, due to their mountainous nature. So we currently sit in 3rd place overall. But the top of the division is competitive!

Clearly, Coalition Delusion does well with the TTT format. Next week’s punchy points race on Glasgow Crit Circuit will be interesting, to say the least. There’s still potential to improve our overall ranking, but given the last two races of Round 2, it won’t be easy.

One takeaway from this week: I definitely won’t be doing a heat training the day before next week’s race.

We finished our ride with the customary team shot:

Your Thoughts

How did your TTT go? Share below…