Alexander Isak's Liverpool Arrival: A Striker's Redemption
Alexander Isak did not just arrive at Portman Road. He finally arrived at Liverpool.
The £125m striker tore into Ipswich Town with two ruthless finishes inside nine minutes, sealing a 2-0 win, Liverpool’s first Premier League victory of the season and the first of Andoni Iraola’s reign after replacing the sacked Arne Slot. By the time the home crowd had caught its breath, the contest was effectively over and Isak was walking off at full-time with the match ball and, perhaps more importantly, his reputation restored.
Yes, the context matters. Ipswich are newly promoted, brave enough on the ball but leaking goals at this level, as shown by the five they conceded at Manchester United a week earlier. They look vulnerable when faced with genuine attacking class. Liverpool brought plenty of that to Suffolk – and for the first time since his record-breaking move from Newcastle United last summer, Isak looked like he truly belonged among it.
This was the version of the Sweden forward Liverpool thought they were buying when they smashed the British transfer record to prise him from Tyneside in an acrimonious deal. Sharp. Lean. Relentless in his running. A menace whenever space appeared behind a defender’s shoulder.
Last season, he was the opposite. He arrived out of shape after forcing through the move, then drifted through a campaign blighted by injuries and indifference. On the pitch he looked like a stranger in red, an emblem of excess in a title defence that crumbled so dramatically it cost Slot his job barely a year after lifting the Premier League trophy.
The numbers told their own damning story. Across all competitions he managed 22 appearances and 1,033 minutes, scoring four times – one goal every 258 minutes. In the league, it was even more stark: 703 minutes, three goals, a strike rate of one every 234 minutes. While he floundered, Hugo Ekitike stole the spotlight up front, leaving Isak looking like the most expensive luxury mistake in British football history.
That is why this night felt different. It was not just that Isak matched his entire league tally from last season within the opening weeks of this one. It was the way he did it. The body language. The aggression in his pressing. The hunger to run in behind, again and again, exactly as he did at Newcastle when his value soared and his name became one of the most coveted in Europe.
Iraola’s tweak was simple but ruthless: play to his strengths or do not play him at all. Liverpool pushed higher, turned Ipswich around and asked Isak to live on the shoulder of the last defender. The reward came almost instantly, twice, and with it came something Liverpool had not seen from him in a year – the look of a striker who knew he was the main man.
He did not do it alone. Cody Gakpo, who could easily have been spending this weekend in Manchester City colours preparing for Coventry City at Etihad Stadium had that transfer not collapsed, knitted everything together behind him. Gakpo’s performance had the feel of a player liberated by a move that never happened, drifting into pockets, sliding passes between lines, dictating tempo. Ipswich could not get near him.
The Dutchman’s virtuoso display might have dominated the headlines on another night. Instead, it became the perfect supporting act to Isak’s redemption story, the clever foil that allowed the Swede to attack the spaces he craves.
There was more for Iraola to enjoy. Bradley Barcola’s £123m price tag carries its own weight of expectation, but in 26 minutes off the bench the winger showed exactly why Liverpool paid it. He stretched Ipswich with bursts of devastating pace, the kind that makes full-backs backpedal and crowds rise. It was only a glimpse, but it was enough to hint at the chaos he can bring once fully integrated.
Even that, though, could not eclipse Isak. Every sprint, every press, every finish suggested a player who has finally tuned into the demands of his new club. For Liverpool, who spent so much and waited so long, the feeling walking out of Suffolk was clear.
The code might just be cracked.





