RDU and Chakki among players for first Legendary Series Match Day

The Hearthstone Legendary Series is officially underway, with the first Challenger Tournament having kicked off this Monday! More than 400 players took up the challenge to seize one of the two qualification slots that will enable them to take part in the Legendary Series Match Day and face the invited pros.

Check out our Hearthstone Legendary Series portal!

The four invited pro players have already been confirmed, meaning that the first Legendary Series Match Day Week will feature:

  • Reynad
  • Chakki
  • RDU
  • Hosty

Furthermore, the pre-tournament already took place last week, with compLexity Gaming’s Alchemixt having locked down one slot for the Legendary Series Match Day and gcttirth having been the second player to qualify. The only thing that remains now is to determine the final two Challenger Series players who will join RDU and company in the Legendary Series Match Day on November the 22nd.

You can read up on the tournament format on the official Hearthstone Legendary Series portal or in our previous announcement article. Don’t forget that you can still sign up for the Open Challenger Series Tournaments for the following weeks - if you want to play against some of the world’s best Hearthstone players, why not give it a go?

 

Login at ESL & Partner

Chose the Account you want to login to play your favorite game

Newsletter

Stay up to date

* indicates required


By clicking the "Subscribe" button, I consent to the processing of my personal data and tracking of my activity for marketing purposes, and I agree to receive marketing communications, including newsletters, raffles and surveys from ESL Gaming GmbH, in joint controllership with Dreamhack AB and ESL Gaming Online Inc., all around their products/services. I have read ESL Privacy Notice and I understand I can withdraw my consent at any time.

I understand Braze, a marketing platform, is being used. By clicking to subscribe, I acknowledge that my personal data will be transferred to Braze for processing. Learn more about Braze's privacy practices here.