SportsCatch
EN

Olise wants €200m release clause to keep Real Madrid door open

Michael Olise is negotiating a contract extension with Bayern Munich but is pushing for the inclusion of a release clause that would allow him to leave, with Real Madrid in the background and a figure around €200 million under discussion.

1 min read
Olise wants €200m release clause to keep Real Madrid door open
Share

Michael Olise is negotiating a contract extension with Bayern Munich, but the French international wants to include a release clause that would give him the freedom to leave — a demand that is complicating talks with the Bavarian club’s management.

According to Spanish newspaper AS, Olise is pushing to obtain this contractual exit door, a mechanism unusual in the Bundesliga but already used by Erling Haaland, Josko Gvardiol and Dani Olmo. Bayern, backed by the fees charged during last summer’s transfer window — marked by several transfers exceeding €100 million — is demanding a threshold of €200 million. The player’s entourage, meanwhile, would prefer a more accessible figure to keep doors open.

The German club remains determined to keep its winger and would be willing to double his annual salary, raising it from €14 million to €27 million, which would place him above Jamal Musiala and Harry Kane in the club’s wage hierarchy.

The extension would therefore not end the saga. Several rumours circulated this summer about mutual interest between Olise and Real Madrid, and they are considered credible by market observers. The former Crystal Palace player, brilliant since his arrival in Bavaria and regularly decisive with the France team, has established himself as one of the most coveted profiles in European football.

The outcome of this matter could make Olise the big attraction of the 2027 transfer window, provided both parties find common ground on the release clause amount — the real crux of the ongoing negotiations.

Share
{# Sitewide native fullscreen interstitial — our own bet-CTA card blown up to a takeover (replaces the SDK overlay). The shared card animations + countdown load once, AFTER the interstitial markup, so the countdown script's first tick sees this card's node too (the in-read card, in
above, already exists). One include covers both surfaces. #}