Padikkal Test Recall 167: “Perform When Given The Chance”

Devdutt Padikkal’s Test comeback story flipped in a single knock at Galle on August 16, 2026. That’s when the southpaw made 167 in the first innings against Sri Lanka.

Before this recall, the “what if” conversations had hung over his career for nearly two years—his last appearance came in November 2024. Then, in his first outing back, Padikkal turned that waiting period into runs. He batted through 230 balls, spending more than five hours at the crease before being stumped off Prabath Jayasuriya. Worth noting: his 167 came with 15 fours and 1 six.

Before The Gap, The Pressure Question Around Padikkal Test

Padikkal’s last Test appearance had come in November 2024, and the time away created a simple but brutal question for India’s selectors and fans alike—can a batter re-enter Test cricket and still control his tempo?

He joined the squad as an injury replacement for Sai Sudharsan, so the opportunity arrived quickly rather than as a planned return. That’s the “before” state: limited Test exposure for a stretch, followed by a recall that many would expect to bring nervous starts.

Instead, the innings he played at Galle International Stadium looked built for clarity, not hesitation.

The Catalyst Knock: 167 In India’s Galle First Innings Build-Up

Here’s the thing: when India reached 460-9 on the second day of the opening Test, Padikkal’s contribution stood out as the kind that stabilizes a chase—or sets the marathon narrative.

In the first innings, he made 167 off 230 balls, striking 15 fours and 1 six, then carried that momentum into the second innings with 44. Padikkal also addressed the mental side of performance after his maiden Test century.

He said, “I’ve dreamt of this moment,” and added that he had spent the last two years working hard so he could do something special when the chance came.

In the same breath, he stressed process over outcome—saying the key was not to “react all the time” and to have a couple of shots ready in his head. That clarity helped him keep pressure on Sri Lanka’s spinners throughout the spell.

After The Break: Partnerships, Spin Pressure, And The “Chance” Philosophy

After the centurion knock, what really matters is how Padikkal framed his selection moment. He told the media he hadn’t sought assurances about his future in the side, insisting that whenever the opportunity arrives, he needs to perform rather than chase conversations.

That theme—performing when given the chance—became the line fans will remember from the press room. BBC Sport‘s match coverage style also highlights how batters who manage their mindset can lift the entire innings structure.

Worth noting: in India’s first innings, Padikkal formed a 151-run stand with KL Rahul. The partnership shaped the contest’s rhythm, taking the game away from Sri Lanka’s ability to dictate the middle overs.

Rahul was later forced to retire hurt due to cramp, cutting that stand short before it could be extended further. Still, Padikkal’s job had been done—India had a backbone, and the tail-end options became easier because the pressure was absorbed earlier in the innings.

Padikkal Test Recall: Before Vs After (What Changed?)

Here’s the verdict for readers tracking India’s Test batting ecosystem: if you want to judge Padikkal’s future, don’t just look at the century headline—watch whether his shot-selection discipline holds when conditions swing. If it does, pick padikkal test momentum as the deciding factor for India’s next selection calls. For wider coverage, see ESPN.

Related Articles

• Labuschagnes Test: 42-Innings Drought Puts Him On Edge
• Rishabh Pant Test: Fastest To 100 Test Sixes—4,918 Balls
• Renshaw Test Call-Up: Weatherald Dropped for Bangladesh 2nd Test

FAQs

What did Devdutt Padikkal say

Was this article helpful?

Your feedback directly improves future articles on this site.

Great topicBoring topicWrong nicheWell writtenNeeds improvement

Thanks! Your feedback helps us improve.

Share feedback to improve articles (sends your vote only, no personal data)

Feedback saved locally only.