|
Post by Tempus Fugit on Jun 27, 2010 19:10:46 GMT
A few weeks ago, when I was watching a T20, one incoming batsman seemed to be taking a long time to get ready and there was an appeal for Timed Out. Unfortunately the umpires had not been timing him accurately and eventually decided they could not be certain and allowed him to continue.
Since then, I have been timing batsmen and have been surprised how many do actually exceed T20's 90 seconds without anyone noticing.
On the other hand, in normal cricket, I have also had fielders complaining abot the delay even before 2 minutes have elapsed.
Has anyone else been taking this issue seriously? Would you be in a position to answer an appeal to for timed out with evidence?
|
|
|
Post by wisden17 on Jun 27, 2010 20:50:11 GMT
Yes, I have a stopwatch on my watch I always start when the wicket falls, never had occasion to actually make use of it though.
|
|
snicker
Junior Contributor
Posts: 6
|
Post by snicker on Jun 27, 2010 21:18:32 GMT
A batsman has three minutes to be at the crease following the fall of a wicket. An umpire should record the time at the fall of a wicket. If subsequently the fielding side makes an appeal for "timed out" then you have a record in which to make your decision.
|
|
|
Post by chartman on Jun 29, 2010 2:41:43 GMT
I simply make a note of the time of the fall of wicket. I then don't concern myself too much with how long the new batsman takes to come out and take guard (I have not experienced a delay so far) but am prepared should an appeal be made.
Also it is not an appeal I would answer without first consulting with my colleage (who I usually go and stand with at the fall of a wicket).
|
|