Arsenal and Mikel Arteta 'reveal' Emile Smith Rowe transfer stance amid West Ham and Fulham links

Emile Smith Rowe has started just twice in the Premier League since the beginning of last season

Arsenal are not prepared to let Emile Smith Rowe leave on loan this winter, according to reports. A string of injuries has frustrated the 23-year-old’s progress at the Emirates. Astonishingly, Smith Rowe has started just two Premier League games since the beginning of last season.

Mikel Arteta has a preferred attacking trio of Gabriel Martinelli, Martin Odegaard and Bukayo Saka playing behind a lone striker. Signing Leandro Trossard and Kai Havertz in recent windows has resulted in him falling further down the pecking order.

Hide Ad
Hide Ad

The Gunners boss told reporters ahead of the clash against Crystal Palace that he is “happy” with Smith Rowe’s progress. Arteta said: “I’m really happy with Emile. He’s on the right trajectory and now he’s settled, he’s training really well and you know I’m not going to be talking about any individual situation.

“Emile is Emile. He’s got incredible qualities and we are really happy to have him. What he needs now is a chance to put all the desire and qualities that he has on the pitch and in order to do that we have to give him minutes.”

Now reports are claiming Arsenal will reject any approaches for their academy product in the January transfer window. West Ham United had emerged as a possible destination until the end of the season. David Moyes is aiming for an attacking solution after losing Jarrod Bowen and Lucas Paqueta to injury. The latter is not expected to return until March - making a move for Smith Rowe a priority.

However, the Gunners are not expected to entertain any offers mid-season for the midfielder. Fulham were another London club considering a loan move for the Croydon-born star.

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.