Digvesh Rathi Mankad Attempt: In a dramatic twist during the IPL 2025 clash between RCB and LSG, fans were left surprised when Jitesh Sharma survived a Mankad attempt. While replays clearly showed he was outside the crease, the third umpire still gave him not out. But why? Let’s explain everything in simple words.
Digvesh Rathi Mankad Attempt: What Actually Happened on the Field?
It was the final ball of the 17th over. RCB was chasing a huge target of 228 runs and every run mattered. LSG’s young spinner Digvesh Rathi saw Jitesh Sharma at the non-striker’s end stepping out early. Rathi stopped his delivery stride and removed the bails in a Mankad-style attempt.
The on-field umpire checked if Rathi wanted to appeal. Rathi said yes and the matter was sent to the third umpire. Everyone waited. The replays showed Jitesh was clearly out of his crease. But then came the twist — the third umpire said, “Not out.” The decision surprised many, but there’s a solid reason behind it.
Why Jitesh Sharma was Not Out – The Real Reason
According to the cricket rulebook (MCC Law 38.3), a bowler can only Mankad a batter if the non-striker is out of the crease before the bowler completes their delivery action. This means, once the bowler’s arm reaches the highest point — the usual point of releasing the ball — he cannot attempt a Mankad.
In Rathi’s case, the umpire ruled that he had already completed his bowling action before taking the bails off. So even though Jitesh was out of his crease, the attempt came too late. Hence, the third umpire followed the rule and declared Jitesh not out.
What About Rishabh Pant’s Role in This?
LSG captain Rishabh Pant showed great sportsmanship by withdrawing the appeal, and even hugged Jitesh Sharma after the decision. But this didn’t change the result. Even if Pant had not withdrawn the appeal, Jitesh would still have been given not out — because Rathi broke the stumps after finishing his action.
However, if the Mankad was legal and successful, only then the captain’s decision to withdraw the appeal would have mattered. In this case, the third umpire’s decision was purely based on the timing of the bowling action.
Why this Rule Exists in Cricket
The MCC updated the Mankad rule in 2022 to bring clarity. There were many debates earlier on whether Mankading is in the “spirit of the game.” Now, the rule is very clear — if a bowler wants to Mankad a non-striker, he must do it before his arm goes past the release point.
This rule protects batters from unfair dismissals but also warns them to stay inside the crease until the ball is delivered.
Did this Impact the Match Result?
Absolutely yes. Jitesh Sharma stayed on the crease and went on to play a brilliant knock. His aggressive batting, supported by Mayank Agarwal, helped RCB chase down the massive total. The Mankad moment added a lot of drama to the already high-pressure game and was one of the biggest talking points of the night.
So, Jitesh Sharma’s survival wasn’t about luck — it was all about rules. Digvesh Rathi’s timing was slightly off, and that’s why the Mankad didn’t work. The incident also showed the gentleman’s side of cricket when Rishabh Pant chose to withdraw the appeal and hugged Jitesh in a lovely moment of sportsmanship.
Also Read: PM Modi on Operation Sindoor: India Hit Terror Camps in 22 Minutes, All Recorded on Camera
FAQs
Why was Jitesh Sharma not given out during the Mankad attempt?
Because the bowler Digvesh Rathi completed his bowling action before removing the bails.
What is MCC Law 38.3?
It says a bowler can only Mankad the non-striker before their arm reaches the highest point of the delivery.
Did Rishabh Pant’s withdrawal of the appeal change the result?
No, the third umpire had already ruled it not out due to the timing of the action.
Who won the match between RCB and LSG?
RCB won the match by six wickets in a thrilling chase.
