The ZwiftQuest is back. It’s a fun way to break the routine of indoor cycling with a unique competitive format. (It’s been a while since I’ve done my last Zwift race. My issue with them is not so much that I can’t hold the pace of the leaders in my category… it’s that I’m a bit tired of all the multi-lap crits around the Volcano or the London Classique course.) To me, ZwiftQuest sounded very promising.

The idea of ZwiftQuest is some sort of virtual bike treasure hunt. Each challenge provides a map with a list of checkpoints that you need to pass. The trick is to be fast, but you can be fast in different ways. You can just push as hard as possible, or you try to find the smartest route. If you want to win, you need both. You can complete the ZwiftQuest at any time over a period of several days. The inaugural London ZwiftQuest was active for the three London days that also brought us the Leith Hill expansion.

A quick look at how this works:

  • First, connect your Strava account with ZwiftQuest on at
  • Then, plan your route and get going
  • You start by crossing the start/finish arch. One of the five to six checkpoints is going to be the one that you should cross last. (You can pass it several times before on your way to other checkpoints. ZwiftQuest considers the last time you pass by.) ZwiftQuest will automatically estimate the distance that you covered between the first and last checkpoint, and it will validate that you included all other checkpoints in between. Spoiler: I didn’t.
  • After your ride, include a specific code word in your activity title (for the first London quest, it was ZQLDN1), and if necessary, re-process the results from ZwiftQuest’s results page.
  • Magically, you will appear in one of the results list. It should be the one with the actual results. For me, it was the list of failed attempts.

My FTP is high enough to compete in C, but even in C, I will come in among the last in a race. I knew in advance that I would not win the ZwiftQuest by time. For me, the challenge was in finding the shortest route. The key is to make use of u-turns as much as possible in order to avoid unnecessary loops, then to turn around as fast as possible after you’ve reached the checkpoint, and not to take the wrong turns.

On my first attempt, I did pretty bad and reasonably well at the same time. Pretty bad, because at some point I turned left one road to early, and wasted something like 500m on recovering from that. Pretty bad, because I missed that one checkpoint that kicked me out of the classification. I simply forgot about it. Pretty bad, because I approached the final checkpoint as my penultimate checkpoint (of those that I remembered). Pretty good, because had I not made these mistakes, I actually would have found the shortest route (alongside almost all others). But I didn’t. So in the list of failed attempts, my distance is actually the one that I covered until I really passed all the checkpoints.

One thing I like about the ZwiftQuest is that it’s not intrusive. I don’t have to decide between race and workout. I can do other things on that ride. I can do a normal workout. I could even participate in another race. I can (and did) continue riding after I (thought I) completed my journey along the checkpoints. I added my first attempt of Leith Hill afterwards. All that does not cause trouble for ZwiftQuest. You only need to include that code word in your activity title and follow a valid route.

And you can do it at the pace you want. As ZwiftQuest grows, I can imagine informal group rides will form, so people can benefit from drafting. And in fact, there has been a ZwiftQuest race in the past. For the time being, it’s a lone adventure. Imagine being dropped after the first kilometer in a Zwift race and completing it by yourself. (We’ve all been there, haven’t we?) Pretty much like that, but minus the frustration because you might still do well thanks to your superior navigation skills.

ZwiftQuest is not for people like my highly appreciated former colleague from Rotterdam. Whenever he adds a bike ride on Strava, it’s either route A or route B. ZwiftQuest is for people like me. This past summer I did not follow the exact same route in my usual training area in Milan a single time. On every ride, I tried to find at least one tiny bit of new street. I know all Zwift’s streets, but I try to always change the way I combine them. Still, there are some bits that I usually avoid. For instance, I don’t often go up the Epic KOM on Watopia because it takes half or two thirds of my usual workout time. ZwiftQuest is a fun incentive for me to go for the roads less visited.

Truth is: ZwiftQuest works best on a complex network of roads. The latest two expansions of Watopia and London are vital. Nonetheless, the best routes might soon look very similar. The team at ZwiftQuest could keep it more dynamic if they are going to use their start and finish checkpoints flexibly. And then every new expansion will add more fun. Is it only me or did I see several points on the new roads that already feature some junctions that could turn into expansions? Like that gravel street on top of Leith Hill? ZwiftQuest has great potential. Personally at least, I’m already looking forward to the next quest already.

There are only a few small things that I would love ZwiftQuest to adjust on their website. I finish up this post with them:

  1. It would be great if the results page could highlight the Zwifter that found the shortest route. After all, that’s half of the achievement of completing the ZwiftQuest.
  2. The Zwift page contains a menu item labelled “Events/Results”. However, that’s not where I find the results. In order to see those, I need to go to “My ZwiftQuest”.
  3. I find the button on the “My ZwiftQuest” page to reprocess the results a little bit difficult to see, given how important it is.
  4. Those who completed the Quest can open a detailed look at their attempt, including a map of their route. (Once the quest is completed, everyone can look at the details of anyone’s attempt.) Those who failed can’t. However, they might benefit from having a look at which checkpoint exactly they failed.
  5. The ZwiftQuest website is mobile friendly. That’s awesome, but there’s a catch: I can’t zoom into the map of the running Quest. In order to really understand the location of a marker, I’d need a bigger screen or to zoom in. For instance, for the first London quest, I couldn’t detect on my smartphone whether the marker close to the Western tube tunnel comes before or after the junction that leads to the tunnel.