Kishan Said 'My Best Game Comes Under Pressure' — Then Proved It With 270

The story of Ishan Kishan's 2026 is the story of a man who was told, in the most public way possible, that he wasn't needed. Dropped from the India setup. Told to go back to domestic cricket and prove himself. The kind of messaging that, for most players, is a polite career obituary dressed up as an opportunity.

On September 7, in the searing Chennai heat at the MA Chidambaram Stadium, Kishan responded in the only language that truly matters in cricket: runs. Not a polite, steady-the-ship 60. Not an aggressive cameo. A monumental, record-shattering, history-making 270 off 334 balls in the Duleep Trophy final — the highest score ever by a wicketkeeper-batter in the tournament's history. He batted for 522 minutes. He hit 30 fours and seven sixes. He retired hurt from sheer fatigue at 250, came back, and kept going.

Three national selectors sat in the stands. Chief selector Ajit Agarkar among them. They watched every single ball.

Kishan's 270 didn't just break one record — it bulldozed through an entire shelf of them. The previous highest score by a wicketkeeper-batter in Duleep Trophy history was Dinesh Karthik's 183, set in the 2010 final. Kishan smashed past it by 87 runs. In a final. While captaining his side. While the selectors took notes.

He became only the seventh batter in the tournament's history to score a double century in a Duleep Trophy final, joining a list that includes Mansoor Ali Khan Pataudi, Raman Lamba, Anshuman Gaekwad, Yusuf Pathan, Cheteshwar Pujara, and Yashasvi Jaiswal. His 270 is now the second-highest score in any Duleep Trophy final — behind only Raman Lamba's 320 from 1987.

He also became the first East Zone batter ever to score a double century in a Duleep Trophy final. In the process, he crossed 4,000 first-class runs — a milestone that seemed irrelevant three years ago when he was India's white-ball wicketkeeper pick and red-ball cricket appeared to be someone else's problem.

If Kishan's knock was the earthquake, Aakash Chopra's commentary was the aftershock that arrived the next morning. Speaking on his YouTube channel — which, in Indian cricket discourse, functions as an unofficial selection committee press briefing — Chopra didn't just praise Kishan. He issued a direct warning to India's two incumbent Test wicketkeeper-batters.

Rishabh Pant is India's first-choice keeper in Tests. Dhruv Jurel has cemented himself as the primary backup, impressing with his composure in England and at home. Together, they form a seemingly airtight keeper hierarchy. Chopra's message? The lock on that hierarchy has a new key, and it's 270 runs heavy.

This wasn't idle punditry. Chopra pointed specifically to Kishan's transformation since being told to earn his stripes in domestic cricket — the willingness to grind through Ranji Trophy matches, the 173 against Tamil Nadu, the consistent red-ball output that showed intent, not just talent.

Here's what makes this story different from the usual "dropped player scores big in domestic cricket" template. Kishan didn't just survive his exile from the India setup — he fundamentally changed the way he approaches red-ball cricket.

The old Kishan was a white-ball dasher who treated red-ball innings as a formality. The criticism wasn't unfair: he'd been accused of not showing enough desire for the longer format, of treating domestic cricket as something beneath him. The BCCI essentially told him: prove you care, or we'll find someone who does.

He responded by travelling the length and breadth of India playing multi-day cricket. He led Jharkhand in the Ranji Trophy, scored a 173 against Tamil Nadu that signalled real intent, and then carried that form into the Duleep Trophy where he's been the tournament's highest run-scorer with 409 runs at an average of 102.25 across five innings.

The 270 wasn't an anomaly. It was the peak of a sustained climb that started the day he decided exile wasn't a punishment — it was an education.

Let's be honest about the uncomfortable reality: even with 270, Kishan probably doesn't walk straight into India's Test XI. Pant is immovable. Jurel has done nothing wrong. India don't play two specialist wicketkeepers, and Kishan batting at six as a pure batter is a waste of his glovework.

But cricket selection isn't just about the current XI — it's about the squad of 16, the touring party, the bench strength for a five-Test series abroad. And right now, if India were picking a squad for a long overseas tour, can you honestly leave out a man averaging 102 in the Duleep Trophy who just scored the highest ever by a keeper in the tournament's history?

Chopra's framing was precise: Kishan isn't knocking down the door. He's standing right behind it. And in Test cricket, injuries, form slumps, and rotation policies have a habit of opening doors that seemed welded shut. Pant's history with injury makes a reliable third keeper not a luxury but a necessity. Kishan has just told the selectors — with 270 reasons — that he's that man.

If you want to understand the new Ishan Kishan in a single moment, it's not the cover drives or the sixes over long-on. It's what happened at 250. Chennai heat. 500-plus minutes at the crease. Body cramping. The old Kishan would have walked off, taken the standing ovation, and called it a day. Career-best. Double century. Job done.

The new Kishan retired hurt, got treatment, watched Shami fall from the dressing room, and walked back out. He added 20 more runs, taking his total to 270 — pushing the team total to 708 and ensuring East Zone's grip on the final was absolute. Then he came back in the second innings and scored 80 off 98 balls, giving him a match aggregate of 350.

That's not a white-ball specialist playing a cameo in domestic reds. That's a man who wants a Test cap more than he wants comfort. The selectors were watching. They saw the number. More importantly, they saw the intent behind it.