Two Wickets, Eleven Overs: I Opened the Ledger on Ebadot's Light Workload

In Abu Dhabi, at the close of Day 2, I opened the scorebook and one entry kept catching my eye. Bangladesh's leading wicket-taker in this innings — two — was Ebadot Hossain. He had bowled eleven overs. Fewer than every other bowler bar Naeem Hasan. In more than fifty years of reading cricket's ledgers, one habit never leaves me: the scorecard never tells the whole truth; it only records debts and credits. Today's entry reads: high output, low workload. The question is about process, not result.

This is a Test, Day 2. Afghanistan, four down, still 135 behind. In Test arithmetic, six wickets in hand makes 135 a manageable deficit — a reading that fits the grain of the game. But the real story sits in the bowling workload, not the scoreline.

The match is being played in Abu Dhabi, in the United Arab Emirates, which is effectively Afghanistan's home. The venue is neutral; the familiarity is not. The pitch is slow, and it is expected to assist spin as the match wears on — the strongest internal signal of the fixture. The team's plan leans accordingly on spin; the word is that the spinners will decide Day 3.

Add one more condition — extreme heat. At this time of year, Abu Dhabi is brutal for a fast bowler. Former spin coach Mushtaq Ahmed said it plainly: continuous fast bowling in this heat is hard, so short spells and adequate hydration are the keys to lasting a five-day match. Any workload discussion has to sit on top of that environmental reality.

Now to the core sum. Ebadot took two wickets in eleven overs — roughly one wicket every five and a half overs. On that rate he was Bangladesh's most incisive bowler in the innings. Yet he was used less than anyone. That gap between output and workload is today's real puzzle.

Listen carefully to Mushtaq Ahmed's explanation: he is not certain; Ebadot may not be fully fit, or he may have been underbowled relative to plan. Notice that both are guesses, neither a confirmed fact. A spin coach commenting on a pace bowler's workload is itself a small signal: the decision may not belong to the bowler alone, but to the wider coaching group, or to the captain inside the ropes.

Here is where I ask for caution. Two wickets and fewer overs are related, but relation is not cause. Correlation is not causation. It is easy to assume Ebadot was held back through poor form or neglect; in reality at least three explanations are equally possible. The first is fitness — but that remains inference. The second is plan — a spin-centric strategy naturally reduces a seamer's overs. The third is heat — long spells are risky in this temperature, and Ebadot is historically an expensive yet wicket-taking quick; give such a bowler a long spell in the heat and both runs and fatigue climb.

My experience says decisions like this rarely have a single cause. After the 2026 Russia World Cup semi-final between England and Croatia, I learned that visible effort and true control are never the same thing. Croatia's 14.3 kilometres and Bangladesh's eleven overs are different games, but the lesson is one: what catches the eye is not always the real story. The data's job is to correct the eye, and the ledger's job is to record the correction.

Watch one more thing — Naeem Hasan also bowled fewer overs than anyone. That parallel under-use may not be coincidence; the side may be deliberately hoarding spin for Day 3. In that case Ebadot's light load is no accident but part of a plan. Whether the plan fails depends on how much the pitch turns.

The risks are plain. The biggest is player welfare: a pace bowler of doubtful fitness in extreme heat is a familiar precursor to heat-related and soft-tissue injury. The second is tactical: if Ebadot is genuinely being held back, then once the surface turns Bangladesh will have no pace fallback, and the whole match rests on spin.

So my eye stays on three places next. One, the length of Ebadot's spells on Day 3 — a sudden long spell means either a change of plan or pressure. Two, a clear fitness statement at the post-match press conference — if an injury is confirmed, the conversation takes a new turn. Three, the split of spin versus pace wickets on the pitch — that will show whether the spin-led plan was right.

This is not a fitness report, and it is not a critique. It is an act of reconciliation: the bowler who took the most wickets was asked to bowl the least, and why is not written in today's ledger. It will be written in tomorrow's spell.