Mankading Explained: The Non-Striker Run-Out Rule in Cricket (With Examples)

Every few months, a bowler runs out the non-striker for backing up too far, and cricket has the same argument all over again. It happened in a 2025 IPL game between Lucknow Super Giants and Punjab Kings, it happened in a TNPL match involving Ravichandran Ashwin, and it will happen again before this season is out. The dismissal has a nickname — “mankading” — that makes it sound like a trick rather than a law. This guide explains exactly what the Laws of Cricket say, when the dismissal is legitimate, why it still splits opinion, and how scorers should record it when it happens on your scorecard.

What Is Mankading?

Mankading is the informal name for running out the non-striking batter while the bowler is in the act of delivering the ball. It is named after Indian all-rounder Vinoo Mankad, who ran out Australia’s Bill Brown this way during a Test match in 1947 — at the time considered unusual enough to be named after him, even though it was never against the laws.

The situation: the non-striker backs up out of their crease early, trying to gain ground before the ball is bowled, the way sprinters do at the start of a race. If the bowler notices this before releasing the ball, they can remove the bails at the non-striker’s end instead of bowling. If the non-striker is out of their ground at that moment, they are run out.

What the Laws Actually Say

The dismissal is covered by Law 38.3 of the MCC Laws of Cricket (“Non-striker leaving his/her ground early”). This is a meaningful detail: the law sits under Run Out, not under Unfair Play. That was not always the case — until a 2022 update to the Laws, the same dismissal was filed under Law 41 (Unfair Play), which is partly why it carried such a stigma. Moving it into the Run Out law was the MCC’s way of saying: this is a normal dismissal, not a special case that needs extra justification.

Two conditions have to both be true for the dismissal to stand: the non-striker must be out of their ground, and the bowler must act before completing their normal delivery action — not after. A bowler cannot complete the bowling action, pause, and then run the non-striker out after the fact; that would not be given out.

When Is It Out — and When Is It Not?

• Out: non-striker leaves the crease before the bowler reaches the point of release, and the bails are removed before the non-striker regains their ground.
• Out: the bowler chooses to complete the delivery instead of running the non-striker out, but throws it at the stumps at the non-striker’s end and the fielding side appeals correctly through the normal run-out process — that is just an ordinary run out, no different from any other.
• Not out: the bowler removes the bails after they have completed their normal delivery stride and would already have released the ball in the course of play.
• Not out: the non-striker has already made their ground again by the time the bails come off, even if they left early.
• No warning required: unlike the old convention that many players still expect, the current Laws do not require the bowler to warn the batter first. It is a run out, and run outs do not come with warnings.

Why It’s Still Controversial

Legally, there is very little left to argue about — the 2022 rewording settled most of the ambiguity. The controversy that remains is almost entirely about the Spirit of Cricket: a preamble to the Laws that asks players to play in a sporting way, beyond simply what is legal. Critics of the dismissal argue that penalising a batter for backing up — something every non-striker does to some degree — feels like exploiting a technicality rather than genuine skill. Defenders point out that backing up early is itself an attempt to steal ground unfairly, and that the non-striker can always avoid the entire situation by staying in their crease until the ball is released.

Commentary tends to split along the same lines every time it happens: one camp calls it a legitimate dismissal that batters should simply stop giving bowlers a reason to use, the other calls it against the spirit of the game no matter how clearly it is worded in law. Both camps are reading the same Law 38.3 — the disagreement is about sportsmanship, not the rulebook.

Recent High-Profile Incidents

Notice the pattern: the controversy is rarely about whether the law permits the dismissal — it almost always does. The arguments that follow are about whether the bowler should have used it, which is a question the Laws deliberately leave to the players.

How Should Scorers Record a Mankad Dismissal?

For anyone scoring a match, a non-striker run out is recorded exactly like any other run out — there is no special dismissal type in the scorebook. A few details matter for an accurate scorecard:

• The dismissal is credited as “Run Out”, not to the bowler’s wicket-taking figures.
• The non-striker is the batter dismissed, not the one on strike — make sure the correct player is marked out.
• No run is scored off the delivery (the ball is not bowled — it is a dead ball from a scoring standpoint if the appeal is upheld before release).
• The bowler’s over is not affected: no ball is deducted from their over count if the dismissal happens before a legitimate delivery is bowled.

If you are scoring with CricPulse, logging this correctly is the same flow as any other run out — select the non-striker as the batter out, choose “Run Out” as the dismissal type, and continue the over as normal. See our guide to scoring a cricket match for the full run-out workflow, and our beginner’s guide to cricket scoring rules if you want the full picture of how dismissals are logged.

Mankading at Club and School Level: What Captains Should Know

This is where the rule matters most in practice. International players rarely leave their crease early by more than a stride or two, and umpires at that level are used to handling the appeal calmly. At club and school level, non-strikers back up much further out of habit, and captains are often unsure whether attempting the run out will be seen as poor sportsmanship by their own team as much as the opposition.

Two practical points for local leagues: first, most club competitions still expect a verbal warning before a bowler attempts it, even though the Laws no longer require one — check your league’s own playing conditions, since some retain the old convention as a local rule. Second, whatever your view on the Spirit of Cricket debate, non-strikers who simply stay in their crease until the bowler releases the ball remove the issue entirely — it is the one dismissal in cricket that is completely avoidable by the batter.

The Bottom Line

Mankading is not a loophole, a trick, or “not really out” — it is a plainly worded run out under Law 38.3, and has been treated as an ordinary dismissal in the Laws since 2022. What keeps the debate alive is not the rulebook but the Spirit of Cricket, and that argument will keep resurfacing every time it happens on a big stage. For scorers, the good news is there is nothing special to learn: record it as a run out, credit the right batter, and move on with the over.

Unusual dismissals like this are exactly where a good scoring app earns its keep — correcting a wrongly logged wicket mid-over should take seconds, not a re-score of the innings. See why CricPulse is built for exactly this kind of match-day edge case.