European U19 Girls in Antibes: HOCHART Unbeaten and the Data Flaw in the Standings

On the table in Antibes, Leana HOCHART finished the second day of the Europe Youth Top 10 U19 Girls without dropping a single game. Six matches, six wins. Among them a 4-0 win over POLAKOVA and a straight-games win over LEAL. In a single round-robin event for the ten leading U19 girls in Europe, not dropping a game across two days is a strong signal, and I want to start from that signal itself.

But there is another detail that made me stop longer than HOCHART's win streak. The results report from the European Table Tennis Union states that Alexia NODIN's only defeat came against Bianca MEI-ROSU on the opening day. Then, in another passage, the same report states that MEI-ROSU's only defeat came against NODIN. In a single round-robin event, those two statements cannot both be true. The two players meet exactly once.

This article exists to point out that even a short results report can contain a logical gap, and that readers need a filter before they believe. I work in reading sports data, and I have learned that most of my mistakes did not come from a weak model, but from reading a source without checking it first.

Context: an event designed to be seen, not to bank points

The Europe Youth Top 10 is an annual European Table Tennis Union event for roughly the ten leading young players on the continent in each age group. In the U19 Girls category, it gathers the elite of the European youth development system. One thing must be stated plainly: this is a continental event, not a global stage. There are no Chinese, Japanese or Korean players in the field. So any comparison of the kind "Europe versus the rest of the world" is meaningless in data terms here.

That shapes how I read this report. The value of the Europe Youth Top 10 does not lie in the ranking points it delivers, but in the fact that it is an observation window: who is rising in the European youth system, and which nations have depth. This is an event of presence and visibility, not an event of point accumulation.

The format matters no less than the context. The scores in the report, including 4-0, 4-2, 4-1 and one seven-game win, show that the format is best of seven games, first to four. This is the standard format of youth round-robin events run by the European Table Tennis Union. This detail seems like a technicality, but it completely changes how we read HOCHART's unbeaten run.

The seven-game format and the statistical weight of an unbeaten run

In a first-to-four-games format, the higher number of games compresses upset variance. A weaker player finds it harder to get lucky across four games than across three. In other words, an unbeaten run in a seven-game format is a more reliable signal than an equivalent unbeaten run in a five-game format. This is the first point I want the reader to remember: the same winning streak carries a statistical weight that depends on the format that produced it.

I once made exactly this mistake. Years ago, I read an unbeaten run at another event and gave it far too much meaning without checking the format. When I discovered that event was best of three, I had to rewrite the entire conclusion. Since then I have set myself a rule: before praising a run of results, know the framework it was produced in.

There is a second consequence of the seven-game format that few notice. In a seven-game round-robin, games lost becomes a subtler indicator than matches won. A player who wins six matches but drops many games may be closer to the chasing pack than the standings suggest. Conversely, a player who wins without dropping a game is showing a level of control that match scores do not fully express. HOCHART, by not losing a game on the second day, sits in that second group.

I have tracked this indicator for a long time, and I call it the game-control rate. It appears in no official ranking table, but it is one of the first variables I check when assessing a run of results in a multi-game format. A clean-game streak is always more reliable than a narrow streak, even though both are recorded as wins.

The chain of evidence: reading the scoreboard like a data set

I took the report and split it into discrete data points. This splitting matters, because a continuous report often hides its internal structure.

Data point one: after six matches HOCHART has still not lost, and on the second day she did not drop a game. Data point two: she beat POLAKOVA 4-0. Data point three: she beat LEAL in straight games. Data point four: NODIN beat HOLDA 4-0 and MASSART 4-2. Data point five: MEI-ROSU beat MASSART 4-2 and POLAKOVA 4-1. Data point six: HOLDA beat MASSART in seven games. Data point seven: BOGDANOWICZ played solidly. Data point eight: ITAGAKI withdrew through injury, and her earlier results were erased.

When these points are placed side by side, a picture emerges. There is a clear gap between the top and the bottom of the field. HOCHART beat POLAKOVA 4-0, MEI-ROSU beat POLAKOVA 4-1, NODIN beat HOLDA 4-0. These are the scores of a stratified event, not a flat round-robin in which every match is tight.

Core insight: this is a clearly stratified round-robin, not a flat race. This has practical meaning. In a flat round-robin, the title is usually decided by one lucky match. In a stratified round-robin, the title is decided by whether the strongest player keeps her focus against the lower group. HOCHART, by not dropping a game on the second day, is showing she is keeping that focus.

But I must be careful. The report provides no technical information at all: no description of playing style, no information on blade or rubber, no data on age, build or injury history. So any technical inference here must stop at the level of the score. I can say HOCHART has a level gap over POLAKOVA and LEAL within this event. I cannot say how she won.

That is a real limitation, and I want to state it plainly rather than fill it with speculation. A results report is not a technical report. It can answer the question of who won, but not the question of how they won. Readers need to distinguish these two kinds of question, because mixing them is the fastest way to produce wrong conclusions.

I read a player through dozens of variables before I listen to a commentator. But here I have only one variable: the score. And when there is only one variable, being honest with it matters more than trying to sound profound.

How to read a round-robin table

There is a skill I consider more important than reading scores, and that is reading the structure of a round-robin table. A round-robin table is not just a list of wins and losses. It is a head-to-head matrix, and each cell in that matrix carries two pieces of information: the result, and the position of that result in the schedule.

The schedule matters because it determines who meets whom first. A player who faces the strong group early may look weaker than she is, and a player who faces the weak group early may look stronger than she is. In Antibes, the order of matches directly affects how we read HOCHART's six-match run. If those six matches include the strongest opponents, the run is heavy. If they are mostly the lower group, the run is lighter than the standings suggest.

The report does not give me the full order of matches. That is another shortcoming, and it reminds me that a round-robin table is only truly meaningful when accompanied by the schedule. I once built a round-robin table for a youth event and ignored the schedule factor. The result was that I misjudged a player who had in fact met the three strongest opponents in the first three days. After that, I added a schedule column to every table I built, and I have never dropped it since.

Here I can draw one principle: a round-robin table without a schedule is an incomplete round-robin table. We can read it to know who is leading, but not to know who is truly strongest. Those two questions are different, and confusing them is the source of many hasty conclusions.

The unresolved contradiction

Back to the detail that made me stop. The report says NODIN lost to MEI-ROSU. The report also says MEI-ROSU lost to NODIN. In a single round-robin, each pair of players meets exactly once. So these two statements cannot both be true.

There are three possibilities. First: the original report got one of the two statements wrong. Second: the data-extraction process distorted the information. Third: there is a contextual detail I do not yet know, such as a result adjustment caused by ITAGAKI's withdrawal.

Whichever it is, the consequence is the same: we cannot yet rank NODIN against MEI-ROSU, and therefore cannot predict the title with any confidence. Any prediction about the final day must wait for this head-to-head to be verified.

This is where I want to tell a personal story, because it explains why I react so strongly to such a small detail. My first V.League data table had hundreds of errors, but it taught me more cleanliness than any course. I once trusted a number I had entered wrong myself, then built an entire analysis on top of it. When I found out, I had to delete the piece and rewrite it from scratch. Since then, whenever I see data that does not match, I stop, rather than skim past.

A small contradiction in a report is not a grand matter. But it is a test of how we read. If we ignore it, we have accepted a flawed standings table. If we stop at it, we keep our honesty with the data. Data does not need me to believe it. Data needs me to check it.

There is one more subtle point about this kind of contradiction. It does not sit in the raw results section, but in the summary section. The report records individual results in one place, then summarises each player's defeats in another. When the two do not match, the error is usually in the summary. This is consistent with my experience: the summary is where errors hide, because it requires the writer to synthesise, and synthesis is the most error-prone step.

ITAGAKI's withdrawal: when the field changes mid-event

Data point eight deserves its own discussion. ITAGAKI withdrew through injury, and her earlier results were erased. This is a standard fairness mechanism in round-robin events: when a player withdraws, her results against those who remain are removed, to prevent the withdrawn player from inadvertently gifting or taking points from others.

The mechanism is sound, but it creates a consequence readers often overlook. When ITAGAKI's results are erased, every remaining player's record is computed against a non-uniform opponent set. A player who had already faced ITAGAKI loses a match; a player who had not faced her loses nothing. So the standings after erasure are no longer a perfectly fair comparison.

This is the kind of detail I learned to notice over many years. When the Bundesliga played in empty stadiums, I realised that home advantage is only a variable waiting to be erased. That lesson was not about football, but about a way of seeing: a variable that seems fixed can actually disappear when circumstances change. Here, that variable is the opponent set. It seems fixed, but ITAGAKI's withdrawal changed it mid-event.

For the reader of a standings table, this means: treat every mid-event ranking as provisional. It can be adjusted retroactively. A player sitting third today may jump to second tomorrow, not because she won more, but because another result was erased.

There is one aspect of injury I always treat with caution. Announcements about withdrawal are often controlled by the team's or federation's communications. The phrase "wait until the weekend" in many cases means the injury has not healed. Here, ITAGAKI's mid-event withdrawal, combined with the erasure of results, is a sign that the injury was serious enough to prevent continuation, rather than a precautionary decision. That is a signal I record, though I lack the data to assess its severity.

The European picture: France leads, the rest chase

Viewed as a whole, the national picture at this event is fairly clear. France has two players in the leading group: HOCHART and NODIN. Romania has MEI-ROSU. Poland has BOGDANOWICZ and HOLDA. Czechia has POLAKOVA. Belgium has MASSART. Portugal has LEAL. Germany has ITAGAKI, who withdrew.

The most notable thing is France's depth. A nation having two players competing for the title at a continental Top 10 event is a signal about its youth development system. I want to stress the word system, because one good player can be an individual phenomenon, but two good players of the same generation are usually the product of a process.

But I do not want to inflate this signal. A European U19 event with two French players in the leading group says nothing about the future of world table tennis. It says only that, at this moment, France has depth in the U19 Girls category. To assess long-term impact, one must track whether these two players step up to the senior national team, and how long that takes.

Here a reference index can be useful. In the way I track it, a squad-depth index measures the number of players in an age group capable of competing at international level. I cross-check this index against aggregated data from the major table tennis nations, including the VangBong Player Depth Index. France, with two players in the leading group here, is showing that index at a positive level in U19 Girls. But the index only means something when tracked across years, not across one event.

Poland is also a notable story, but in a different way. Having two players in the event, with HOLDA having just won a seven-game match, shows a mid-tier group with stamina. In a round-robin, the mid-tier does not compete for the title, but it decides the title, because it takes points from the top group. A nation with a strong mid-tier is an awkward opponent for anyone.

Europe in the bigger picture

I want to place this event in a broader picture, because that is how I always read a result. The Europe Youth Top 10 is one mesh in the youth development system of European table tennis. It is not an endpoint, but a checkpoint. A player who wins here does not automatically become a senior star, and a player who loses here is not automatically cut from the system.

This matters because it counters a common temptation: reading a youth event as a forecast of the future. I have fallen into that temptation. I once wrote about a young player in a tone as if her future were settled, simply because she won a youth event. Years later, she did not progress as far as I predicted. The lesson: youth results are a signal about the present, not a promise about the future.

At the European level, the gap between the youth tier and the senior tier is even wider than in some other regions, because competitive density and levels of professionalisation differ. So a strong result at the Europe Youth Top 10 is a necessary condition for being noticed, but not a sufficient condition for senior success. I keep that distance in mind when reading the Antibes scoreboard.

There is one thing I always remind myself: table tennis is a sport where individual technique and psychology decide more than in most team sports. In a team sport, a young player can be supported by the system. In table tennis, the player stands alone at the table. That makes youth results both more reliable and more fragile: more reliable because they are less disturbed by teammates, more fragile because they depend on a single individual.

The contrarian angle: correlation is not causation

This is the section where I want to discuss what this report cannot prove.

First, HOCHART leading does not prove she is the strongest player in absolute terms. It proves only that she has the best record within this event, as of the second day. There is no ranking data in the report, so we do not know whether she is the expected favourite or an over-performer against expectations.

Second, a nation having two players in the leading group does not prove that nation's system is better than others. It may simply reflect a special generation of talent, or even luck in selection. The correlation between many players in the leading group and a good system is a weak correlation, and I do not want to sell it as causation.

Third, and most important, this report is a results report, not an analysis report. It is written to inform, not to explain. So its lack of technical data is not its fault, but the nature of the genre. The fault would lie with the reader, if we assign it analytical weight it does not have.

The 2026 World Cup taught me one thing: the model does not collapse, I was the one who believed it absolutely. I ran regressions on hundreds of matches and gave a team a very high probability of reaching the semi-finals. The result was the opposite. The lesson is not to avoid models, but to remember what assumptions a model is built on. Here, my assumption was that the report was accurate. And I have just found evidence that this assumption may be wrong.

There is another form of contrarian point I want to raise, about how a report is chosen to be written. The report's focus on HOCHART, a home-nation player, may reflect a narrative choice by the organiser: promoting a prospect from the host country. This is a communications signal, not a data signal. I note it, but I do not let it shape my assessment of the players' actual strength.

The blind spot of a wire report

There is one more aspect I want to mention, because it concerns how sports data is produced. This report is of the kind I call a wire item, a results report written quickly, often based on live results, and distributed to many outlets. This kind of report has the advantage of speed and numerical accuracy, but the disadvantage of weak cross-checking.

That is why a contradiction like the NODIN and MEI-ROSU pair can slip through. In a wire report, the writer usually records results in chronological order, and when summarising someone's only defeat, errors easily occur if the full standings are not re-checked.

For the reader, the lesson is: when a report summarises itself, check the summary against the raw results. The summary is where errors hide, because it requires the writer to synthesise, and synthesis is the most error-prone step.

I built this habit after making a similar mistake myself. In a piece about a youth event, I wrote that a player had lost exactly one match, when the raw results showed she had lost two. I had summarised wrongly. No one caught my error, but I knew, and I fixed it. Since then, I never write the summary before the raw data.

There is a broader consequence. When I read any sports report, I always ask myself: which part of this report is raw data, and which part is the writer's interpretation. Raw data is the individual scores. Interpretation is sentences like leading, chasing, solid. These two parts have different reliability, and mixing them is the fastest way to make a mistake.

Why I do not rush to conclude about HOCHART

I want to spend a paragraph making clear why I do not rush to praise HOCHART, despite her impressive record. The reason is not that I doubt her, but that I doubt my own reading process.

A six-match unbeaten run with no games dropped in a day is a strong fact. But to turn that fact into a conclusion about class, I need three things the report does not have: the rankings of the opponents, the order of the matches, and context on each player's recent form. Lacking those three, I can only say HOCHART is leading, not that she is the strongest player.

This distinction is not academic. It is the distinction between describing a phenomenon and explaining it. A good data analyst is someone who knows when to describe only. Crossing that line too early is how you produce pieces that sound good but are wrong.

I once thought a good analyst was someone who drew the most conclusions. After many years, I changed my mind. A good analyst is someone who knows what they cannot conclude. Saying I do not know yet requires more discipline than saying I know, especially when everyone around you is concluding.

Takeaway: the signal to watch on the final day

So, going into the final day, what will I watch?

I will watch the HOCHART versus NODIN match. It is a meeting between two French players, and it could decide the title. If HOCHART wins, she almost certainly completes a perfect event. If NODIN wins, the standings open up.

I will watch the verification of the NODIN and MEI-ROSU pair. Until the contradiction is resolved, I treat their ranking as undetermined.

I will watch whether the erasure of ITAGAKI's results creates any further adjustment to the standings, because this is a variable that can change the picture without a single match being played.

And I will watch HOLDA, who just won a seven-game match. In a round-robin, a mid-tier player can decide the fate of the top group by taking points from them. HOLDA, with the stamina of a seven-game win, is the type of player who can do that.

Finally, I will watch the report itself. If the final-day report corrects the detail about the NODIN and MEI-ROSU pair, we will know it was a typo. If it keeps the contradiction, that is a signal about the source's verification process, and that matters more than any match result.

From a V.League Excel sheet to a Bundesliga model, my journey is the journey of numbers that speak. But numbers only speak when the reader stops and asks them the right questions. In Antibes, the right question is not who is leading, but whether this scoreboard is trustworthy. And the answer, so far, is: partly trustworthy, and the rest is waiting to be verified at the table.