Fact-checked by Grok 2 weeks ago

Run out

Run out is a method of dismissal in cricket whereby a batter is declared out if, at any time while the ball is in play, their wicket is fairly broken by the fielding side and, at that moment, no part of the batter's bat or person is grounded behind the popping crease (i.e., they are out of their ground).^[1] This dismissal most commonly occurs during attempts to score runs by exchanging ends between the wickets, where fielders throw the ball to break the stumps before the running batter reaches safety, but it can also happen if a batter strays from their crease without attempting a run, such as when the non-striker backs up too far and is run out by the bowler—a maneuver sometimes referred to as a "Mankad" after Indian cricketer Vinoo Mankad, who popularized it in 1947.^[2] If a batter is run out, the run in progress at the moment of dismissal is not scored, though any runs completed by the batters before the wicket falls, along with boundaries or extras from no-balls or wides, are credited to the team's total.^[1] The umpire must judge whether the wicket was "fairly" broken, meaning the ball must be thrown or handed to the fielder who dislodges the bails without undue force or obstruction.^[1] Run out is one of ten recognized methods of dismissal under the Laws of Cricket, governed by the Marylebone Cricket Club (MCC), and it emphasizes the importance of quick fielding and accurate throwing in the sport. Special cases include protections against run outs if the batter has left their ground after the ball becomes dead or during a legitimate call of "dead ball," and 2023 amendments clarify that non-strikers are liable to be run out from the moment the ball comes into play until the instant when the bowler would normally have been expected to release the ball, reducing ambiguity in such incidents.^[3] Collisions between batters attempting to avoid a run out do not excuse the dismissal, but the umpire may intervene if the fielding side obstructs the batters unfairly.^[1] This mode of dismissal can dramatically shift momentum in a match, often leading to tense appeals and requiring precise umpiring, especially with the aid of technology like Hawk-Eye for close calls.

Definition and Fundamentals

Core Definition

A run out is a method of dismissal in cricket governed by Law 38 of the Marylebone Cricket Club (MCC) Laws of Cricket, under which either batter is out if, at any time while the ball is in play, they are out of their ground and their wicket is fairly broken by the action of a fielder, regardless of whether a No ball has been called (except in specific circumstances outlined in Law 38.2).^[4] This dismissal can occur even if a run is not being attempted, provided the ball remains in play as defined in Law 20.^[4] A batter is considered out of their ground unless some part of their person or bat is grounded behind the popping crease at that end.^[5] For the striker, this refers to the popping crease at the batting end; for the non-striker, it applies to the crease at their end during the batsmen's crossing or positioning.^[5] The "wicket is fairly broken" means the bails are dislodged or at least one bail is removed from the top of the stumps, or a stump is struck out of the ground, by direct contact with the ball or by the fielder's hand or arm holding the ball. Unlike other dismissals such as bowled (Law 32), where the ball directly strikes and breaks the wicket after pitching, or caught (Law 33), where the ball is intercepted after contact with the bat, a run out does not require any contact between the ball and the batter's bat or body.^[4] Instead, it hinges solely on the batter's position relative to their ground and the fielding side's action to break the wicket while the ball is in play.^[4]

Requirement for Ball in Play

In cricket, a run out dismissal requires that the ball be in play at the moment the wicket is put down by the fielding side. According to Law 20 of the Laws of Cricket (2017 Code, 3rd Edition 2022), the ball is considered in play from the moment the bowler starts their run-up (or bowling action if no run-up) until it becomes dead.^[6] This period encompasses the active phase of the delivery, during which fielders may effect a dismissal like run out under Law 38, provided the batsman is out of their ground and the wicket is fairly broken.^[1] The ball becomes dead in specific circumstances that terminate play for that delivery, thereby invalidating any subsequent run out attempt. Key scenarios include the ball being finally settled in the hands of the wicket-keeper or bowler, lodging in the clothing or equipment of a fielder or umpire, or the umpire calling "dead ball" due to events such as a boundary being scored, an injury, or interference.^[6] For instance, if the ball reaches the boundary rope before the wicket is put down, it is dead upon crossing the boundary, and no run out can occur even if a batsman is out of their ground afterward.^[6] This requirement ensures the integrity of the dismissal, as Law 38 explicitly states that a batsman is out run out only "at any time while the ball is in play," emphasizing that the ball's status is a fundamental prerequisite.^[1] If the ball is dead when the stumps are hit—such as after the umpire has signaled a wide—the action does not constitute a valid run out. For no-balls, the ball remains in play, permitting run outs subject to exceptions in Law 38.2.^[1] Umpires enforce this strictly to prevent unfair dismissals outside the active play window.^[6]

Mechanics of the Dismissal

Running Between Wickets

In cricket, running between the wickets allows the batting team to score runs by having the striker and non-striker exchange ends after the ball is struck, provided both batsmen safely cross the pitch and ground some part of their person or bat behind the opposite popping crease while the ball remains in play. This exchange must be completed end-to-end for the run to count, with the batsmen required to remain within the playing area during the process.^[7] Either the striker or non-striker can be vulnerable to dismissal during this maneuver, as both are considered out of their ground—and thus at risk—if not properly grounded behind the popping crease when the wicket is broken.^[4] The risks of run out heighten during quick singles or pursuits of overthrows, where split-second decisions demand precise coordination between the batsmen. Hesitation in initiating or aborting a run often strands one batsman midway, exposing them outside their ground and inviting a direct hit on the stumps. Miscommunication, such as ambiguous calls like "yes," "no," or "wait," exacerbates these dangers, leading to confusion and incomplete exchanges that leave batsmen unprotected.^[8] Protection from run out is strictly tied to the popping crease, which extends 1.22 meters in front of the stumps and defines the batsman's safe ground; arrival is only secure once the bat or body is grounded behind this line, and partial crossing or hovering short of it offers no safeguard. This rule ensures that runs are earned through full commitment to the exchange, underscoring the precision required in batsmen's positioning throughout the run.^[7]

Fielding and Stump Hitting

In effecting a run out, fielders must swiftly collect the ball after it has been struck by the batter and either throw it directly at the stumps or run towards the wicket to break it with their hand while holding the ball, ensuring this occurs while the relevant batter is out of their ground.^[7] The process demands quick decision-making, as fielders assess the distance and angle to prioritize speed over perfection, often backing up throws to prevent overthrows that could allow additional runs.^[9] For the dismissal to be valid, the wicket must be "fairly put down," meaning at least one bail is completely removed from the top of the stumps, or one or more stumps are struck out of the ground.^[10] This can be achieved by the thrown ball directly striking the stumps (a direct hit), the fielder's hand or arm holding the ball breaking the wicket, or even the ball rebounding off the fielder onto the stumps, provided the ball remains in play and no unfair action occurs.^[7] Temporary disturbances, such as a bail being nudged but not fully dislodged, do not constitute a fair breakdown of the wicket.^[7] Techniques for stump hitting emphasize accuracy and power, with fielders employing overarm throws for longer distances—standing side-on, pointing the non-throwing arm at the target, and releasing with a forward rock to ensure the ball flies true toward the wicketkeeper's gloves for a clean hit—or underarm throws for closer ranges to minimize error.^[9] In professional cricket, direct hits are prized for their efficiency, requiring fielders to maintain focus on the stumps while executing rapid pickups and pivots, as even slight inaccuracies can turn a potential dismissal into boundary runs.^[9] Precision drills, such as throwing from 8-12 meters at marked targets on the stumps, help build this skill, scoring higher for central hits to simulate game pressure.^[9]

Special Cases and Exceptions

Non-Striker Leaving Ground Early

In cricket, the non-striker may be dismissed run out under Law 38.3 if they leave their ground prematurely before the bowler completes the delivery stride. Specifically, Law 38.3.1 states that the non-striker is liable to be run out at any time from when the ball comes into play until the instant the bowler would normally release the ball—defined as the point when the bowler's arm reaches its highest position during the delivery swing—and the wicket is fairly put down by the bowler throwing or handing the ball to break the stumps, regardless of whether the ball is delivered.^[4] After this release point, such a run out under this law is not permitted, though a general run out may still apply if the batsmen are attempting a run.^[11] This dismissal, often termed "Mankading," originates from an incident involving Indian all-rounder Vinoo Mankad during India's 1947-48 tour of Australia, where he twice ran out Australian opener Bill Brown for backing up too far—first in a tour match after issuing a warning, and then in the second Test at Sydney.^[12] The term gained prominence from this event, though similar dismissals occurred earlier in cricket history; it became a point of contention at the time, with Australian media criticizing Mankad, but it has since been recognized as lawful. Ethically, Mankading remains divisive: proponents argue it upholds the laws and deters unfair gaining of ground, while critics view it as contrary to the game's spirit, especially without prior warning, though the Marylebone Cricket Club (MCC) emphasizes that the non-striker should remain grounded until seeing the ball leave the bowler's hand.^[13] In October 2022, the MCC relocated this rule from Law 41 (Unfair Play) to Law 38 (Run Out) to normalize it as a standard dismissal rather than an unfair act, with further clarification in January 2023 specifying that run outs cannot occur post-release even if the non-striker had left early.^[3] The umpire's role involves adjudicating appeals for such dismissals but does not include a mandatory warning for the non-striker backing up excessively; while issuing a caution is a common courtesy rooted in tradition, the Laws impose no such requirement, and modern interpretations by the MCC confirm there is no obligation for even one warning before effecting the run out.^[14] If the ball is not delivered and the dismissal is upheld, the over does not count; if delivered and not upheld, play continues normally.^[4]

Exceptions to Run Out

In cricket, a run out dismissal under Law 38 of the MCC Laws of Cricket is not applicable if the batter has grounded their bat or any part of their body behind the popping crease at the instant the stumps are broken by the fielding side, as this places the batter within their ground and thus safe from dismissal.^[15] This protective rule, defined in conjunction with Law 29 on the batter's ground, ensures that a batter who has safely returned to or remained in their crease cannot be given out, even if the ball is in play and the wicket is fairly put down. Another key exception arises under Law 41.5 when a fielder wilfully obstructs a batter's safe return to the crease during a run; in such cases, the batter is not out run out, and the umpire shall immediately call and signal Dead ball to protect the batter from unfair hindrance by the fielding side, potentially awarding 5 penalty runs. This rule specifically addresses scenarios where the fielding team's conduct prevents the batter from grounding their bat or body behind the popping crease, rendering any subsequent breaking of the wicket invalid for dismissal purposes.^[16] Batters are also not out run out if the delivery is a no-ball, as per Law 21.18; in this case, the run out attempt does not result in a dismissal, and the no-ball penalties apply.^[17] Additionally, no run out can be awarded without a valid appeal from the fielding side, as per Law 36; the umpires must wait for the fielders to appeal ("How's that?") before considering or signaling the dismissal, ensuring that tacit or unappealed attempts to break the wicket do not result in an out decision. This requirement underscores the umpire's role in adjudicating only upon explicit request, preventing erroneous or opportunistic dismissals during play.

Consequences and Attribution

Runs Scored and Overturns

When a batter is dismissed run out, the handling of runs scored from that delivery is governed by specific provisions in the Laws of Cricket to ensure fairness and prevent partial credits for incomplete actions. According to Law 38.5, the run in progress at the moment the wicket is broken is not scored, while any runs completed by the batters prior to that point, along with applicable penalty runs, are credited to the batting side's total.^[4] This rule, cross-referenced in Law 18.8.2, emphasizes that only fully realized runs—those where both batters have safely grounded their bats in the opposite creases—contribute to the score.^[18] In scenarios where batters attempt multiple runs, such as going for two after completing the first, a run out during the second run results in only the first run being counted, as the second remains in progress and is disallowed. For instance, if the wicket is broken while the batters are midway through the second leg of a two-run attempt, the score advances by one run only, voiding the incomplete portion to avoid rewarding an aborted effort.^[4] This application upholds the principle that scoring must reflect actions fully executed before the dismissal. Penalty runs, such as the one run for a no-ball under Law 21.10, stand independently and are added regardless.^[18] Boundaries introduce an overriding element when applicable, as their scoring operates separately from running under Law 19. If the ball reaches the boundary before the run out is effected—resulting in four or six runs—the boundary award takes precedence, and any subsequent run attempts are irrelevant since the ball becomes dead upon boundary contact. However, if batters are running and a run out occurs prior to the boundary being scored, only completed running runs count, not the potential boundary.^[19] This distinction ensures boundary runs, which do not require physical completion by the batters, are not nullified by a dismissal. The overall impact on the innings is that it continues immediately with the incoming batter, but the voiding of incomplete runs prevents any unfair inflation of the score from the dismissed delivery. This mechanism maintains the integrity of the game's scoring system by prioritizing completed actions, allowing the non-dismissed batter to resume from their original or crossed position as determined by the dismissal circumstances.^[4]

Credit for the Dismissal

In cricket scorekeeping, credit for a run out dismissal is attributed to the fielder who breaks the wicket by dislodging the bails with the ball while the batter is out of their ground.^[4] The bowler receives no credit for the wicket in a run out, as the dismissal is independent of the delivery and does not count toward their bowling figures.^[4] Standard abbreviations include "run out (Jones)" for a single fielder or simply "ro" in abbreviated scorecards, maintaining clarity in official records.^[20]

Historical and Notable Instances

Evolution in Cricket Laws

The run out dismissal has roots in the informal practices of early 18th-century cricket, where batsmen were occasionally dismissed by fielders dislodging the stumps while attempting to reach safety, often through rudimentary methods like touching an umpire's bat or a hole in the ground.^[21] These practices evolved into a more structured rule with the first codification of cricket's laws in 1744, which explicitly defined run out as occurring "if in running a Notch, the Wicket is struck down by a Throw, before his Foot, Hand, or Bat is over the Popping-Crease, or a Stump hit by the Ball, though the Bail was down."^[21] This formalized the dismissal, distinguishing it from other modes like stumped, and established the popping crease—set at 3 feet 10 inches from the wicket—as the safe boundary for batsmen.^[21] Subsequent refinements in the mid-18th century, such as the 1755 laws agreed at the Star and Garter in Pall Mall, retained the core wording on run out while standardizing crease measurements and emphasizing the fielder's throw to break the wicket.^[21] The Marylebone Cricket Club (MCC), formed in 1787, assumed custodianship of the laws in 1788 and continued to evolve them, with run out remaining a fundamental dismissal without major alterations until the 20th century.^[4] A significant update came in the 2000 Code of Laws, which under Law 42.15 permitted the bowler to attempt a run out of the non-striker before entering their delivery stride, calling it a dead ball if unsuccessful and ensuring no runs or extras were awarded.^[22] This clarified the bowler's right to enforce the rule proactively, addressing ambiguities in earlier interpretations where such attempts were discouraged or penalized as no-balls.^[22] The 2017 Code further refined the non-striker provision in Law 41.16, retitling it from "Bowler attempting to run out non-striker before delivery" to "Non-striker leaving their ground early" and shifting the vulnerability point from before the delivery stride to before the instant the bowler would normally deliver the ball.^[23] This change removed any mandatory umpire warning for such dismissals—previously implied in some applications—and aligned it more closely with standard run out and stumped laws, reducing the perception of it as unfair play.^[24] In 2022, MCC relocated this provision from the "Unfair play" section (Law 41) to the "Run out" section (Law 38), fully destigmatizing what is known as Mankading.^[25] The run out rule remains consistent across all formats—Test, One Day International (ODI), and Twenty20 (T20)—governed uniformly by MCC Laws 38.^[4] However, in limited-overs formats like ODI and T20, the rule gains tactical emphasis due to the faster pacing and pressure to complete runs quickly, often leading to more frequent fielding efforts to effect run outs during hurried singles.^[25]

Famous Examples

One of the most iconic run outs in cricket history occurred on December 13, 1947, during the second Test match between India and Australia at the Sydney Cricket Ground, when Indian all-rounder Vinoo Mankad dismissed Australian opener Bill Brown for 18. Brown had backed up too far at the non-striker's end before Mankad delivered the ball, prompting Mankad to remove the bails with Brown out of his ground; this was the second such instance in the tour, the first occurring in a tour match. The dismissal sparked immediate controversy, with Australian media criticizing it as unsportsmanlike, but it was upheld as legal under the laws of cricket. This event gave rise to the term "Mankading," which refers to running out a non-striker for leaving the crease prematurely, and it has since influenced ongoing debates about the spirit of the game versus strict adherence to rules.^[26]^[27] In the 2019 ICC Cricket World Cup semi-final between India and New Zealand at Old Trafford on July 10, MS Dhoni was run out for 50 by a direct hit from fielder Martin Guptill positioned at fine leg. Dhoni, attempting a quick single with India needing 25 runs off the last 10 balls, was short of his ground after a misfield by Guptill himself turned into a game-changing throw that hit the stumps; the third umpire confirmed the dismissal via multiple replays. The incident ignited widespread controversy over New Zealand's fielding restrictions, with social media and fans alleging a violation of the powerplay rule allowing only five fielders outside the 30-yard circle, as images appeared to show six. However, fact-checks confirmed the placement was legal, with the sixth fielder inside the circle at the moment of release, underscoring the precision required in modern umpiring technology and field setups.^[28]^[29] A pivotal run out defined the 1999 ICC Cricket World Cup semi-final between South Africa and Australia at Edgbaston on June 17, where South African all-rounder Lance Klusener was dismissed for 31 after a mix-up with Allan Donald. With South Africa needing one run to win off the final ball of a tense chase of 214, Klusener had smashed two boundaries off Damien Fleming in the previous two balls but hesitated on a non-existent single after backing out midway, allowing Australian keeper Adam Gilchrist to throw down the stumps from mid-on. The dismissal resulted in a tie, but Australia's superior net run rate from the Super Six stage advanced them to the final, eliminating South Africa in heartbreaking fashion. Klusener's explosive 277 runs and 17 wickets in the tournament remain legendary, yet this moment encapsulated the high stakes of run outs in knockout cricket.^[30]^[31] A notable Mankading occurred on September 24, 2022, in the third women's ODI between India and England at Lord's, when Indian bowler Deepti Sharma dismissed England's Charlie Dean for 1. With England needing 17 runs to win and only one wicket remaining, Dean backed up too far at the non-striker's end, allowing Sharma to break the stumps without delivering the ball. The dismissal secured a 16-run victory for India, completing a 3-0 series whitewash, but drew boos from the crowd and reignited debates on the spirit of the game. Sharma later stated that Dean had been warned multiple times, though England captain Heather Knight disputed this. Occurring just days before the MCC's October 1, 2022, law change moving the provision to Law 38, the incident highlighted ongoing tensions around such dismissals.^[32] These instances highlight the dramatic impact of run outs on cricket's narrative and tactics. The Mankading incident challenged traditional notions of fair play, fostering a gradual shift toward viewing such dismissals as legitimate strategy rather than unsportsmanlike, as evidenced by the Marylebone Cricket Club's 2022 law update reclassifying it under standard run-out rules. Dhoni's dismissal amplified scrutiny on fielding positions and technology, reinforcing the need for accurate broadcasts and umpiring to prevent misinformation. Klusener's run out, meanwhile, emphasized the critical role of batsman communication under pressure, influencing coaching emphases on situational awareness and contributing to the acceptance of aggressive, opportunistic fielding as a core competitive edge in limited-overs formats.^[33]^[34]

References

[1]
The Home of Cricket
**Definition and Key Points on Run Out in Cricket:**
[2]
A glossary of cricket terms | ESPNcricinfo
Mar 6, 2006 · Mankad is when the bowler brings his arm round and, instead of releasing the ball, runs out the non-striker by whipping off the bails.
[3]
Non-striker run-out Law amended by MCC in wake of Adam Zampa ...
Jan 19, 2023 · The Marylebone Cricket Club has amended the law covering non-strikers leaving their ground early, to avoid the ambiguity caused by incidents such as Adam Zampa ...
[4]
Run Out – The Laws Of Cricket | Lord's
If either batter is dismissed Run out, the run in progress when the wicket is broken shall not be scored, but any runs completed by the batters shall stand.
[5]
Batsman Out Of His Her Ground – The Laws Of Cricket | Lord's
1 A batter shall be considered to be out of his/her ground unless some part of his/her person or bat is grounded behind the popping crease at that end. 30.1.2 ...Missing: 29 text
[6]
The Home of Cricket
**Summary of Law 20: Dead Ball (2022 Code)**
[7]
[PDF] Laws of Cricket 2017 Code - 3rd Edition 2022
The bowler does not get credit for the wicket. LAW 38 RUN OUT. 38.1 Out Run out. Either batter is out Run out, except as in 38.2, if, at any time while the ...
[8]
[PDF] ECB Coach - Running between the wickets - The Teesra
Description of Players: Equipment: 6 cones per group of 3-4; 2 bats per group; 1 ball. For game – re-use one set of cones; additional cones to define safety.
[9]
[PDF] FIELDING: Throwing Skills 1 - Cricket America
For accuracy, aim to throw the ball into the wicket keeper's hands if attempting to hit the stumps. Some Fielding Rules. • Each team has a minimum of eight ...
[10]
MCC clarifies Law on non-strikers leaving their ground early
Jan 19, 2023 · 38.3.1 At any time from the moment the ball comes into play until the instant when the bowler would normally have been expected to release the ...
[11]
Stay grounded - ESPNcricinfo
Feb 17, 2008 · The most famous instance of this mode of dismissal came when Vinoo Mankad ran Bill Brown out in the Sydney Test in 1947-48. Mankad, in the act ...Missing: history | Show results with:history
[12]
MCC backs bowlers running out non-striker's leaving the crease
Feb 23, 2023 · ... Law." Running non-strikers out for backing up too far tends to foster the argument that it isn't so big a mistake that it should cost a wicket.<|control11|><|separator|>
[13]
MCC statement on Mankad incident in IPL match
Mar 26, 2019 · To clarify, it has never been in the Laws that a warning should be given to the non-striker and nor is it against the Spirit of Cricket to run ...
[14]
The Laws of Cricket | MCC
Find out more about the history of MCC, our work in the Community and ... Obstructing the field · Law 38. Appeals and Dismissals. Run out · Law 39. Appeals ...
[15]
Scoring Runs – The Laws Of Cricket | Lord's
When runs are disallowed, the one-run penalty for No ball or Wide shall stand and 5-run penalties shall be allowed, except for Penalty runs under Law 28.3 ( ...
[16]
Boundaries – The Laws Of Cricket | Lord's
1 A Boundary 6 will be scored if and only if the ball has been struck by the bat and is first grounded beyond the boundary without having been in contact with ...
[17]
[PDF] Cricket Scoring: Getting Started | NZC
RUN OUT is recorded as 'RUN OUT', then record the name of the fielder who per- formed the RUN OUT inside brackets beside the words RUN OUT. Remember that the.
[18]
[PDF] A SHORT GUIDE TO SCORING
Record the method of dismissal in the "how out" column. • Write the bowler's name in the "bowler" column only if the bowler gets credit for the dismissal. • ...
[19]
The Laws of Cricket
If he runs out of his Ground to hinder a Catch, it's out. If a Ball is nipp'd up, and he strikes it again wilfully, before it came to the Wicket, it's out. If ...
[20]
[PDF] Laws of Cricket 2000 Code 4th Edition - Final - WordPress.com
Sections (a), (b), (c) and (d) of Law 38.2 (Batsman not Run out) shall apply. (ii) he is out Stumped if the delivery is not a No ball and the wicket is fairly ...<|control11|><|separator|>
[21]
New gender-neutral cricket laws officially released by MCC
Apr 11, 2017 · Changes to the so-called Mankad rule mean the non-striker now risks being run out if he or she leaves his or her ground before the bowler would ...
[22]
[PDF] Summary of changes to the Laws of Cricket 2017 Code
Since 2013, the Law has provided protection to a batsman from being Run out if his/her foot has been grounded beyond the popping crease, he/she has continued.
[23]
MCC moves to de-stigmatise non-striker run-outs in latest Law updates
Mar 8, 2022 · A reframing of the law for running out non-strikers while backing up, and a permanent ban on using saliva to shine the ball are among the changes to MCC's Laws.
[24]
When real Vinoo Mankad 'mankaded' Australian batsman Bill Brown
Mar 26, 2019 · Mankad was among the earliest bowlers to run a non-striker out. The incident dates back to 13 December 1947 during India's tour to Australia.
[25]
REWIND! No, Mankad didn't cheat on December 13, 1947... - Rediff
Sep 26, 2022 · Everyone knows that Mankad ran out Australian opener Brown for 18 as he had backed up too far at the non-striker's end during the Sydney Test match in December ...<|separator|>
[26]
MS Dhoni Run Out Sparks Debate On Twitter Over Legality Of Delivery
Jul 11, 2019 · Livid fans, however, blamed an umpiring error for his dismissal and questioned New Zealand's field placement. MS Dhoni was at the crease with ...
[27]
Fact-checking Dhoni run-out in WC 2019 semi-final - Alt News
Jul 12, 2019 · Alt News found that there was an error in the graphic of the field setting shown by the broadcaster before the ball was delivered off which Dhoni was dismissed.
[28]
1999 World Cup semi final: The run out that still haunts South Africa
Jun 17, 2020 · Klusener makes his ground at the non-striker's end. Australia captain Steve Waugh gestures frantically to throw the ball to the keeper's end.<|control11|><|separator|>
[29]
AUS vs SA Cricket Scorecard, 2nd Semi-Final at Birmingham, June ...
2nd Semi-Final, Birmingham, June 17, 1999, ICC World Cup. AUS Flag AUS. (49.2 ... Lance Klusener. 9, 1, 50, 0, 5.55, 28, 4, 1, 0, 3. Hansie Cronje. 1, 0, 2, 0 ...
[30]
Explained: Why Mankading is no longer 'unfair play' in cricket
Mar 9, 2022 · The Marylebone Cricket Club has announced its new code of laws, under which Mankading has been made a normal mode of running out the non-striker.
[31]
When Lance Klusener set the standard for cricketing all-rounders
May 22, 2019 · The 1999 World Cup ended in tears for Klusener and South Africa but his work with bat and ball was still astonishing.