How the Race Was “Won”: Questionable Officials at Green to Screen

On November 3, I did my first-ever race on New York’s Green to Screen route. Having ridden several laps of this route in previous Thursday Pizza Burner rides, I knew it was flat and fast, with a good portion of the “climbing” being the escalators up from the subways that aren’t really climbing at all.

I also knew roughly where I stood against my competitors, having raced with them several times in this round of the ZRL. I knew there were strong riders in the group, but I was one of them. With a real chance at the podium this week, I was prepared to go all in for the possibility of a rare win.

So you could say I went into this race with high hopes. And while I ended with a good result, it was sort of… tainted? But I’m getting ahead of myself…

A Messy Round 1

The first round of Zwift Racing League’s 2026/27 was, I think, the messiest in ZRL history.

It began with race 1, the first-ever “Race of Truth”, which quickly devolved into more of a “Race of Confusion”. TT bikes were supposed to be disabled in this draftless event, but they weren’t. If even one rider had a TT bike in the event, it basically made all the results useless. So this race got annulled for everyone. (Happily, I wasn’t able to do this race.)

Races 2 and 3 were great. Race 4, a TTT on Watopia Figure 8 Reverse, was mostly fine, apart from people’s powerups being taken as they rode through the downtown Watopia arch. (This is a bug related to assigning 250 XP bonuses to lap arches.) A bummer for sure, when you were planning on getting a little help from that draft boost, but it’s not a race-ending/breaking issue.

Then race 5 on Green to Screen imploded as something in Zwift’s event join flow broke for a couple of hours at peak race time. This wasn’t a WTRL issue – it affected all events on Zwift. But it meant some riders (including myself) weren’t able to join the start pens, leading to races with a reduced number of riders, with some just ending the race because they knew it was a waste of time.

Race 6 to Spiral Summit seemed to go off without a hitch. But then WTRL had to figure out how to re-run race 5 (which they were now confusingly calling race 4). They put it to a vote of team managers, and my division decided they wanted to race it again.

What a mess. Here’s hoping for a smoother round 2.

The Warmup

I got on the bike with plenty of time before the 11:15am PST race, giving me a full half hour to wake up the ol’ ticker and spin up the legs. I was already one dirty chai and a few pieces of Neuro caffeine gum into my warmup by the time I got on the bike, so I was nicely caffeinated. I had also rubbed PR Lotion into my legs to keep the burning at bay.

My Warmup “Stack”

I rode my Factor Hanzō TT bike during the warmup, since I’m working on upgrading this weapon and need to log as much time on it as possible. (Currently working on stage 4, which requires 540 minutes!)

The Start

We jumped out of the Prospect Park start pens, and the race was on. But this was one of the most chill race starts I’ve ever experienced. Nobody wanted to push the pace or attack, as the start was slightly downhill and there was no need to contest the sprint segment we rolled through around 2.5km in. I averaged just 230 watts (2.8 W/kg) for the first 6 minutes.

The Hill KOM would be the first test of just how spicy this group was going to be. It didn’t take long to see that the group wasn’t interested in watt-maxxing the hills, even though I did get a PR on the segment (54 seconds at 414 watts). With only 21 riders in the pack, and two big animators (Mahot and Miller from TBR) not in the mix, it was looking like I’d be able to sit in until the final minutes of this race without expending too much energy.

Which was exactly what I wanted.

The Middle

With the early race jitters out of the way, I settled into riding efficiently, knowing we had another ~15km before the biggest obstacle of the day: the Brooklyn Bridge KOM. While I could have attacked during this middle section to “make it interesting,” I’m not one for long-range attacks, as I don’t have the pure steady power to stay away from a group. For me, attacking in the middle would mean:

• Tiring my legs needlessly before the biggest climb of the day
• Making others work to catch me – but nobody would have to work as hard to catch as I’d have to work to attack solo
• Maybe dropping a few of the weakest riders in the group, but not those I’d actually be competing with at the pointy end of the race finish

So I stayed in the draft, usually just a bike length or two from the front. The pack would stretch out when we hit any sort of a rise – including the Manhattan Sprint climb and the Times Square loop at the halfway point – but I wouldn’t panic. I tried to stay in the draft, trusting the group would pull back the one or two riders who might be just off the front.

I got an aero powerup at the Manhattan Sprint, which is the powerup I wanted for the finish. So I decided I’d hold onto it for the finish, unless the Brooklyn Bridge KOM section unexpectedly blew up and I needed to use it to grab back onto the group.

Perhaps the most interesting moment of the race (apart from the finish) came at 18.8km, when Engledow (INC) attacked as we entered a subway. Van Gestel (Velosity) followed. I considered jumping as well, but felt it was too early, with almost 10km to go. So I messaged:

In my mind, it was up to the teams who were both 1) competing for the overall league win and 2) had numbers in the group to do the work to pull back attacks. A dangerous assumption, perhaps? But it worked – one rider (S.T. from LeVeL) put in a good dig on the front, and I followed his wheel to close down the attack. Everything came back together just a minute or two from the Brooklyn Bridge KOM.

With 20 of the original 21 riders still in the front group, the race had clearly been an “easier” effort. But as we hit the slopes of the Brooklyn Bridge, it was time to work. I buckled down and kept the power up, wanting to hold onto that aero powerup. While the effort was hard, I wasn’t quite on my limit. It was the perfect effort, really: fast enough that no riders could jump off the front, but also a segment PR for me (3:16, averaging 337 watts). We dropped 4 riders over the top.

The Finish

As we all caught our breath after the climb, everyone was mulling over their options for the finish. Personally, I didn’t want to leave it to a bunch sprint. But I didn’t want to instigate a long attack, either. So I decided to follow any riders who chose to go long, hoping to benefit from their draft then counterattack over the top.

And that’s exactly what happened – S.T. (LeVeL) came up from the back of the pack, feather powerup flying high as he jumped hard just after the final escalator with 1.5km to go. I hesitated a moment more than I should have, then jumped. S.T.’s numbers immediately went orange, and so did mine! We quickly gapped the rest of the group, but S.T. was flying, and I was so far behind that I was barely receiving any draft benefit.

I kept pushing, knowing I couldn’t survive in the wind all the way to the line. With 700 meters to go, I finally got in S.T.’s draft. He was still pushing hard, so I took a moment on his wheel to survey the situation. With 400 meters to go, two riders had nearly chased us down, while the rest of the group was strung out 4-5 seconds back.

I no sooner thought, “I’ll need to grab onto any riders who come through,” when Adam Riley (TBR) absolutely blasted past me! I went all in (again, a bit too slow on the draw) as the second chaser (Mine from LeVeL) came around. I activated my aero powerup. 200 meters to go.

Mine (LeVeL) and I were neck and neck for a few seconds, then he dropped off. I could see I was closing the gap to Riley, but had I left it too late? Head down, I just put everything I had into the pedals, glancing up as I crossed the line to see Riley finishing around a bike length ahead:

But when the results popped up, this is what I saw:

I’m not sure how that works. How Zwift’s servers decided that Riley finished second, with a time gap to me of 0.00, is above my pay grade. But I celebrated the win, even though it didn’t quite feel like one!

See my ride on Strava >

Watch the Video

Takeaways

That finishing effort took everything I had, regardless of the final result. I barely beat my all-time 2-minute power PR (450 watts), and I know some other riders did the same.

Riley, I, and others commented on our Strava activities after the race, with everyone basically in agreement that Adam was robbed. But there’s nothing you can do to “appeal” this sort of result, as far as I know. What Zwift’s server sees is what it sees, and that doesn’t always match what our clients show.

This is, of course, something we’d all love to see Zwift fix. It’s an issue that has been around since official events came to Zwift over a decade ago, and while, thanks to changes Zwift made a few years ago, what we see on screen more closely matches what the server sees, it’s still far from perfect. This race is probably the most egregious example I’ve seen in a while, with seemingly everyone in the race seeing Riley cross first.

Props to you, Adam. I would give you the win if I could, as you had me by a bike length. I figure the next-best thing I can do is write this post, tell the story of what happened, and push Zwift to improve their systems so this can’t happen.

This was the last race of the round for us, and while my team’s overall result wasn’t great, I think it’s the best set of ZRL results I’ve ever had individually. So I’ll look on the bright side! I finished as the overall points leader on WTRL’s cool new “League Stats” tab:

Your Comments

How was your Green to Screen race? Ever lost (or won) due to an official who clearly needed their eyes checked? Share your thoughts below…

The first race of Zwift Racing League 2026/27 Round 2 happens on Tuesday, November 17, and it’s our first time racing the London Calling route in ZRL.

While the route may be unfamiliar due to its newness, the roads it covers are well-worn by Zwift racers over the years. This is one of the less technical TTT routes we’ve raced, which may be welcome news if you’re on a team of diesels or one lacking TTT experience.

With key TTT rule changes in effect and Zwift releasing a pile of new TT frames and disc wheels last month, there’s a lot to process as we prepare for this event. So let’s get into it!

Looking at the Route: London Calling

All categories will race 1 lap of the course, which totals 31.8km with 211m of climbing:

Instead of a complex course breakdown outlining each section, I think it’s simpler to highlight the key climbs and powerup locations:

• Aero Boost at lap arch (0.6km)
• Northumberland Kicker (3.6-4km): Our first proper uphill of the day, you’ll want to up the watts on this short climb to keep your speeds high. Recover on the slight descent that follows.
• Piccadilly Rise (10.9-11.8km): You’ll know this rise is coming when you ride below the overpass. This is a straight, draggy two-step climb on your way to the Classique Reverse section. Hold formation, but kick up the effort to keep your speed up.
• Draft Boost at The Mall Sprint arch (16.5km)
• Richmond Rises (25.8-28.2km): The longest climb of the day, this is really a two-part climb. The first 600 meters is steeper, then there’s a slight flat/downhill section before the final kilometer of slack, very draftable climbing.
• Up from the Underground (30.1-30.2km): Zwifters are familiar with these short, sharp kickers up from the tube. You’ll want to hit the ramp with speed and keep your power high up and over the top. This ensures you maintain momentum and get back up to cruising speed afterward.

Apart from what I’ve listed above, the course could generally be described as “rolling” with lots of small changes in gradient, but nothing major apart from what I’ve called out. That means you’ll want to ride with Trainer Difficulty at 50% or more, so you can be sure to feel small changes in gradient and respond automatically with boosted power, to keep your speed high even on slight rises.

Read more about the London Calling route >

Powerups

This race includes a draft boost and aero boost powerup, as shown above.

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.)

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).

Teams should discuss how best to use these powerups, as you’ll only receive one of each during the race. I see “offense” and “defense” approaches to powerups in this race:

• Offense: Leverage the powerups to maximize your speed on the front. That means triggering your draft boost ~45 seconds before your turn on the front, so your legs are as fresh as possible and you can pull a bit harder. It would also mean using your aero boost while you’re on the front. Note: I’d recommend warning your team over the radio that you’ll be taking a harder/faster pull, so they’re ready for the speed increase.
• Defense: Leverage the powerups to minimize your effort so you can stay in touch with your team without slowing them down. If you’re one of the weaker riders on your team, use the draft and aero boosts while you’re sitting in the wheels to grab a bit more recovery so you can stay in formation and help your team all the way to the finish.

Bike Frame + Wheel Choice

Zwift released several new disc wheelsets back in October, and you may want to buy one for this race. I recommend the CADEX 4-Spoke/Disc, as it’s only 0.2s slower than the most aero disc wheelset in game (the new Reserve Infinity Disc) while climbing 11.5s faster. (It’s also 1.6s faster on flats than the good ol’ DT Swiss 85/Disc many riders own, and handily outclimbs that wheelset.)

Which frame is best for this route, given the terrain? Zwift also released 10 new or updated TT frames in October, and TT racers have been trying to upgrade their frames to stage 5 ever since! If you’re comparing TT frames that are all at the same stage, the new Factor Hanzō is the best choice, as it’s the most aero by 3.1 seconds. The new Canyon Speedmax CFR, which many riders have fully upgraded, is the next best choice.

The Upgrade Stage Question

Of course, many riders will be in a place where they must choose between their older, fully-upgraded TT bike and a newer, less-upgraded one. Happily, you don’t have to do much math to figure out which one to choose! Zwift’s TT bike upgrade scheme is such that the final upgrade step (to stage 5) is massive, making the bike ~26.5 seconds faster across an hour of flat riding. That’s huge, and completely eclipses the performance differences between the top TT frames. Read all about the performance improvements you receive from upgrades >

So despite Zwift releasing a pile of fast TT frames, we’ll see most racers rocking fully upgraded CADEX Tri and Canyon Speedmax CFR bikes this week. Because those are by far the fastest TT weapons most riders have in their garage.

Dive deeper into TT frame and wheel performance:

• TT Frame Performance Charts
• Wheelset Performance Charts

More Route Recons

Many recon rides are planned each week on the upcoming ZRL route. If you’re unfamiliar with this course, jump into an event and familiarize yourself with the route! Find a list of upcoming ZRL recon rides 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. See those below…

John Rice

J Dirom

TTTips

Successful team time trialing on Zwift requires mastering a challenging mix of physical strength, proper pacing, precise positioning, and Zwift minutiae like picking the fastest rig, understanding drafting in a TTT context, and fully upgrading your frame. On top of that, this is only our second ZRL TTT with two key rule changes:

• 5-Person Teams: Time is still taken based on your fourth rider across the line, so you can only lose one rider! This means teams must be extra careful to stay together longer, and “mechanicals” can really mess up your race.
• Steering Enabled: Will riders use steering to come off the front? Cut corners? Position themselves in the pace line? Or let the game auto-steer because it gets too messy otherwise?

Flatter courses like this week give valuable seconds to teams with two strengths:

• Big pure-power riders who can keep their watts high on the front while staying in single-file formation to conserve in the draft behind – this will be the biggest key to top performance in London
• Good course awareness, with the rider on the front upping the power significantly on rises in order to maintain pack speed

On a course like this week’s, I recommend all team members set their Trainer Difficulty to the same value, and make sure that value is at least 50%, so you feel slight gradient changes and increase power to compensate. This will help you automatically punch on the uphills, keeping your overall speed high.

Your goal in a ZRL TTT is to get four riders across the line in the shortest time possible. That means every team’s pace plan will differ based on each rider’s abilities. I highly recommend having an experienced DS on Discord directing your team, especially if your team contains inexperienced TTT riders.

Lastly, if you want to go further down the TTT rabbit hole, I highly recommend Dave Edmond’s Zwift TTT Calculator tool.

Questions or Comments?

Share below!