Bangladesh 110/3: Sadman's Fifty, Shanto's Wasted Review, and the Warrican Over That Told More Than the Scoreboard

Bangladesh were 110 for three in the fifth over after lunch. Najmul Hossain Shanto looked at the big screen, signalled for the review, and sent the ball upstairs. The tracking came up, the umpire's arm went up, and the scoreboard sat on 110/3 for the next twenty minutes. What actually changed was this: Bangladesh had one fewer review for the next eighty overs. In years of watching from the ground and from a Delhi night desk, I have logged the same thing repeatedly — the spectator is handed the verdict, never the reasoning. The big screen shows an outcome, not an argument.

The source material here is a live score update: short, fast, unfinished. No venue, no series, no day, no innings; no score for Sadman, no score for Shanto, no detail on what exactly was reviewed. Four facts are on the table: Sadman Islam's tenth Test half-century, Shanto lbw to Jomel Warrican, the review failing to help, the score reading 110/3. I will work with those four, and wherever I am estimating, I will say plainly that I am estimating.

A tenth Test fifty is not a small thing for an opener, but a half-century is a lagging indicator. It records how long a batter survived, not what the team got from those balls. A fifty made at 110/3 and a fifty made at 300/3 sit in the same column while pulling the match in opposite directions — one is built under the weight of a fallen wicket, the other in the comfort of a set pitch. To price Sadman's fifty I need three things: his strike rate, his balls-per-boundary, and the size of the partnership it anchored. None of the three is in this update. So the safest sentence available is this: he batted well, and the opposing spinner was pushing him toward a scoring shot throughout, which is equally true.

I trust a model only after I can name the condition that would make it wrong. To call Sadman's fifty "solid" I would need his strike rate to sit above the rest of the top order on that pitch, and the innings to have been played under the pressure of wickets falling. If either fails, the fifty is a count, not a story. That is an old habit of mine — I stopped asking why a number was wrong and started asking what it was measuring.

Now the ball that is the real event in this update. Warrican bowls left-arm orthodox, and the hardest bowler for a left-hander is the one whose ball lands in the rough and turns toward the stumps. The dangerous thing against left-arm spin is not the sweep; it is the premeditated sweep. When the ball is turning, bouncing low, and a ring is set on the leg side, the sweep is a priced risk: runs come, but if the line shifts an inch the pad is forward and the stumps are behind. Shanto's review failed, meaning the tracking showed the ball hitting the stumps — the classic pattern, delivered from inside the line and landing on middle. Anyone calling this a technical flaw is making the mistake I made nine years ago: collapsing a shot-selection decision into a cricket decision.

A review is a resource, not a shield. Two per innings, reset after eighty overs, written into the ICC playing conditions — the rule was deliberately built as an economy. A captain burning his review costs more than any other batter's review, because the men who come later cannot take the bet the captain could have. My working prior — a prior, not a measurement — is that batter-initiated reviews succeed roughly one time in four. If that rate holds in this series, Shanto's was a low-probability stake, and his side spent its only insurance at the moment of maximum need. I think of the May 2026 night in Hyderabad, when Mumbai made 129/8 and my ball-by-ball model gave Rising Pune Supergiant 68 per cent at the innings break. That week I rewrote my death-overs prior instead of defending the call, and published the calibration failure myself. The model did not break; it met a score it had never been taught to fear. Reviews behave the same way — the captain's bet was not wrong, it was taken in a situation where its cost exceeded its probability.

One thing needs clearing up. The original report describes Shanto's batting as "shaky" — an unsourced adjective, and I would call it mood rather than reporting. To label a captain demoralised when he is playing a spinner on a turning pitch and gets trapped lbw, I would want his last three innings ball by ball, his defence-to-attack ratio, and a count of his mis-hits in that session. I have none of it. What I have is a description of one wicket.

The easiest reading of this whole story is that Bangladesh are in trouble — 110 for three, captain out, review gone. My objection is not to the conclusion but to its arithmetic. Three wickets down by the fifth over after lunch is not abnormal in Test cricket, particularly when one spinner is bowling a long spell and the batters are under pressure to score. A score of 110 for three can be the median outcome of the conditions rather than evidence of team failure. The genuine concern is not the wicket but the review ledger — because the next time a batter is genuinely wronged by an umpire, Bangladesh will have no route to rescue him.

The headline chose "could not survive even with review", presenting the review as a shield that shattered. A review is not a shield, it is a bet, and losing a bet is a cost, not a failure. Blurring that distinction hands the reader the illusion that technology betrayed the batsman, when in fact the system did precisely what it was designed to do. The overpay was real; the correction was the part my spreadsheet had not priced — and here the overpay was not the ball but the review the captain spent without doing the sum.

Over the next session I will be watching three things: whether Warrican changes to over the wicket or repeats the same rough-line; whether Sadman rotates strike after his fifty or waits for boundaries; and how Bangladesh's No. 5 survives to the second new ball. I have no firm forecast, because backtest is not forecast — but one line deserves to be written down: the question is not what Bangladesh make from 110/3. It is how many overs they will have left when they next want a review.