Sheffield United v Tottenham Hotspur build-up - Blades injury doubt

Sheffield United midfielder John Lundstram is battling to be fit for tonight’s Premier League encounter with Tottenham at Bramall Lane.
By YP Sport
Published 2nd Jul 2020, 11:59 BST
Updated 2nd Jul 2020, 12:06 BST
John Lundstram: Holding his arm before going off injured during the FA Cup match at Bramall Lane. Picture: Simon Bellis/SportimageJohn Lundstram: Holding his arm before going off injured during the FA Cup match at Bramall Lane. Picture: Simon Bellis/Sportimage
John Lundstram: Holding his arm before going off injured during the FA Cup match at Bramall Lane. Picture: Simon Bellis/Sportimage

The 26-year-old Lundstram could miss out after an arm injury forced him off in the FA Cup defeat to Arsenal on Sunday.

“It looked quite an awkward fall so I should imagine he’ll be touch and go,” said manager Chris Wilder.

Hide Ad
Hide Ad

Wilder added that Jack O’Connell was “back on the grass” following the impact injury in training that has ruled him out since the restart and the defender will be assessed.Tottenham have no new injury concerns to contend with.

Defenders Juan Foyth (knee) and Japhet Tanganga (back) are the two absentees for the game at Bramall Lane.

Mourinho has an embarrassment of attacking riches and could rotate his squad.

Sheffield United squad: Henderson, Moore, Verrips, O’Connell, Robinson, Basham, Egan, Baldock, Lundstram, Stevens, Berge, Fleck, Norwood, McBurnie, Sharp, Freeman, Mousset, Clarke, Zivkovic, McGoldrick, Jagielka, Rodwell, Osborn.

Hide Ad
Hide Ad

Tottenham squad: Lloris, Vorm, Gazzaniga, Aurier, Sanchez, Dier, Alderweireld, Vertonghen, Davies, Sessegnon, Winks, Lo Celso, Ndombele, Sissoko, Fernandes, Skipp, Alli, Moura, Lamela, Son, Kane, Bergwijn.

Related topics:John LundstramChris WilderPremier LeagueTottenham HotspurBramall LaneArsenalJack O'Connell

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.