Iran's Winning Goal Disallowed: Why the Offside Rule Is Not What Most Fans Think

The Moment That Had Iran Furious and Twitter Melting Down

Ninety minutes and six seconds of additional time. Iran leading Egypt 2-1 in a 2026 FIFA World Cup group match. A goalmouth scramble. A rebound falls to Iran's #4, who tucks it away. Pandemonium — and then, silence. Referee Szymon Marciniak is called to the monitor, and the flag goes up. Goal disallowed. Offside.

The Iran players surrounded Marciniak. On Twitter, the football world erupted in the other direction: "The keeper touched it!" "It came off the post!" "How is that still offside?!" Seventy-one community downvotes on the OURVAR.AI submission against four upvotes tell you everything about how the public read this moment.

The public were wrong. The AI was right. And the gap between those two positions is a gap in understanding one of football's most misread rules.

What OURVAR.AI Ruled

OURVAR.AI's verdict on Case #143: CORRECT DECISION, HIGH confidence.

The platform cited Law 11 — Offside, and specifically the clause that governs exactly when offside position is assessed: the instant the ball is last played or touched by a teammate. Iran #4 was in an offside position at that precise moment — the original shot that preceded the rebound. That position was not estimated or eyeballed. It was confirmed by semi-automated offside technology (SAOT), which generates a frame-accurate skeletal position of every player at the critical millisecond. There is no margin for human error in the position determination here.

The recommended action: goal disallowed. Correct.

Why the Law Says What It Says

Here is where most people switch off in frustration, so let's go slowly.

Step one: when is offside judged?

Not when you score. Not when the ball reaches you. Offside is judged at the moment the ball leaves your teammate's foot — or head, or any body part. Everything after that is consequence, not cause.

In this case, the moment is the original shot. At that instant, #4 is ahead of Egypt's second-last defender (#9, since the goalkeeper is the last). That makes #4 in an offside position before anything else happens.

Step two: does the rebound change anything?

This is the crux, and the answer depends entirely on what the ball rebounds off.

The rebound in this case came off the goalkeeper, the post, or a deflection — the case data makes clear it was not an Egypt defender making a deliberate, controlled play on the ball. That one column on the right — the only scenario that resets offside — never applied.

Step three: what does #4 do?

He scores from the rebound. Under Law 11, that act — playing the ball while in an offside position from an unsettled phase — makes him an active offside player. That is the offside offence. The goal must come off.

The logic is not arbitrary. The rule exists precisely because if a goalkeeper's save automatically reset offside, attackers could simply stand in front of the keeper and poach every rebound, rendering the offside law meaningless in the six-yard box. IFAB closed that loophole deliberately, and it has been in the Laws for years.

The Community Votes: A Tutorial in the Making

71 downvotes to 4 upvotes. The submitter left no rating. But those numbers are a perfect illustration of why OURVAR.AI exists.

The community clearly felt — overwhelmingly — that the goal was good. The "keeper touched it" logic is deeply intuitive. Football fans are used to the idea that when a goalkeeper parries a ball, something resets, something changes. In a sense it does: it is a new phase of open play. But it is not a new phase for offside purposes if no defender deliberately played the ball. Intuition collides with statute, and statute wins.

The vote gap is not a sign that the platform got it wrong. It is a sign that Law 11's rebound clause is genuinely counter-intuitive — and genuinely misunderstood at scale. That 71-to-4 split would not look very different in a room full of football journalists, let alone casual fans.

When Does This Call Go the Other Way?

This is worth asking. The rule above — deliberate defensive play resets offside — does come up in real matches, and it does occasionally favour attackers.

Under general IFAB Law 11 guidance, if an Egypt defender had chosen to play the ball in that goalmouth scramble — a header away, a deliberate block into a different direction, a clearance that was controlled and intentional — the offside from the original shot would have been wiped. #4 would have been judged from that new moment, and if he was onside then, the goal would have stood.

The practical problem is that "deliberate" versus "deflection" is itself a judgment call, and it sits with the VAR team watching high-frame-rate footage. In cases where the contact is ambiguous — a defender sticking out a foot at speed — you can construct arguments either way. This case, evidently, was not ambiguous. The VAR and SAOT system gave Marciniak the confidence to disallow it at HIGH certainty.

The wider lesson: if you see a scramble in the box and want to know whether a rebound goal will stand, the question to ask is not "did the keeper touch it?" The question is "did a defender choose to play the ball?" Those are very different things, and the answer to the second question is what the Law actually hinges on.

The Bottom Line

In the sixth minute of stoppage time, with Iran leading 2-1, #4 scored a rebound goal that looked and felt like a legitimate finish. Referee Szymon Marciniak — one of the world's most experienced officials — had it checked, had it confirmed, and disallowed it. The semi-automated technology placed #4 in an offside position at the original shot. The rebound came off the keeper or the woodwork, not a deliberate defensive play. Law 11 is unambiguous. The goal was not.

OURVAR.AI's analysis — CORRECT DECISION, HIGH confidence — backs Marciniak fully.

Before you write the next furious tweet about a disallowed rebound goal, ask yourself the one question the law actually requires: did a defender choose to play the ball? If the answer is no, the original offside stands.

See the full frame-by-frame case breakdown at https://ourvar.ai/case/143