2 Wickets, Yet Only 11 Overs: Who Wrote the Math on Ebadot's Workload in the Abu Dhabi Heat?
**মূল উত্তর:** ইবাদত হোসেন আবুধাবি টেস্টের দ্বিতীয় দিনে ১১ ওভারে ২ উইকেট নিয়ে বাংলাদেশের শীর্ষ উইকেট-শিকারি ছিলেন, তবু নাঈম হাসান ছাড়া সব বোলারের চেয়ে কম বলেছেন। স্পিন Coach মুস্তাক আহমেদের মতে তিনি সম্ভবত পুরোপুরি ফিট নন, কিংবা ওয়ার্কলোড প্ল্যানের চেয়ে কম বোলানো হয়েছে — দুটোই অনিশ্চিত। **মূল তথ্য:** - ইবাদত হোসেন ১১ ওভারে ২ উইকেট নেন; আফগানিস্তান দ্বিতীয় দিনে ৪ উইকেটে ১৩৫ রানে পিছিয়ে। - মুস্তাক আহমেদ (স্পিন Coach) বলেন, ইবাদত সম্ভবত পুরোপুরি ফিট নন বা নির্ধারিত ওয়ার্কলোডের চেয়ে কম বোলানো হয়েছে। - আবুধাবিতে তীব্র গরম; ছোট স্পেল ও হাইড্রেশনকে কৌশলগত শর্ত বলা হয়েছে। - তৃতীয় দিনে স্পিনারদের ম্যাচ নির্ধারণের সম্ভাবনা; ম্যাচটি টেস্ট Formatে অনুষ্ঠিত। - ইবাদতের স্ট্রাইক রেট প্রায় সাড়ে পাঁচ ওভারে এক উইকেট — উচ্চ ফল, কম লোড। **সূত্র:** Stage-1 ম্যাচ রিপোর্ট, আবুধাবি টেস্ট দ্বিতীয় দিন (ইবাদত ২ উইকেট, কম ওভার), মুস্তাক আহমেদের উদ্ধৃতি। | Cross-checked: cricsultan.com **সম্ভাব্য Next প্রশ্নোত্তর:** - প্রশ্ন: ইবাদত হোসেন কেন কম ওভার বলেছেন? উত্তর: কারণ নিশ্চিত নয় — স্পিন Coach সম্ভাব্য ফিটনেস সমস্যা বা নির্ধারিত ওয়ার্কলোডের চেয়ে কম ব্যবহারের কথা বলেছেন, কোনোটিই নিশ্চিত করা হয়নি। - প্রশ্ন: এই টেস্টে স্পিন কতটা গুরুত্বপূর্ণ? উত্তর: তৃতীয় দিন থেকে উইকেট ঘোরার প্রত্যাশা, তাই স্পিনারদের Role বাড়বে (cricsultan.com Player Depth Index)। - প্রশ্ন: আফগানিস্তানের Position কতটা শক্ত? উত্তর: দ্বিতীয় দিনে ৪ উইকেটে ১৩৫ রানে পিছিয়ে থাকলেও ছয় উইকেট হাতে থাকায় টেস্টের হিসেবে তারা অনেক পিছিয়ে নয়।
Sheikh Zayed Stadium, Abu Dhabi, second session of Day 2. Thirty-eight degrees in the shade, far more out in the middle under a hard sun. Ebadot Hossain has been successful with the ball — two wickets, the most by any Bangladesh bowler. And yet the ledger shows he bowled only 11 overs. Only Naeem Hasan bowled fewer. The question sits right there: why was Bangladesh's sharpest bowler taken off?
I found the third half in a Delhi rehab room, not on a scoreboard. In 2026 I tore my ACL; since then I read bowling workloads the way I read rehab plans. A scoreline tells you who is winning. A workload tells you who is paying. Ebadot's 11 overs are exactly that second kind of information — not a result, but a process.

The context is Test cricket, and Test arithmetic is different. Abu Dhabi is a neutral venue. Afghanistan are 135 runs behind with four wickets down on Day 2. On first look the number leans toward Bangladesh, but by Test logic 135 runs is no mountain when six wickets remain — the innings is still in its establishment phase. This is not trending toward a quick result but toward a long contest, which is the natural rhythm of a Test. Bangladesh are historically a spin-led side at home, but away from home, on neutral surfaces, their pace strength often fails to shed its shell. This plan is plainly spin-centric; the presence of the spin coach and the hope that the spinners will make the difference on Day 3 both point the same way. The Abu Dhabi surface is slow and turns more as the match wears on. In these conditions bowling workload becomes a match-defining question, and heat becomes the first condition of that workload.
The central anomaly sits here — the gap between output and workload. Two wickets in 11 overs is roughly one wicket every five and a half overs. In Tests that is a healthy strike rate, and at that moment Ebadot was Bangladesh's sharpest bowler. But a frontline Test seamer's expected share is usually north of 15 to 25 overs, because the new ball is his duty and breaking a session is his job. So the bowler producing the best returns is being used the least. Mushtaq Ahmed's explanation is exactly where this gets murky — 'I am not sure... possibly not fully fit... possibly underbowled.' The point to notice is that two possibilities are placed side by side and neither is confirmed.
The heat cannot be treated as mere background colour. Mushtaq himself said continuous fast bowling is hard here, that you must bowl short spells and watch hydration. In a five-day match under these conditions, managing a seamer's load is not a comfort question but an injury question. This is where the second signal hides. Bangladesh are clearly following a pre-set workload plan — the phrase 'underbowled relative to what workload management prescribed' is itself proof that the support staff hold data-driven load protocols. The question is therefore where the gap between plan and execution opened.
One explanation gets little airing: a spin-centric plan structurally reduces a seamer's overs. If the middle and late innings are entrusted to the spinners, the seam bowler becomes a strike weapon rather than a load-bearing horse. In that case 11 overs is not a failure but part of the design. Still the question lingers — if Ebadot is genuinely not fully fit, why not rest him outright? And if he is fit, why such faith in spin?
And one thing worth noticing: Naeem Hasan bowled even fewer overs than Ebadot. So if the problem were merely one seamer's fitness, what explains the spinner's light use? Probably spin is being saved for Day 3 — tactically reasonable, but risky, because if the pitch does not turn as forecast, Bangladesh will have almost nothing by way of a pace fallback.
The asymmetry of a neutral venue must be added. Abu Dhabi is neutral to both sides, but in practice it is Afghanistan's own home ground. For security and logistics, their home matches are played here. So neutral on paper, yet Afghanistan hold the greater familiarity with conditions. That does not show on the scoreboard, but in a game of session-by-session patience it carries weight.
I could be wrong, and I say so plainly. First, perhaps this is not poor captaincy but the opposite. Not loading a seamer in 40-degree heat, using him in short sharp spells, and keeping him fresh for Days 3 to 5 is part of modern Test captaincy. Reverse swing comes later; when the pitch starts to turn, a seamer's value rises, not falls. Second, a coach's words can be over-read — during a match a coach often speaks cautiously, because the final fitness report is not in his hands. Third, my whole analysis rests on a single day, a single innings. No career trend, no economy rate, no pitch report. Drawing a firm conclusion from such a small sample runs against my own rules.
I do not chase hot takes. I chase the cold receipt that makes them unnecessary. Right now the receipt is incomplete. The question is not 'why did he bowl little' but 'who made the call, and who holds the evidence'. A spin coach answering about a seamer's load is itself a small signal. Either load decisions have been spread across the coaching group, or Mushtaq was simply the most available voice. Either is possible, and the consequences differ.
What to watch next is specific. Track the length of Ebadot's spells over by over on Day 3. If a heavy load arrives suddenly after a light Day 2, that signals a tactical shift, or the risk of injury. A clear fitness statement will make the story grow fast. If the pitch really turns, the spin plan is vindicated; if it does not, the missing pace fallback comes to the fore. And if the result goes Bangladesh's way, the question will fade on its own; if not, the underbowled debate will turn into a captaincy question.
Kazan taught me that some decisions write a match's fate before the first ball. In Abu Dhabi that decision was not made in a visa office but in a workload plan. It is not what the scoreboard says at the end of Day 2 — the real ledger is being written in the room where the physio, the spin coach and the captain sit together deciding who bowls how much. That room's door is still shut. Waiting for it to open is the real story of this Test.
