Asian Cricket
Afghan Cricketer Afsar Zazai Punished for Time Wasting in Abu Dhabi Test
আফসার জাজাই সময় নষ্টের দায়ে শাস্তি পেয়েছেন: আফগানিস্তানের দ্বাদশ খেলোয়াড় আফসার জাজাই আবুধাবি টেস্টে আফগানিস্তানের দ্বিতীয় Inningsের ১৩৯তম ওভারে অনুমতি ছাড়া বারবার মাঠে প্রবেশ করে খেলার গতি ব্যাহত করার দায়ে আইসিসি আচরণবিধির লেভেল-১ লঙ্ঘনের জন্য দোষী সাব্যস্ত হয়েছেন। তাকে সরকারিভাবে তিরস্কার করা হয়েছে এবং এক ডিমেরিট পয়েন্ট আরোপ করা হয়েছে। তিনি অভিযোগ স্বীকার করায় কোনও শুনানির প্রয়োজন হয়নি। চব্বিশ মাসের মধ্যে চারটি ডিমেরিট পয়েন্ট সংগ্রহ করলে নিষেধাজ্ঞা জারি হতে পারে। এই ঘটনা প্রমাণ করে যে আইসিসি আচরণবিধি শুধু মাঠের একাদশ নয়, স্কোয়াডের সকল সদস্যের জন্য প্রযোজ্য।
A recent incident during the one-off Test match between Afghanistan and Bangladesh in Abu Dhabi has sparked discussion in the international cricket community. Afghan twelfth man Afsar Zazai was found guilty of repeatedly entering the field of play and disrupting the pace of the game, and was officially reprimanded for breaching the International Cricket Council's Code of Conduct. This incident has once again brought the importance of time management and discipline in the long format of Test cricket to the forefront.
According to details of the incident, Zazai entered the field during the 139th over of Afghanistan's second innings. It is believed that the prolonged nature of the match and the intense heat and humidity in Abu Dhabi may have contributed to player fatigue, creating the context for such an incident. However, after repeated warnings from the field umpires, he continued to enter the field without permission, prompting the umpiring panel to formally lay charges.
Under the ICC Code of Conduct, this constituted a Level 1 offence. Level 1 offences carry penalties ranging from an official reprimand to a fine of up to fifty percent of the match fee and one to two demerit points. In Zazai's case, the penalty imposed was an official reprimand and one demerit point. Since he admitted the charge, no formal hearing was required.
The umpiring panel comprised Ahsan Raza, Alauddin Palekar, third umpire Asif Yaqoob, and fourth umpire Iztullah Safi. The panel laid the charges together. This incident proves that the reach of the ICC Code of Conduct is not limited to the playing XI alone but applies equally to all members of the squad.
Afsar Zazai is a professional wicket-keeper batter. In this match, he was part of the squad as the twelfth player. In the role of twelfth man, it is common to frequently enter the field to deliver gloves, drinks, and messages. In this context, his repeated entries onto the field can be partially explained. However, continuing this behaviour despite repeated warnings from the umpires has been viewed as a serious disciplinary matter.
According to the ICC demerit point system, accumulating four demerit points within twenty-four months can result in a player being suspended. One demerit point was imposed on Zazai, and given his clean record over the preceding twenty-four months, this penalty is administratively negligible for his career. This point will automatically lapse within the next twenty-four months.
However, this incident points to a broader trend. Slow over rates and time-wasting in Test cricket have become a serious concern in recent years. Slowing down the pace of play in the long format damages the spectator experience and creates complications for broadcast management. The fact that Afghanistan's second innings extended to the 139th over suggests that the pitch was batting-friendly and that the team adopted a strategy of prolonged batting.
Abu Dhabi was used as a neutral venue. Due to security concerns, Afghanistan hosts its home Test matches abroad. For this reason, neither team enjoyed a true home advantage. No conclusion about either team's strength or weakness can be drawn from this incident based on a match played at a neutral venue.
This decision by the International Cricket Council proves that cricket's disciplinary system is functioning effectively. Whether players are on the field or off it, they will face penalties for breaching the Code of Conduct. This incident will serve as a warning for other players in the future.
This incident will have no direct impact on the Bangladesh cricket team. However, the disruption to the pace of the match may have had some effect on Bangladesh's strategic planning. Time management is an important strategic aspect of Test cricket. If a team deliberately slows the pace of play, psychological pressure is created on the opposing team. The International Cricket Council has taken a firm stance to prevent such tactics.
The lesson from this incident is that maintaining discipline and the pace of play in international cricket is extremely important. Players at any level, even the twelfth man, fall under the Code of Conduct. It is hoped that this decision by the International Cricket Council will play a helpful role in preventing similar incidents in the future.


Related Players
Popular Reads
From Buyout Clause to Loan Obligation: How €222 Million Rewrote the Transfer Market's Rulebook2026-11-14
Beyond the Scorecard: Lifetime Honor Recognizes Lutfor Rahman's Quiet Role in Building Bangladesh Cricket2026-11-13
Rawalpindi's Fourth Morning: From 404/4 to 446, and the Truth Buried Under a Debut2026-11-13
The Risk of Publishing Cricket Analysis Without Facts: No Match Report Without a Match, Team or Player2026-11-13
Recommended
Missing Evidence in Asian Cricket Analysis: Original Source Needed for Reliable Assessment2026-11-09
65.2 Overs in Durban: A Broken Top Order and the Quiet Arithmetic of the Empty Channel2026-10-10
Starc's 6/72 Triggers South Africa Collapse at Newlands, Joins Steyn at Joint Sixth2026-10-28
The Zero-Information-Point Report: Why a Null Result Is Itself a Finding in Cricket Analysis2026-10-30
Cricket's Empty File and the Blockchain Ledger: Reading the Data Crisis Through the Third Replay2026-10-06
The Zero-Information-Point Ledger: In Asian Cricket Analysis, the Real Risk Is Manufactured Certainty2026-10-28
Recommended
Hardik-Arshdeep Swap: A Test of Squad Balance in the Final Week of the IPL Trade Window2026-11-05
Babar and Rizwan's T20I Return: Farhan's Open Door and What the Selection Ledger Says2026-10-09
A 99-Run Win and an Impossible Name: A Layered Audit of the Zimbabwe-Bangladesh Report2026-10-19
83 off 71: The Valuation Sprint Behind Tanjid Tamim's Near-Miss Century2026-10-10
Lahore's Soil, Muqeem's Rest: The Unfinished Sum in Pakistan's Spin Equation2026-10-26
From Pitch to Ledger: Cricket's Data Integrity and the Lesson of an Empty Handoff2026-10-04
Recommended
Autopsy of an Empty Envelope: The Cricket Report That Contained No Cricket2026-10-26
Asia's Cricket Data Revolution Is a Myth — The Numbers That Never Walk Out to Bat2026-11-03
Rain-Drawn Rawalpindi Test: Saud Shakil’s 97 and the Battle Against Time2026-11-14
The Flat Deck at Mullanpur and Two Open Files: What India's 2-0 Lead Is Really Hiding2026-10-04
The Zero Ledger: The Silent Failure of Cricket's Data Pipeline and the Franchise Economy2026-10-11
'Game-changing approach': ACB chief hails ILT20 management after 25 Afghan players earn contracts2026-10-07
