Bangladesh's 213/3 at Mirpur: The Fourth Wicket Missing From the Scorecard, and an Innings Stopped Twice

Play stopped for the second time in the day. Only four overs had been possible between the first stoppage and this one. Sher-e-Bangla National Cricket Stadium, Mirpur — 74 overs, 213 runs, three wickets, and a batter unbeaten on 99 who was stopped by the light, not by ball or bat.

I went back to the tape before I trusted the consensus. The scorecard says three wickets have fallen. The scorecard does not say that a fourth specialist batter has left the field — Towhid Hridoy, retired hurt on 42. So four top-order batters have been used for three wickets. That difference is the real shape of an innings, and it is nowhere near what the scoreboard prints.

I changed how I read scorecards some years ago. I used to look at runs and wickets first as well. Now I check how many overs were actually possible, in what condition each batter had to bat, and who was not on the field at all. This Mirpur day belongs to that same category of story: an innings carrying more weight than its card shows, and a match whose biggest controlling variable is weather, not cricket.

One thing needs saying clearly, because it has become normal to watch Test cricket through a limited-overs lens: the toss result is not available here, the day number is not stated, and Bangladesh have not bowled a single over yet. Filling missing information with inference is the easiest mistake in this trade. So I will write what is on the tape, and where I am inferring, I will say so.

Mirpur's surface did not behave the way the home side would have wanted. In the first session the seamers found movement — Jayden Seales, Shamar Joseph, Justin Greaves. That is the trio that lives on new-ball movement away from the bat, and against a left-hander's outside edge that line is the most expensive one in the game. Tanzid Hasan Tamim fell for seven at 9/1, driving at a ball leaving him, edging to slip. That is not coincidence; it is a technical signature that Test cricket writes over and over.

The first session ended 96/2. If that came in around 28–30 overs, the rate was 3.2 to 3.4. After lunch the tape changes. From 117/1 to 213/3 — only two wickets fell in that stretch while 96 runs came. The whole innings: 213 in 74 overs, 2.88 an over. That is the number I put above 213. The recent global Test norm sits around 3.1 to 3.3. A rate of 2.88 means this was not an easy batting surface, and this total is a survival platform, not dominance.

There is more information in 2.88 than in 213. On a pitch where the ball moves in the first session and turns from the second onwards, batting under three an over is a deliberate choice — the batter reduced risk, the bowlers bought overs. That strategy works if you reach 350. It puts you in trouble if you fold for 280, because then the opposition spinner gets, in the fourth innings, the very surface he has been bowling on all match.

Sadman Islam's innings has to be opened up separately, because 99 not out makes people assume it was fast. It was not. The fifty came off 95 balls — a strike rate of 52.6. Five fours in 99 runs means only 20 runs came in boundaries. Asian Test openers typically take 40 to 55 percent of their runs in boundaries. Sadman sits at 20 percent. That is the character of the knock: low boundary dependency, singles and twos, endurance.

That profile is safe, and that is precisely its risk. When you score 99 with only five fours, your score climbs slowly and your concentration is tested for a very long time. One lapse does not just cost you a hundred — it costs the innings its tempo. A boundary hitter takes risk to make runs; a batter like Sadman avoids risk to make runs, and avoidance is also a skill with a ceiling.

One more thing worth logging: this is his tenth Test fifty, and the fourth against West Indies. Ten fifties is now a meaningful sample. A question follows that I cannot answer — how many hundreds have come out of those ten? If the ratio is low, then "99 not out" should be read as a known pattern rather than a coincidence. I am not asserting that; I am saying it is the question that should be asked next.

Captain Najmul Hossain Shanto's innings was described in the report as "shaky". Sixteen off 42, a strike rate of 38.1. This is not merely a form issue; it is a decision issue. Sweeping a left-arm spinner on a turning Mirpur pitch, on 16 off 42, is a shot against the grain of the surface. Ball-tracking showed the ball hitting middle-leg stump. Shanto's dismissal is a tactics story, not a luck story. What was required of the captain was to leave the ball and get his pad forward; what happened was a sweep.

A pause is needed here, because the fielding side reviewed this dismissal and the decision was overturned. This is not the DRS argument we have grown used to. Ball-tracking placed the ball on middle-leg stump — clearly inside the zone, outside the margin of error. Had the projection been "clipping", the on-field not out would have stood. Here a genuine error was corrected. The reversal rate is the only opinion that survives the audit, and in this innings the reversal rate is 100 percent: one review, one correction, no controversy.

In 2026, during the IPL in the UAE, I sat on review graphics for 60 matches and logged 38 player reviews. That work taught me something football's VAR never did: in cricket a challenge costs something. The review West Indies took here succeeded, so they lost nothing. That is the correct instinct — every call is a threshold problem wearing a story, and West Indies read the threshold correctly.

Mominul Haque's dismissal is the innings' clearest unforced error. Twenty-eight off 51, a strike rate of 54.9. He and Sadman were together at 68/2, a 59-run stand had formed, and the report's word for both of them was "comfortable". Then Mominul stepped out and mistimed a loft to mid-off. 110/3. That was not the bowler's achievement; it was patience breaking. When your largest partnership ends that way, the cost is bigger than the runs: you lose the platform on which a 350 was supposed to be built.

And here the scorecard starts to lie. From 110/3 to 213/3, 103 runs were added. Subtract Liton Das's 10 not out and roughly 93 belong to the Sadman–Hridoy stand — a stand that ended not by a wicket but by retirement. A partnership worth about 93 runs does not appear on the scorecard at all. When I ran that calculation, it became clear that the middle order played better than any record of it survives.

Towhid Hridoy's 42 is the single largest unknown in this match. What the injury is, how it happened, when the scan is due — none of it is disclosed. On the law: retired hurt (Law 25.4) means the innings is suspended, not ended. He may resume at the fall of a wicket, with umpire approval. In practice Bangladesh's card may keep showing "three down" while four specialist batters have already been used — and that gap reshapes the plan for the second innings.

Here is the threshold I would set. If Hridoy does not bat in the second innings, I will not model Bangladesh's second innings without confirmation of his availability. The No. 4 slot at Mirpur against spin is exactly where Mushfiqur Rahim's absence is most expensive — and Mushfiqur is not in this XI, with no stated reason. Injury, rest, rotation or selection: the structural effect is identical.

Look at West Indies' bowling shape. New ball from Seales, Joseph through the middle, Greaves in the cordon, then Warrican. Roston Chase's involvement in the review indicates he is in the XI, stationed in the cordon or inner ring — meaning West Indies also read the pitch as a turner and picked pace plus two spin options. This side is bowling to a plan, not to a scoreboard.

The defining technical contest of this match is not Seales versus Sadman with the new ball; it is Warrican versus a right-handed middle order. On a turning Mirpur surface, a left-arm orthodox bowler holding a stump-to-stump line and extracting turn is the cheapest weapon against a right-hand-heavy order. Warrican dismissed Shanto exactly that way. In the second innings he will carry the same overs, and he will decide whether Bangladesh's total is par or below it.

Now the matter that shaped the whole day and that nobody controlled. Play stopped twice, and only four overs were possible between the stoppages. One stoppage can be coincidence; a second within four overs says the light was marginal and fluctuating, not a single cloud. Dhaka's winter haze is a plausible cause, but it is not stated anywhere, so I keep it inside the inference boundary.

A technical point that is routinely muddled: DLS does not apply to Tests. In limited-overs cricket rain or light triggers a recalculation of the target; in Tests lost time is recovered through extended sessions, and if time runs short, the default outcome is a draw. Seventy-four overs means roughly 16 short of the 90-over requirement. Because the cause is light rather than the fielding side's conduct, no over-rate sanction follows — but those 16 overs must be recovered in later sessions, and the recovery will be paid for in bowlers' workload.

The controlling variable of this Test is weather, not cricket. I priced the shutdown before I let myself mourn it. Here the price is plain: in a home Test Bangladesh must bowl West Indies out twice to win. Every lost session lowers that probability. In a match where three wickets fell in 74 overs, forcing a result in four days is already a tight equation; if the light keeps this pace, the Test drifts towards a draw, and then the umpires' light management becomes the story of the match.

I will be direct about the line I would draw. A decision on light is the umpires' discretion, and discretion is not a fault — but when play stops again within four overs, the question is not whether a law was broken; the question is whether the same standard will apply in the second innings. Consistency of application is what trust rests on, and it is the one thing that can be checked on the tape.

Now the part where I disagree with the room.

The day's big story was framed as Sadman missing a hundred by one run. That is true, and it is romantic. But if I identify this day by two facts, they are: a batter retiring hurt, and the sessions being cut repeatedly. A player stranded on 99 is the third fact, not the first. The headline is doing narrative work the cricket has not yet earned. Treating an unfinished innings as a completed landmark, while filing the day's structural damage in brackets, is a newsroom habit, not analysis.

My second disagreement concerns home advantage. Mirpur is regarded as Bangladesh's most spin-favourable venue and historically their most realistic route to a Test win. This time the surface helped seam first and spin later. That means the host lost its biggest weapon in the first session and reinforced the visitors' strength — new-ball seam. It is the worst of both worlds: a claim of home advantage on a pitch that suits the touring attack.

The third point is usually said softly. It is simple: West Indies have won at this ground before. On the 2026 tour they won both Tests in Bangladesh, Mirpur included. That does not mean they will win this one; it means the assumption of a routine home win has nothing behind it. Between mid-tier Test sides this pairing has produced result-heavy, short-form-length Tests in Asia rather than attritional draws. So the first-innings total is the decisive variable, and it is unfinished.

The fourth point I do not take lightly. The report used the word "shaky" for the captain, in the context of 16 off 42. Bengali match reporting does not apply that word to a captain without cause. It is a pressure signal, and if this innings does not convert, questions about Shanto's form and his place will follow. I am calling it a signal, not a prediction.

The fifth thing that strikes me most on the tape: the one review in this innings was clean. I am logging it separately because our habit is to discuss DRS only when there is a controversy. There was none here — the ball was hitting middle-leg stump, the decision was overturned, and the innings moved from 68/2 to 110/3. The system did what it is designed to do. A correct correction deserves recording too, or the audit becomes one-sided.

Now an inference I will label as an inference: play stopping at Mirpur for light is not new. The word "again" in the headline comes from that experience. If the ground is floodlit and the match starts in the morning, this pattern will repeat in a hazy month. I do not have the start time or the moment the floodlights came on — so I hold this as probability, not conclusion.

One thing outside the field that looks unrelated but leaves a mark: stopped sessions do not only eat overs, they eat broadcast inventory. Every stoppage removes live minutes from a rights-holder's schedule. In a market where Test cricket already struggles for advertising yield, repeated stoppages are an economic cost, not a neutral event. That is not a claim about any deal in this match; it is the industry's general structure.

If the series is short — one or two Tests — this first match matters many times over, and a light-affected draw changes the trophy arithmetic. Neither the series length nor the WTC status is available to me, so I keep that inference inside its boundary as well.

As for West Indies' batting, it has not been tested at all. Every assessment of them rests entirely on their bowling. How their top order stands against Bangladesh's spin on a fourth-innings surface is the least examined question of this Test.

So how do I read this day? On a Mirpur surface where the visiting seamers were helped with the new ball and the visiting left-arm spinner thereafter, Bangladesh's 213/3 stands almost entirely on Sadman Islam's patient 99 not out. The innings' true shape is worse than the card, because the fourth specialist batter is retired hurt and the fifth was not in the XI. But the decisive variable of this Test is not a player; it is the light. Two stoppages with four overs between them — lost time will decide whether a result is possible here at all.

My frame for what to watch next is clear. First, Sadman resuming: on 99, after an interruption, against a turning ball, with the second new ball not far away. The chance is immediate and binary — hundred or not. Second, Hridoy's status: if he does not bat again, both the second-innings balance and the fielding plan change. Third, Warrican's overs and turn: if he takes wickets in the second innings, Bangladesh's total will prove par or below. Fourth, the second new ball from Seales and Joseph after over 80: that decides whether this innings passes 300 or stops near 280. And fifth, the umpires' light management: a third stoppage on the same day raises the draw probability and fixes the post-match argument.

I will not close by writing that Bangladesh are in a strong or weak position. I will write that the first question of this Test is not who wins, but whether five full days of cricket are available here. On a day when three wickets fell in 74 overs and light stopped play twice, assuming the result is in the players' hands is forming an opinion before the audit. Frame by frame, the room got quieter — and the story got clearer: this match is a long way from its most settled turn, and Sadman's hundred is the shortest route there, not the longest.