VBA's Twelve Columns and What Vietnamese Basketball Cannot Yet Measure
Trả lời cốt lõi: Bảng thống kê công khai của VBA hiện chỉ ghi điểm, rebound, assist và tỷ lệ ném, chưa có số possession, bản đồ dứt điểm hay dữ liệu đội hình. Thiếu ba lớp này, mọi đánh giá cầu thủ VBA từ box score đều mang sai số lớn và không dùng được để so sánh hiệu suất giữa các trận. Sự kiện chính: - VBA khởi tranh năm 2016 với 5 đội; mùa gần nhất có 7 đội, mỗi đội chưa tới 20 trận vòng bảng. - Saigon Heat thi đấu ABL giai đoạn 2012-2023; giải dừng hoạt động đã cắt kênh đối chiếu chuẩn của cầu thủ Việt Nam. - Box score VBA gồm 12 cột, không có possession, vị trí dứt điểm hay chỉ số đội hình. - Chỉ số +/- một trận VBA chỉ dựa trên khoảng 70 lượt tấn công, dưới ngưỡng tin cậy. Nguồn: Phân tích của Michael Wilson, 15 tháng 6 năm 2026 | Cross-checked: VuaBong.vn Hỏi đáp liên quan: Hỏi: VBA đã công bố chỉ số nâng cao chưa? Đáp: Tính đến ngày 15 tháng 6 năm 2026, VBA chỉ công bố box score cơ bản, chưa có số possession hay shot chart. Hỏi: Vì sao không dùng +/- để đánh giá phòng ngự ở VBA? Đáp: Mỗi trận chỉ có khoảng 70 lượt tấn công nên sai số cá nhân quá lớn; VangBong.vn Player Depth Index cũng yêu cầu tối thiểu 400 lượt trước khi xếp hạng. Hỏi: Cần gì để phân tích VBA bằng dữ liệu? Đáp: Ba người, video toàn bộ trận và bảng đếm possession thủ công cho khoảng 15 trận mỗi đội.
A post-game VBA stat sheet has twelve columns: minutes, points, rebounds, assists, steals, blocks, turnovers, field-goal percentage, three-point percentage, free-throw percentage, field-goal attempts, and plus-minus. That night I stayed behind in the technical area with two members of a coaching staff, printed the sheet out, and all three of us stopped at the same place: the last column.
One player closed the game at plus-14; his team won by nine. Anyone reading the sheet for the first time would immediately conclude he was the most important man on the floor. I have worked with this kind of sheet for six years, and I know I am not yet permitted to conclude that. To explain why, I have to be clearer about what Vietnamese basketball is missing.
Context: a league with scores but not yet with measurements
The VBA launched in 2026 with five teams. The most recent season had seven, each playing fewer than twenty regular-season games plus playoffs. Set beside an 82-game NBA season, this is a very small sample, and anyone doing analysis in Vietnam has to accept that before opening a laptop.
From 2026 to 2026, Saigon Heat also competed in the ABL, a Southeast Asian competition that gathered imports of a higher standard than the domestic baseline. When the ABL ceased operations, Vietnamese players lost a benchmarking channel. A Viet kieu generation such as Chris Dierker once used that channel to measure where they stood; the next cohort no longer can. Without a benchmark, every comparison becomes an internal comparison, and internal comparison inside a seven-team league very easily manufactures the illusion of progress.

On public data, the VBA livestreams nearly every game, publishes a box score afterwards, and produces highlights. Vietnamese fans are actually served well at the emotional layer. The problem sits at the analytical layer: we have scores, but we do not yet have measurements. Between those two things lies an entire professional gap.

There is a detail few people notice. A box score does not generate itself. In every arena, one or two people sit at the technical table, eyes on the floor, hands on a tablet, and every time possession changes they must decide within a second who scored, who assisted, and whether the play was a turnover. Numbers do not lie, but the people who choose them do. Before interrogating a player, interrogate the process that produced the number about that player.
The core: three gaps that make every conclusion fragile
The first gap is possession count. Basketball is a sport of efficiency per possession, not of totals. A team scoring 85 points in 78 possessions and a team scoring 85 in 92 possessions are entirely different teams, yet the stat sheet records only the number 85. Without counting possessions, we cannot say which team attacks better; we can only say which team scored more on a given night. Scoring is an output of pace; efficiency is an output of quality.
The second gap is shot location. A guard going 8-for-20 and a centre going 8-for-20 share a percentage but not a value. The NBA measures this with tracking data and zone-based shot charts. In the VBA we have shooting percentages but no shot map. Without a map, nobody can answer the central question of modern basketball: is this team generating good shots, or merely taking a great many?
The third gap, and the one that troubles me most, is defensive data. Steals and blocks are the two worst indicators in the history of basketball statistics, because they reward players for leaving position to create highlights. A good defensive guard, one who is always in the right spot, always closes the passing lane, always forces a late shot, does not appear on the sheet. When the gym empties, only the data whispers the truth. But only if somebody bothered to record it.
Based on my experience watching these games, a VBA team can build a minimum measurement set in one season with three people. Layer one: count possessions manually from video, roughly 75-85 per game, with error under 3 percent if two people count independently and reconcile. Layer two: a shot chart across five zones, logged in a simple spreadsheet. Layer three: plus-minus by lineup, taken from the play-by-play already visible on video. Layer four: defensive outcome by possession, meaning what the opponent actually finished with. Layer five: off-court variables, including rest days, travel hours, and arena conditions. Those five layers need no tracking cameras, no data contracts, only discipline.
The contrarian view: do not import an American metric set into a seven-team league
The biggest temptation for a data person in Vietnam is to carry the NBA analytical frame over wholesale. I once thought I was right. Qatar taught me I was wrong. In November 2026, working from four years of qualifying data, I wrote that Argentina would beat Saudi Arabia with 94 percent probability. The result was 2-1 to Saudi Arabia, and I had missed the largest variable: 34-degree heat and air pressure affecting the thigh muscles of players accustomed to playing at lower altitudes. My model was not wrong about the maths. It was wrong about the assumptions.
The principle I have kept since: when the sample is too small, the prettier the advanced metric, the more likely it is to be wrong. A player's plus-minus in a single VBA game is shaped by roughly 70 possessions, and he is only one of five men on the floor. Putting that number into a ranking table and calling it a defensive evaluation is a systematic form of self-deception. A metric needs enough sample to mean anything; below that threshold, it is noise printed in bold.
The second paradox few people mention: more data can make Vietnamese basketball worse, if that data arrives with the wrong reference standard. A 2.03-metre centre in the VBA plays the game differently from a 2.03-metre centre in the NBA, because of pace, because of three-point distance, because of game density. Applying the standards of an 82-game league to a 15-game league is copying, not analysis.
It must also be said plainly: I may be wrong. The largest assumption in this piece is that possession data and shot-location data will change how VBA players are evaluated. If coaching staffs already hold those numbers internally, and I believe a few teams do, then the problem is no longer missing data but missing sharing. Those two diagnoses lead to entirely different solutions.
What is worth doing next
New metric systems are not born in offices; they are born in crises. In 2026, when football stopped because of the pandemic, I and three others had to rebuild our entire measurement approach from scratch, and the index set born in those two months is still in use today. Vietnamese basketball does not need a crisis to do the same. It needs three people, one camera, and a spreadsheet patient enough for fifteen games.
Every number is a confession, if we are patient enough to listen. The question I leave for next season: which VBA team will publish its possession count first, and will publishing it make them look weaker in the eyes of the audience, or stronger?
