Three Wickets for 24, Then 172 in 34 Overs: Bangladesh Lost the Chase in the Wicket Column, Not the Run Rate

Twenty-four runs, three wickets down. Before Taskin Ahmed had even finished his spell, the boy sitting next to me on a Mymensingh rooftop said, 'They'll be all out for fifty today.' I said nothing. There was wind on the roof, the smeared noise of the city below, and on the screen three Zimbabwe wickets already fallen. My habit is not to trust the scoreline but to look for the thing still invisible behind it. That afternoon the invisible thing was Zimbabwe's middle order.

Because at the end of the day Zimbabwe's name had 271 beside it. A side that loses three wickets for 24 runs and still reaches 271 has done something specific: it has batted out roughly forty-six overs and taken 247 runs off everything Bangladesh had left. That 247 is where the match actually lived, and it never made a Bangladeshi headline, because the headline was Bangladesh's 172 all out in the 34th over.

The report is clear on the skeleton. Bangladesh, chasing 272, were bowled out for 172 in the 34th over. Taskin Ahmed removed Zimbabwe's first three batters inside 24 runs. The opening stand broke at 47; two wickets fell inside the powerplay; Najmul Hossain Shanto went early. After that no batter offered resistance — the report's own words are that no other batter showed fight. Towhid Hridoy, standing in as captain in Liton Das's absence, said afterwards that the pitch was quite good for batting, that his side could not do well in the middle overs, and that some foolish mistakes were made.

An honest inventory first, because the worst dishonesty in data writing is pretending to know what the source does not say. The report carries no venue — Dhaka, Chattogram, Harare or Bulawayo, none of it. No toss, no series position, no word on DLS, no individual bowling figures, no score for Hridoy himself. The format is not stated either; a 272 target, an all-out in 34 overs and the existence of a powerplay together make ODI the reasonable inference, and inference is what it stays.

What can be calculated is the most useful finding here. 272 in 50 overs is 5.44 an over. Bangladesh's 172 in 34 overs is 5.06. If they were somewhere near 52 for 2 at the ten-over mark — consistent with a 47-run opening stand broken plus two powerplay wickets — then the remaining 24 overs produced roughly 120 runs at about five an over. The required rate never left their reach. The wicket column did. Eight of Bangladesh's ten wickets fell in the middle overs. The chase did not die of scoring speed. It died of partnerships.

That single sentence inverts the narrative, because Hridoy's own language is not the language of run rate either. In the middle overs Bangladesh actually scored. What they could not do was keep two batters at the crease.

From twelve years of watching this side, the pattern is familiar. Bangladesh's chases break in the same place every time, and it is not temperament — it is strike rotation. When the field spreads and five or six fielders sit inside the ring, a chase moves on singles and twos. Bangladesh's batting goes looking for fours instead, because the ones and twos are not a trained habit. Four dot balls an over do not immediately damage the scoreboard, but they accumulate pressure, pressure produces wickets, and wickets turn a modest required rate into a wall. A 172 all out in 34 overs is precisely that: the realisation arriving late that 5.44 was never reachable, because the man to finish the innings was never there.

And this is where Taskin's spell becomes a small tragedy. Three wickets for 24 with the new ball is match-winning shape in the modern ODI. Zimbabwe still made 271, meaning the rest of the attack and the fielding conceded 247 across the remaining overs. The most valuable individual performance of this match came from the losing side, and that is the most unjust part of the result. The report praises the bowlers, which is half true. The other half is that Bangladesh could not press home the advantage. A spell creates pressure; a system sustains it.

One thing nobody has written: on the same pitch, in the same light, Zimbabwe went from 24 for 3 to 271 while Bangladesh went from a chase of 272 to 172 all out. One side absorbed a collapse, the other could not. That is not luck. That is the difference between a middle order with batters who occupy the crease for two hours and a middle order that restarts from zero every time pressure arrives.

Hridoy's three remarks, read together, form a pattern. He said responsibility should have been taken. He said the middle overs went badly. He said foolish mistakes were made. All three are correct, and all three close off the pitch as an excuse. A captain's two easiest refuges after a defeat are the surface and bad luck; he took neither. For a stand-in captain that is unusually good media management.

Which is also the problem. Because he has already accepted the batting failure publicly, the press no longer has to do that work, and the conversation will stop at 'they played badly' rather than reaching the structure of the batting unit. That is the real cost.

Liton Das's absence belongs at the centre of this and the report steps around it. No cause is given — injury, rest, personal reasons, unknown. The uncertainty is enormous because it supports two entirely different stories. If Liton was rested, this is a low-stakes bilateral, a rotated XI, and calling it a crisis is foolish. If Liton is injured, Bangladesh entered a chase without their captain and their opening anchor and then lost the middle order on top of it. This piece claims neither, because the source supports neither.

The load of acting captaincy is real and uncounted. In Bangladesh the word 'acting' usually does not mean rotation; it usually means the vice-captain is also unavailable. The leadership chain is thin. The man handed the job carries three tasks at once — running the side, facing the media, and protecting his own batting. Nobody accounts for the third because it has no column on the scorecard, and Hridoy's own score is not in the report. This match gives no basis for judging him as a captain.

One more detail gets buried. Hridoy raised reviews — 'sometimes you also have to trust the bowlers and the keeper', and 'we will definitely talk about it'. That is not an umpiring complaint; it is an internal decision-making issue. ODI reviews are finite, and a wasted one is paid for later. A captain raising it in a press conference means there was at least one disagreement between him and the bowling unit during the match. He softened the line immediately, which shows he knows it is sensitive. Small fractures of this kind have grown large in South Asian dressing rooms before.

Now the place where collective memory is about to get this wrong.

The first error is the phrase 'no other batter showed fight'. That is the reporter's characterisation, not a scorecard fact. It sits comfortably with 172 all out, but 'fight' is a judgement about attitude, and attitude cannot be proved by a scorecard. A batter making 12 off 30 can be a failure of will or a failure of strike rotation; the two look identical and are not. In Bangladesh's case it is almost always the second.

The second error is the comfort of 'the target was chaseable'. It is true and incomplete. 272 is chaseable on a good deck in the modern game. The useful question is: chaseable by whom? For a batting unit that eats four or five dot balls an over in the middle phase, 272 is not a target, it is a trap. The target was easy; the route was hard; and nothing about the route was imposed from outside.

The third error is the largest. We will label this a batting failure and move on, forgetting that the bowling success is what concealed the real problem. Three wickets for 24 in the opening overs was Bangladesh's biggest opportunity of the match. Converting it needed pressure from the other end, an attacking spin quota, and one catch held. No spinner is named in the report, no dropped catch mentioned. What is there is 247. That number holds the story that will return in the next series, when Taskin may not take three for 24 again — and then who stands up?

I once climbed to a Mymensingh rooftop to watch champions fall, and heard the city exhale. That rooftop taught me that collapse is not an ending; it is a crowd learning to breathe again. This match is no collapse. It is an accounting exercise in which the runs were right and the wickets were wrong. Silence has a sound when twenty thousand seats remember what they used to hold; in Bangladesh's middle order those seats have been empty for a long time and nobody has been counting them.

The next match will settle what this was. Same XI, same batting order, another middle-overs collapse — that is structure, not form, and structure is not repaired by speeches but by strike-rotation work and by finding a finisher. If Liton returns and the side wins, the conversation disappears, and that will be the greatest danger of all, because the problem will still be there, just invisible on the scoreboard again.

I want to see one thing next time. Not eight wickets down by the 34th over, and someone playing a responsible innings — fifty off fifty, no fours needed, just standing at both ends. That innings would be the real answer to this defeat, and it will take a player who refuses to let Taskin's three for 24 go to waste.