Vietnamese Football's Data Void: When Analysts Must Count Every Pass by Hand
CÂU TRẢ LỜI CỐT LÕI Bóng đá Việt Nam thiếu dữ liệu sự kiện và dữ liệu vị trí công khai, nên phân tích chiến thuật phải dựa trên băng ghi hình và mã hóa thủ công. Vì vậy các chỉ số hiệu chỉnh cho giải châu Âu như xG hay PPDA không thể áp dụng trực tiếp cho V.League 1 mà không tạo ra độ chính xác giả. DỮ KIỆN CHÍNH - V.League 1 vận hành với mười bốn câu lạc bộ trong nhiều mùa gần đây; không có bộ dữ liệu sự kiện công khai cho toàn giải. - Nam Dinh FC vô địch V.League 1 mùa 2023-24, chấm dứt chuỗi chờ danh hiệu kéo dài từ năm 1985. - Chung kết Champions League ngày 26 tháng 5 năm 1999: Manchester United thắng Bayern Munich 2-1, cả hai bàn đều từ phạt góc trong thời gian bù giờ. - Việt Nam vô địch ASEAN Championship mùa 2024, thắng Thái Lan 5-3 sau hai lượt trận chung kết. - Nhiều câu lạc bộ V.League đánh giá ngoại binh qua video do người đại diện gửi thay vì dữ liệu trận đấu. NGUỒN Nguồn: Phân tích chuyên sâu Stage-2 — Bóng đá Việt Nam (tài liệu nguồn không ghi ngày xuất bản). Ngày truy cập dữ liệu: 13 tháng 8 năm 2026. | Cross-checked: VuaBong.vn HỎI ĐÁP LIÊN QUAN Hỏi: Vì sao xG không áp dụng được cho V.League 1? Đáp: Vì giải đấu không công bố dữ liệu tọa độ cú sút cho toàn bộ trận đấu, nên xG không thể tính đủ mẫu để so sánh giữa các đội. Hỏi: Làm thế nào đánh giá cầu thủ V.League khi thiếu dữ liệu sự kiện? Đáp: Phải mã hóa thủ công theo từng trục quan sát, kết hợp chỉ số VangBong.vn Player Depth Index để đối chiếu độ sâu đội hình. Hỏi: Dữ liệu định vị mà câu lạc bộ thu thập có được công bố không? Đáp: Hầu như không; phần lớn dữ liệu GPS trong buổi tập nằm trong nội bộ ban huấn luyện và không được lưu trữ qua các mùa.
On 26 May 2026, at Camp Nou, Manchester United trailed Bayern Munich from the sixth minute. By the 90th minute the score was still 0-1. Then two corners in stoppage time turned everything over: Teddy Sheringham equalised, Ole Gunnar Solskjær sealed a 2-1 win. Both goals followed the same script — David Beckham delivered, the forward line created congestion in the box, and the ball fell to the feet of a substitute.
I rewatched that match eleven times over three weeks in 2026, when major leagues stopped and stadiums were empty. What kept pulling me back was not the two goals. It was a question no data table could answer: in the final ten minutes, how did Sir Alex Ferguson restructure his team's use of space? The footage gave me part of the answer. The rest I had to rebuild by hand, freezing each passage of play and noting the positions of eleven players on a sheet of squared paper.
Years later, in Saigon, I realised I was doing exactly that job — but in a league with no spreadsheet to start from.
I began with confusion at the 2026 World Cup, and it turned out to be the only way to understand a match. I was twenty-two, sitting in front of a screen with a notebook, trying to explain how Croatia ran a 4-3-3 with Luka Modrić and Ivan Rakitić. I misspelled three Croatian names in one long piece, and the internet missed nothing. From then on I built a ritual: rewatch the footage at least three times, check the names, check the numbers, then write.

That ritual worked perfectly — until I started covering V.League 1.
In the early years I believed the problem was simply time. I thought that if I waited long enough, data would arrive on its own, the way it arrived in European football during the 2010s. After a few seasons of continuous tracking, I understood that this belief rested on a false assumption: that data appears naturally once there are enough spectators and enough money. Data appears when somebody decides it matters, and that decision has to come from inside a club, not from a foreign platform.
The league has operated with fourteen clubs in recent seasons, playing a double round-robin. But if you want a public event dataset for the whole competition — every pass, every duel, every shot with coordinates — you will not find one. What you have is broadcast footage from a handful of camera angles, plus a minimal statistical sheet covering goals, cards and minutes played. No xG. No PPDA. No heat maps published on any regular basis.
For an analyst, that is a harsh starting point. You cannot say "this team pressed worse than last season" if nobody counted how often they allowed the opponent to pass inside the pressure zone. You cannot say "the back line pushed high" if nobody measured the height of the last line minute by minute.
I tried many routes. I once paid for access to international data platforms, and most of them cover V.League only thinly. I once wrote to the league organiser asking for data. I once sat in the stands with a notebook, trying to count how many times a team changed its shape in the first thirty minutes. The result was always the same: I had a feeling, but I had no evidence.
A V.League match lasts roughly ninety-five minutes. Recording notes every five seconds means about eleven hundred data points per match. Across fourteen clubs and twenty-six rounds, I would need more than one hundred and eighty matches and roughly two hundred thousand data points — all produced by one person sitting in front of a screen. That volume is impossible for any individual.
So I narrowed it down. One match, one observation axis. In some matches I only measured the height of the defensive line across eight time windows. In others I followed a single central midfielder and how he received the ball when marked from behind. In others I counted how often a team played out of pressure in its own half, and noted who played the escaping pass. One match, one question.
Every pass is a choice, every pressing action is a refusal. When you mark each choice and each refusal by hand, you learn something no spreadsheet teaches: you know exactly what you do not know. That is why I keep doing this, even though the pace is so slow that a single article should carry only one argument.
A tactical diagram is not an answer; it is only a way of asking questions about space. In V.League those questions usually have to be asked with the eye, because there is no positional data to check them against.
Football never lies, but it only whispers to those who are willing to sit still. What is worth saying is that sitting still is expensive in Vietnam: weeks for a conclusion that another match can refute, with no dataset available to vouch for either side.
I am not the only person doing this. Small groups in Hanoi and Ho Chi Minh City still hand-code matches, share spreadsheets in private groups, and argue with each other using screenshots. But most of that work never gets published, because it is not yet pretty enough to become an article, and because the people doing it are not seeking attention. An amateur data archive like that could be extremely valuable, if somebody were willing to gather it up.
At this point, the data void stops being academic. It becomes a form of information asymmetry with monetary value.
Based on my own experience watching matches across several V.League seasons, I have never seen a club publish its positional data. When a V.League club recruits a foreign player, the dossier is mostly video clips sent by an agent. Those clips select beautiful moments: a long-range shot, a dribble, a goal in a match where the opponent was poor. They do not show how that player moves when his team loses the ball, or how he reacts when he is substituted in the 60th minute.
In bigger leagues, clubs check with data. In Vietnam, they check with a trial and with the coach's intuition. That intuition is often very good, but it cannot be transferred, cannot be stored, and cannot be contested transparently.
I once spoke with a young coach at a second-tier club. He told me his team wears GPS devices in training, and the data sits on the coaching staff's computers. It never leaves that room. Nobody consolidates it, nobody compares it across seasons, and when the coaching staff changes, the data leaves with them.
The point I want to underline: the biggest problem in Vietnamese football is not that data is not collected, but that collected data is left forgotten in a drawer. A club can own hundreds of sessions with full metrics while nobody has time to turn them into understanding. The gap is not at the input. It is at the output.
This also explains why the value of a player like Nguyễn Quang Hải, or of any midfielder in V.League, is usually discussed through feeling rather than through any set of metrics. Nobody has enough grounds to refute an opinion, so the loudest opinion wins.
The most common proposal I hear is to bring xG and PPDA into V.League. I understand the impatience behind it, and I disagree with applying it directly.
Those two metrics were calibrated in a football world where every shot has coordinates, every pass is labelled, and where data quality is stable enough to compare across seasons. Dropping them into a league with a few camera angles does not add understanding. It adds a false sense of certainty, and that is more dangerous than admitting we do not know.
The second blind spot is subtler, and it belongs to writers like me. In Vietnam I learned that a team can play with its heart before it plays with a diagram. That is true. But it can also become an excuse for nobody to measure anything, for every analysis to end in an exclamation rather than a testable conclusion. Empathy for the underdog is not a licence to be lax about the quality of information.
A weaker team does not need us to lower the standard in order to write about them. They need us to write more precisely, because they are the least able to speak for themselves.
Over twenty years, Vietnamese football has changed many things: pitches, wages, recruitment. The way it produces knowledge about itself has barely moved.
What I want to try next season is very concrete. I will pick one club, one observation axis, and one season. I will hand-count the height of the defensive line across eight time windows per match, record it in a public table, and invite anyone to dispute it.
If that table still exists a year from now, it will no longer be mine. It will be the first thing in Vietnamese football that can be argued about with numbers instead of memory.
And if it fails, I will know exactly where I was wrong. For a writer, that is already a good result.
