The 170 Ledger at Mirpur: Shanto Blamed the Bowlers, but the Batting Wrote the Number

Bangladesh took two wickets in the fourth innings at Mirpur. Two. The target was 170, ten wickets were available, and the match finished without a single passage of genuine theatre. The reader has to do the subtraction, because the next morning's headlines did not contain the number — two wickets in the fourth innings means West Indies won by eight wickets. An eight-wicket margin in a low-scoring Test is not a narrow defeat; it is a defeat in which the opposition never once felt real pressure.

After the match, Najmul Hossain Shanto said the bowlers could not hold their length, that the line and length was a bit erratic, and that 170 was a defendable total. Every outlet ran that as the headline: "Shanto blames the bowlers." Cricket journalism runs on an old rule — what the captain says becomes the story, and what the scorecard says becomes the footnote. Here, the two were pointing in different directions. Count what the headline left out before you form the hot take.

The Mirpur context, and its unstated condition

The Sher-e-Bangla Stadium in a Dhaka winter is a known quantity: low bounce, slow pace, and spin assistance of exactly the kind a tired fourth-innings surface offers. Bangladesh's home Test formula has been unchanged for a decade — an under-par first-innings total, a second-innings grind, then a spin squeeze. That blueprint carries one unstated condition: the pitch has to deteriorate innings by innings.

A target of 170 is the output of that blueprint — not inadequate, merely insufficient. On a slow Asian surface in the fourth innings, 170 is competitive but not comfortable; only above 200 do the bowlers earn the right to make a mistake. Bangladesh's own framing contains the buried admission that 170 "could have been defended" — and when a captain calls a target defendable, he is quietly also saying it was short. That is not self-defence, it is a rhetorical contradiction, and it sits at the centre of the entire case.

What Shanto did in the press conference was technically sound. The length diagnosis was correct — on a slow turning track, the wicket-taking ball is slightly fuller and slightly wider, and an erratic length lets batters play comfortably off the back foot. The failure was in allocation. In one breath he blamed "the bowlers" as an undifferentiated collective, named no individual, and also brushed the batting with the line that "we perhaps scored a few too few runs." That sentence is the real story of the press conference, and it is the story that never made the headline.

Whether this match sat inside the World Test Championship cycle is not clear from the available sourcing, and I will not build a case on that inference. What is clear is that a home Test defeat always costs more than the scoreboard shows, because Bangladesh bank both points and confidence at home.

The full arithmetic of two wickets

Two wickets in the fourth innings does not mean the bowlers were bad — it means the match never reached a state where a single over could turn it. Defending 170, the minimum bowling requirement is six to eight wickets, even in a losing cause. Two wickets is the signature of a chase in which no partnership was ever broken, no pressure was sustained, and the captain had no weapon that could suddenly crack a dying surface.

But the argument should not stop there. The batting set the price and the bowling paid the bill. That arithmetic has repeated itself across many seasons of my watching: the lower the target, the less margin the bowling gets. Had Bangladesh crossed 200 in the second innings, two wickets would still have been a two-wicket story — but then the debate would be about how much the pitch helped. At 170, that debate closes.

The accountability asymmetry

Shanto's statement was politically clean. He pre-empted three lines of criticism — credit to the opposition, the umpiring, and the insistence that none of it is an excuse. A player who has three doors of defence ready usually knows which way the wind is blowing.

The substantive point is that he used "the bowlers" as a single undivided unit and never placed any individual inside the accountability frame. In elite team management, that is one of two things: deliberate protection of a young, rotating attack, or avoidance of a confrontation whose consequences would land on his own captaincy. Neither option solves the problem the scorecard described.

London taught me to read the crowd, not just the chant. Five umpire's calls were recorded in this match and all five went against Bangladesh. That number is striking and deserves discussion. But an umpire's call is not proof of an umpiring error — it is a defined technology margin, designed precisely so that the on-field decision survives when ball-tracking falls inside its area of uncertainty.

The more interesting question sits behind it: an umpire's call only exists if you challenged. Five of them means Bangladesh spent review capital and lost it. In a defence of 170, a review is the net you throw under the one delivery that might break a partnership. Empty the net, and the next appeal rests on the umpire — and an argument resting on the umpire never wins a match. This is the same old story that video review has not changed anywhere in the world: technology does not end controversy, it moves it off the field and into the review room and the grey zones of the rulebook.

The real contradiction: the surface was defended, the bowlers were dropped

The quietest thing Shanto said was what he did not say. He did not complain about the pitch anywhere. Calling 170 defendable implicitly also asserts that the surface was fine, the conditions were fair, and no excuse exists. In a home Test, control over pitch preparation sits with the host board, and for a home captain that choice is never easy — blaming the pitch is questioning your own preparation.

The remaining option is this: when the pitch is protected, the blame is parked with the bowlers. This is an incentive structure, not a character flaw. The captain had two available narratives — "the pitch did not help" or "the bowlers could not hold length." The first was institutionally expensive. So the second one sold at the press conference.

Credit to West Indies, and an outdated template

Chasing 170 with eight wickets in hand on a turning surface in the fourth innings is not a small achievement. The notion that Caribbean batters collapse against spin in Asia is now an old template. In Dhaka in 2026, West Indies won a similarly low-scoring, spin-dominated Test. I am drawing that historical example from the general cricket record, not from this match's scorecard, and it should be verified before being cited externally. The signal, though, is clear: West Indies' Test rebuild is breaking the very template on which their weakness was assumed.

A single-source caveat that would be dishonest to hide

This entire report rests on one post-match press conference, and in the available material every information point is logged with "Source: None." Neither outlet nor byline is specified. Every quote is therefore single-source and unverified. Shanto's own batting figures, the names of the bowlers, who initiated which review — none of it is confirmed. I have built the argument on the structure of the match and its arithmetic, not on quotes alone. A reader who misses that distinction will mistake a captain's press conference for a team's truth.

Where I could be wrong

The first point is the cleanest: one Test and one press conference cannot establish a bowling unit's decline. Two wickets is a fact about a match, not a trend. By my own standard, the sample is dangerously thin.

The second point is more uncomfortable. If the Mirpur fourth-innings surface had died completely — if no length at all was doing anything — then blaming length is unjust. On 19 December 2026 in Adelaide I fought exactly this argument: India were bowled out for 36, Hazlewood took 5/8 and Cummins 4/21, and everyone wrote that the team had surrendered. I said that night that it was not a failure of character but a scheduling problem — the third session of a day-night Test. Apply the same logic in reverse: sometimes conditions and surfaces write the number, not the players. If the Mirpur pitch had flattened, the real fault belongs to the batting in the first two innings, and the captain blamed the wrong group.

A third possibility: he did name individuals and the reporting compressed them into a collective. In a single-source, unverified press conference, that is entirely possible. And a fourth point, which is not an excuse but an outcome: West Indies' batters genuinely played well. An opposition playing well against a 170 defence is not forgiveness, it is the result.

None of that moves one thing. A target of 170 on your own surface is a self-imposed constraint, and the people who set it are the batters. Length deserves the debate, but it is the second debate.

What to watch next

The scorecard was not wrong; the commentary was. The next Test's playing XI will settle this argument. If Bangladesh bring in a seamer or a variation bowler for a spinner, the diagnosis was length and plan. If the change comes in the batting order, the captain was misreading his own ledger. The larger lesson is that the unit of analysis should be the incentive structure — selection, pitch preparation, review allocation — not an individual's name. The pattern is boring until it predicts the next overreaction.

The question is not whether Shanto told the truth. The question is this — with 170 on the board and ten wickets in hand, how much room for error did he actually give his fastest bowlers?