Bassey confirms contract talks with Fulham amid United interest
Summarised from 2 outlets · Updated 22 Nov, 13:43 · Archive
Fulham defender Calvin Bassey says he is negotiating a new contract with the club despite Manchester United interest.
Calvin Bassey has confirmed he is in contract negotiations with Fulham amid reported interest from Manchester United. The 26-year-old centre-back is happy at the club and committed to extending his stay in west London.
Bassey, who is in the third year of a four-year contract at Fulham, was expected to be a transfer target for Manchester United manager Mauricio Pochettino in the January window. Fulham made him captain in the summer and want to keep him, holding the option to extend his contract by a further 12 months beyond its current summer expiration.
After Fulham drew 1-1 with Manchester City on Saturday, Bassey told TNT Sports: 'We are negotiating, we are still talking. It's an amazing place to be, I have settled in nicely and the manager has put a lot of faith and trust in me.' Fulham manager Alvaro Arbeloa described Bassey as 'one of the best defenders in the world'. Bassey has played every minute of Fulham's league campaign this season.
How it is being reported
- Manchester United transfer target confirms new contract talksCalvin Bassey to settled at Fulham amid talks to extend his stayEvening Standard · 22 Nov, 13:23
- Calvin Bassey responds to Man Utd interest after Fulham star frustrates Man CityBassey helped Fulham pick up a point at the Etihad (Picture: Shutterstock) Calvin Bassey says he is happy at Fulham amid interest from Manchester United , confirming negotiations are underway over a new contract. Bassey, 26, has emerged as a leading transfer target for United with new head coach…Metro · 21 Nov, 15:00
In this story: Calvin Bassey · Fulham · Manchester United · Mauricio Pochettino · Alvaro Arbeloa · Manchester City
This summary was written by AI from the headlines and standfirsts above, and states as fact only what at least two outlets report. How we use AI · Report a problem · Corrections log
Comments (0)