top of page

Morocco's King, awarded by CAF, Announced Joint Bid with Spain, Portugal to host 2030 World Cup

Kigali - The Moroccan King Mohammed VI announced on Tuesday Morocco's joint bid with Spain and Portugal to host the World Cup in 2030.

"I would like to announce, before this assembly, that the Kingdom of Morocco has decided, together with Spain and Portugal, to present a joint bid to host the 2030 World Cup," said HM the King in a message on the occasion of the presentation of the Confederation of African Football (CAF) President's Outstanding Achievement Award 2022 to the Sovereign in Rwanda's Kigali.

"This joint bid, which is unprecedented in football history, will bring together Africa and Europe, the northern and southern Mediterranean, and the African, Arab and Euro-Mediterranean worlds," said the Sovereign in this message read by the Minister of National Education, National Formation and Sport, Chakib Benmoussa.

The Sovereign further specified that this candidacy "will also bring out the best in all of us - in effect, a combination of genius, creativity, experience, and means."


It is important to mention that the Confederation of African Football (CAF) awarded on Tuesday in Kigali, Rwanda, its President's Outstanding Achievement Award 2022 to the Moroccan King Mohammed VI and Rwandan President Paul Kagame.

The trophy "CAF President's Outstanding Achievement Award" was presented by FIFA President Gianni Infantino and CAF President Patrice Motsepe to the Minister of National Education, Preschool and Sports, Chakib Benmoussa.

The award ceremony was attended by FIFA President Gianni Infantino, members of the CAF Executive Committee, Presidents of CAF Member Associations and soccer legends.

The ceremony was marked by the screening of a video recounting the epic of the Atlas Lions in the Qatar-2022 World Cup and highlighting the leading role of the Moroccan King Mohammed VI in the promotion and development of national soccer.

3 views0 comments

Comments

Couldn’t Load Comments
It looks like there was a technical problem. Try reconnecting or refreshing the page.
bottom of page