Injury
Benjamin Sesko ruled out until at least January with shin injury
The Manchester United striker has not featured since September and will miss several more weeks of action.
FootVal Newsroom
Manchester United striker Benjamin Sesko is confirmed out until at least January with a shin injury, BBC Sport and The Athletic report. The 23-year-old Slovenian has not played since September and requires a period of rest to ensure a full recovery.
The news compounds a difficult spell for manager Michael Carrick. According to Mundo Deportivo, United sit fifth from bottom in the Premier League, a single point above the relegation zone, and Carrick's position as head coach is already under scrutiny.
The Daily Mail notes that the absence highlights United's decision not to sign an additional striker last summer, leaving them short of options in attack. Sesko had made four appearances in all competitions this season, scoring once, before the injury curtailed his campaign.
FootVal values Sesko at €77m, close to his Transfermarkt market value of €75m. He joined United on a contract running until June 2030.
Sources
This article is based on reports by:
- BBC Sport — Sesko ruled out until January with shin injury
- Record — Sesko custou 76,5 milhões, não joga desde setembro pelo Man. United e vai ficar fora até ao fim do ano
- Mundo Deportivo — Es un no parar: otro problema para Carrick y se trata de una lesión
- Evening Standard — Benjamin Sesko facing months out as Manchester United injury misery compounds
- Maisfutebol — Man United continua sem goleador: Sesko só regressa em 2027
- Laurie Whitwell (@lauriewhitwell) — 🚨 Confirmed: Benjamin Sesko out until at least January through shin injury.
- Daily Mail — Man United dealt major blow with Benjamin Sesko set to be ruled out until January with shin injury - compounding club's decision not to sign another striker last summer
- Mirror — Man Utd hit with major injury blow as Benjamin Sesko faces months out
Written by the FootVal newsroom from the reports below, with figures from FootVal’s own database. Spotted a mistake? Tell us. · How we report