HomeAsian CricketAfghan Cricketer Punished for Time-Wasting in Abu Dhabi Test: An Analysis of Governance and Pace of Play
Afghan Cricketer Punished for Time-Wasting in Abu Dhabi Test: An Analysis of Governance and Pace of Play
আবুধাবিতে আফগানিস্তান ও বাংলাদেশের মধ্যে অনুষ্ঠিত একমাত্র টেস্ট ম্যাচে আফগানিস্তানের দ্বাদশ খেলোয়াড় আফসার জাজাইকে সময় নষ্ট করার অভিযোগে শাস্তি দেওয়া হয়েছে। ১৩৯তম ওভারে বারবার সতর্কতা সত্ত্বেও তিনি মাঠে প্রবেশ করেন এবং খেলার গতি ব্যাহত করেন। আইসিসির কোড অব কন্ডাক্টের লেভেল ১ লঙ্ঘনের জন্য তাকে সরকারিভাবে ভর্ৎসনা ও ১ ডিমেরিট পয়েন্ট দেওয়া হয়। তিনি অভিযোগ স্বীকার করায় শুনানির প্রয়োজন হয়নি। এই ঘটনাটি প্রমাণ করে যে বেঞ্চের Playersও মাঠের আচরণবিধির আওতায়। টেস্ট ক্রিকেটে ধীর গতি একটি বড় সমস্যা, এবং এই শাস্তি ভবিষ্যতে সতর্কবার্তা হিসেবে কাজ করতে পারে।
An Afghan cricketer was recently punished for wasting time during a Test match held in Abu Dhabi. This incident has raised important questions about the rules and governance of the game, player conduct, and the pace of Test cricket. The match, played between Afghanistan and Bangladesh, was a one-off bilateral Test at a neutral venue. In the 139th over of the match, Afghanistan's 12th man, Afsar Zazai, entered the field and disrupted the pace of play. Despite repeated warnings from the umpires, he entered the field, which was identified as a breach of the ICC Code of Conduct. As a result, he was officially reprimanded and given one demerit point. This penalty falls under Level 1 of the ICC Code of Conduct, where the minimum penalty ranges from a reprimand up to a 50% match-fee fine and 1-2 demerit points. Since Zazai committed this offence for the first time and had a clean record over the past 24 months, he received the minimum penalty. The investigation revealed that he admitted the charge, so no formal hearing was required. The entire umpiring panel—Ahsan Raza, Alauddin Palekar, third umpire Asif Yaqoob, and fourth umpire Iztullah Safi—laid the charges. This incident makes it clear that not only the main XI players but also bench players are subject to the on-field code of conduct. Time-wasting in Test cricket is a longstanding issue. Especially during long innings, such as Afghanistan's second innings of 139 overs, players can become fatigued and may slow down the game. The hot and humid weather of Abu Dhabi could also influence such behaviour. However, there is no evidence that this incident was part of a team strategy; rather, it appears to be the result of individual over-eagerness or poor time management. Afghanistan has been a Full Member since 2026 and usually hosts its home Tests abroad due to security reasons. Therefore, Abu Dhabi cannot be called their true home venue. Similarly, Bangladesh did not enjoy a genuine home advantage there. No conclusion about the match result or team strength can be drawn from this report, as scorecard or performance data is absent. According to analysts, the main significance of this event lies in its governance aspect. Under the ICC demerit point system, accumulation of 4 points within 24 months triggers a suspension. In this incident, only 1 point was given, which will not have a major impact on his career in the future. However, it can serve as a warning. Slow over rates in Test cricket is a major concern. Sometimes teams deliberately slow down the game to influence the result. The ICC has already tightened over-rate penalties. But if players continue the same behaviour despite repeated warnings, stricter measures are needed. This incident indicates that need. Additionally, bench players need to be properly trained so they understand the rules of entering the field and the importance of maintaining the pace of play. Overall, this incident from the Abu Dhabi Test is a small but significant example of rule governance. It shows that cricket's rules are not limited to the field of play but apply to the entire squad. To avoid such incidents in the future, increasing player awareness and greater vigilance by umpires are necessary.


Related Players
Recommended
Death-Over Geometry: Not the Death of the Yorker, but the Stale Field2026-09-30
Not a Storm of Sixes but a Chain of Timestamps: Sadakat's 96 and Sri Lanka's Silent 82-Run Collapse2026-10-12
The Lucknow 43-Ball Century Belongs More to West Indies' Structural Fault Lines Than to Iyer2026-10-07
Rahmat Shah's Record: Sixth in History, But Three Questions Before Placing Him Beside Kohli2026-10-13
The Field Clock and the Screen-Room Monitor: How Asian Cricket Now Files Its Controversies2026-09-29
Two Finals, Tiny Margins, One Open Ledger: Why Asian Cricket Doesn't Keep Its Own Books2026-09-29
Recommended
An Empty Analysis Is Still a Signal: Lessons from a Blank Blockchain in Cricket2026-10-09
Not a Storm of Sixes but a Chain of Timestamps: Sadakat's 96 and Sri Lanka's Silent 82-Run Collapse2026-10-12
The Blockchain Ledger: A New Chapter in Sport, Investment and Regulation2026-10-03
The Cricket Audit: Eight Layers From a Blank File to a Verdict2026-10-12
The Testimony of an Empty Notebook: When Cricket Analysis Chooses Silence2026-10-11
Abu Dhabi Arithmetic: A 124-Run Stand, a 317/8 Night, and Bangladesh's Long Wait2026-10-10
Recommended
The Middle-Over Ledger: A Deep Accounting of Bangladesh's T20 Batting Debt2026-09-26
Kotla's Slow Soil, Pant's Hips, and the Void Kuldeep Left Behind2026-10-08
Reading the Empty Field: When Cricket's Data Never Arrives2026-10-08
Where Did Home Advantage Move in Cricket After the Empty Stadium Era?2026-10-01
The Dot-Ball Tax: After Asia's Powerplay Party, the Silence of Overs 7–152026-09-29
The Anchor's Extinction: The Role Asian T20 Auctions Have Stopped Paying For2026-10-02
