Manila, three in the morning, early July 2026. On the LCK stream, Lee Sang-hyeok — Faker — rotated his right wrist four times between games and set his hand down on his thigh. The camera cut to the scoreboard. No medical statement, no file opened, no timestamp recorded. Days later, T1 announced he would step back with a wrist injury, and only in early August 2026 did he return to the starting roster.

On a European pitch, a moment like that immediately produces a data row: minute 27, hamstring group, strain grade, expected days out, MRI date. In esports, that row does not exist. Across years of watching matches from a screen, I still cannot answer a very basic question: where are esports players' injuries actually stored?

One industry with surveillance, one industry with a hole

Football has the UEFA Elite Club Injury Study, running since 2026, collecting injury data from top European clubs season by season with shared definitions of “injury,” “absence,” and “recurrence.” Because of that structure, a hamstring tear in a smaller domestic league can be placed beside a similar case in the Champions League to compare frequency, cross-check the calendar, and test whether match load is crossing the body's tolerance threshold.

Esports has no equivalent. There is no shared definition of an “esports injury.” There is no obligation to disclose why a player is absent. Each publisher, each tournament organiser, each team decides what to say and how far to go. Most absences reach the public as “personal reasons” — a phrase that cannot be measured, compared, or used for any medical conclusion.

I came to esports from the opposite direction. In June 2026, when European football returned after a three-month shutdown, I took data from five top leagues and looked at the first 287 matches. I counted 41 muscle tears; the same number of matches the previous season produced 28. That 32 percent rise pushed me into a long piece, which I sent to five experts and got conflicting replies for. I kept the same counting method when I moved into esports — and the result came back as a blank sheet.

Europe closed its pitches, so I opened the files and counted every muscle tear. In esports, I opened the files and found blank paper.

The injury clock runs in weeks, not seconds

There is a technical reason counting is far harder here: most esports injuries have no in-match timestamp. A player's wrist does not tear at minute 27. It degrades across thousands of practice hours, long scrim blocks, bootcamps, and seasons where the gap between rounds is only enough to travel and catch up on sleep. The second-by-second timeline I use for football injuries becomes meaningless; I have to switch to weeks and months, where the margin of error is far larger and the memory of the people involved becomes the primary data source.

Based on my experience tracking matches and the practice schedules teams publish, I keep noticing a load type with almost no equivalent in traditional sport: the double shift. Players scrim in afternoon and evening blocks with their team, then stream for several more hours afterwards to fulfil platform obligations. Add review sessions, opponent analysis and solo practice, and the mental load plus the micro-load on wrists, cervical spine and lower back accumulates continuously with no mandatory rest day written into league rules.

In the Philippines, the market I follow weekly, MPL Philippines is one of the largest Mobile Legends: Bang Bang leagues in Southeast Asia, played on a stage with a live audience in Manila. Most starting rosters sit between 17 and 22 years old. The calendar is dense, with domestic and international travel plus pre-tournament bootcamps. Across that entire system, I have never seen a document limiting scrim hours, mandatory streaming hours, or minimum rest days between rounds.

The player's body is writing a dictionary of injuries that the coaching world has not agreed to open.

Whoever holds the file owns the story

When there is no injury registry, the power to interpret sits with whoever holds the information. In football, I worked a January 2026 transfer case: striker Kevin Tabora moving from Stallion Laguna to Muangthong United, a deal that collapsed at a second medical. I read the clinic report, spotted an old meniscus tear in his right knee dating to 2026, called Stallion's doctor, and ran the numbers against similar cases in the J-League. His recovery index came out better than 82 percent of players in the same position. The buying club then sent an additional doctor to Manila to re-examine him. That story only moved because a file existed with dates, images and a named physician.

Esports runs the opposite way. A contract buyout can be completed without the buying side ever seeing an injury file, because the file may not exist. The selling club controls the narrative; the buying club inherits the risk. For young contracts, that risk converts directly into early retirement, with no party legally accountable because nothing was written down.

Three data fields that could start now

I am not proposing a heavy system. I am proposing a minimum deployable inside one season: date of record, body region affected, and cumulative hours under load in the previous 30 days. Those three fields are enough to build a baseline, enough to spot injury clusters by position, and enough to compare teams within the same league. Everything more sophisticated — imaging, return-to-play protocols, risk stratification — only has value once a baseline exists.

The counter-angle: more data is not automatically better

There is an objection I raise before anyone raises it for me. Medical transparency in a transfer market can be weaponised. Injury records have been used to drive down contract values, to apply pressure during renegotiations, and to shape public opinion against a player. A young player with a history of wrist pain can be treated as damaged goods simply because his data was recorded while others' was not. The cost of transparency is not distributed evenly, and the people who pay it usually hold the least power.

The second objection is methodological and, I think, more important. Comparing esports injuries to football injuries may be a category error. A hamstring tear is trauma from short, high-intensity exertion. Wrist pain, eye strain, chronic sleep loss and cervical degeneration in esports look closer to office ergonomics than to elite sports medicine. If that holds, the most effective interventions are absurdly cheap: scrim hour caps, mandatory rest windows, standardised keyboards, mice, chairs and screen distance. None of that generates revenue for anybody, none of it produces a sponsorship deal, and that may be exactly why it has not been implemented.

The third objection is about my own trade. A blank sheet does not mean no injuries occurred. It only proves nobody counted. I have read a case wrong before by trusting a single source, and I had to rewrite an entire conclusion after one email from Copenhagen. I do not want to repeat that mistake by turning the silence of data into a medical finding.

Why this matters beyond one season

For an industry selling the images of very young athletes to sponsors, failing to keep even a basic injury ledger is a technical debt. That debt comes due the moment a 21-year-old retires over a wrist, and nobody in the meeting room has enough evidence to answer whether it could have been avoided. I do not write about injuries. I write about what the body screams when language runs out. The body does not lie — it simply speaks a language the medical room has not translated yet. When the next tournament starts in Manila, try counting how many absences are filed under an empty line.