Recent from talks
Nothing was collected or created yet.
Timed out
View on WikipediaTimed out is a method of dismissal in the sport of cricket. It occurs when an incoming batter is not ready to play within a given amount of time of the previous batter being either dismissed or retired.[1][2] This is one case of a 'diamond' or 'platinum' duck, as the player is out without having faced a ball. The purpose of the law is to ensure there are no unnecessary delays to the game. It is easily avoided, and it is very unusual for a batter to get out 'timed out'. As of March 2025[update], there have been no instances of this type of dismissal in Test cricket, a single instance each in One Day International and Twenty20 International cricket, and seven instances in first-class cricket.
Background
[edit]"Timed Out" as a specific method of dismissal was added to the Laws in the 1980 code.[3] It provided two minutes for the incoming batter to "step on to the field of play". In the 2000 code, this was revised to three minutes for the batter to "be in position to take guard or for his partner to be ready to receive the next ball".[4] However, the first printed Laws of cricket, in 1775, already required the umpires "To allow Two Minutes for each Man to come in when one is out".[5]
In 1919, Sussex cricketer Harold Heygate was given out by the umpire Alfred Street as "timed out" in a first-class County Championship match with Somerset at Taunton. MCC, then in charge of the Laws, later ruled that the umpire was correct in ending the Sussex innings when Heygate failed to appear within two minutes, but that the batter should be marked as "absent", which is how it appears in the 1920 edition of Wisden Cricketers' Almanack. Under present rules, Heygate would have been recorded as "absent hurt", and this is how his innings is now recorded in CricketArchive. The match ended in a tie.[6]
Current Law
[edit]Law 40 of the Laws of Cricket provides that an incoming batter must be in position to receive the ball or for their partner to be ready to receive the next ball within a given amount of time of the fall of the previous wicket or the previous batsman retiring. If not, the incoming batter will be given out, timed out, on appeal.[7]
The amount of time given for the incoming batter to be ready varies depending on the match playing conditions. The default period of time defined in Law 40 is 3 minutes,[7] but this is amended to 2 minutes for Test cricket and one day international cricket.[8][9] Twenty20 cricket shortens the period of time even further to 90 seconds, and an on-field dugout is often provided in this format (in a similar manner to some other team sports such as association football and rugby) to enable incoming batters to make their way to the wicket immediately when a wicket falls to avoid being timed out.[10] The umpires cannot rule on any appeal for timed out until someone takes the field of play.
The "incoming batter" may be any batter who has not yet batted. There is no prescribed batting order in cricket, i.e. the team does not have to come out to bat in any specific order even if one has been published. Until one batter has set foot on the field the batting captain may pick any player who has not yet batted who, when they appear on the field, may then be given out on appeal.[11] Knowing that a better batter will shortly be able to take the field, the captain can therefore sacrifice onto the field their worst remaining batter (colloquially the "No. 11") or one who is present injured, even one who previously retired hurt.
Whether or not an appeal for timed out is made, if the delay in which no batter comes to the wicket extends beyond the prescribed minutes, an "extended delay" is judged and the umpires follow the procedure in Law 16.3 with a view to award the match to the opposing team.[7] They will discuss the situation together, make contact with the Captain of the team who are refusing to play and can award the game to the bowling side.[12]
If no remaining not out players are able to take the field (e.g. through absence, injury or illness, or suspension or ejection as a result of a players' conduct offence) then none is given out timed out; instead the innings is to be considered as completed and "absent ill/injured/hurt" (or retired in the event of a players' conduct offence) is noted next to all remaining players' names as appropriate.[13][14]
Dismissals
[edit]Test cricket matches
[edit]No batter has been dismissed timed out in Test cricket as of November 2023, but there are some notable incidents where a batter could have potentially been dismissed in this manner:
- During the third Test at Cape Town's Newlands Cricket Ground of the 2006–2007 series between India and South Africa, India quickly lost two opening batters at the start of their second innings. Sachin Tendulkar was listed as the fourth batter, but as he had been replaced as a fielder for 18 minutes at the end of South Africa's first innings, he was ineligible to bat in India's second innings until another 18 minutes had expired from its commencement. After confusion in the Indian dressing room about Tendulkar's ineligibility resulting in a six-minute delay, Sourav Ganguly came in as the next batter. South African captain Graeme Smith did not appeal for a "timed out" dismissal of the incoming batter as the Umpires had told him it would not be entertained due to confusing information given by the match referee regarding Tendulkar's short suspension, and Ganguly was allowed to commence his innings.[15]
- During the second Test in the 2023 Ashes series, Australian player Nathan Lyon suffered a severe calf injury while fielding that prevented him from moving at a normal pace. During the Australian second innings he decided to take his place as the final batter and to avoid the potential for England to appeal and have him dismissed by a time out, Lyon moved closer to the field than the Australian players pavilion so he could hobble onto the ground within the time limit. He avoided being timed out, scoring 4 runs before he was dismissed.
One Day International cricket
[edit]The first batter in One Day International cricket (or indeed in any form of international cricket)[16] to be timed out was Angelo Mathews in a group stage match against Bangladesh during the 2023 Cricket World Cup. Mathews was making his way to the crease after the dismissal of Sadeera Samarawickrama when his helmet strap broke and he sought a replacement helmet on the edge of the field before being ready to face the next ball, with the time taken between Samarawikrama's dismissal and Mathews' readiness to face the next ball consequently exceeding the 2 minutes permitted under the tournament playing conditions.[17] Subsequently, Bangladesh captain Shakib Al Hasan appealed for timed out, which was upheld by the on-field umpires Richard Illingworth and Marais Erasmus. Despite Mathews' protestations, Shakib refused to withdraw the appeal. The dismissal generated controversy, with some praising and others criticising Shakib for his actions.[18][19] It later emerged that Mathews would not have been ready to face the next ball in time even had his helmet strap not broke, and that he had been warned by the umpires about the possibility of being timed out before the helmet malfunction.[20]
| No. | Player | Team | Opposition | Venue | Competition | Date | Result |
|---|---|---|---|---|---|---|---|
| 1 | Angelo Mathews | Arun Jaitley Stadium, Delhi, India | 38th Match, 2023 Cricket World Cup | 6 November 2023 | Lost[21] | ||
| Mathews was making his way to the crease following the dismissal of Sadeera Samarawickrama when his helmet strap broke, exchanging his helmet on the boundary before proceeding. The resulting delay meant that Mathews failed to be ready to receive the next ball in time, however he still would not have been ready in time even without the helmet malfunction.[1][20] | |||||||
Twenty20 International cricket
[edit]The first batter in Twenty20 International cricket to be out Timed out was Ghana's Godfred Bakiweyem against Sierra Leone in the 2023 Africa Cricket Association Africa T20 Cup, occurring only a month after the aforementioned Mathews dismissal in One Day International cricket. Notably, Bakiweyem was involved in another unusual dismissal earlier in the same match when Sierra Leone's Abass Gbla made intentional contact with Bakiweyem while Bakiweyem was attempting to run Gbla out, resulting in Gbla being given out obstructing the field.[22]
| No. | Player | Team | Opposition | Venue | Competition | Date | Result |
|---|---|---|---|---|---|---|---|
| 1 | Godfred Bakiweyem | Willowmoore Park, Benoni, South Africa | 12th Match, 2023 Africa Cricket Association Cup | 17 December 2023 | Won[23] | ||
| Following the dismissal of Samson Awiah, Bakiweyem was uncertain as to whether he was next to bat, the resulting delay meaning that he failed to be ready to receive the next ball in time.[22] | |||||||
First-class cricket
[edit]| No. | Player | Team | Opposition | Venue | Competition | Date | Result |
|---|---|---|---|---|---|---|---|
| 1 [note 1] | Andrew Jordaan | Eastern Province | Transvaal | Adcock Stadium, Port Elizabeth, South Africa | 1987–88 Howa Bowl | 20 February 1988 | Drawn[25] |
| Jordaan was due to open the batting but was prevented from reaching the ground due to flooded roads following an overnight downpour.[24] | |||||||
| 2 | Hemulal Yadav | Tripura | Orissa | Barabati Stadium, Cuttack, India | 1997–98 Ranji Trophy | 17 December 1997 | Drawn[26] |
| Yadav was in conversation with his team manager on the boundary at the fall of the 9th wicket, and made no attempt to reach the crease.[27] | |||||||
| 3 | Vasbert Drakes | Border | Free State | Buffalo Park, East London, South Africa | 2002–03 SuperSport Series | 27 September 2002 | Lost[28] |
| Drakes had been playing for West Indies in the Champions Trophy and was included in Border's team under the assumption that he would arrive on time. His flight from Colombo was delayed and he had not yet arrived at the ground when he was due to bat.[29] | |||||||
| 4 | Andrew Harris | Nottinghamshire | Durham UCCE | Trent Bridge, Nottingham, England | 2003 University Centres of Cricketing Excellence | 12 April 2003 | Won[30] |
| Harris had strained a groin muscle and was not initially expecting to bat, but later decided to bat as Chris Read was nearing a century but was running out of batting partners. He was not yet ready to bat at the fall of the 9th wicket and was still making his way to the field when time elapsed, stranding Read on 94 not out.[29] | |||||||
| 5 | Ryan Austin | Combined Campuses and Colleges | Windward Islands | Arnos Vale Ground, Kingstown, Saint Vincent and the Grenadines | 2013–14 Regional Four Day Competition | 4 April 2014 | Won[31] |
| Austin was the last nominated batter and failed to be ready to receive the next ball in time. Despite this, he won the Player of the Match award due to his career-best bowling of 11-101 contributing towards an 82-run win.[32] | |||||||
| 6 | Charles Kunje | Matabeleland Tuskers | Mountaineers | Queens Sports Club, Bulawayo, Zimbabwe | 2017–18 Logan Cup | 3 December 2017 | Lost[33] |
| After Matabeleland Tuskers lost 3 wickets in 6 balls, Kunje was unprepared to bat and failed to be ready to receive the next ball in time.[27] | |||||||
| 7 | Saud Shakeel | State Bank of Pakistan | Pakistan Television | Rawalpindi Cricket Stadium, Rawalpindi, Pakistan | Final, 2024–25 President's Trophy | 4 March 2025 | Lost[34] |
| After State Bank of Pakistan lost 2 wickets in 2 balls, Shakeel was unprepared to bat and failed to be ready to receive the next ball in time.[35] | |||||||
See also
[edit]Notes
[edit]References
[edit]- ^ a b Fidel Fernando, Andrew (6 November 2023). "Mathews becomes the first to be dismissed timed out in international cricket". ESPNcricinfo. Retrieved 6 March 2025.
- ^ "What Is Timed Out Law? Explaining Angelo Mathews' World Cup Dismissal Against Bangladesh | Cricket News". NDTVSports.com. Retrieved 6 November 2023.
- ^ "Laws of Cricket 1980, Law 31". acscricket.co. Archived 27 September 2007 at the Wayback Machine
- ^ "Laws of Cricket 2000, Law 31". www.lords.org.Archived 1 May 2008 at the Wayback Machine
- ^ "Laws of cricket 1775". acscricket.com. Archived 27 September 2007 at the Wayback Machine
- ^ See the CricketArchive Scorecard. Heygate was given out under Law 45 of the Laws of cricket, 1884 code – 1919 revision Archived 27 September 2007 at the Wayback Machine.
- ^ a b c "Law 40 – Timed Out". Marylebone Cricket Club. Retrieved 8 November 2023.
- ^ "Men's Standard Test Match Playing Conditions" (PDF). International Cricket Council. June 2023. p. 55. Archived from the original (PDF) on 7 November 2023.
- ^ "ICC Men's Standard ODI Playing Conditions" (PDF). International Cricket Council. June 2023. p. 52. Archived from the original (PDF) on 7 November 2023.
- ^ "ICC Men's Twenty20 International Playing Conditions" (PDF). International Cricket Council. June 2023. p. 50. Archived from the original (PDF) on 7 November 2023.
- ^ MCC Answers to Questions on Law 31
- ^ "Law 16 – The Result". Marylebone Cricket Club. Retrieved 8 November 2023.
- ^ "Law 13 – Innings". Marylebone Cricket Club. Retrieved 8 November 2023.
- ^ "Law 42 – Players' Conduct". Marylebone Cricket Club. Retrieved 8 November 2023.
- ^ Dileep Premachandran (5 January 2007). "Out of sight, out of time". ESPNcricinfo. ESPN Inc. Retrieved 17 March 2015.
- ^ Martin, Ali (6 November 2023). "Sri Lanka's Angelo Mathews timed out in World Cup loss to Bangladesh". The Guardian. ISSN 0261-3077. Retrieved 6 January 2024.
- ^ "Mathews' unwanted history - watch unique dismissal, reaction and vote". BBC Sport.
- ^ Macpherson, Will; Burrows, Josh (6 November 2023). "'Disgraceful': Sri Lanka outraged as Angelo Mathews timed out against Bangladesh". The Telegraph. ISSN 0307-1235. Retrieved 6 January 2024.
- ^ "Mathews dismissed timed out: 'Eye-opener for all batters'". ESPNcricinfo. 6 November 2023. Retrieved 6 March 2025.
- ^ a b Gollapudi, Nagraj (8 November 2023). "Umpires informed Mathews of timed-out threat before helmet malfunction". ESPNcricinfo. Retrieved 6 March 2025.
- ^ "BAN vs SL Cricket Scorecard, 38th Match at Delhi, November 06, 2023". ESPNcricinfo. Retrieved 6 March 2025.
- ^ a b "Watch: Batters given out obstructing the field and timed out in Ghana-Sierra Leone Africa Cup T20I". Wisden. 18 December 2023. Retrieved 7 February 2025.
- ^ "GHA vs SLE Cricket Scorecard, 12th Match, Group B at Benoni, December 17, 2023". ESPNcricinfo. Retrieved 6 March 2025.
- ^ a b Engel, Matthew; Samson, Andrew (2006). "Setting the records straight". ESPNcricinfo. Wisden Cricketers' Almanack. Retrieved 6 March 2025.
- ^ "EPR (SACB) vs TVL (SACB), at Port Elizabeth, Feb 20 1988 - Full Scorecard". ESPNcricinfo. Retrieved 6 March 2025.
- ^ "Orissa v Tripura at Cuttack, 17-20 Dec 1997". ESPNcricinfo. Retrieved 6 March 2025.
- ^ a b Saini, Aakash (6 November 2023). "Top Batters Who Have Been Timed Out Before Angelo Mathews". OneCricket. Retrieved 6 March 2025.
- ^ "BOR vs FS Cricket Scorecard, Pool A at East London, September 27 - 29, 2002". ESPNcricinfo. Retrieved 6 March 2025.
- ^ a b Lynch, Steven (2 April 2012). "What a way to go". ESPNcricinfo. Retrieved 6 March 2025.
- ^ "NOTTS vs DurhU Cricket Scorecard at Nottingham, April 12 - 14, 2003". ESPNcricinfo. Retrieved 6 March 2025.
- ^ "WWD vs CC&C Cricket Scorecard at Kingstown, April 04 - 06, 2014". ESPNcricinfo. Retrieved 6 March 2025.
- ^ "T&T leap into lead with big win". ESPNcricinfo. 7 April 2014. Retrieved 6 March 2025.
- ^ "TUSK vs MOUNT Cricket Scorecard at Bulawayo, December 03 - 05, 2017". ESPNcricinfo. Retrieved 6 March 2025.
- ^ "PakTV vs SBP Cricket Scorecard, Final at Rawalpindi, March 04 - 08, 2025". ESPNcricinfo. Retrieved 6 March 2025.
- ^ Rasool, Danyal (5 March 2025). "Saud Shakeel timed out in President's Trophy final". ESPNcricinfo. Retrieved 6 March 2025.
External links
[edit]- The Laws of Cricket
- Wisden Cricketers' Almanack
The dictionary definition of timed out at Wiktionary
Timed out
View on GrokipediaHistory
Origins and Early Development
The concept of penalizing delays by incoming batsmen emerged in the early codified laws of cricket during the 18th century, primarily to curb deliberate time-wasting and ensure the game's progression in an era of multi-day matches on uncovered pitches susceptible to weather interruptions. Although the specific dismissal mode known as "timed out" was not formalized until later, precursor rules addressed the issue through team-level penalties rather than individual outs. In the 1774 code of laws, umpires were instructed to "allow two minutes for each man to come in" following the fall of a wicket, with an additional fifteen minutes between innings; failure to comply after the umpire called "Play" resulted in the defaulting side losing the match.[7] This provision, without numbering in the early informal codes, underscored umpires' discretion in managing delays, reflecting the need for efficiency in village greens and early county fixtures where logistics like horse-drawn travel could already prolong proceedings. The rule was refined in subsequent revisions, with the 1884 code designating it as Law 45, maintaining the two-minute allowance for the incoming striker while explicitly stating that umpires "shall allow two minutes for each striker to come in" to expedite play and deter stalling tactics.[8] The emphasis on umpires' authority highlighted the era's challenges, including longer formats without modern protections, where even minor delays could significantly impact match outcomes. Despite these stipulations, no verified instances of the rule's enforcement appear in records before 1900, attributable to its informal application and the slower pace of early cricket, where travel constraints and rudimentary organization often led to natural pauses rather than deliberate infractions.[6] The current MCC Law 40 extends this to a three-minute limit for individual dismissal, evolving the original intent to penalize wilful tardiness. The first recorded instance of a timed out dismissal occurred in 1987-88, when South African batter Andrew Jordaan was timed out in a first-class match for Eastern Province against Transvaal due to travel delays from flooded roads.[6]Evolution and Rarity Prior to 2023
The timed out dismissal was formally introduced as a specific method in the 1980 revision of the MCC Laws of Cricket, stipulating a two-minute limit for the incoming batter to be ready to face the next ball after the fall of a wicket.[9] This provision aimed to prevent deliberate time-wasting, building on earlier informal practices where umpires could rule a batter absent without formal dismissal status. In the 2000 code revision, the time limit was extended to three minutes to accommodate evolving aspects of the game, such as more complex protective equipment and strategic fielding rearrangements that could delay the incoming batter's arrival.[9] Prior to 2023, the rule's application remained exceedingly rare, with umpires showing reluctance to enforce it due to the "Spirit of Cricket" preamble introduced in the 2000 MCC Laws, which emphasized fair play and mutual respect over strict adherence to technicalities.[10] This cultural norm, reinforced by a preference for issuing warnings rather than dismissals, aligned with cricket's tradition of sportsmanship, where appeals for timed out were viewed as contrary to the game's ethos. Additionally, logistical challenges in pre-1980 cricket, including inconsistent timing mechanisms and the absence of standardized stopwatches at many venues, contributed to non-enforcement, as umpires relied on visual estimates rather than precise measurements.[4] Statistics underscore this infrequency: before 2023, only six confirmed timed out dismissals occurred worldwide, all in first-class cricket spanning 1987 to 2017, with zero instances in international matches across Test, ODI, or T20I formats.[6] These cases typically involved exceptional circumstances, such as travel delays or personal issues, rather than routine delays.Legal Framework
MCC Law 40
Law 40 of the Marylebone Cricket Club's (MCC) Laws of Cricket governs the dismissal method known as "timed out," establishing a strict timeline for an incoming batter to be ready after a wicket falls or a batter retires.[1] The precise wording of the law, as per the 2017 Code (3rd Edition 2022), is as follows:40.1 Out Timed outThis provision ensures the game progresses without undue delays, with the 3-minute window beginning at the moment the umpire signals the dismissal of the previous batter or announces the retirement.[1] The enforcement of Law 40 requires an appeal from the fielding side, typically initiated by the captain or a fielder asking the umpire, "How's that?" or a similar phrase; without such an appeal, the dismissal cannot be given, even if the time limit expires.[1] If the appeal is upheld and the batter is given out timed out, the decision is final, with no provision for the batter to return or for the innings to resume from that point.[11] Umpires are responsible for accurately timing the interval, starting the clock immediately upon the wicket's fall or retirement call, and they may account for brief, justifiable delays such as those caused by injury or equipment retrieval only if deemed reasonable under the circumstances.[1] An key exception suspends the 3-minute countdown if the umpire calls "Time," such as during intervals or other official breaks, resuming only when play is ready to restart.[11] Law 40 applies universally across all formats of the game—Test, One-Day International, and T20—unless specific playing conditions approved by governing bodies like the International Cricket Council explicitly modify the timing or procedures.[1]
40.1.1 After the fall of a wicket or the retirement of a batter, the incoming batter must, unless Time has been called, be ready to receive the ball, or for the other batter to be ready to receive the next ball, within 3 minutes of the fall of the wicket or retirement. If this requirement is not met, the incoming batter will be out, Timed out.
40.1.2 In the event of an extended delay in which no batter comes to the wicket, the umpires shall adopt the procedure of Law 16.3 (Umpires awarding a match). For the purpose of this Law, either umpire shall call and signal ‘Time’ after the 3 minutes is up.[11]
Variations in Playing Conditions
In international limited-overs cricket, the International Cricket Council (ICC) modifies the timed out rule under MCC Law 40 to enforce stricter time limits aimed at minimizing delays. For One Day Internationals (ODIs), the playing conditions stipulate a 2-minute window for the incoming batter to be ready to receive the ball after a dismissal or retirement, as applied during the 2023 Men's ODI World Cup.[12][4] This reduction from the MCC's default promotes faster play in 50-over matches, with umpires required to enforce it upon appeal from the fielding captain. For Twenty20 Internationals (T20Is), the ICC further shortens the limit to 90 seconds to suit the format's emphasis on pace, a standard implemented since the early 2010s and reaffirmed in updates to the playing conditions.[12][13] This adjustment ensures minimal interruption in the short 20-over game, where appeals for timed out must still be made explicitly. Domestic competitions often adapt these international standards or revert to the MCC baseline. In the Indian Premier League (IPL), a major T20 league, the timed out limit is set at 2 minutes to balance speed with the format's demands, while first-class matches typically default to the MCC's 3-minute allowance unless tournament-specific conditions specify otherwise.[14][1] Following the 2023 ODI World Cup, the Marylebone Cricket Club (MCC) issued a clarification on interpreting timed out in cases of equipment delays, stating that such issues do not excuse the dismissal if not communicated to umpires within the applicable time limit, though extraordinary circumstances may allow discretionary extensions under umpire authority.[15]| Format/Organization | Time Limit | Appeal Requirement |
|---|---|---|
| MCC (default, e.g., first-class) | 3 minutes | Yes, by fielding side captain |
| ICC ODI | 2 minutes | Yes, by fielding side captain |
| ICC T20I | 1.5 minutes | Yes, by fielding side captain |
