![tribune tribune](https://i.tribune.com.pk/media/images/Pak-v-Ban-Rawalpindi-1st-Test1724683890-0/Pak-v-Ban-Rawalpindi-1st-Test1724683890-0.jpg)
Pakistan and Bangladesh have both been penalised for maintaining slow over-rates during the first Test in Rawalpindi, resulting in fines and points deductions in the ICC World Test Championship (WTC).
Pakistan has been fined 30 per cent of their match fee and penalised six WTC points after being found six overs short of the target, taking time allowances into account. Bangladesh, meanwhile, has been fined 15 per cent of their match fee and docked three WTC points for falling three overs short.
The penalties were imposed by Ranjan Madugalle from the Emirates ICC Panel of Elite Match Referees. According to the ICC Code of Conduct, players are fined five per cent of their match fee for every over their team fails to bowl within the allotted time. Additionally, WTC playing conditions mandate that one point is deducted for each over a team is short.
Captains Shan Masood of Pakistan and Najmul Hossain Shanto of Bangladesh accepted the penalties without contest, thereby avoiding the need for formal hearings.
This development comes after Bangladesh secured their first-ever Test victory over Pakistan, winning by 10 wickets on Sunday. Both teams struggled in the hot conditions on a flat Rawalpindi pitch, but Bangladesh ultimately prevailed.
As a result of the slow over-rate penalties, Pakistan has dropped to eighth in the nine-team WTC points table, while Bangladesh has moved to seventh.
In a related incident, Bangladesh all-rounder Shakib Al Hasan was fined 10 per cent of his match fee and received a demerit point for breaching the ICC Code of Conduct. Shakib threw the ball at Pakistan's Mohammad Rizwan in frustration during the 33rd over of the second innings after Rizwan backed away.
The second and final Test of the series will also be played in Rawalpindi, starting this Friday.
COMMENTS
Comments are moderated and generally will be posted if they are on-topic and not abusive.
For more information, please see our Comments FAQ