The Muscat Scorebook: Who Was Keeping Count of the Eleventh Over?

In the scorer's box at the Muscat ground there is one thing nobody else in the stadium possesses — the book. The batsman has his crease, the bowler his run-up, the fielder his thirty yards of turf, the crowd its noise. The scorer has the sheet of paper that becomes the truth by evening.

What happened in Muscat that evening is not the story of a six or a yorker. It is the story of a cap being handed over. The captain gives his cap to the umpire at the end of an over, the umpire walks it to the next bowler, and in that interval the scorer's eye leaves the page for a moment. In that moment an over changes hands.

Hours later, in a dressing room in the same complex, a young analyst looks at his notebook, then at his phone. The notebook says eleven. The ESPNcricinfo scorecard on the phone says ten. Between him and the truth stands a single over — and that over is the fulcrum of the entire dispute.

I have not broken the habit of checking the first copy of the scorebook after a match, not in thirty-eight years. I keep a notebook of everything the camera missed. This time what the camera missed was one over. And when an over goes missing, what actually goes missing is trust.

Context: a level series, a lost match, and a letter

Bangladesh U19 and Afghanistan U19 played a four-match ODI bilateral series in Muscat. The series finished 2-2. That detail matters, because it means the third ODI — the match at the centre of the allegation — was no dead rubber. It was a match that decided the shape of the series, and Bangladesh lost it.

The allegation: Afghanistan U19 captain and lead bowler Sohail Khan bowled eleven overs in that match. In 50-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 at all. The controversy is therefore format-anchored, and dragging it into T20 or Test argument would be dishonest.

The Bangladesh Cricket Board raised the matter with match referee Yasir Latifzai across two rounds of discussion, and then wrote a formal letter to the Afghanistan Cricket Board. Bangladesh said it had warned Afghanistan to be more careful. After the fourth ODI, the two coaching staffs argued over LBW and caught-behind decisions; the exchange ended with a handshake and a conversation. I do not treat that handshake lightly. When two staffs argue on the field and still shake hands, the dispute stayed inside bilateral channels rather than climbing to the ICC. That is a good sign. It does not answer the question.

Core: one event, two stories — and conflating them is the great error

This needs saying plainly, because in the coming weeks many people will merge the two.

Bangladesh's story is that Sohail Khan bowled eleven overs. The official record's story is that ten overs were bowled, and that the extra over was credited to a teammate who did not bowl a single ball in the match, because a cap-handover mix-up went uncorrected by the scorer.

These are not the same claim. The first says a rule was broken. The second says no rule was broken, only the counting. The outcomes diverge.

In my experience, when a dispute carries two stories and only one side is speaking, the truth usually lives somewhere else — in the sheet nobody read. Here that sheet sat on the official scorer's terminal, and the Bangladesh dressing room had no access to it.

That is the most concrete and least discussed fact in this affair. The complaining team did not have the official feed. It built its case from its own count and a publicly available scorecard. Both readings of that are correct. One: if a team on the field has no way of knowing how many overs the opposing captain has bowled, that is a system failure, not a scorer failure. Two: if your case rests on a record that is not official, your case is only as strong as the phone.

I remember an old count of my own. In 2026, when Hansie Cronje's confession broke and Mohammad Azharuddin's life ban followed, I was a staff writer on a Bangalore daily with a statistics degree and something to prove. I spent eleven weeks building a spreadsheet of no-ball and wide counts across 84 one-day internationals, hunting for spells that did not behave like cricket. My editor spiked it in an afternoon. He ran instead a two-hour interview I had done with a Karnataka seamer who had been offered money in a hotel lobby and refused.

That day taught me two things. A count is only as good as its keeper. And a count never becomes truth on its own — it needs a witness standing on the ground. In Muscat, Bangladesh had the count and not the witness.

Neutral venue, U19 level, and a thinning rope

The new arenas have the same heartbeat; only the language changed. In Muscat the crowd was small, the noise was small, and the cameras were fewer than they would be at Wankhede or Eden Gardens. When cameras thin out, the third eye standing behind an umpire's decision weakens too.

This is not a conspiracy. It is economics. A bilateral U19 series carries no broadcast money, so the technical support is narrower than at senior level and the pool of experienced officials is thinner. A neutral venue compounds it, because no host board has a natural stake in protecting the quality of local scoring and local appointments — and the host board is precisely the body normally responsible for that quality.

The likeliest culprit in this affair is not a bowler. It is capacity. That has bothered me for twenty years. Ranji coverage outside knockout week has collapsed in India, and scoring oversight in associate cricket thins out in the same direction. What you do not cover, you do not audit. What you do not audit becomes the subject of next season's argument.

A captain who is also the lead bowler

Sohail Khan is captain and lead bowler. That concentration is not itself a fault — in youth cricket the best player is often the captain. But it has a side effect: when one man bowls continuously and sets the field at the same time, fewer eyes are counting him. A captain's overs tend to be counted in the background. They make no noise.

It is therefore entirely possible that an extra over was bowled past the quota and nobody called it. Possible, not proven. The gap between those words is large.

What is proven is narrower: there are no bowling numbers in this dispute at all. No economy, no wickets, no strike rate, no spell breakdown. The only data in play is the over count itself, split across three records — the analyst's notebook (eleven), the phone scorecard (ten), the official terminal (ten, with one over misattributed). This is not a moment to comment on a bowler's quality. The paper is speaking, not the cricket.

The third ODI was not a dead rubber. The series finished 2-2, and the contested match was the one Bangladesh lost. Had the series already been decided, the extra-over question would be academic. Here it attaches to a match that shaped the outcome. And yet: it does not follow that the extra over changed the result. We do not know the runs from it, the batsman involved, or what a different bowler would have produced. There is no performance analysis in this file. There is procedure.

Contrarian: the argument I could not defeat

My habit is to look at a clean-looking case from the other end. What I saw there is uncomfortable, and I will not hide it.

First: even if eleven overs are proven, cricket has no mechanism to change a result. Results are not amended for over-count errors. The ceiling of this complaint is a caution and a better protocol. In the winter of 2026 I watched the system convert an investigation into a technical footnote when it needed to protect itself. It will do so again here.

Second: the headline this story will carry — 'Afghanistan broke the rule' — is not what the record says. The record says a scorer misplaced an over during a cap change. That is an administrative lapse, not manipulation. And that reading is, oddly, less comfortable for the complainant, because it means their case rests on an unofficial count.

Third, and most important: the timing. A technical over-count claim travelled in the same envelope as the anger over LBW and caught-behind decisions from the fourth ODI. When a technical claim travels with an emotional one, the technical claim loses credibility by association. That is the real price, and the side claiming to be right pays it.

Fourth: the report carries no Afghanistan side at all. No captain, no coach, no match official. When only one voice is heard, treating an allegation as fact is not journalism, it is publicity. My rule after thirty years: if one party is silent in a story, the silence deserves a line in the story.

And one last uncomfortable truth. There is no fixing allegation here. This is official error. But cricket's public memory is wired so that the phrase 'counting error' summons the winter of 2026. That memory is unjust, and it is present — and it is why a small administrative lapse gets inflated into a crisis. People like me helped build that memory.

Takeaway: the sheet that blinked

The ground remembers what the scoreboard forgets — I have written that many times. In Muscat it ran the other way. The scoreboard was the only witness left, and the scoreboard blinked.

What to watch is clear. The match referee's formal finding: does it record that an extra over was bowled? The Afghanistan Cricket Board's response: accept, reject, or stay silent? And above all, whether scoring and third-umpire protocols for neutral-venue U19 fixtures change in the coming months. If they do not, this affair ends as a handshake and a letter.

In my notebook, under this case, sits a question I cannot answer: when forty people on a ground cannot agree how many overs a bowler sent down, whose memory is the record? A scorebook is not the truth. It is only what everyone has agreed to accept. In Muscat, nobody agreed.