# Enzo Maresca Calls Out VAR Mistake in Manchester Derby

> Maresca highlights past VAR error to challenge City’s recent win.
- Title: Enzo Maresca Calls Out VAR Mistake in Manchester Derby · SI
- Summary: Maresca highlights past VAR error to challenge City’s recent win. Maresca criticized Manchester City’s controversial VAR decision in the derby, citing a…
- Keywords: enzo maresca, manchester city, manchester united, var, manchester derby, erling haaland, enzo fernandez, bruno fernandes, marcus rashford, premier league, sports, Enzo
- Source: SI — https://si.com/soccer/enzo-maresca-old-manchester-derby-beef-make-point
- Published: 2026-09-16T15:30:39+00:00
- Read time: 1 min
- Topics: enzo maresca, manchester city, manchester united, var, manchester derby, erling haaland, enzo fernandez, bruno fernandes, marcus rashford, premier league, sports
## Maresca responds to derby controversy
Enzo Maresca called Manchester City’s performance 'quite poor' after their controversial derby win.

> quite poor
## VAR decision in derby match
The match was decided when Erling Haaland turned the ball into the net at the far post, initially flagged offside.
## VAR failed to assess Fernández
A VAR intervention deemed Haaland onside but failed to establish Enzo Fernández was actively involved from an offside position.
## Maresca’s performance critique
Maresca said City played for 70-75 minutes with 10 players after Phil Foden’s red card and called the performance 'unbelievable'.

> unbelievable
## Maresca on lucky breaks
Maresca acknowledged City got a lucky break but insisted it’s just life in football.
## Maresca’s 2023 derby reference
Maresca cited a similar offside error from January 2023 where United won 2-1 with Bruno Fernandes scoring after Marcus Rashford chased the ball.
## Maresca’s call for apology
Maresca said City still waits for an apology for the 2023 error, which no one apologized for.

> no one apologized
## Key takeaway

Maresca criticized Manchester City’s controversial VAR decision in the derby, citing a similar mistake from 2023 that went unapologized.