Rishabh Pant doesn’t really need a spreadsheet to explain what he can do with the bat. The swagger, the unpredictability, the ability to turn an unlikely situation into something that looks simple—those are his calling cards. Yet in cricket, especially in the 20-over format, people inevitably measure impact through numbers: how often runs come, how quickly they arrive, and how those outputs swing match outcomes. That’s why Pant’s recent IPL struggles have drawn such sharp scrutiny, even though his talent has never been in doubt.
Why Pant’s IPL form is under the microscope
Viewed through the lens of results, Pant has been a noticeable letdown—both personally and for those around him. He arrived on the international T20 scene about a year and a half before his Test debut, but he is now no longer in contention for the national team “radar.” In the IPL, however, the story has been less about a dip in class and more about a string of failures, despite the fact that the league’s format often suits his aggressive instincts.
In 2025, he did manage a late lift from a disastrous run: in the final of his 14 innings, he remained unbeaten on 118, albeit in a losing effort. That knock helped bring his season tally to 269 runs, with an average of 24.45 and a strike-rate of 133.17. Still, the second season has been far tougher, and the numbers have reflected it. With Lucknow Super Giants, after an unbeaten 67 against Sunrisers Hyderabad about two and a half weeks ago, he has scored just 72 in his next five innings. That stretch includes a disappointing three-ball duck on Wednesday against Rajasthan Royals—an outing that, in many ways, summed up where he is in 20-over cricket right now.
The Wednesday collapse: situation, selection, and decision-making
That Wednesday match offered a clear case study of Pant’s extended “brain-fade” phase. Lucknow were chasing 160 on a red-soil surface that offered bite, and the innings began with a setback: Ayush Badoni was dismissed in the opening over via a run out. Pant’s reaction, by his standards, was furious—and also ill-judged. He missed the first ball, charging and swinging at a delivery from left-arm pacer Nandre Burger of South Africa. Then came a clumsy contact on a hard-length ball that only trickled toward mid-wicket. Finally, a crucial attempt outside off stump resulted in an edge that landed in Dhruv Jurel’s gloves.
What the chase required was patience and wicket control, particularly during the Power Play. Rajasthan were operating with three seamers—Jofra Archer and Brijesh Sharma were the other two—and the required run rate was not overly demanding. On a pitch that didn’t really reward reckless ambition, Pant’s choices stood out. Whether it came from ego, misplaced belief, or simply a failure to read the moment, the outcome was the same: little regard for the game situation and the conditions.
- Lucknow lost Ayush Badoni in the first over to a run out while chasing 160.
- Pant missed a first-ball charge and then followed with two more poor-risk shots, including one that went to Dhruv Jurel.
- Rajasthan used three seamers (Jofra Archer, Brijesh Sharma, and Nandre Burger), making wicket preservation in the Power Play crucial.
- The target pace was not high, and the surface did not favour overly optimistic attacking.
Where Pant is batting—and why his role matters
As captain, Pant is ideally placed to set the tone, shape a stable batting plan, and communicate it clearly with the support staff—head coach Justin Langer and strategic advisor/coach Jane Williamson. Yet, he hasn’t quite been consistent in how he’s positioned himself in the lineup.
After one tentative spell at the top as an opener ended with a run out at the bowler’s end (following a hesitation), Pant dropped to No. 3. In his most recent six innings, he has held the No. 3 spot. That slot may be the best fit for him: it gives him control over the innings, whether he arrives early (even after the second ball) or later when the field opens up post-Power Play. With two major batters—Aiden Markram and Nicholas Pooran—immediately behind him, the temptation to reshuffle could become strong. But his most productive returns have come at one-drop, and the argument is that he should keep that role for the rest of the season to rediscover his scoring rhythm.
Shot philosophy, aggression, and rebuilding confidence
Pant’s batting comes with extremes. When he pulls off something outrageous, he becomes a national highlight reel. When he plays a shot that ignores percentages, the reaction is harsher—“Stupid, stupid, stupid” is the kind of refrain that can follow. The underlying issue is not that he lacks options; he has every shot in the book, and often executes them with ease. Whether it’s driving through the covers, pulling through mid-wicket, or going for the falling hoick and an audacious reverse ramp, his range is real.
Still, the piece of advice here is simple: perhaps Pant sometimes gets tangled in which stroke to choose, given how many he can attempt. If that is the case, then slowing down slightly could help. Spend time assessing the pitch and bowling, allow the innings to settle, get a few runs on the board, and then express himself in the way he wants. With the “rub of the green” not currently flowing his way, stepping back from the edge of the chaos might be the route to more consistent outcomes.
It’s also argued that Pant needs to stop trying to force everything too soon. In a 120-delivery innings there is time to build; a batter like Vaibhav Sooryavanshi can hammer 15-ball half-centuries because conditions and momentum favour him. Pant, however, is older and more mature than a decade ago, and no longer a “man-child” in a hurry. He should avoid being a victim of expectations—especially the expectation to entertain and bat in fifth gear from the outset. When things aren’t going his way—as they have largely been for the last season and a half—the better plan is to dial down early aggression and construct an innings in a more measured, quasi-classic way. This becomes even more important because the surfaces may not always be ideal for ambitious stroke-making.
Alongside that, there is a caution about greed when the ball sits up. Pant has often been guilty of trying to hit too hard, and that’s frequently why his shape breaks. Timing and power are both his strengths, but if he abandons touch for pure muscle, he does himself little good. A six remains a six whether it clears the rope or lands in the second tier—but the point is to make sure the process is sustainable, not just the result.
Confidence recovery after setbacks
Success can breed success, but failure can also create more failure. Pant is naturally optimistic, but he isn’t immune to what’s happening around him—especially when he is captaining a side on a downward spiral with no clear end. On top of the pressure, he has to address the host broadcaster soon after each loss. Add to that his own batting misadventures, and the picture becomes one of a tense, brooding figure carrying the weight of the moment.
So how does he regain confidence? The route described is through bat-on-ball moments: striking a few from the middle, lifting the bat to acknowledge small milestones, and—most importantly—spending time at the crease. In T20 cricket, the most reliable way to score is not to get dismissed.
Injury setbacks and the road back to his T20 identity
There’s another factor in the narrative: injuries. Pant has been a recurring target for knocks, including in the last three matches. He suffered a blow to his left elbow while batting, was struck on his right forearm while batting, and took impact on his nose while trying to collect a ball from the deep. These aren’t described as major injuries, but the argument is that they disrupt rhythm—particularly when they occur during batting.
Even beyond short-term knocks, the season has carried unhelpful injury timing. Pant was set to return to the national 50-over side after a year and a half during January, but he was ruled out of the entire series due to a right-sided strain and a muscle tear picked up in the nets. That setback arrived less than six months after he broke his foot while attempting a reverse sweep against Chris Woakes in the Manchester Test.
His recovery has shown resilience. He has largely operated as “mind over matter,” returning to bat with the fracture and producing a half-century in that Test. Now the next task is to prove to himself—and to everyone watching—that the T20 version of him is still alive and kicking. To do that, he needs patience, nous, common sense, confidence, prudence, practicality, and awareness of the match situation. None of those are beyond him, and resilience has always been his defining trait.
- Pant suffered a left elbow blow while batting in one match.
- He was hit on his right forearm while batting in another.
- He was struck on his nose while trying to collect a ball from the deep.
- He later faced a right-sided strain and a muscle tear in the nets, ruling him out of the full January national 50-over series.
- Earlier, he broke his foot attempting a reverse sweep against Chris Woakes in the Manchester Test.
Even when the story turns difficult, it’s still rooted in evidence. In his first IPL season after his serious car accident, he scored 446 runs at a strike-rate of 155.40 in 2024. And in his first Test back in September that year, he struck 109 off 128 against Bangladesh. The question now is whether he can deliver another turnaround—starting with the 20-over format that has always suited his instincts. Over to you, Rishabh Pant.
