Man City reveal key injury ahead of Brighton as Liverpool earn title boost
Manchester City have confirmed that striker Erling Haaland will not be fit for their clash with Brighton on Thursday.
Advertisement
Hide AdAdvertisement
Hide AdThe Norwegian was absent for his side’s semi-final victory over Chelsea at the weekend after limping off against Real Madrid in the Champions League as they were knocked out in the quarter-finals. There was also questions marks next to both John Stones and Phil Foden who both also missed out against Chelsea and Pep Guardiola revealed the latest on the trio at his press conference ahead of their trip to the Amex Stadium.
“Erling is not ready for tomorrow and the other two are ready,” he told reporters in Wednesday’s press conference. “I’m not concerned [about Haaland]. It’s not a big issue but he is not available for this game.”
Asked about the possibility of rotating his squad, the City boss added: “I don't know what rotate means. Players deserve to play and every person has their starting XI but everyone has their contribution. Now we had three or four days, the last game against Chelsea and tomorrow is one of the toughest games of the season. Brighton away in my calendar is one of the toughest ones for the way we play.”
Advertisement
Hide AdAdvertisement
Hide AdHaaland has been in good goalscoring form, netting 31 goals in 39 games in all competitions and he had scored in his last two league games before the defeat to Madrid.
City travel to face 10th-place Brighton who are missing a whole host of first team names hoping to make up ground to both Liverpool and Arsenal who won at Fulham and Wolves, respectively, at the weekend to pull clear in the title race. Liverpool face Everton in the Merseyside derby while Arsenal posted a dominant 5-0 win over Chelsea last night but City will still have a game in hand after Brighton.
Comment Guidelines
National World encourages reader discussion on our stories. User feedback, insights and back-and-forth exchanges add a rich layer of context to reporting. Please review our Community Guidelines before commenting.