ENG vs PAK: Visitors fined for slow over-rate in Lord's Test
Pakistan is 1-0 up in the two-match Test series.
View : 3K
2 Min Read
Pakistan defeated, rather thumped the hosts England by nine wickets in the first of the two-match Test series at the Lord’s on Sunday. It was a comprehensive victory for them at the Home of Cricket as they managed to have a lid on their opponents from the first day itself. Their bowlers were exceptional throughout who also managed to extract a serious amount of reverse swing. However, International Cricket Council (ICC) has fined the skipper Sarfraz Ahmed 60 percent of his match fee for maintaining the slow over-rate during the Test match.
The visitors had ruled to be three overs short of their target when the time allowances were taken into consideration. The match referee, Jeff Crowe, imposed the punishment even as the players were also fined 30 percent of their match fee. The time allowances include treatment given to a player; player leaving the field as a result of a serious injury; all third umpire referrals and consultations; time wasting by the batting side; two minutes per wicket taken and four minutes per drinks break (one per session for Test matches)
According to Article 2.5.1 of the ICC Code of Conduct for Players and Players Support Personnel, players are fined 10 percent of their match fee for every over their side fails to bowl in the allotted time and the captain in fined double.
No formal hearing
Sarfraz Ahmed, the captain of Pakistan, pleaded guilty to the offence and accepted the proposed sanction as there was no need of a formal hearing. The charges were levelled by the on-field umpires Paul Reiffel and Rod Tucker, third umpire Bruce Oxenford and fourth umpire Rob Bailey.
If Pakistan commits another such offence in a Test within next 12 months with Sarfraz at the helm, the skipper will face a suspension. The second and final Test match of the series will be played in Headingley on June 1 as the visitors will aim to win the series an create a history.
[interaction id=”5b0a70888b3c7b5afd931033″]
Keep following CricTracker for more news and updates
Download Our App