Nine Blank Sections: Notes from Binh Duong on Vietnamese Esports Data

Tuesday, August 13, 2026, 3:40 p.m., Binh Duong.

I opened a file named post-match-analysis.json. It ran to twelve thousand four hundred characters. It had a title. It had nine analytical sections. It had a metrics comparison table. It had a six-row risk matrix. It had a "Professional Conclusion" at the end, correctly indented, correctly bolded, correctly formatted for publication.

And every data cell inside it read: "Insufficient information, cannot assess."

Not one cell. Nine sections. All of them.

I sat still for a long while. The window of my office looks onto a road in Thu Dau Mot, and trucks rattling past shook the wooden desk. On the screen, a formally perfect analytical document was telling me it knew nothing.

Reading files like this is my job. Eighteen years of it. I have read thousands of reports, metric tables, heat maps, probability models, transfer dossiers. For the first time in a long while, I realised I was looking at the most dangerous object in my profession: a beautiful template.

What chilled me was not the empty file itself. It was that this file would pass review. It would be published. It would find readers, sharers, people citing it. Because it looked complete. And in Vietnamese esports today, looking complete is the only standard many people still check against.

Data never lies; we simply haven't asked the right question. But when there is no data inside at all, the right question saves no one. Then you have to ask a different one: what is this template hiding?

Context: a decade of learning to speak in numbers

To understand why an empty file is dangerous, you have to understand how Vietnamese esports got here.

In 2026, I began my career as a player and then a tournament organiser, before moving into media. Back then, an esports match report in Saigon or Hanoi was written by feel. Writers described teamfights with adjectives: "brilliant", "overwhelming", "unbelievable". Nobody asked what the winning team's gold-lead margin was. Nobody asked how many resources the losing team lost in the first ten minutes.

Then the data wave arrived. From around 2026, English-language automated stat sites began covering Vietnamese competitions. Viewers learned "KDA", "CS", "lane win rate", "damage per minute". By 2026, as VCS entered a period of heavy professionalisation and domestic Arena of Valor leagues settled into regular group stages, data became part of fan identity. Fans no longer argued only about which team was stronger; they argued with charts.

I was part of that wave, and I know its underside.

In 2026, aged twenty-five, I was a reporter for a new football outlet in Binh Duong. I hand-charted data from 182 V-League matches off video, rewinding and replaying every phase, counting every pass under pressure. I found that Long An had the league's lowest PPDA, 7.8. They let opponents hold the ball comfortably but conceded only 0.7 goals per match, thanks to extremely fast counter-attacks. I wrote a piece titled "Low pressing is not cowardice".

A veteran coach called me a soulless statistician. The young assistant coach of Binh Duong FC invited me to build a pressing map for the team. Two opposite reactions to the same article, and both were right in their own way.

V-League is a mess, but every mess has its own rules. What I learned then was not "numbers always beat intuition". It was this: numbers only have power when someone is accountable for how they were produced.

Vietnamese esports datafied far faster than football did, and skipped the accountability layer. We had metric tables within a few years, but we never built the verification tier. We have formats, not discipline.

That empty file is the end product of that gap.

Anatomy of nine blank sections

The report in my hands was divided into nine parts. On the surface it was the standard analytical skeleton of any professional data desk: patch and meta, tournament format, teams and players, regional landscape, club finance, rules and governance, risk profile, public narrative, and industry transmission.

Every part was empty. But every part also pointed precisely at what Vietnamese esports is missing, and where. I walked through those nine parts the way you walk through nine empty rooms of a house whose shell is finished.

Part one: version and meta

The report read: game title unidentified, patch unidentified, magnitude of change unidentified.

In Vietnamese esports, this is the most common and most expensive blind spot. A balance update in League of Legends can reverse mid-lane priorities within a week. A patch in Arena of Valor can turn a champion nobody picks into a mandatory professional selection. In Free Fire or PUBG Mobile, a change in weapon damage or map layout can collapse an entire tactical system a team spent a season building.

The problem: most Vietnamese-language esports analysis does not state which version it is talking about. The writer watches a domestic tournament match, draws a conclusion, and applies that conclusion to every other match — including international matches running on a different tournament build.

I once sat with the analytics group of a youth team in Ho Chi Minh City. They had six opponent-tracking sheets, each one beautiful enough to frame. When I asked which patch the data came from, the whole group went quiet. Nobody had written it down. They tracked by eye, stored in memory, and presented in spreadsheets.

That is why I always place the version question before the tactics question. The order is not ceremony. It is the condition for anything downstream to mean anything.

Part two: tournament format

Unidentified tournament, unidentified tier, unidentified format.

This sounds obvious, but it is where Vietnamese esports analysis fails systematically. Format determines upset probability. A best-of-three series has a far lower chance of the weaker team winning than a single game. A Swiss-system group stage produces a different opponent distribution from a fixed-group stage. A knockout bracket with a play-in path creates different incentives from a pure knockout bracket.

In domestic Arena of Valor events, the difference between group stage and playoffs is routinely ignored. In VCS, the structure changes year to year, and each change makes historical data harder to compare.

When you aggregate win rates across seasons with different formats, you do not have a number. You have a mixture.

Part three: teams and players

The report read: analysis subject unidentified, roster phase unidentified.

This is the area where Vietnamese esports is strongest in inspiration and weakest in method. We have players whose names are everywhere. We have countless community-built individual rankings. But we have almost no roster data by phase.

The issue is this: a player does not operate independently. The same person, in the same position, playing inside two different tactical systems, produces two different metric sets. If you strip the individual out of the system and compare, you are comparing two things that are not the same kind of object.

I have spent years watching Vietnamese teams play, and the thing I am most certain of is this: in esports, a person's role only becomes visible when you know what that person was asked to do. A jungler under pressure to free the top lane will post entirely different numbers from a jungler under pressure to control major objectives.

A metric table does not tell you who is good. It tells you who has been assigned what.

Part four: regional landscape

Unidentified region, unidentified regional tier.

Regional comparison is one of the most beloved topics in Vietnam and one of the sloppiest. The question "where does Vietnam stand relative to Korea, China, Taiwan" has no single answer. The answer depends on the title, the tier of competition, the point in the season, and which criteria you are measuring.

In League of Legends, the gap between the Vietnamese region and major regions shows up clearly in roster depth, not only in peak-match results. Our best team can trade blows with a mid-table team from a major region for one game. Playing five games in seven days with the same structure is a different matter.

In mobile titles the picture inverts. Vietnam sits among the world leaders in several disciplines, which makes blanket "weak region" analysis meaningless without naming the title.

I once wrote a regional strength comparison for a foreign platform, and the editor asked me: "Which title are you talking about?" It was the best question I have ever received from an editor.

Part five: club finance

Unidentified event type, unidentified financial health.

This is the darkest part of the picture. Vietnamese esports has a paradox: fans know team names very well, know achievements very well, and know almost nothing about revenue structure.

A professional Vietnamese esports club can live on several sources: brand sponsorship, prize money, publisher revenue sharing, streaming contracts, jersey and merchandise sales, and sometimes investment from a parent company. The weightings determine sustainability. Yet almost no figures are published, beyond a few press releases about new sponsors.

When financial data is absent, the transfer market becomes a speculation arena. Communities debate salaries, transfer fees, and who is richer than whom based on feeling. Some numbers circulate for years without ever being verified.

This is the class of risk I cannot screen with public data, and I name it correctly: an unassessed blind spot. Unpaid wages and dissolution are high-frequency, high-severity risks in regional esports, but in the Vietnamese market they tend to surface only when it is already too late.

Part six: rules and governance

Unidentified applicable rule system, unidentified compliance risk level.

Vietnamese esports sits under several overlapping layers of rules: publisher rules, tournament organiser regulations, regional publisher policy, and the domestic legal framework around electronic games and esports.

This layering creates grey zones. Conduct prohibited at one layer may be undefined at another. A penalty at an international event may have no domestic precedent.

Over the years, competitive-integrity issues in Southeast Asia have shown a worrying pattern: late sanctions, incomplete disclosure, and unsystematic remedies. In Vietnam, some cases were handled and others were discussed and then buried.

The absence of an allegation in a report does not mean the absence of a violation. It only means nobody has yet brought evidence into the light.

Part seven: risk profile

Cannot be rated overall.

That line is the one that stopped me longest. In most analyses I read about Vietnamese esports, the risk section is treated as a footnote. Writers spend two thousand words on tactics and two lines on risk.

But for a Vietnamese esports team, risk does not live in tactics. Risk lives in undisclosed variables. A player injured while the club chooses to say "taking a break for personal reasons". A coaching change made quietly. A contract ending without announcement.

I have held this position for years: medical confidentiality blinds fans and media, and clubs disclose injury information only when it suits their image. That is not wrong from an HR standpoint. It simply means every analytical model built on public data has a fixed blind spot in the middle.

Part eight: public narrative

Unidentified current narrative, unidentified heat cycle.

Public narrative in Vietnamese esports runs on very short cycles. A good match generates a wave lasting a few days. A brilliant play generates hundreds of clips within twelve hours. A young player shining in one match is called a phenomenon before the season ends.

The problem with short cycles is that they do not leave time for verification. When a story is built too fast, nobody gets to ask the most basic question: how large is this observation sample?

I learned this in 2026, when competitions froze because of the pandemic. I spent the time analysing 252 matches in a European national league played from May to June that year, with no spectators in the stadium. Home win rate fell from 43 percent to 29 percent, and away teams covered 6 percent more distance.

I posted the comparison chart. A European analytics platform shared it and called it scientific evidence for home advantage. Then they invited me to collaborate.

What I carried away from that experience was not pride. It was the memory of abandoning the topic the moment I had proven my point, instead of digging deeper. Applause in an empty stadium records a truth nobody wants to hear.

Part nine: industry transmission

Unidentified trigger event, unidentified transmission chain.

Every major shift in esports starts upstream: with the publisher. A scheduling decision, a qualifier format change, a new broadcast rights policy — all of it transmits down through clubs, streaming platforms, sponsors, and finally fans.

In Vietnam, that transmission chain is far shorter than in major markets, and that is an underexploited advantage. When the chain is short, the lag between an upstream decision and a downstream effect is short too, and signals become easier to read.

But exploiting that advantage requires something we do not yet have: the habit of taking notes.

Contrarian view: blank space is not neutral

There is a common belief among young analysts: if there is no data, the best thing is to say nothing. I understand the logic. It sounds humble and scientific.

But it is wrong on one important point.

Blank space in data is not neutrality. It is a container. And in a media environment, every container gets filled. If the writer, out of discipline, does not fill it, someone else will. If nobody fills it with data, people fill it with guesswork — and guesswork in Vietnamese esports spreads by word of mouth far faster than data.

That is why a nine-part empty report is more dangerous than a wrong report. A wrong report can be caught. An empty report that is formally complete gets caught by nobody, because there is nothing to catch. It just waits to be filled.

In 2026, I staked my career on a probability model named Croatia. I was sent as an analytical reporter to the World Cup in Russia after a run of data pieces on Vietnamese football. After the quarter-finals, I predicted Croatia would beat England, based on Croatia's average expected goals of 2.3 against England's 1.1, even though Croatia had gone through multiple periods of extra time.

Colleagues laughed. One told me football is not mathematics.

Croatia won 2-1 after extra time. My piece was shared more than ten thousand times, and the newsroom gave me a dedicated column.

But the real lesson was not that I was right. It was that I was right for a different reason than I thought. Croatia was not a miracle; it was well-managed variance. They did not win through luck. They won because they consistently created more quality chances than their opponents and accepted that the conversion of probability into goals has a lag. It was a model, not an omen.

The difference between those two interpretations is the entire content of my profession.

In esports, that difference is being erased daily. People take one metric from one match, turn it into a definition of a player, then use that definition to explain every subsequent match. That process has all the formal features of analysis but lacks any self-correction mechanism.

At EURO 2026, I published research on 342 penalties across five top European leagues, showing that Italy's goalkeeper dived to his right in 72 percent of cases when facing right-footed takers. I predicted Italy would beat Spain on penalties. The piece was called fortune-telling.

The semi-final happened. Italy won 4-2 on penalties, and that goalkeeper saved two kicks to the right. The piece reached 1.2 million views.

What I told nobody was that I got lucky. My sample had a time lag, and goalkeeper behaviour may have shifted after I collected the data. If I rewrote that piece today, I would add a paragraph on margin of error. But back then I was chasing praise, and I skipped the most important part.

That is the trap any data analyst in Vietnam will meet while the market is still young: rewards come from being right, not from being honest about how certain you are.

What the empty report actually reveals

There is one technical detail in the file I opened on August 13 that matters more than everything else.

The "entities involved" field in the report was not marked empty. It read: "identify from the information points above".

That is a self-referential instruction. It defines one data field by pointing to another field that may also be empty. In design terms, it guarantees that when the input is empty, this field will be empty in a way that cannot be detected.

Vietnamese esports is running on a great many self-referential instructions like that.

One ranking built from other rankings. One roundup written from other roundups. One statistic cited with the source given as "according to the community". Nobody is lying. But nobody is accountable for the starting point.

This is the most dangerous class of error, because it does not produce loud failure. It produces silent failure. My report had all nine sections, all the tables, all the formatting, and if I had not read it carefully I could have published it under the headline "Deep Analysis".

In esports, silent failure has a concrete shape. A team misreads an opponent because the data recorded the wrong patch. A coach prepares tactics based on a metric table aggregated across three seasons with different formats. A young player is undervalued because his numbers do not reflect his real role in the system.

None of them fail from lack of data. They fail because they trusted data with no provenance.

We think we understand the game, until the data table opens our eyes. And sometimes what the data table opens is emptiness.

So what should be done

I do not have a complete solution for Vietnamese esports. I have a few habits that changed how I work, and I think they can scale.

First, every number must come with three things: source, timestamp, and scope of applicability. If one of the three is missing, it does not go into the piece. This is the most time-consuming discipline and the only one that actually works.

Second, an analysis must be allowed to end with "insufficient data". In current publishing culture, that conclusion reads as failure. But in analytical work it is a valid result and often the correct one. A system that cannot stop when the input is empty is a system that will produce fabricated content.

Third, when a topic stops being hot, keep taking notes. I am the worst offender here. I start three or four research projects at once and abandon them once the initial point is proven. The result is that I have many conclusions and very few complete models. Over eighteen years, that is my biggest weakness.

Fourth, publish the margin of error. A correct prediction is worth less than a correct prediction where readers know how many cases it could be wrong in.

There is one image I kept from 2026 and have carried ever since. A stadium with no spectators. Players still ran, still contested the ball, still scored. Their shouts rose into empty space and nobody answered. But the data was still recorded in full. Every pass, every metre covered, every duel.

That is what I believe about Vietnamese esports: data will exist whether or not anyone looks. Our job is to stop it being filled with something else before it can be read.

A starting point for the next cycle

The file post-match-analysis.json now sits in a folder I named "do not publish". I keep it, not because it has analytical value, but because it is a specimen. It shows exactly what my system will produce when the input is empty and I do not check.

In the coming months, as domestic competitions enter their closing stretch, hundreds of analyses will be published. Most will contain numbers. Some will have sources. Very few will state clearly that they know nothing.

The last group is the trustworthy one.

I will track one specific signal next season: the share of Vietnamese-language esports analyses that state their patch version and data source. If that share rises, the industry is maturing. If it stays flat or falls, we are accumulating a data debt that will be unpayable in a few years.

And if you run an esports analytics desk in Vietnam, the question I want to leave behind is not "do we have enough data".

It is this: when the data is empty, does your system stop — or does it fill itself in?