The 170 Arithmetic at Mirpur: Shanto's Diagnosis Is Right, His Address Is Wrong

Two numbers sat on the table at the Sher-e-Bangla press conference: 170 and 2. The first was the target Bangladesh set in the fourth innings; the second was the number of wickets it took defending it. The match was over. Najmul Hossain Shanto picked up the microphone, and his first line was about length — we could not hold the length, it was a bit erratic. Then came the sentence every outlet headlined the next morning: 170 could have been defended. And after it, a half-finished condition — even if we lost, had we taken seven or eight wickets, it would have been a different conversation.

I am not writing a post-mortem of a captain's press conference. I am auditing the arithmetic buried under the statement. Whenever a dispute lands on my desk, my habit is the same: I go back to the monitor to see what the referee actually saw. Here the monitor was the scorecard, and the scorecard pointed somewhere other than the captain did.

Context: this is Test cricket, and Mirpur's soil writes its own rules

Settle the format first, because every conclusion in this report sits inside Test logic and cannot be dragged into ODI or T20 reasoning. Five days, a fourth-innings chase, a 170 target — that combination is itself an argument. On a fourth-innings Asian surface, 170 is what the trade calls competitive but below par; at 200-plus a bowling captain can breathe, at 170 he does arithmetic every over.

The Mirpur surface has a known character: low bounce, slow pace, spin dominance, and in the local winter, haze and bad light. On a deck like that, wickets do not fall from magic; they fall from discipline. That is why Shanto's length diagnosis is not technically wrong. On a slow, low pitch the wicket-taking ball is slightly fuller and slightly wider, and once the length goes erratic the batter plays off the back foot, because he keeps receiving the ball inside his shot arc.

Bangladesh's home Test formula has been unchanged for a decade: an under-par first innings, a grinding second, then a spin squeeze on a fourth-innings surface. That formula carries one condition — the pitch must deteriorate. The day the surface does not break up, the formula inverts, and the home side ends up playing against its own plan.

One transparency note is essential. This report rests on a post-match press conference, and the available material marks no source for any information point, no outlet, no byline. Every quote is therefore single-source and unverified. I am presenting it so the reader can separate what the captain said from what the scorecard says. Where the scorecard is missing, I will call an inference an inference and a conclusion a conclusion.

Core analysis: one innings, four angles

Angle one — the arithmetic. In the fourth innings the hosts took two wickets. A Test innings has ten. Two gone, eight left: West Indies completed the chase eight wickets down. In a low-scoring Test that is a heavy margin, and it is the kind of margin that marginal DRS calls cannot explain, because in an innings where the chasing side was never genuinely pressed, umpiring detail becomes an excuse rather than a cause. The captain's own hedge — had we taken seven or eight wickets — is an implicit admission that the defeat sat in bowling structure, not in luck.

Angle two — the precondition. The 170 did not fall from the sky. It was the output of the second innings, and the captain himself left open the possibility that the runs were too few. A fourth-innings Test target is drawn on the bank balance of the first two innings. Set 170 and you are asking your bowlers for near-perfection: no partnership allowed, a question asked every over. Set 250 and the bowler is allowed an error. Bangladesh handed its attack a job with no margin and then held it responsible for the job. The technical criticism is sound; the address is wrong.

Angle three — review capital. Here the litigation begins. Five umpire's calls were recorded, all against Bangladesh. Five in a single Test is an unusually high count — normally one to three. But the way to read that number is not to hunt a conspiracy. Umpire's call is a defined technology margin, not a proven error. When ball-tracking finds the ball inside the margin around the stumps, it preserves the on-field decision, and the mechanism was working exactly as designed.

Underneath that sits a procedural truth. Umpire's call only exists when a team challenges. Five umpire's calls means Bangladesh spent review capital and lost it. In a 170 defence, the review is the safety net kept for the one marginal decision that could break the chase. Burn that net early and you are left with arguments on every fine ball, not with decisions. A machine drew the line, but we drew the argument.

I should state plainly that the per-innings review quota in force is not in the available material and must be checked against the ICC Test playing conditions applicable at the time of the match. A number is not assumed, it is retrieved. The clause was on page nine, and it shaped the innings.

Angle four — the address of accountability. The captain criticised the bowlers and named none of them. He chose the language of the collective. From a management seat that reads two ways: deliberate protection of a young, rotating attack, or avoidance of a confrontation with a senior seamer. Neither motive is written in the statement, so it is inference, not accusation. But one thing is clear — when a captain speaks of 'the bowlers' as an undivided group, the next Test selection sheet usually carries one changed name.

A second detail sits in the same frame. One line in the statement refers to the wicket at the start that we did not get. Had that been a DRS overturn, the captain would have folded it into the umpiring paragraph. He kept it separate, which usually means a chance missed or a catch spilled. Small detail, larger signal: discipline inside the bowling unit was not confined to length; it extended to the fielding sync around it.

Contrarian angle: 'the decisions went against us' is the cheapest alibi

Here is the line that got me called naive on three platforms before. If you ask me what caused the Mirpur defeat, the answer is not umpiring. Five umpire's calls are startling, but they are a technology margin inside which the on-field call stands. On a pitch where the ball is grazing the stumps, five such outcomes also describe the surface — it tells you how low the ball was staying. It does not tell you that anyone wronged Bangladesh.

The genuinely counter-intuitive point is this: a home defeat is more serious than an away defeat, because it targets your only competitive edge. Bangladesh's Test identity rests on spin and home conditions. Losing at Mirpur means the foundation of that identity has a crack. In the captain's language, 'it could have been defended' is not a weakness but a defence mechanism — an attempt to tell us the error was small. Two wickets while defending 170 is not a small error, especially when the batting handed over only half its share.

Which brings the question I ask at the end of every rules analysis: who does this rule actually hurt? The umpire's-call mechanism hurts the team that treats reviews as chips to be pushed in, and the captain who has no clear protocol for who calls for one — captain, keeper or bowler. That protocol was not visible in this Test. When five out of five go against you, the question is not what the eye saw. The question is who told the eye when to look. Before I judge the call, I want to know who trained the eye.

Takeaway: the next selection sheet and the next review protocol

Watch three things in the next Test. First, the length map — does the attack hold the third-to-fourth-stump channel in the second innings, or slide into the back-foot arc. Second, the ownership of reviews — does one designated voice decide, or do four hands go up every ball. Third, the batting bank balance — until the definition of 170 changes in the second innings, the search for bowling culprits will keep repeating itself.

For West Indies, this win is solid evidence in low-scoring Asian Tests; completing a fourth-innings chase eight wickets down says this generation does not fold against spin. For Bangladesh, the question is not who was blamed yesterday. It is whether, the next time the captain sits at that table, the scorecard backs his sentence. For now, the line that most deserves scrutiny is the one least quoted: even if we lost, had we taken seven or eight wickets.