# Jaiswal run-out in Galle 2026: Manjrekar slams “lost in his world” URL: https://technosports.co.in/yashasvi-jaiswal-run-out-galle-2026/ Published: 2026-08-15 Updated: 2026-08-15 Author: Reetam Bodhak Yashasvi Jaiswal was run out for 32 off 37 balls on the final ball of the 11th over as India played Sri Lanka in the first Test at Galle International Cricket Stadium on August 15, 2026. Sanjay Manjrekar later called it a “horrible mix-up” and said the opener “seemed to be lost in his own world” during the dismissal. The wicket came when India were 47/1, with KL Rahul stranded at the other end. Worth noting: the run-out hinged on misreading at the crease. According to the match incident described in coverage, Rahul nudged Keshara Nuwantha’s delivery toward the leg side, looking to rotate strike, but the moment quickly turned chaotic. **Stat/Verdict** **Jaiswal’s dismissal was India’s only setback in the opening session as they reached 101/1 at lunch.** ![Jaiswal](https://technosports.co.in/wp-content/uploads/2026/08/aisjhsjs.jpg) ## What exactly happened in the 11th over? The key sequence arrived on the last ball of the 11th over. KL Rahul faced Keshara Nuwantha and nudged the ball toward the leg side, a move that typically demands a quick, clear decision on the second run. Instead, confusion took over within seconds at the crease, leading to a mix-up between the two batters. Jaiswal’s role in the incident was particularly stark. Reports and commentary described that Jaiswal made contact with Nuwantha while attempting to stop the ball, and that minor bump seemingly disrupted his balance. With his attention not fully on partner movement, he failed to reach his ground in time. Sanjay Manjrekar’s assessment summed up the body language of the moment. He said Rahul would have been able to complete his end comfortably, but Jaiswal “seemed to be lost in his own world,” as per his on-air remarks carried by mainstream coverage. ## The quote that raised eyebrows Manjrekar didn’t just describe a run-out—he questioned the clarity of awareness. By saying Jaiswal looked “lost in his own world,” the former India batter highlighted a familiar theme in top-level cricket: when the batter’s mental map doesn’t update fast enough, even routine strike rotation becomes dangerous. That said, the dismissal wasn’t painted as purely a batter-only mistake. The “brain fade moment” label and “horrible mix-up” framing pointed to a communication failure between batters as well as Jaiswal’s brief loss of track after the collision at the crease. The fact that the run-out happened while Rahul was attempting a simple rotation made the error feel even more avoidable. The immediate impact was measurable in context. India were 47/1 when the wicket fell, and with the match later reaching 101/1 at lunch, it was clear the opening session otherwise worked—just not in the exact moment that mattered. ## What it means for India: Padikkal comes in, focus shifts fast When Jaiswal was dismissed, Devdutt Padikkal replaced him at the crease. That’s where the psychological part of Test cricket kicks in: not only do you replace a batter, you also repair the rhythm of a partnership before the new spell of bowling and field changes arrive. This was also not a random statistical oddity in the wider story of Jaiswal’s Test journey. The dismissal was noted as the third time he has been run out in Tests, which puts a spotlight on running between wickets—especially in tight conditions where a small collision or late acknowledgment can swing the call. Worth noting: this match sat within India’s two-Test series against Sri Lanka in Galle. So every batting adjustment has two layers—impact on this Test and implications for consistency across the series—because selection battles in Tests often sharpen around small technical lapses. For readers tracking technique and temperament, the next question is simple: how quickly does India tighten between-wicket communication after one of their batters is removed in a “mix-up”? The answer will show in the next partnership, and it will be watched closely by observers connected to teams and broadcast analysis, including desks covered by ESPN and CricInfo for live-match and post-day breakdowns at https://www.espn.com and https://www.espncricinfo.com. ## Conclusion: one wicket, but a loud warning Jaiswal’s run-out at Galle—32 off 37—was a classic Test chaos moment: a leg-side nudge, a crease misread, and a brief lapse after contact with the bowler. Manjrekar’s “lost in his own world” line wasn’t just criticism—it was a warning about awareness under pressure. Next time India will want Rahul and Jaiswal to synchronize instantly, because Tests don’t forgive second thoughts. ## Related Articles - [Jose Hazlewood becomes ninth Australian to 300 Test wickets in 2026](https://technosports.co.in/hazlewood-becomes-ninth-australian-300-wickets/) - [Gill and Jaiswal get in their drills ahead of Sri Lanka Tests (2026)](https://technosports.co.in/gill-and-jaiswal-drills-sri-lanka/) - [Indian](https://technosports.co.in/category/athletes/indian/) --- ## FAQs ### Why did Jaiswal get run out in Galle? He was run out for 32 off 37 after a “horrible mix-up” during the final ball of the 11th over, following KL Rahul’s leg-side nudge off Keshara Nuwantha and a collision that disrupted Jaiswal’s balance and awareness. ### What did Sanjay Manjrekar say about Jaiswal’s dismissal? Manjrekar said Jaiswal “seemed to be lost in his own world” while discussing the run-out, as quoted in coverage of his on-air comments. ### What was the score when Jaiswal was dismissed? India were 47/1 when Jaiswal was dismissed, with KL Rahul at the other end. ### Who came in after Jaiswal’s wicket? Devdutt Padikkal replaced Jaiswal at the crease after the run-out. ### Was this Jaiswal’s first run-out in Tests? No—coverage noted it was the third time he has been run out in Tests.