Why Manchester United replaced Alejandro Garnacho during Liverpool FC draw as double injury update issued

The Argentine teenager was taken off during Man Utd's draw with Liverpool FC in the Premier League
Alejandro Garnacho has played a lot of football recentlyAlejandro Garnacho has played a lot of football recently
Alejandro Garnacho has played a lot of football recently

Erik ten Hag has explained why he made the controversial decision to take Alejandro Garnacho off during Manchester United’s draw with Liverpool in the Premier League.

United were held to a 2-2 draw by Jurgen Klopp’s side at Old Trafford after a spirited second-half performance that saw them come from behind to lead in the match. Liverpool were ahead at half-time through Luis Diaz before two superb strikes from Bruno Fernandes and Kobbie Mainoo turned the game on its head.

Hide Ad
Hide Ad

United had looked to hold onto their lead by bringing on the defence-minded Sofyan Amrabat in place of Garnacho, however, they were denied a victory five minutes later when Mohamed Salah levelled from the penalty spot following a foul by Aaron Wan-Bissaka.

Garnacho had been one of the stars of United’s clash with Chelsea in midweek and after the match Ten Hag revealed why that played a part in his early withdrawal against Liverpool. “Today Alejandro wasn’t his game,” he told reporters. “He wasn’t that fresh as he can usually be, he always had some decisive moments in games, he was tired, we are winning at that moment, they went more offensive in that period, to bring more control in the centre of the midfield.”

Raphael Varane and Jonny Evans both missed the match after they were taken off in the Chelsea defeat and Ten Hag was coy on when they could return to action.

Quizzed on the pair, he simply said: “I don’t think at short notice they will return.”

Related topics:

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.