The Eleventh Over in Muscat: Bangladesh's Complaint, the Scorer's Tally, and a Question the Scorebook Cannot Answer

The Eleventh Over in Muscat

Somewhere in the third one-day international, an analyst with the Bangladesh Under-19 side counted overs in his notebook. Sohail Khan had bowled ten. A little later the same hand held a phone, the Cricinfo scorecard loaded, and the screen said eleven. One bowler, one match, two numbers. I was not in that room — I was in Bengaluru, reading the detail — but five decades in press boxes have shown me this moment many times, when a single digit slips out of place and nobody catches it.

In cricket, the over-count is the number we question least. Runs can be disputed, wides can be argued over, the height of a catch and the height of an LBW can be litigated for years — but how many overs a bowler has sent down is treated as machinery, not opinion. That trust is the root of this story, and also its illusion.

Lord's, 2026: a notebook, a deadline, and a quieter truth. That day I tallied overs in the margin of my notebook and later found my count was one ahead of the scorebook. I was not embarrassed; I simply understood that counting overs by eye is not a reliable human task. It needs a system, and a system needs discipline. Where discipline is thin, digits slip. What happened in Muscat rests not on a ball but on a crack in that system.

The context

This bilateral one-day series between Bangladesh Under-19 and Afghanistan Under-19 was played in Muscat, Oman — home to neither side. The series finished 2-2. The third ODI, the match at the centre of the dispute, was lost by Bangladesh. That single fact sets the temperature of everything that follows: the complaint concerns a match the complainant lost. It raises a question of motive, and separately a question of whether a technical irregularity existed. They are different questions and should not be fused.

The complaint is that Afghanistan captain and lead bowler Sohail Khan delivered eleven overs in the third ODI, against a ten-over cap. The Bangladesh Cricket Board took the matter to the Afghanistan Cricket Board through a formal letter, after two rounds of discussion with match referee Yasir Latifzai. The captain's report — traditionally the vehicle for noting umpiring decisions — carried the additional grievance. Bangladesh also advised Afghanistan to be more careful in future.

Running alongside, and often conflated with it, is a second and separate complaint. After the fourth match the two coaching staffs argued sharply over LBW and caught-behind decisions. That argument ended in a handshake and a conversation. The detail looks small but matters: the atmosphere was heated, the margins were thin, and umpiring was already a flashpoint in the series.

What the available reporting makes clear is that no ICC action, code-of-conduct charge or formal allegation has so far been recorded. This sits as an administrative matter between two boards. And one more thing, which an old reporter's habit insists on noting: the report contains no perspective from the Afghanistan Cricket Board or the match officials. What we have is one side's book. In fifty years I have learned that one side's book makes a story, never a verdict.

The ten-over line

In fifty-over cricket a bowler may deliver a maximum of ten overs — twenty per cent of the innings. T20 caps it at four; Test cricket has no cap. The detail sounds mundane and is the whole hinge. The Muscat quarrel is not about form, captaincy or an umpire's judgement. It is about a playing condition that can be counted.

That distinction matters. An LBW question is interpretive — where the ball pitched, where the stumps were, whether a shot was offered. Reasonable people will disagree. Whether a bowler has bowled an eleventh over is not interpretive; it is a recordable fact. Which is why dismissing Bangladesh's complaint as merely the excuse of a losing side is not as easy as it sounds. If the record shows eleven, a rule was broken. If it does not, the complaint has no ground. There is no middle.

Then the story turns, and this is where the debate leaves the rails.

Two accounts of one event

Bangladesh's claim is that Sohail Khan bowled eleven overs. The official scorer's record is that he bowled ten, with the eleventh credited to a team-mate who never bowled it. According to the report, the confusion arose from a cap handover that the scorer failed to catch.

These two accounts describe the same event and say different things. The first says the rule was broken on the field. The second says the rule was broken on paper. The first concerns a bowler's act, the second a scorer's act. If the first is true, the match's legitimacy is in question. If the second is true, what we have is a recording error. Treating them as one is the subtlest mistake being made in this affair — and it is being made widely, because 'eleven overs' makes a headline and 'one over credited to the wrong name' does not.

The real story, I think, is the second, and it is less exciting, which is precisely why it is being ignored.

How a count slips

I have spent four decades in press boxes across this country and I have seen the cracks in over-counting at close range. They are never dramatic. They are dull. An over ends, a captain walks to the umpire to return the cap, the next bowler marks his run-up, the batsman adjusts his gloves, the crowd shifts, the camera looks elsewhere. Somewhere in that moment a number advances on a scorer's terminal and someone must decide whose name it carries.

If ball-by-ball discipline is in place, if a second scorer sits as a check, if the third umpire's responsibility for the over-count is clearly assigned — the error is difficult. At a bilateral Under-19 fixture, at a neutral venue, none of those three conditions can be assumed. That is not an accusation; it is a description of the tier. Coverage is thin, and so is procedure.

And here is a detail buried inside the report that deserves more attention than it has received: Bangladesh did not have access to the official scorer's feed. Their complaint was built on the Cricinfo scorecard and their own analyst's tally. That cuts both ways. It suggests a transparency gap in match-day governance — why should a competing team not see the official record? It also means the foundation of the complaint was a platform, not a document. Two parties were reading two books and did not discover it until the match was over.

A scorebook error and a field error are different creatures. One can be corrected; the other cannot. We routinely sharpen our stories by presenting the first as the second.

The question nobody asked on the field

What startles me most about this affair is not whether an eleventh over happened. It is that nobody was stopped on the field in order to find out.

Consider it. If a bowler begins an eleventh over, an umpire stops him; that is among the most basic duties in the game. Eleven fielders, two umpires, a scorer — and nobody intervened. That tells you the event probably did not occur on the field, because if it had, someone would have caught it.

Look also at what the argument was about. After the fourth match the coaching staffs fought over LBW and caught-behind, not over an over-count. Had an eleventh over unfolded in front of everyone, that would have been the first, hottest, most immediate grievance. Instead the issue surfaced later — with paperwork, with tallies, after the match. This dispute came out of a file, not off the pitch.

That does not thrill me; it chills me. It means the most consequential process in that match was not the bowling but the bookkeeping. And the bookkeeping failed.

The blind spot of collective memory

Now the part on which you need not agree with me, but which deserves argument.

Collective memory will file this under: 'Bangladesh were wronged in Muscat.' Five years from now, a sentence about this series will contain 'eleven overs' and will not contain 'one over was recorded against the wrong bowler.' Memory prefers the sharper sentence to the accurate one.

My objection is twofold. First, the allegation is unproven, and the same report that carries it also carries the detail that weakens it — the misattribution. If that detail is right, Sohail Khan did not bowl an eleventh over. The scorebook did. That is a large difference, and it is the first condition of any decent argument.

Second, and this troubles me more: even if an eleventh over did occur, the game has no remedy. Results are not revised retrospectively. No committee will void the third ODI. What can happen is a report, a caution, a protocol change. The value of the complaint lies in the future, not the past.

And a third thing, from an old reporter's instinct. The central figure here is a teenager, or thereabouts, whose bowling we are given no numbers for, and whose name is now fused to a controversy. He may have done nothing wrong. A captain who is also the lead bowler is precisely the situation in which over-management gets loose. We should pause before loading such weight onto young shoulders. In my experience, the players who speak least are the ones whose names appear most often in disputes.

And Afghanistan's side?

There is a large silence here that should not be ignored. The available reporting carries no statement from the Afghanistan Cricket Board, no formal finding from the match referee, no explanation from the officials. We are forming opinions on a case in which one party has said nothing at all.

The discipline I was taught is simple: until both sides speak, write allegation, not fact. That discipline matters especially here, because the precise facts — which over, which bowler, at which minute — exist only on the official scorer's terminal, which the complaining side could not access.

How large is this, really

I want to be clear, because at sixty-seven honesty is the only inheritance worth keeping. This is not a fixing story. There is no betting signal anywhere in it. There is no financial dimension, no broadcast dispute, no franchise interest. It is an administrative controversy from an Under-19 bilateral series with negligible industry consequence. Presenting it as a scandal would be inflation.

Treating it as trivial would also be wrong, for a reason that belongs to this tournament cycle. When the big events arrive, our attention goes to senior scoreboards. Under-19 and women's Under-19 fixtures are played on the same neutral grounds, under the same thin officiating arrangements, on the same ageing scorer terminals. The same officials and systems surface later in senior associate cricket. A single over-count is small; the habit is not.

The Muscat episode is a photograph of a system we rarely look at. And within that photograph there is one frame I will keep returning to: the handshake. After the sharp words following the fourth match, the two coaching staffs shook hands and talked. It may never make a headline. It is the most reassuring part of the story. Bilateral channels worked.

What to watch

The referee's formal finding: whether it records a scoring error, and whether it records that an eleventh over was genuinely bowled. The ACB's response: silence is also an answer, and it too has meaning. Officiating appointments for future neutral-venue Under-19 fixtures: if they change, the complaint did its work. And whether the friction reappears the next time these two sides meet.

Brisbane taught me to watch the second XI warm up. From the same habit I am watching something small here: the question this time sits not on a fast bowler's pace but on a scorer's terminal. Perhaps that is the most honest image of this era — the future of the game is decided less on the field than in the rooms where numbers are written down.

There is no hero in this story for me, and no villain. There is an over with no owner, an over that went and sat in someone else's account, and two boards that shook hands and closed the conversation. When the scorebook and the eyes are reading two different books, whose account will the truth be entered in? Perhaps next time an analyst counts overs in his notebook, he will knock on the scorer's door instead of refreshing a scorecard. A small habit. A large difference.

I have learned to trust the hush before the whistle. In Muscat that hush was hidden inside a single over, and nobody heard it.