Himass and TanVuu: What the PUBG Scoreboard Cannot Measure

Opening

The circle closed at a distance of less than forty metres. On my second monitor, the compiled data table showed a line that looked entirely reasonable: a Vietnamese player topped the lobby in damage dealt, ranked second in kills, and sat in the leading group for average survival time. His team left the tournament in eleventh place.

I stayed two more hours, opened the footnote column — the column almost nobody reads — and found a very different answer from the one the scoreboard told. His damage was produced mostly at ranges beyond two hundred metres, in the mid-game, in situations where both sides already had cover and both could heal. In other words: he shot a great deal, and converted almost none of it into points.

I tell this story because it does not belong to one person. It belongs to Himass (Lã Phương Tiến Đạt), to TanVuu, and to an entire Vietnamese PUBG: BATTLEGROUNDS PC scene being measured by instruments that were never designed for this sport.

Before you trust a number, ask where it came from. The PUBG scoreboard was born from an event-counting system, not a value-pricing system. That is the starting point of nearly every error in the arguments I have read over the past several years.

Context: a sport without a scoreline that means anything

PUBG: BATTLEGROUNDS PC is operated by KRAFTON, and KRAFTON also runs the professional circuit. A standard match has sixteen teams of four — sixty-four players on one map. There is no first half. There is no ball. There is no fixed period. There is only a shrinking blue zone and one repeated question: who is still standing when the last circle closes.

Scoring at major events such as the PUBG Global Championship (PGC) and the PUBG Global Series (PGS) combines a tiered placement table with one point per kill. The higher the placement, the greater the reward; most teams finishing ninth or below receive no placement points at all. This is a deliberate design: KRAFTON wants to reward survival, not merely aim.

In the Asia-Pacific region, the path Vietnamese teams take to the international stage usually runs through domestic and regional qualifiers before a slot at PGS or PGC. It is a long road, and that same road produces a data paradox worth naming.

Vietnamese teams play a great many qualifiers, yet they face genuine international opposition only rarely. A PGC group stage typically gives each team roughly eighteen to twenty-four matches. For a sport in which every match contains sixty-four variables and hundreds of micro-decisions, eighteen matches is an alarmingly small sample.

I say this not to excuse any defeat. I say it because I once made exactly this mistake, and I remember precisely how long it took me to correct it.

The model was not wrong; the world changed while I was not looking. In 2026 I built a model on the assumption that the team controlling more territory would win more often. That assumption holds in football, where possession and pitch position correlate tightly with results. It collapsed completely in PUBG, where holding good ground in circle five can become a fatal trap in circle seven simply because the zone decided to move elsewhere. I had to rewrite the entire evaluation framework.

Damage is the most devalued currency in PUBG

Start with the most quoted and most misunderstood metric.

Damage in PUBG: BATTLEGROUNDS is recorded as the actual health removed from an opponent. The system counts accurately; there is nothing technically to dispute. The problem lies elsewhere: the system cannot distinguish damage that mattered from damage that did not.

One headshot at one hundred metres drops an opponent instantly. A burst at three hundred metres into a player crouched behind a rock removes a fraction of health and costs them one bandage. Both are added to the same column. Their value is not remotely the same.

I compiled data from recent international events and sorted damage by range and by match phase. The result forced me to rewrite most of my older reports: the bulk of damage in a professional PUBG match is generated beyond one hundred and fifty metres, and the bulk of it changes nothing about the state of the match. It is pressure damage — damage that forces opponents to burn utility, or simply holds ground.

Damage converts into value only when it produces one of three things: a knock, a forced relocation of an opponent out of good ground, or a safe window for your own team to rotate. Without those three, damage is decoration.

This is why I am cautious about judging any player on the damage column alone — and why I always open the footnotes before forming a view.

The knock is the real accounting unit

If I had to choose a single metric to read a PUBG match, I would choose knocks in relation to the placement points the team banked.

The reason is concrete. A knock in PUBG forces the opposing team into a set of expensive simultaneous decisions: whether to revive, where to revive, whether to smoke or use natural cover, who holds the angle, who leaves position. Even if the revive succeeds, time and utility have been spent. In a match where the rotation window lasts a few dozen seconds, that expenditure can decide a whole circle.

So when I assess Himass or TanVuu, I look at conversion rate: of the opportunities a player had to knock, how many did he actually convert, and how often did his team gain positional advantage as a result.

That is a far harder metric than raw kill count. Raw kills reward players who play more matches. Conversion rate rewards players who act at the right moment.

I have re-checked my archives many times. A player can lead a tournament in kills and still post a meaningfully lower conversion rate than someone ranked below him, simply because most of his kills came in matches where his team was already eliminated or already safe with no placement points left to win.

Small data is what big data always exposes. Eighteen matches are not enough to conclude anything about a person. Eighteen matches are only enough to ask a question.

The safe zone does not lie, but it does not tell the whole story

There is a metric I consider more honest than damage: the quality of survival inside the zone. Not raw survival time — that metric rewards hiding — but the team's position relative to the circle at each time marker.

My method is quite manual. I split each match into phase markers, record the team's relative position to the circle centre, its approach speed, and the moment it begins to move. Then I compare against the final result.

One finding recurs across Vietnamese teams: they read the zone correctly, but late. Not technically late — they still get in — but late in information terms. They enter once the situation is already settled, once other teams have claimed the good ground and memorised each other's movement lines.

In PUBG, information is not distributed equally. It is a contested resource, like high ground. The team that arrives first knows more. And knowing more in circle six means being safer in circle eight.

PUBG analytics has yet to build a standard index for this. Public data platforms give us damage, kills, survival time, distance travelled. They do not tell us which team owned information, at what moment, and at what price. That gap is where a team's real value lives.

Utility: the footprints of invisible players

One of the best ways to read players who never appear on a scoreboard is to read utility consumption.

Smokes, grenades, healing items, reconnaissance gear — none of these produce a kill. None ever appear in an individual leaderboard. Yet they are what separates a team with structure from a team playing on instinct.

I have spent a good deal of time counting smokes used in rotation situations by Vietnamese teams at international events, against the top-tier teams. The gap is not in how many smokes they carry — they carry enough — but in when they use them. Smoke used too late only conceals a situation already lost.

This is the kind of data that makes me speak slowly. I do not have enough of a sample to conclude firmly. But the trend repeats often enough that I place it in the footnotes of every report, with a warning that the sample is small and the margin of error wide.

The in-game leader: a line item absent from the balance sheet

This is the hardest part, and the part I most want Vietnamese readers to read carefully.

In PUBG, the in-game leader role has no metric. There is no column for the person who decided which side of the ridge to take, which team to fight first, which circle to save smoke for. A leader's best decision usually produces a match with nothing to remember: the team gets in, holds ground, banks placement points, and nobody recalls who chose the spot.

Conversely, a leader's worst decision tends to create moments that are remembered for years, because it produces spectacular fights.

The result is a system that records failure but not success. That is a structural defect, and it renders most debates about Vietnamese PUBG in-game leaders meaningless by default, because we are arguing without data.

When assessing TanVuu, I am forced into manual methods: reviewing entire matches from the team's perspective, timing each decision, cross-referencing it with the information available at that moment, and asking whether a better option existed. It is time-consuming, highly subjective work, and I always state its limits publicly.

The contrarian angle: we are blaming the wrong thing

The most common explanation I hear in discussions of Vietnamese PUBG internationally is mentality. Vietnamese teams, the argument goes, have the skill but lack the nerve in decisive moments. Big-stage pressure makes them shaky.

I do not deny that mentality exists. But the data I have gathered, with all its limits, points elsewhere.

If mentality were the problem, we would expect errors to cluster late in matches — where pressure peaks. In fact, the errors I reviewed are distributed fairly evenly, and cluster most heavily in the mid-game, roughly circles four to six. That is not the most emotionally pressured phase. It is the phase that demands the most information decisions.

In other words: Vietnamese teams do not collapse from nerves. They slow down from a lack of information, and that slowdown, accumulated across circles, creates the pressure — not the reverse.

Read this way, the correct intervention is not a sports psychologist. It is investment in the information economy: reconnaissance tools, in-match data processes, and the discipline to rotate early.

The Liverpool shock of that year did not make me afraid of data; it made me afraid of confidence. And here, what frightens me most is the confidence of people who have concluded things about Vietnamese players without ever opening the footnote column.

I read the footnote column when everyone else reads only the scoreline. In this case, the footnotes tell me Himass and TanVuu are being judged by a measurement system never designed for their actual roles. Himass is measured by kill count while his greatest value lies in holding position and creating space. TanVuu is measured by what he did not show, while his greatest value lies in what he decided not to do.

This is my limit, and I will state it plainly: I do not have enough of a sample to assert this decisively. I have enough to say that the way we argue is methodologically wrong. And in data analysis, being wrong about method is a more serious error than any wrong conclusion.

What comes next

If I could recommend one thing to Vietnam's PUBG analytics community, it would be to build an index for the information economy. Not a perfect index — no index is perfect. Merely one good enough that we begin arguing with data instead of feeling.

Such an index needs to capture at least four things: the timing of a team's entry into the safe zone relative to the circle centre at each marker, the share of utility spent on successful rotations, the number of times a team holds good ground across at least two consecutive circles, and the number of times a team forces an opponent to abandon position without a fight.

Without this index, we will keep having seasons in which Vietnam's best players are undervalued by a scoreboard that cannot count what matters most.

A season is a scripture, each match a verse — do not rush to recite half of it. Before you fight, read last season again — and read the footnotes carefully.

Takeaway

I will keep tracking Himass and TanVuu with the same process: gather first, conclude later, and state the limits at the end of every report. If next season gives us more sample — and I hope it does — I will re-test everything written here, including the parts I believe most firmly.

The question is not who is better. The question is whether we have the courage to measure again from zero.