This is an unofficial Bulletin Board - owned and run by its users. We welcome all fans of the Mighty Collingwood Football Club.
Ad blocker detected: Our website is made possible by displaying online advertisements to our visitors. Please consider supporting us by disabling your ad blocker on our website.
"Bowler running on protected area* It is unfair for a bowler to enter the protected area in his/her follow-through without reasonable cause, whether or not the ball is delivered. If, in that innings, the same bowler contravenes this Law a third time, the umpire shall direct the captain of the fielding side to suspend the bowler immediately from bowling."
Pies4shaw wrote:Running on the wicket - one official warning, I think (don't you get removed from the attack if you run on the wicket again after a formal warning?)
Looks like the rules have been changed - Wahab just got a second warning, as well.
Edit: Yes, K, I see from your post that you do now get two warnings.
Last edited by Pies4shaw on Sun Jun 16, 2019 9:06 pm, edited 1 time in total.
Appeal. Given caught behind. Batsman reviews immediately.
Not out.
And now rain stops play. It came roughly when it was forecasted.
4/305 (46.4).
Kholi 71* (62).
Amir 2/34 (8 ).
Kholi reached the landmark of 11,000 ODI runs shortly before the rain break.
There is debate over which side the rain is helping. 75 minutes is the rain time needed before overs are lost. It'll feel strange if they are delayed 75 minutes and have to come out for 20 balls, before the change of innings.
cricinfo tells us: If India don't bat again, Pakistan will have to chase 327 in 46 overs;
if Pakistan have a 20-over chase, the target will be 184.