India’s Test No. 3 debate has resurfaced after Devdutt Padikkal turned a chance into a statement in Sri Lanka. That matters because Team India can’t afford a “wait-and-see” selection policy when the pitch-reading, spin-handling, and top-order stability are all being tested. Here’s the thing: Padikkal’s case is no longer theoretical—it’s backed by output and by what selectors need at this stage of the cycle.
Devdutt padikkal: The problem: India needs a No. 3 who can own spin and anchor
The pressure point is simple. Padikkal has often been viewed as a replacement option, mainly because Sai Sudharsan occupied the No. 3 slot earlier and got repeated opportunities. But an argument gaining traction—according to a CricTracker analysis published on 16 Aug 2026—is that Sudharsan’s Test average doesn’t justify continued preference when Padikkal is ready to stake a more permanent claim.
Worth noting: selection isn’t just about past labels like “next big thing.” It’s about whether the batter’s skill set fits the conditions India will face across series—especially the turning tracks and long spells where one bad decision can unravel a whole session. Padikkal’s recent knock has directly fed that conversation.
Root cause: a numbers-and-fit gap at No. 3
The root cause behind the confusion is that Sudharsan’s role has been treated as safe, even as the returns have stayed modest. CricTracker’s piece highlights that Sudharsan averages 31.91 across seven Tests, with three fifties and no centuries. It also points out that ahead of the Afghanistan series, his output was 302 runs from six Tests at 27.45, underlining why the “continued preference” argument is being questioned.
That said, the case isn’t anti-Sudharsan. It’s pro-competition based on performance and suitability. Padikkal has been consistently framed as the batter who can solve India’s immediate spin concerns—something Sanjay Manjrekar stressed when he called Padikkal a “godsent” solution for spin troubles and praised his comfort against spin on slow, turning pitches (as covered by CricTracker).
Solution framework: three reasons Padikkal should become regular (with trade-offs)
Here are the three key reasons being pushed forward in the current debate—and the downside of each approach, because no option in Test cricket is perfect.
1) Padikkal’s Sri Lanka Test impact makes “replacement-only” look outdated
Padikkal’s case got a real-time boost in Colombo and Galle. He was praised after an unbeaten 142 against the Sri Lanka Cricket XI, and that knock strengthened the argument that he could be more than a one-off selection.
Then, in the Test window at Galle, the narrative snapped into focus: Padikkal was described as a batter who could replace Sai Sudharsan at No. 3, and he responded with an unbeaten 131 off 178 balls on Day 1, his maiden Test century. That’s not just runs—it’s role certainty. When your top-order batter can score in a measured rhythm while the ball turns, selection becomes easier.
Trade-off: making him regular too quickly could increase pressure on his technique if the next conditions don’t suit his strengths. If the pitch is flatter than expected, the same patience that helped in Sri Lanka might not translate into big scores immediately.
2) Sudharsan’s Test production gap supports a merit swap at No. 3
CricTracker’s analysis leans on a selection logic many fans understand instantly: if one player’s Test average is 31.91 across seven Tests with no centuries, and another batter has just demonstrated a No. 3-ready profile, you can justify a role change. The earlier “he’s still settling” argument starts to weaken when the team needs consistently high output in the middle overs of batting innings.
Manjrekar’s comments strengthen that logic by focusing on conditions, not just numbers. He highlighted how Padikkal can handle spin better on slow, turning pitches—exactly where No. 3 batters often become the difference between building a platform and losing control.
Trade-off: switching No. 3 can destabilize the batting order if Sudharsan still has form bursts and the team’s plan was built around his specific strengths. A wrong timing in rotation can cost an innings even when the decision is justified on paper.
3) Experience at first-class level gives Padikkal the “repeatability” India needs
Selectors worry about repeat performances, not just debut bursts. A separate profile cited by CricTracker noted Padikkal has played 56 first-class matches, scored 3,800 runs, and has 9 centuries and 21 fifties. That profile matters because Test cricket rewards temperament and the ability to reproduce patterns—especially when handling different attack styles and pitch behaviors.
There’s also a continuity angle: Padikkal made his maiden Test appearance against England in early 2024 as a replacement for Rajat Patidar. That indicates he’s not arriving as a completely untested name; he’s been in the international conversation and can build on prior exposure.
Trade-off: first-class success doesn’t always guarantee immediate Test conversion in high-pressure phases. If India chooses him for permanence and he struggles early, the confidence cycle can become a problem, and the team may need to react mid-series.
Conclusion: if India wants a settled No. 3, they should pick Padikkal—and commit
This debate is trending because it’s no longer about “who looks good.” It’s about the combination of a credible Test-ready century at Galle, an unbeaten 142 in a Sri Lanka XI context, a clearer match between skill and turning pitches, and a statistical case that Sudharsan’s returns—31.91 average across seven Tests—may not justify blocking the next step.
Related Articles
- Devdutt Padikkal century vs SLC XI: India’s warm-up boost 2026
- Padikkal comes in as India bat in Galle 50th Test: Nuwantha debuts
- Padikkal’s maiden century leads India’s dominance
FAQs
Why does Devdutt Padikkal deserve a regular spot in the India XI?
Because the current argument pairs output with fit: his unbeaten 131 at Galle supports his case for the No. 3 role, and Manjrekar specifically cited his comfort against spin on slow, turning pitches.
What did Padikkal do in Sri Lanka that boosted his case?
He was praised after an unbeaten 142 against the Sri Lanka Cricket XI in Colombo, which added weight to the view that he’s ready for a more stable Test role.
Does this decision depend only on replacing Sai Sudharsan?
Not purely. The selection logic being argued is broader—Sudharsan’s Test average of 31.91 across seven Tests is part of the case, but Padikkal’s first-class record (56 matches, 3,800 runs, 9 centuries) and spin-handling are equally central.
How does “No. 3” change the pressure on the batter?
No. 3 is where India often faces either the first real challenge of the pitch or the sharper phase of the opposition’s bowling plan. That’s why Padikkal’s ability against spin on turning surfaces has been singled out.
Is Padikkal’s claim tied to one match?
No. The debate stacks multiple signals: his maiden Test century at Galle, his performance in the Sri Lanka XI game, and his domestic track record for repeat scoring under different conditions.
Closing takeaway: If India’s goal is a reliable No. 3 for spin-heavy contests, Padikkal’s recent form and conditions fit make him the most logical “regular” call in 2026.
Was this article helpful?
Your feedback directly improves future articles on this site.
