LALIGA’s final match commentary records Elche 2–3 Real Sociedad on 7 September 2026. The same timeline includes an earlier Real Sociedad effort that was ruled out after VAR. That combination is a useful reminder: an apparent goal, a decision about that goal and the final score are three different pieces of information.
For readers following Elche vs Real Sociedad, the safest starting point is the official LALIGA match record, not an isolated goal notification. This guide explains how to read those updates. It is not a prediction, a betting recommendation or a claim that every conflicting score is caused by VAR.
What the match timeline actually records
The official commentary lists a disallowed Luka Sucic effort at 61 minutes and a no-goal VAR decision at 63 minutes, with the score still Elche 0–2 Real Sociedad. Later entries record Elche’s two goals and a separate Sucic goal at 90 minutes. The closing commentary gives the final 2–3 result.
Those entries should not be combined into an extra goal for Real Sociedad. The earlier disallowed effort and the later scoring event are separate incidents, even though the same player’s name appears. Nor should a reader reconstruct an exact review duration simply by subtracting rounded minute labels.
The rule explanation below does not claim to reconstruct the referee’s complete reasoning in this match. A short text entry is not a substitute for an official explanation of a disputed decision or full footage of the incident.
Goal alert, review decision and final result
When reading a timeline, give each update a job. An event alert tells you that something has happened. A review entry tells you the status of a decision. The completed result tells you how the match ended. Keeping those jobs separate makes the page much easier to interpret.
| What you see | What it establishes | What to check next |
|---|---|---|
| A goal notification | The feed has reported a scoring event | Whether a later entry confirms or cancels it |
| A VAR check or review message | An incident is being assessed | The referee’s resulting decision |
| A goal-disallowed entry | That effort does not count as a goal | The corrected running score |
| A half-time score | The score at the interval | The second-half record, not a final-result assumption |
| A full-time result | The recorded outcome of the completed match | The competition’s official result page if feeds disagree |
This table is a reading aid, not a promise that every app uses identical labels. One service may update a banner before its commentary; another may present the same information in a different order. If the pieces disagree, avoid inventing a reason for the mismatch.
What VAR can check around a goal
The IFAB VAR protocol includes goal/no-goal decisions. Reviewable issues can involve an attacking offence in the build-up, such as offside or a foul, or the ball going out of play before the goal. The referee makes the final decision, using VAR information or an on-field review as appropriate.
A check does not automatically mean a goal will be overturned. Equally, the absence of a pitchside-monitor visit does not establish that no check took place. The protocol distinguishes the video checking process from an on-field review. It also prioritises accuracy over a fixed review time limit.
For readers, the useful action is to wait for the recorded decision rather than predicting it from a replay angle or the length of a delay. This article covers the goal-related reading question, not every reviewable category or competition-specific implementation.
Two examples that prevent double-counting
Example A: an apparent equaliser is ruled out. Imagine a team trailing 0–1 puts the ball into the net and a notification briefly presents 1–1. A later decision rules that effort out. The accepted running score remains 0–1; the alert and the correction are not two separate scoring events. These numbers are hypothetical, not a description of the Elche incident.
Example B: a later goal by the same player stands. Imagine the same player subsequently scores a valid equaliser. The timeline can now contain a disallowed effort and a valid goal under that player’s name. Count the valid goal once. Searching the page for the player’s name and counting every mention would produce the wrong total.
These examples explain why a timeline needs to be read in sequence. The striking image, the first notification and the loudest reaction may help you notice an incident, but none is enough to settle the running total by itself.
If two pages show different scores
Check the basics before choosing which page to trust. Are the teams and fixture date identical? Is one page showing half-time or an earlier minute? Does one have an explicit final-result entry? Are you reading the page itself or an older search snippet?
For this article, the final-result evidence is LALIGA’s closing commentary and its Real Sociedad results list. During research, some extracted page summaries still reflected an earlier stage of the match. That is a reason to examine the status and the detailed record, not proof of another goal or a specific technical fault.
The same principle applies outside football. A cricket total can describe an unfinished innings rather than a win; our Hong Kong vs Nepal scorecard guide explains how runs, wickets and overs fit together. In both sports, preserve the context when sharing a screenshot.
A short final-score check
- Open the exact fixture and confirm the date and competition.
- Look for an explicit completed-match result.
- Read later decisions attached to any goal that was checked or disallowed.
- Keep separate incidents separate, even if the same scorer appears twice.
- If an official explanation is unavailable, say what the record shows without supplying your own cause.
A late event also needs the right time label. Added time is not the same as the separate extra-time periods used in some competitions; see added time versus extra time for that different question. Here, the central habit is simpler: confirm the status of the event before treating a score alert as the result.
Editorial note: Checked on 8 September 2026 against the linked LALIGA record and IFAB protocol. The cover is an illustrative editorial graphic, not a photograph of this match or its officials.