Ebadot's 11 Overs in the Abu Dhabi Heat: The Arithmetic of a Bowling Workload

Second session, day two, at the ground in Abu Dhabi. The temperature under shade is brushing forty, and the air over the outfield carries dust and heat haze. The scoreboard says Afghanistan have lost four wickets and trail by 135. The bowler who took one of those wickets — two, in fact — is Ebadot Hossain Chowdhury. Based on my years of watching matches, when a seamer takes two wickets the spell usually gets longer, the captain throws him one more over. This time the arithmetic runs backwards. Eleven overs. Eleven overs on a day built for twenty-five or thirty. The ratio sticks in the mind: one wicket every 33 balls. That is the real question of the day — why did Bangladesh's sharpest bowler bowl the least?

The context needs clearing first. Test arithmetic is not ODI or T20 arithmetic. Here the maths of survival matters more than the maths of winning. Four wickets down and 135 behind at the end of day two means the opposition is still in the match — 135 is no mountain with six wickets in hand. The game is being played in Abu Dhabi, a neutral venue, where the pitch is usually slow, comfortable for batting early, and sharper for spin as the days wear on. In Mushtaq Ahmed's words, the spinners can make the difference on the third day. Bangladesh's plan is therefore spin-centric, which is a reasonable call on this kind of surface.

One term deserves plain translation, because 'workload management' is heard constantly but means something simple. A fast bowler's shoulder, back and knee are limited assets. If he hurls twenty-five overs in one day, the battery drains for the next three. So teams pre-set who bowls how much — that is the prescribed workload. Seen from outside cricket, it works like instalments on a debt: a large sum is not paid at once but spread across five days. Mushtaq Ahmed is Bangladesh's spin bowling coach, yet the question has arrived about a pace bowler's overs — that mismatch of roles is itself a signal.

Core analysis. In my notebook, the Mount Maunganui spell of 2026 is still written beside Ebadot's name — 6/46 on New Zealand soil, one of the most memorable pace performances in Bangladesh's Test history. There are two ways to know that bowler: he takes wickets, and he also concedes runs. On this pitch, in this heat, the captain has two paths open. One, hand him long spells and attack. Two, hold him in short spells so the body does not break over five days.

Today's ledger reads like this: two wickets in eleven overs, a strike rate of roughly one wicket every 33 balls — Bangladesh's best in this match. Yet in overs bowled he is second-lowest, ahead only of Naeem Hasan. A gap between production and usage is plain here, and that gap is the day's central curiosity. In Test cricket there is no ordinary explanation for under-bowling your best bowler.

Two explanations can be laid on the table. The first is fitness: Mushtaq has said he is not sure whether Ebadot is fully fit. The second is tactics: perhaps he was bowled even below the prescribed workload, with an eye on the heat and the days ahead. Notice that both are inference — the coach himself said he was 'not sure'. Treating either as settled fact would be wrong.

The heat here is not background colour; it is a tactical limit. A continuous spell means losing hydration, a body weakened by sweat, and slower nerve decisions. The essence of Mushtaq's point: in these conditions, short spells and timely hydration are how you survive five days. On that logic, holding Ebadot back is not weakness — it is protection.

But there is another layer that rarely enters the discussion. Under-bowling a seamer means betting the day's biggest risk on spin. If the pitch breaks on day three, the plan works. If it does not, Bangladesh are left with tired spinners and a half-used seamer. Tactically this is close to an option-pricing decision — buying a cheap option so you can exit fast if the market turns. In cricket terms, Ebadot is that option, preserved for the final day rather than spent in the middle of this one.

The contrarian angle. The official explanation settles on 'heat and fitness'. There is a blind spot here. If there were genuine fitness doubt, why expose him to eleven overs at all — at least in the first spell? The question is therefore larger than fitness; it is captaincy. Mushtaq Ahmed is the spin coach, and his hedged answer about a pace bowler's overs suggests the decision may not have come from the bowler's medical file but from the collective coaching calculation.

A second blind spot: Naeem Hasan bowled even fewer overs than Ebadot. A spin-centric plan says the spinners are the main weapon, so why bowl them so little? The answer is probably simple — thinking about the day-three pitch. But the curiosity remains: those under-bowled today will carry a heavier load tomorrow, and in this heat a heavier load means higher injury risk.

A third blind spot is the data gap. This report carries no scorecard totals, no bowling averages, no injury history, no toss result. So it cannot be said how difficult the pitch was for those wickets, or whether wind and cloud played a part. Jumping from here to large conclusions would turn a one-day snapshot into a season-long truth.

Takeaway. The first session of day three will answer it. If Ebadot suddenly begins long spells, then day two's eleven overs were a planned saving. If he remains confined to short spells, the match will rest on spin, and Bangladesh's pace option will exist only on paper. Whichever path unfolds, the Abu Dhabi heat and the 'one wicket every 33 balls' arithmetic will remain — strike rates rise, over-bank balances do not.