Mohammad Ashraful Was Removed Four Days Before Mirpur. Bangladesh's Own Test Record Disagrees.

In the small hours of Saturday, 24 October 2026, a message landed in an official Bangladesh Cricket Board WhatsApp group. Two lines. Mohammad Ashraful is being relieved of his duties as national batting coach. His contribution is acknowledged. That same morning, Ashraful had run a session with the batters at the pre-series camp at Mirpur's Sher-e-Bangla National Stadium. A man who was in the nets at breakfast was out of a job by dinner — a sentence that belongs to the board's press release only in the sense that the release never once wrote it that way.

The first Test against West Indies begins at Mirpur on 28 October 2026. The second begins at Sylhet on 5 November 2026. The decision came four days out — the headline says four, one line inside the report says three. The discrepancy is small. It is also diagnostic: this is a wire item built from a statement, unedited, and the statement does not contain a reason. No named board official. No captain's quote. No head coach's explanation. No performance metric. One release, one WhatsApp message, and a coach in between.

Ashraful belongs to the generation that watched Bangladesh become a Test side — a century against Sri Lanka at seventeen, the captaincy soon after, then the long gap in which his international career stopped against a substantial anti-corruption sanction and never resumed at that level. That background is not in the report. It is public record, and I put it here because it will travel with the coaching appointment regardless: a man who has been put under scrutiny will have his removals scrutinised too.

He was appointed national batting coach in November 2026. The tenure is given as November 2026 to October 2026. In October 2026 he was removed. The release added one further line — he will be given another responsibility later. That line carried no title, no date, no reporting structure. The interim is a coach from the board's High Performance unit, with an explicit condition attached: until a permanent batting coach is appointed.

The conventional reading deserves a fair hearing first, because it is coherent. The board acted on performance. Bangladesh lost the T20 series 3-0 to Australia in June. The batting did not fire at the Asian Games. It did not fire at the Abu Dhabi tri-nation. The batting group has lacked consistency in recent months. A coach is accountable. That is the story, and if you come back to the headlines it is the only story there.

The problem is that it does not survive the tape. I rewound the tape until the crowd disappeared, and what was left was this: a board removed a batting coach who had almost everything except the Test record on his side.

Under his tenure Bangladesh played eight Tests and won five, drew one and lost two. That is 62.5 per cent. Converted to World Test Championship arithmetic — five wins at 12 points, one draw at 4, out of a maximum 96 — it lands at roughly 66.7 per cent. For Bangladesh that figure points upward, not downward. A board that removes a coach with five wins in eight Tests is conceding that Test outcomes were not the operative criterion. And if Test outcomes were not the criterion, then removing that coach four days before a Test series has no remaining cricket logic to stand on.

Now look at the negative evidence the decision rests on. The June T20 series. The Asian Games. The Abu Dhabi tri-nation. All three are short-format events. Not one average, not one strike rate, not one innings total has been disclosed from any of them. Judging a batting coach immediately before a Test series on T20 output is a category error — it is measuring weight with a ruler. Both produce a number; they do not produce the same meaning. Cricket analytics has repeatedly failed to show that a coaching method transfers intact between formats: Test batting is about leaving the ball, using the crease and occupying a session, while T20 batting is about run rate and risk arithmetic.

The same report offers a second number: 11 centuries in 34 international matches. It is presented as an achievement, and in the very next breath the batting is called inconsistent. Those two claims do not contradict each other, which is the entire point. Centuries measure peaks, not consistency. A batting unit can produce eleven hundreds and still fold regularly below 150 — that is the classic bimodal distribution, where both tails exist at once. And 34 international matches almost certainly pools Tests, ODIs and T20Is in unknown proportions; adding centuries across three formats produces decoration, not arithmetic. The correct diagnostic set would be the distribution of innings totals, the percentage of innings below 200, the frequency of collapses of three wickets for fewer than 30 runs, and average partnership length. Not one of those numbers has been published.

The one genuinely diagnostic datapoint is the 64 all out in Australia and the defeat inside two days. The red ball moved slowly; the story moved slower. It tells you how low this batting order's floor is. But it is one innings, on one tour, away from home — in a country where Bangladesh have never won a Test. Using a single away innings to settle a home appointment, while leaving out of the calculation the ground the match will actually be played on, is the most common error in evaluation design.

I have to file two caveats here, because the pause button caught what the live feed missed. First, the positive results cited in the report include 2-0 against Ireland and 2-0 against Pakistan. That Pakistan result corresponds to the away series of August–September 2026, which predates a tenure stated to begin in November 2026. Second, there is no recorded instance of Bangladesh winning a Test in Australia. When a results set collides with its own timeline, the journalist's job is not to reconcile it but to date-stamp it. What was knowable on the morning of 24 October 2026 was this: a coach was running a session. What became known that night was that he no longer had the job. Everything in between rests on a single source.

Now to the ground where the series begins. Mirpur's Sher-e-Bangla is widely read as the country's most spin-dominant, lowest-scoring Test surface; Sylhet generally offers better early batting conditions before taking spin. I learned to read a pitch like a mechanic reads a gearbox — the question is never how the surface looks, but which skill it rewards. At Mirpur that skill is specific: the sweep, the use of the crease, and the ability to bat ninety-plus minutes without reaching for a release shot. That skill sits inside the batting coach's remit.

Bangladesh's identified fragility is batting against spin in home Tests; Mirpur is the most spin-dominant venue in the country; and the specialist whose entire remit was that skill was removed four days before the assignment. An interim coach cannot install technique in three days; he can only triage — who bats where, who is barred from the sweep, who needs reminding to bat time. In a two-Test series a single collapsed session decides the outcome, and Mirpur is the ground where collapse is likeliest. The interim inherits maximum downside exposure with minimum preparation time.

The part of this episode that speaks louder than the cricket is the administrative sequence. A coach runs a session in the morning and is out by night. A board with a handover plan runs the session afterwards, or puts the replacement in place first. This is a governance signal, not a cricket signal. And the 'another responsibility later' line is the standard South Asian board formula: no title, no date, no reporting line. Where all three are missing, redeployment is the less likely reading and a sideways exit the more likely one.

Wankhede in winter taught me to trust the empty seats — a crowd tells you what people came to watch, and empty seats tell you why they stayed away. There is no crowd in this statement. No official to name, no captain standing up, no head coach explaining his own role. There is a release, and a WhatsApp message in which the word thank you is two words long.

Here is the turn where I had to withdraw my own first thesis. I sat down to write that this is the board which sacks Test coaches on T20 evidence — clean, sharp, quotable. Rewinding the tape, it did not hold. The 'another responsibility' line is not written for a performance dismissal; it is written for a relationship that ended and which the board does not wish to litigate in public. The likelier reading is that this was not a performance decision at all but part of a support-staff restructuring beneath the head coach, and that the board reached for performance vocabulary because it has no other public dictionary.

Having said that, the board may still be right on merit. If an internal review concluded that the coach's methods were not reaching the batting group, removal is defensible, and we cannot see that review. What is indefensible is the timing — the day, the absent handover, the night after the session. One fair counter-argument belongs on the record too: a home series against West Indies is the softest landing in the calendar, so if a change had to be made, this was the rational window. But such changes are made before a camp, not during one.

So what to watch at Mirpur on 28 October 2026. Three numbers. First, Bangladesh's first-innings total — past 300 and Ashraful's absence stays theoretical. Second, the count of sweeps played against spin and how often the batter actually reached the line of the ball; that is a coaching question in plain sight. Third, average partnership. An average below 40 means the group wobbled, and we will not even know whether it wobbled from his absence or from the conversation about it.

And then the question Sylhet settles by 5 November 2026: is a permanent batting coach named by then. If not, the 'another responsibility' sentence will have told its whole story. The tape will tell us whether the batting group missed him. The tape will never tell us why he went. That record sits with the board, and the board has not run it yet.