Tottenham Hotspur have agreed a £55 million transfer fee with West Ham United for highly-rated right winger Mohammed Kudus.
The Ghanaian international is now set to undergo a medical before finalising terms on a long-term contract with Spurs.
Kudus, 24, moved to West Ham from Ajax for £38 million in the summer of 2023.
Although the midfielder had an £85 million release clause, his recent performances and potential saw significant interest from multiple top clubs. Despite this, well-placed sources revealed that Kudus had made it clear he wanted to join Tottenham, beating other suitors to his signature.
Veteran sports journalist David Ornstein broke the news on X.
🚨 EXCLUSIVE: Tottenham Hotspur reach total agreement with West Ham United to sign Mohammed Kudus. Deal for 24yo #WHUFC forward worth in region of £55m. Medical scheduled on Thursday ahead of Ghana international joining #THFC on 6yr contract @TheAthleticFC https://t.co/eioDT7TZfX
— David Ornstein (@David_Ornstein) July 9, 2025
Having made 65 Premier League appearances for the Hammers, Kudus scored 13 goals and provided 9 assists during his time at the London Stadium.
However, after an electric start to his West Ham career in 2023-24, the winger's form waned last season, scoring just five goals in the Premier League.
His dip in form came as he struggled to adapt to head coach Graham Potter’s tactics, often being deployed in unfamiliar roles up front, rather than in his preferred wide positions. West Ham also had Jarrod Bowen in a similar role, making it difficult for Kudus to consistently deliver.
Kudus’ move to Spurs marks a fresh start, where he will be hoping to rediscover his best form and make an impact under new Tottenham head coach Thomas Frank.
As the 2025-26 season approaches, Spurs fans will be keen to see how the winger fits into their plans, with his creative abilities and goal-scoring potential offering exciting prospects for the club's future.
COMMENTS
Comments are moderated and generally will be posted if they are on-topic and not abusive.
For more information, please see our Comments FAQ