V.League 1 and the Data Gap: When Every Column Returns N/A

It was 11:47 pm and the lights at Hoa Xuan Stadium had been off for over an hour. The pitch still held the wet streaks of the last watering, and from the technical corridor the sound of a ball rolling against a wall was clear enough for me to count the rhythm. I stayed behind in stand A, opened my laptop, and finished the last row of my personal tracking sheet for a V.League 1 match. The sheet returned a single character, repeated in every cell: N/A.

No duels contested. No average distance between the midfield line and the defensive line when the ball was lost. No passes into the final third.

When the stadium is empty, the sound of the ball becomes data. I listen and I write it down. That night, what I wrote down was a void, and that void deserves more discussion than any spreadsheet I have ever built.

Context: a big league, a thin data layer

V.League 1 operates with 14 clubs, roughly 182 matches per season under a double round-robin format. That scale is enough to sustain an analytics industry if the infrastructure allows it. The infrastructure does not.

What the public can access on a regular basis includes scorelines, goals, cards, and a few basic possession and shooting metrics. What a tactical analyst needs sits on a different layer: how high the defensive line pushes when the team is in possession, who triggers the press, how many metres the gap between the two lines stretches in the first ten seconds after losing the ball.

International data providers do cover Southeast Asian football to a certain degree, but the level of detail varies between competitions. For V.League 1, most of it stops at discrete events: who passed to whom, in which minute. To understand how a team defends, the work has to be done by hand.

Public attention on the domestic league has risen sharply through generations of players such as Nguyen Quang Hai, Nguyen Hoang Duc and Nguyen Tien Linh. Attention does not automatically produce data. The more people watch, the more opinions appear, and the fewer people verify.

I am used to that. The hand-drawn diagrams from the 2026 World Cup still read tonight's match. The frame of reference does not age; only the data is missing.

Analysis: charting by hand, measuring distance, and what it costs

My method is simple and very slow. I time every phase, mark the positions of the four defenders and two central midfielders each time possession changes, then use a ruler on the video frame to convert pixels into metres. One match takes six to eight hours. Then I redraw it as a hand diagram, in pencil, on graph paper.

Here is an example from a match I watched live in Da Nang. The home side conceded twice, both from the left channel. The conventional account stops there: the left side of the defence is weak. When I charted it again, the story was entirely different.

First goal: the left-back pushed 12 metres ahead of the back line, while the nearest central midfielder stood 9 metres inside. The distance between the defensive and midfield lines at that moment was 31 metres, 9 metres wider than that team's own match average of 22 metres. The pass into that space travelled 34 metres and took under two seconds.

Second goal: almost an exact replica, only the starting point differed. The left-back did not push this time, but the holding midfielder was dragged 7 metres toward the touchline, exposing the inside channel. One design flaw, two expressions of it.

That is the entire value of charting by hand. You see exactly where the gap is, how wide it is, and who is responsible for covering it. You also see what the scoreline never says: that team is not bad at defending, it defends a broken structure in one specific zone.

The cost is equally clear. It does not scale: I cannot chart 182 matches in a season. It is subjective when converting the video frame into metres, with an error margin of up to 1.5 metres depending on camera angle. And it depends on me being there, or on a recording sharp enough to use — which not every V.League match has.

Once I verified myself a different way. In May 2026, when the Bundesliga returned to empty stadiums, I wrote a Python script filtering data for the first 12 matches after the restart. Average goals rose from 2.8 to 3.2 per match, and passes into the final third increased by 9 percent. A coach in Vietnam's second tier messaged me asking for the raw data. It was the first time I saw raw data create real-world influence.

I learned the same lesson in reverse from Japan's match against Colombia on 19 June 2026 at the World Cup in Russia. Japan won 2-1 after Colombia lost a man in the third minute. The popular account is that Japan got lucky. When I redrew six hand diagrams, the average distance between Japan's midfield and attack was only 22 metres, against 35 metres for Colombia. The team with the extra man did not rush to push up; they stretched the opponent by keeping their own lines compact. Data does not lie, but it is very good at hiding surprises.

The biggest weakness of a thin data layer sits on the consumer side. Without numbers, stories get written by feeling. A team that loses three in a row is labelled as having a defensive crisis, when those three defeats may all have come from set pieces — a completely different problem in nature and in remedy.

The same logic applies to the transfer market. In V.League, a signing is usually judged on last season's goal tally, almost never on how well the player fits the new team's structure. A striker who scored 12 goals in a counter-attacking side can be nearly invisible in a possession side. Without data on where he receives the ball, that deal will be judged on feeling for the first six rounds.

I also chart pressing traps separately, the hardest thing to read on television. A trap on the right channel has three layers: the wide forward presses inside to cut the pass back to the centre-back, the central midfielder seals the touchline, and the full-back steps up at the right moment. Off by half a second, the opponent escapes and the whole block has to drop 20 metres. On a stats sheet, that phase appears only as a completed pass.

In V.League, such phases are barely recorded at all. No metric measures them, so they vanish from every report. A team that presses well and a team that presses luckily look identical on paper.

Even youth development suffers the same problem. At academies in the country, assessing a fifteen-year-old relies mostly on a coach's impression across a few sessions. Very few places record how often that player receives the ball facing forward, or how many passes he plays in a forward direction in a single practice match.

My job, put briefly, is to rebuild the distance between feeling and structure. Tactics are not magic. It is just that some people look a little longer.

The contrarian angle: an empty cell is a signal, not a void

There is a habit in the industry I want to name directly: treating an empty cell as a safe cell. When an analytical sheet has no data, internal reports tend to say "no notable issues found". The N/A gets read as fine.

An empty data cell does not mean risk is zero. It means risk is unmeasured. The two sentences differ in exactly one way: the first lets you sit still, the second forces you to go find the footage.

I have paid the price for misreading one number. In December 2026, analysing Morocco's defence at the World Cup, I wrote that they won 14 of 14 aerial duels. The true figure was 13 of 14. An account dedicated to auditing data spotted it within hours. I did not argue. I deleted the post, rewatched all the footage, and republished a correction within two hours, opening with a line stating exactly where the error was. Readership doubled, but what actually grew was my discipline afterwards.

Since then, every number I publish must pass through at least two independent sources, with the date the data was collected attached. One source is the footage. The other is my own hand chart, redone on a different day, when my eyes have forgotten.

Many people ask me, sometimes without hiding their scepticism, what a person who writes about football can possibly write. They ask what a girl knows about football. I show them a pressing trap: a diagram of a trap on the right channel, quantified, with timestamps.

The deeper problem sits in coaching education. Former stars opening youth academies is good for image and inspiration, but most of it stops there. What is severely missing is a systematic pathway for grassroots coach education — people who teach a ten-year-old to read space, not to shoot harder. Without that layer, the data layer above stays thin forever.

What to verify next round

Three things I will do myself next round, made public so anyone can check them. One: re-measure the distance between the defensive and midfield lines for the two teams labelled weakest defensively over the past three rounds, to separate structural errors from set-piece errors. Two: count losses of possession within 15 metres of the opponent's box. Three: find the team whose line-breaking passes have surged while its chances created have not moved.

Based on my experience watching matches, most wrong conclusions come not from a lack of data, but from reading an empty cell as reassurance. The crowd watches the stars; I watch the space behind them. A match does not end at the 90th minute, it ends when I find the pattern. If next round the data sheet returns an empty column, I will write exactly one line in it: not yet measured. Then I will close the laptop, rewind the footage, and measure it anyway.