The Eleventh Over in Muscat: The U19 ODI Dispute Is Not About Sohail Khan, It Is About the Scoring Protocol

My ledger always opens at the under-17 World Cup, where every name is an unread page. But on this evening in Muscat the first entry was not a scoreline. It was a question I could not file away.

In September 2026, covering the FIFA U17 World Cup across New Delhi and Navi Mumbai, my editor wanted the celebration piece — Jeakson Singh's 82nd-minute header against Colombia, India's first goal at any FIFA finals. I took the 21-man squad list home and opened a ledger instead: district, school, first academy, first coach, birth year. Three players carried conflicting birth years across federation and school records. I left the discrepancies in the row rather than smoothing them out.

The over-count in Muscat is the same sheet. In the third ODI of a Bangladesh U19 versus Afghanistan U19 series, Afghanistan captain Sohail Khan is alleged to have bowled eleven overs in a format where the legal maximum for any bowler is ten. Bangladesh took the complaint through two rounds of discussion with match referee Yasir Latifzai, then the Bangladesh Cricket Board (BCB) wrote formally to the Afghanistan Cricket Board (ACB), warning Afghanistan to "be more careful."

But the same report carries a line the headlines dropped. On the official scorer's terminal, Sohail Khan was credited with ten overs; the disputed over was logged against a teammate who never bowled it. The stated cause was a cap-handover mix-up the scorer failed to catch.

That sentence turns the story. What reads at first glance as a broken rule is, on the evidence available, a wrongly written record. Conflating the two is the single largest error available in this case.

Muscat, two boards, and one piece of paper

The facts, in order, because interpretation before sequence is a bad habit in my trade.

This was a four-match bilateral U19 ODI series in Muscat, Oman — a neutral venue, no home advantage for either side. The series finished 2-2. That matters, because the contested third ODI was one Bangladesh lost, and a 2-2 series means the match was no dead rubber; its result shaped the series.

After the fourth match, the two coaching staffs argued over LBW and caught-behind decisions. That argument ended in a handshake and a conversation — friction, not rupture. The extra complaint travelled forward through the captain's report, the post-match form captains submit.

Three things are clear. The substance of the complaint is numerical, not emotional — a count of overs. The route is administrative — referee to board, not to the ICC. And no party has alleged fixing or betting involvement. This is a competence question, not an honesty question.

Afghanistan's side does not appear in the report. No formal finding from the referee appears either. We have one party's account and an official record that does not match it. My practice at this level is fixed: what is claimed gets written as an allegation, what is recorded gets written as fact.

The ten-over cap: the rule that created the dispute

One technical point, without which the story is meaningless.

In 50-over cricket no bowler may deliver more than ten overs — twenty per cent of the fifty available. That is a playing condition, not a convention, and it exists only in this format. T20 caps a bowler at four overs, twenty per cent of twenty. Test cricket has no cap at all.

So the eleventh over is an offence only in ODI cricket. Had this happened in a T20, the fifth over would be the dispute; in a Test, there would be no dispute. Anyone reading this through the "pressure of T20" or "decline of the long form" lens is opening the wrong file. The controversy is format-anchored and has no meaning outside the format.

The second technical point is where most observers slip. Who counts the overs? The umpire counts deliveries on the field, but the official over account is built and amended at the scorer's terminal. If one over is credited to the wrong bowler there, the record is wrong even if everything on the field was right — and nobody notices, because the record is the truth we all consult.

This is the argument I built in Russia in June and July 2026. First World Cup with VAR, 64 matches, and I logged every review, its minute and its outcome in a paper notebook: a record 29 penalties, including the first VAR-awarded penalty in a final, Perišić's handball in France's 4-2 win over Croatia at Luzhniki. I filed nothing for nine days, then argued against importing VAR into Indian leagues on the strength of highlights. My copy has carried sample sizes since. Here the sample is one match and the evidence is a phone screen.

One over, three records

What is genuinely interesting is not the bowler but the collision of records. Three versions of the same over exist.

1. Bangladesh's analyst, counting by hand. He counted ten overs completed by Sohail Khan, then saw one more credited to him.
2. The Cricinfo scorecard, open on a phone. Bangladesh's team confirmed its suspicion against a public scorecard.
3. The official scorer's terminal. Ten overs against Sohail Khan; the eleventh logged against a teammate who never bowled it, after the cap-handover mix-up.

Set the three side by side and an uncomfortable fact emerges: Bangladesh's complaint rests not on the official record but on a public website and a hand-kept count. That does not make the complaint false — an eleventh over may genuinely have been bowled and wrongly filed. It does raise the question of why the people on the field had no access to the official feed.

A bilateral U19 series typically carries no third umpire, no DRS, and none of the live-scoring mesh of senior international cricket. When the scorer's terminal is closed to teams, every over-count is a dispute waiting to be filed. This is not the system failing. It is the system being disclosed.

A captain who is also the lead bowler

The report tells us very little about Sohail Khan: captain of Afghanistan U19 and the team's main bowler. No average, no economy, no strike rate, no wickets, no pitch detail, no indication whether he bowls pace or spin.

I will state it plainly. The report contains no performance data on Sohail Khan, so a single sentence assessing his bowling would be speculation, and speculation does not occupy the space reserved for numbers. The object of analysis here is process, not player.

One structural observation is available, and it is reasoning rather than guesswork. A captain who is also the lead bowler makes an over-count error easier to miss. When one player takes long unbroken spells, none of the three parties who might catch the error — scorer, umpire, team management — gets a natural break in the counting. Without a break, the boundary between ten and eleven blurs.

This is also not senior cricket. At under-19 level, workload discipline is weaker, a captain bowls himself long, and there is no voice on the ground saying "that is his eleventh." It is a highly plausible human-error scenario — and human error is a different category of event from deliberate misconduct. Naming them with the same word does this case an injustice.

From my ledger: the lesson of the base rate

Between March and November 2026, with stadiums empty, I called 43 Gujarat academies and recorded the answers: 14 had closed or gone dormant, nine had dropped their under-13 age group entirely. I spent the rest of the hiatus digitising 41 notebooks covering 2026 to 2026. That period gave me a habit I still keep — check the base rate before treating one event as a trend.

The base rate here is that under-19 players reaching a senior national side are the exception. In 2026 I published the five-year audit of the 2026 men's cohort: of 21 players, three had played senior international football — Jeakson Singh, Suresh Singh Wangjam, Amarjit Singh Kiyam — and six were out of professional football.

That base rate connects directly. The tier where an eleventh over gets settled is the same tier that supplies senior players — and if its records can exist in three versions, questioning its capacity is not idle.

I will add that the three conflicting birth years from my 2026 sheet are still in my file, and not one of them resolved itself. Records do not correct themselves. Someone corrects them, and that someone is usually never named.

Neutral venues and the weakness nobody writes about

Muscat matters for another reason: it was neutral ground. Neutral means no home advantage, and it also means match officials are typically drawn from a local or less-experienced panel, because the senior panels are not sent to bilateral U19 series. The referee travels with the series; the umpires and the scorer come from the host's system.

This is economics, not conspiracy. Bilateral U19 series carry almost no broadcast value and negligible audiences, so scrutiny scales down with them. Fewer cameras means less pressure; less pressure means looser process. The largest failure in this case is not that an extra over may have been bowled. It is that at no point did anyone have a shared instrument for checking.

I remember being one of two women among the accredited Indian press in Russia, as I had been at every tournament since 2026. That experience taught me something: in a system where your presence is counted, records get counted. Where no one's presence is counted, neither do the records. Under-19 cricket sits squarely in that second category.

The question is not the bowler. It is the pen.

The turn this piece was written for.

The headline — "Afghanistan's captain bowled eleven overs" — is an allegation, not an established fact. Treating it as fact carries one obvious cost: damage to a reputation that has not had a hearing. The report carries no Afghanistan statement, no formal referee finding, and no mention of an ICC process.

Conversely, the report's most concrete technical detail — an over logged to the wrong account after a cap-handover — points to an administrative root, not an intentional one. It is a scorer's error, and a scorer's error is answered with process, not condemnation.

A second inversion hides inside the story: the real disclosure is not the number of overs but the asymmetry of information. Bangladesh's team had no access to the official terminal and had to rely on their own analyst and a public website. Where teams in a bilateral series are not given a live official feed, every over count becomes a dispute — and this dispute will return in another series under another pretext.

A third inversion will be written about least: the post-fourth-match argument ended with a handshake. The coaching staffs confronted each other over LBW and caught-behind calls, then shook hands and talked. Small event, meaningful signal — the escalation risk is lower than the language of the coverage implies. The matter never reached the ICC; it stopped at two rounds with the referee and one letter.

And the least pleasant point: the probability of the result changing is close to zero. Cricket does not retroactively amend results for administrative error. Even if an eleventh over was bowled and ten were recorded, the third ODI stands as a Bangladesh defeat unless a formal protest succeeds — which is extraordinarily rare.

Which brings back the lesson: what is not in the record is lost even when it happened on the field. That is not cricket's weakness. It is cricket's method.

What gets filed next

Three things to watch, on three clocks.

The formal finding from match referee Yasir Latifzai. If it records that an eleventh over was bowled, the third ODI's validity comes into question — the result may stand, but a note attaches to the record.

The ACB's response. Denial or concession will decide whether this stays bilateral or travels.

And, for me the most important: whether official appointments and the scoring-feed protocol change for future U19 series at neutral venues. If they do not, this remains an incident and not a pattern.

I close the ledger with a question. In a system where six of 21 under-17 players can leave professional football inside five years, and where three versions of a single over's count can coexist in one match file, what exactly are we keeping a record of — the bowler, or the man who picked up the pen?