The Fatigue Index and the Regular-Season Race: Reading V.League Through 12 Movement Metrics

Minute 60, round 18, the 2026 season. I sat in the fourth row of stand B at Thong Nhat Stadium, eyes fixed on a laptop screen receiving signals from four optical cameras mounted on the floodlight pylons. On my dashboard, Nguyen Trong Huy's name blinked yellow: 8.2 km covered after 90 minutes. The team average that day was 9.6 km. He ran 15 percent less than the second-lowest runner. I sent a message to the coaching staff's radio: "Recommend a substitution at minute 60, the left channel is open." Nobody answered. In the 71st minute, Ha Noi FC scored their second goal from exactly that channel. In the 84th, the third. Final score 1-3.

After the match I stayed in the technical room for four more hours and wrote a 14-page analysis. Page three carried a line I still remember: "We lost because one player ran out of fuel from the 55th minute, and nobody on the coaching staff had a number to see it." The next morning the head coach called me in and said one short sentence: "From now on, send me the numbers before the second half." That season, Ho Chi Minh City FC finished fifth, four places better than the pre-season projection.

The regular-season table is a slow document. It records consequences, not causes. That is why I took up data consulting at 62, after forty-six years of watching football and nine years working directly with Vietnamese clubs.

Context: the regular season leaves no room for randomness

The regular season differs from a World Cup in exactly one respect: length. A World Cup is an emotional storm lasting one month, where every mistake can be forgiven because the tempo is too fast. The regular season is a marathon lasting eight to ten months, where every small mistake accumulates and is finally paid for in points. A team can survive three rounds on inspiration. No team survives twenty-six rounds on inspiration.

In the last three matches of a team fighting relegation, their PPDA fell from 11.4 to 8.9, meaning they pressed higher up the pitch. But if you also read the movement data, you see the high-intensity distance of the midfield dropped 12 percent over the same period. A team pressing higher but running less is a team whose structure is collapsing, not a team improving. The table does not distinguish these two states. Movement metrics do.

From 2026, I built Ho Chi Minh City FC a system tracking 12 metrics for every player in every match. The three most important are:

First, high-intensity distance — metres run above 19.8 km/h. This reflects a player's capacity to join decisive actions, not endurance.

Second, the number of presses within 5 seconds of losing the ball. This measures immediate reaction, something television cameras rarely capture because it happens outside the main frame.

Third, the pass rate into the final third. This measures real penetration, not the number of safe passes.

Twelve metrics, one screen, one message into the radio at minute 45. That is the whole method. It is not glamorous. It is simply accurate.

I was born in the United States, now live in Saigon, and have followed five World Cups as a data professional. In 2026 I joined the sports department of a television station in Belgrade, learning to write from early-career observation. In 2026 I hosted "Football Night" for about six years and worked as a producer. Each of those turning points taught me the same lesson: information is never scarce; the people who read it are.

Core: a chain of evidence from three tournaments

Case one: 8.2 km and an empty left channel

Nguyen Trong Huy's 8.2 km appeared in no match report. On television, people talked about "fighting spirit", about "bad luck", about the referee. Nobody talked about 8.2 km. Every number is a confession, if we are patient enough to listen.

When I broke the 8.2 km into 15-minute blocks, the picture sharpened. In the first 15 minutes, Huy ran 1.9 km. In the last 15, he ran 1.1 km. His top speed fell from 31.4 km/h to 24.8 km/h. That decay curve reflects accumulated load over weeks, not a single match.

I checked the previous seven matches. Huy had played 630 minutes in 21 days, including two long-distance trips. His total high-intensity distance in that period was 22 percent above his season average. The coaching staff did not have this number. They had only a feeling that Huy was still fine.

This is the most common blind spot in V.League: a young player is judged by a subjective sense of freshness, while the data shows he has been in the red zone for two weeks. The 71st-minute goal originated in a system that could not measure fatigue, not in Huy's legs.

After 2026 I expanded the system across the whole squad. In 2026, the team's muscle-injury cases fell 31 percent from the previous season. That figure was never published, but it sits in the internal report I sent the board. What matters is that running that system cost less than one month's salary of a substitute.

Case two: 7.9 km at minute 52 and the goal that followed

In June 2026 I worked as a data consultant for a sports television channel covering the World Cup in Russia. During the France–Belgium semi-final I sat in the control room, feeding live numbers to the commentator.

At minute 52, with Belgium pushing, I gave him a figure: Jan Vertonghen had run 7.9 km, and his average speed was down 23 percent from the first half. I recommended he highlight the fatigue in Belgium's back line, especially the left channel. The commentator ignored the number and kept talking about Belgian fighting spirit.

Not long after, France scored the only goal of the semi-final, from a set piece finished by Samuel Umtiti's header. The channel was criticised for missing the main development, and I was partly blamed for relying too much on data.

I spent the next three weeks rewatching footage of all 64 matches to cross-check data against reality. The result was a 200-page document titled "fatigue-index forecasting". It does not claim data predicts every goal. It shows that in 71 percent of goals conceded from the 55th minute onward, the conceding team had at least one defender whose speed had dropped more than 20 percent from the first half.

World Cup 2026 taught us that emotion is the hardest noise to filter out of data. But it also taught me that data does not speak for itself. It needs the right reader, at the right moment, in the right context.

Case three: 57.5 percent and post-tournament syndrome

In 2026, at 57, I studied the effect of Euro 2026 (postponed to 2026) on Southeast Asian players' fitness. I found Vietnam's national team had six players who had played more than 2,800 minutes before entering World Cup qualifying.

I sent a recommendation to the federation, proposing a reduced load for Quang Hai against the UAE in the group stage. It included a chart comparing his accumulated load with the standard injury threshold. All of it was ignored.

In the 23rd minute against the UAE, Quang Hai suffered an ankle injury. Vietnam lost that match and with it the advantage of a deeper run. I am not saying that injury was an inevitable result of overload. I am saying its probability was significantly higher, and that probability had been recorded in a document with a date on it.

I then gathered data on 40 Southeast Asian players who took part in the Euros and the Tokyo Olympics. The result: 57.5 percent of them saw an average performance drop of 18 percent within two months of the tournament. A German researcher later used that report in an article on "post-major-tournament syndrome".

Euro 2026's injuries were not a curse; they were a delayed report. Southeast Asian football does not lack data. It lacks a process for reading data before the season begins.

Applying this to the current regular season

The current regular season carries three signals the table has not yet reflected.

First, fixture density. Teams in continental competitions have schedules 20 percent heavier than domestic-only teams. This does not create an immediate difference, but it creates one in the second phase of the season, from roughly the fourth month, when accumulated load starts to exceed the recovery threshold.

Second, the shift in pressing metrics. When a team raises its PPDA — pressing higher — while cutting high-intensity distance, that is a sign players are pressing by position rather than by effort. That kind of press works for two or three matches, then collapses.

Third, the age of the spine. A spine with an average age above 30 shows a speed-decay curve 30 percent steeper than a spine under 27 across the same season. This is not age bias; it is the geometry of recovery.

Data is a mirror; a fool sees himself in it, a wise man sees the team. When I send a report to a V.League club, I always write: "If the club keeps this workload over the next four rounds, the probability of a midfield muscle injury is 34 percent." That is how I write recommendations — as conditions, not assertions.

Based on my experience following matches, the first three rounds of the second half of the season are when movement data has its highest predictive value all year. That is when a team has accumulated enough load to expose a breaking point, but not so late that results mask the cause.

Metrics and refereeing controversies

An under-discussed part of a data analyst's job is reading late fouls. In my data, fouls from the 75th minute onward are 40 percent more frequent than in the first 15 minutes, and most come from players whose high-intensity distance has dropped more than 25 percent.

This does not excuse individual error. It places individual error in a measurable context. When a defender fouls inside the box in the 88th minute, the right question is not "did he mean it" but "who left him facing that situation when he had already run dry".

I once sent such a report to a coaching staff, recommending a substitution at minute 70. They substituted at 83, after the team had conceded a penalty. The report is still in my inbox, dated.

The transfer market and the surprise story

The transfer market is the only place where people pay for hope, not performance. Every summer I see the same pattern: a mid-table team does well through a tight tactical system, and immediately its core players are dismantled by bigger clubs.

A small club's success is usually the opening form of another talent raid. It loses two or three pillars, receives a sum of money, and enters the next season with a system whose backbone has been removed. This explains why so few V.League clubs hold a high position for three consecutive seasons.

In my data, clubs that lose two or more pillars in one transfer window are 2.3 times more likely to drop places than clubs that keep their frame intact. That is a number no sporting director wants to hear in July.

The data gap in women's football

If V.League men's clubs lack data departments, women's football has almost none. I once tried to collect movement data for a domestic women's competition and found no optical tracking system installed regularly.

That means decisions about female players' fitness are made entirely by eye. Meanwhile, the same organisations that sponsor women's football publish very detailed corporate social responsibility reports. The gap between media reports and actual data infrastructure is something I cannot ignore when writing on this subject.

A women's game that wants sustainable growth needs three things in order: pitches, a stable fixture list, and data. The first two are often mentioned. The third is not, because it does not produce pretty images.

The contrarian angle: correlation is not causation

This is the part I must write most carefully, because it argues against my own work.

Of the twelve metrics I track, at least four correlate with match results but have no causal relationship with them. Total distance correlates with possession share, but possession does not guarantee victory. A team that runs more is not certain to win. A team that runs less is not certain to lose.

In 2026, when I was blamed for over-relying on data, part of that criticism was fair. I presented Vertonghen's 7.9 km as stronger evidence than it really was. A player who runs 7.9 km can still play well if his role does not demand a large distance. Data only means something inside the context of a tactical role.

I have to test myself every week with one question: If the majority is right this time, do I have the courage to write that I was wrong? If the answer is no, I am doing data politics, not data analysis.

There is a paradox I have not solved. In V.League, clubs with limited budgets usually have no data department. My method is therefore most useful to the clubs that need it least — the big ones. The small clubs, the ones that truly need to save every minute of fitness, are the ones with no one to read the data. This is a structural problem in Vietnamese football, not a technical one.

I must also admit the limits of the fatigue index. It forecasts risk, not events. It says "high probability", not "certain". In my 200-page document there is a chapter titled "the times the data was wrong". It runs 18 pages. I keep it because if I published only my successes, I would become the liar I still denounce.

Numbers never lie, but the people who read them do. The worst reader is the one who reads data to confirm what he already believed. I was that reader in 2026.

Takeaway: signals for the next round

Being 62 has not slowed me down; it has told me which data is worth waiting for. I no longer wait for big numbers. I wait for small numbers appearing at the right moment.

Over the next four rounds of the regular season, three signals are worth tracking: the high-intensity distance of midfielders at clubs with heavy schedules; the number of presses within 5 seconds of losing the ball at clubs that just changed coaches; and the pass rate into the final third at clubs fighting relegation.

If you have only one screen for football, the table is what you will open. If you have two, add the high-intensity distance column. just look at the numbers and you understand everything — but they must be the right numbers, read at the right minute, by the right person.

The question I leave for myself, and for anyone doing this work in Vietnam: when your data is right but nobody listens, do you keep sending reports, or do you learn to say it in a way people will hear? I chose the second path in 2026. Nine years later, I am still checking whether that choice made me more accurate, or merely easier to listen to.