Jitesh Sharma’s return to the crease against Delhi Capitals turned into a tough watch, with the RCB wicketkeeper-batter unable to settle or build any meaningful rhythm. Coming in with the expectation that he would help accelerate at the end, he produced only 14 runs from 20 deliveries—hitting just one boundary—before Lungi Ngidi bowled him in the final over as RCB’s chase of momentum late in the innings failed to materialise. The defending champions, once heading toward a hefty total, ended up on 175/8 after their finishers could not deliver when it mattered most, and Jitesh in particular looked off the pace during the closing overs, struggling to time the ball and rotate strike under pressure.
RCB’s late-innings fade and the road to 175/8
RCB’s struggles in the final phase were stark: they managed just one six and a single four in their last six overs, a sharp drop in tempo that ultimately cost them the chance to set a truly intimidating target.
- Jitesh scored 14 off 20 balls, with only one boundary during his stay.
- RCB finished the innings at 175/8, after losing control at the death.
- The team’s late surge was limited to just one six and one four in the last six overs.
From AB de Villiers chat to a real-life “crunch” moment
After the match, a clip of Jitesh’s conversation with AB de Villiers ahead of IPL 2026 resurfaced online and went viral. In that interaction, he described a mindset he has when batting—one that involves hoping for a collapse higher up so he can walk in with the game already tense, then use the pressure as motivation rather than a burden.
Jitesh’s mindset: pressure as an opportunity
In the YouTube conversation, Jitesh said he even prays for the top order to lose wickets so he can arrive and attempt to turn the match with impactful batting. He also talked about staying present—controlling breathing, checking the scoreboard, understanding what is needed versus what isn’t, and focusing on the specific situation in front of him, including the bowler and the shots required—so that pressure gradually fades.
“You won’t believe, I always pray to God, let my top order get collapsed and I can bat and score. I see it as an opportunity to become a hero. I always visualise such innings in my life. I am such a person; I have always wanted to do something magical. Being in the present, focus on your breathing, seeing the scoreboard, what’s required, what’s not required, calculating such things, being yourself, I think help me to handle that pressure. Be yourself, focus on your own assets. What shot should be required now, which bowler is bowling, focusing on such things, so automatically your pressure just goes away,” Jitesh told AB de Villiers on his YouTube channel.
How the “magic” scenario played out vs DC
Jitesh’s match situation mirrored the exact script he had described. With RCB placed at 131/4 in 12.4 overs, he had the time and platform to create the kind of moment he often imagines. Instead, Delhi Capitals kept applying pressure, never allowing him to find real comfort at the crease. He struggled to settle throughout the spell, and even a free hit did not produce a boundary—highlighting how difficult the required execution became under the circumstances.
- RCB were 131/4 in 12.4 overs when Jitesh came in.
- Delhi Capitals maintained pressure throughout his innings.
- He could not find a boundary even off a free hit.
Jitesh’s struggles continue: numbers against pace in IPL 2026
This outing added to a difficult phase for Jitesh with the bat in IPL 2026. Beyond a rapid 23 against LSG, he has struggled to get going, with scores of 0, 5, 10, and 14—including the latest knock versus DC. His problems against pace have been especially evident. In five innings, he has managed just 22 runs off 29 balls, dismissed every time, posting an average of 4.4 and a strike rate of 75.86—figures that underline his ongoing challenges against quicker bowling.
- Scores this season include: 0, 5, 10, 14, plus a quick 23 versus LSG.
- In five innings, he has totalled 22 runs from 29 balls.
- He has been dismissed in each of those five innings.
- Strike rate: 75.86; average: 4.4.
