The Grey Zone of VAR in V.League: The Seconds Nobody Codes

Minute 89, a long ball down the left channel. The referee waves play on. Forty seconds later, his earpiece buzzes, and the whole stadium waits in silence. The clock on the big screen climbs from 0:00 to 3:47. Final verdict: no offside, no penalty.

I sat with that match afterwards and coded it frame by frame. What decided it was not the striker's foot. It was the trailing knee of the defender, at frame 62 of a clip the broadcaster replayed twice. Some numbers never make it onto a statistics sheet; they live between two touches of the ball.

VAR arrived in V.League 1 in the 2026 season, initially in a handful of matches per round and gradually expanding. What is rarely mentioned: not every match in the same round has VAR. The consequence is one league, one rulebook, but different standards of judgement depending on whether a screen is present. A defender in a non-VAR match is playing a slightly different sport from his colleague in the next fixture.

I work as a data consultant for clubs, and since 2026 I have kept a manual coding sheet for every V.League match with VAR that I could watch. It records four things: the duration of each review, the on-field decision, the final decision, and the seconds of live ball lost to each stoppage. There is no advanced metric here. There is no xG for a decision.

What forced me to rethink my own question was duration. My average sits at 1 minute 52 seconds. Yet the group of decisions that provoked the fiercest controversy, the ones where crowds reacted collectively and pundits argued for a week, averaged only 51 seconds. Shorter, not longer.

Review duration does not measure how complex an incident is; it measures how confident the referee team is. When they take nearly four minutes, they are usually looking for grounds to keep their original call. When they decide in under a minute, they are sure, and that is precisely when viewers at home never see the frame the officials saw.

Another layer of the problem is how heavy the original on-field decision is. In my sheet, the reversal rate depends strongly on what the referee already gave. When he awards a penalty, the VAR team rarely overturns. When he does not, the VAR team is even less likely to intervene. Both directions are anchored to the call already made. The “clear and obvious error” threshold written into the laws is not a number; it is the gap between two people watching the same frame and disagreeing about what they are looking at.

Then there is the hardware. Most VAR footage fed to referees in V.League runs at 25 frames per second. At that rate, consecutive frames sit 0.04 seconds apart. A player running at 7 metres per second covers 28 centimetres between two frames. In most offside incidents I have coded, 28 centimetres is the entire distance between offside and onside. One frame earlier is a foul; one frame later is legal. The error is not in the referee's eye; it is in the grid of time the technology hands him.

Behind those numbers are the people who never appear in a data export. Assistant referees are the clearest case. Before VAR, a correct flag was a complete, countable action. After VAR, the correct flag is erased from memory because it creates no argument, while the wrong flag is remembered because VAR intervened. Their record only runs in one direction. I once watched tape of a match where an assistant delivered six consecutive correct offside calls in the first half, and his name was not mentioned once in the post-match coverage. A season is not the sum of 38 matches; it is the repetition of 17 forgotten passes.

In the same group sit the goalkeepers who face penalties. In V.League, a keeper may face only five to seven spot kicks across a whole season. With a sample that small, saving three turns him into an expert in the press, and saving none raises questions about his mentality. We are ranking goalkeepers on a sample smaller than a single match. I once wrote about a young women's goalkeeper with a 43 per cent save rate built on reading the striker's hip movement, something that exists in no data export anywhere.

Meanwhile, most of the airtime goes to names like Nguyễn Quang Hải or Nguyễn Tiến Linh, players who hardly decide any VAR incident at all. The big names take the light; the people who actually decide stand in the dark.

People say VAR has increased the number of penalties in V.League. I have no evidence for that. The penalty count in a given round depends on how many cameras are at the ground, whether VAR was applied to that fixture, and whether the referee was invited to review. Those three variables move together, which makes it very easy to collapse them into a single cause when you look at a chart.

And something more uncomfortable: reducing errors does not reduce controversy. It only moves the argument from what the referee saw to where the intervention threshold sits. Once viewers believe a single correct frame exists, they will demand to see it. In V.League, the audio between the referee and the VAR team is not published. The entire public debate is being conducted on one third of the data that actually exists.

In a corridor, if you only look towards the light, you will miss what is standing in the shadow.

The signal I am tracking next round is not the card count, and not the number of VAR interventions. It is the duration of the first review of each match. A referee team that reviews for under 40 seconds usually had its answer before stepping to the monitor. A team that reviews for more than three minutes is negotiating with itself.