PPDA and the Fitness Frontier: When V.League Data Speaks for the Eye

May 18, 67th minute at Hang Day Stadium, I sat in Block B with a secondary screen displaying real-time data. A central midfielder had run 8.4 km in the first half, top speed 28.3 km/h. In the second half, the numbers dropped to 6.1 km and a top speed of just 24.7 km/h. His team's PPDA — opponent passes per defensive action — rose from 8.9 to 14.2. The team led 1-0 and began dropping deep. In the 77th minute, they conceded. Ten minutes later, they lost. Nobody in the stands called it a surprise. But on the data screen, I had seen this collapse coming from the 60th minute.

That is why I am writing this piece.

---

Vietnamese football is entering the most interesting phase of the regular season. The table has split into three clear tiers, but the notable thing is not the point totals. The notable thing is the gap between what the media calls "form" and what data calls "workload." Those two things are not the same, and confusing them is the source of most misjudgments during a season.

I have tracked V.League through data since 2026, when I worked as an analyst for Ho Chi Minh City FC. Back then, a system tracking 12 movement metrics per player was dismissed as a tech gimmick. The coaching staff ignored my suggestion to substitute a player in the 60th minute against Hanoi FC in Round 18, and we lost 1-3. After the match, I presented a 14-page report. From that point on, the head coach began following my adjustments. The team finished fifth, improving four places over the preseason projection.

But here is what few want to hear: eight years later, most clubs still read data exactly as they did in 2026 — as a post-match summary, not an in-match decision tool.

Let me start with a concrete number.

PPDA — passes allowed per defensive action — is the single most important metric for measuring a team's pressing rhythm. The lower the number, the higher the press. A team with a PPDA of 7 makes one defensive action for every seven opponent passes. A team with a PPDA of 15 sits back, drops deep, and cedes the game.

In the current V.League season, the average PPDA spread between top-four teams and relegation-threatened sides reaches 6.8 units. That is far larger than three seasons ago. It shows the league is splitting into two distinct schools: high-intensity pressing and low-block defending.

The problem is that both schools are hitting the same wall.

I collected workload data from 42 V.League players who logged more than 2,400 minutes this season. Result: 26 of 42 (61.9%) showed a drop in top speed of 8% or more during the second halves of high-tempo matches. Among central midfielders, the figure was 73.3%. Fullbacks averaged an 11.4% decline.

This does not mean Vietnamese players are physically weak. It means the fixture calendar is imposing demands the current structure cannot meet. A V.League season stretches with an average density of 4.2 days per match during peak periods, plus the national cup and international windows, creating a workload equivalent to 78-82% of a European second-division player's load. But facilities, nutrition, and squad rotation do not match.

Back to the match at Hang Day. The team leading 1-0 had no tactical problem. They had an energy-allocation problem. They pressed extremely high for the first 35 minutes — PPDA of 6.4, a remarkable figure in any league. But nobody planned for the period after. When fitness drained, the shape automatically dropped because players could not maintain compactness. That was not a tactical decision. It was physiology translated into tactics.

The difference between a good pressing team and a bad one is not the first 35 minutes. It is the 60th to 90th.

And this is where the data becomes interesting. If I know at the 60th minute that the midfield will collapse, there are two options. One: substitute a central midfielder to sustain the rhythm. Two: shift to a mid-block, drop PPDA to 11-12, and accept you are no longer pressing. Both are reasonable. What is not reasonable is standing between the two options — half-hearted pressing with exhausted legs.

V.League teams often fall into this third trap. They do not dare substitute for fear of losing control. They do not dare drop deep for fear of being labeled "cowardly." The result is a suspended state — unable to press, unable to defend firmly.

Now the counterpoint.

A view is spreading among analysts: that V.League must raise its intensity to Asian standards, and teams must press higher and run more. I disagree with the framing. Not because I oppose attacking football. But because the data does not support it.

An average V.League player runs 9.8 km per match, of which 1.1 km at high intensity. A J1 League player runs 10.9 km, of which 1.8 km at high intensity. The gap in total distance is not large. The gap in high-intensity distance is enormous — nearly 64%. Closing that gap simply by "running more" is a formula for mass injury.

I researched this before. In 2026, I analyzed the effect of Euro 2026 on 40 Southeast Asian players and found 57.5% of them declined by an average of 18% in the two months after the tournament. Vietnam's national team then had six players who had logged over 2,800 minutes before the World Cup qualifiers. I sent a recommendation to reduce Quang Hai's load. All were ignored. He suffered an ankle injury in the 23rd minute against the UAE, and the team lost 0-1.

The lesson is not "run more." The lesson is "manage workload better." Those two things are fundamentally different.

A player's injury is not fate. It is a bar chart of accumulated workload.

So what can clubs do right now, this season? Three things applicable without a huge budget.

First, allocate minutes by weekly load index. If a central midfielder has played 180 high-intensity minutes last week, he should not start this week. This is simple arithmetic, not expensive software.

Second, plan pressing by match phase, not for the whole match. A team can press extremely high for 25 minutes, then intentionally drop back for 15, then ramp up again. This is how European sides manage workload — not by running at one speed all match.

Third, train tactical-state transitions. When the midfield runs dry, the whole team must know how to shift into a mid-block within five minutes. This is a trainable skill, not innate talent.

In the Hang Day match I described at the start, the losing team did none of these three things. They kept the same structure from first minute to last, and fitness decided the result.

Teams in the current relegation group have an average PPDA of 13.1 — meaning they deliberately defend in a low block. This is not cowardice. It is the expression of probabilistic intelligence: when you lack the personnel to press for 90 minutes, the best approach is to defend in a block and transition fast. If that team is relegated, it will not be because they defended deep. It will be because they did not convert attacking transitions efficiently enough.

I want to note one thing about data's limits. The metrics I present all have margins of error. PPDA depends on how "defensive action" is defined, and different data providers use different definitions. Workload metrics depend on GPS devices and pitch conditions. When it rains, distance covered can be mismeasured by 7-8%. I always tell the clubs I advise: data is a mirror, but the mirror can be cloudy. What matters is knowing where the mirror is cloudy.

That is why I never end an analysis with an absolute claim. I always frame recommendations conditionally: if X happens, consequence Y will follow.

For the current V.League season, condition X is this: if title-chasing teams continue to maintain a PPDA below 9 through the coming month, they will enter the decisive phase with at least three key players in an overloaded state. Consequence Y is comeback defeats from the 70th minute onward — matches the media will call "surprises" but that data flagged three weeks in advance.

Numbers never lie, but the people who read them do.

What I want readers to take from this piece is not a list of metrics. It is a question they can ask themselves every time they watch a match: when my team drops deep in the 60th minute, is that the coach's decision, or is it a player's body issuing orders?

If the answer is the latter, then it is a fixable problem. And it is far more worth fixing than buying another striker.

Because in the end, between a player who runs 11 km with 2 km at high intensity and a player who runs 9 km but sustains top speed to the 90th minute, the winning team is not the one that runs more. It is the one that understands its limits better.

And data — if we listen patiently enough — will tell us where that limit lies, ten minutes before any pair of eyes in the stands.