Ishan Kishan Ruled Out of Third T20I in Wellington: BCCI Confirms Adductor Strain Keeps Him Sidelined as India Chase a Series Win

India will try to seal the five-match T20I series in Wellington on Tuesday without Ishan Kishan. The BCCI confirmed on Monday that the wicketkeeper-batter is recovering well from a low-grade right adductor strain but is yet to regain match fitness — and bowling coach Morne Morkel called his absence a precaution. Here is the exact wording, the cover in place, and what it means for the decider.

Highlights

  • The BCCI confirmed on Monday, October 26, that Ishan Kishan is ruled out of the third T20I against New Zealand, to be played on October 27, 2026 in Wellington
  • Kishan sustained a low-grade right adductor strain during the first T20I, missed the second T20I as well, and is yet to regain match fitness despite recovering well
  • Kumar Kushagra, called up as cover before the second T20I, will continue to be with the team for the third T20I
  • India lead the five-match series 2-0, so a win in Wellington would seal the series with two matches to spare

The BCCI update, in its exact words

Ishan Kishan has been ruled out of the third T20I between India and New Zealand, the Board of Control for Cricket in India (BCCI) said on Monday (Indian Express).

The board’s update, posted on X on Monday and quoted in full by the Indian Express, read:

“Ishan Kishan is recovering well from his low grade right adductor strain, which he sustained during the first T20I of the series against New Zealand.

He is yet to regain match fitness and is ruled out of the third T20I to be played on October 27, 2026 in Wellington. The BCCI Medical Team is monitoring Ishan’s progress.

Kumar Kushagra will continue to be with the team for the third T20I.” (Indian Express)

Three things in that short statement do the real work. First, the injury is described as low grade — this is a short-term strain, not a tear that ends a tour. Second, the phrase “yet to regain match fitness” is the operative test: recovering well in training is not the same as being cleared for a full international. Third, there is no return date — the BCCI Medical Team is simply “monitoring” progress, which leaves the fourth and fifth T20Is open rather than ruled in or out.

“Just as a precaution”: what Morkel added

India’s bowling coach Morne Morkel used the same framing at the pre-match press conference in Wellington. Injured wicketkeeper-batter Ishan Kishan will be unavailable for the third T20 International against New Zealand as a precautionary measure, Morkel said on Monday, October 26, 2026 (The Hindu).

His quote, in full:

“Ishan is doing well. He will be training today. For tomorrow, I think he is not available for selection, just as a precaution,” Morkel said at the pre-match press conference in Wellington. (The Hindu)

The Economic Times’ report of the same press conference carried the identical quote (Economic Times). That “training today” detail matters: a player who is training but not being risked in a match is on the standard return-to-play ladder for an adductor problem — and the right adductor is a group of muscles located on the inner side of the thigh (The Hindu), a group a wicketkeeper-batter uses on almost every movement behind the stumps and between the wickets.

AI-generated illustration of a cricket physio treatment table with an ice pack, resistance band and medical bag beside a stadium pitch at dusk, with no people shown

How we got here: an injury in the opener, an absence in the second

The timeline is short and consistent across reports. The 28-year-old had suffered a right adductor strain during the series-opener last week (The Hindu). Kishan missed the second T20I and didn’t bat in the first, and is yet to recover fully from the low-grade right adductor strain that he suffered in the former (Indian Express).

That sequence — injured in the first match without batting in it, then absent from the second — is worth stating plainly, because it corrects a loose version of events: Kishan was not a playing figure in the second T20I at all. His replacement in the playing XI was the teenager Vaibhav Sooryavanshi: Kishan had missed the second T20I as well, with teenage batting sensation Vaibhav Sooryavanshi replacing him in the playing XI (The Hindu).

The squad cover arrived at the same time. The board had called up Kumar Kushagra as backup for Kishan before the second T20I (Indian Express), and Kushagra is an uncapped wicketkeeper-batter who was added to the squad as cover for Kishan (The Hindu). Monday’s update confirms he stays: “Kumar Kushagra will continue to be with the team for the third T20I,” the BCCI said (Economic Times).

What the second T20I showed about life without Kishan

India did not just cope without Kishan in Christchurch — they produced a landmark win, though it was far closer than the series scoreline suggests. India became the first team in the world to complete 200 wins in T20Is after defeating New Zealand by 4 wickets in the 2nd T20I at the Hagley Oval in Christchurch on Saturday, October 24 (News9). We covered that milestone in detail in India’s record 200th T20I win.

The chase itself showed both the depth and the risk in the reshuffled order. Sooryavanshi had been moved out of the opening spots for the first time in his fledgling international career in the second T20I, ended up scoring just four runs in eight balls before falling to Nathan Smith in the seventh over, and India had their backs against the wall for much of their chase of a target of 181 before Tilak Varma and Nitish Kumar Reddy turned it around in the death overs and took India over the line with one ball to spare (Indian Express). The full match story is in our 2nd T20I report.

Read together, those two facts frame Tuesday’s selection question honestly. The No. 3 experiment produced four runs; the rescue came from the middle and lower order. Winning a decider the same way twice is a plan that relies on repeat heroics — which is why Kishan’s absence is a cricketing problem, not just a medical bulletin.

AI-generated illustration of a floodlit cricket stadium in Wellington at night during a T20 match, a batsman shown in silhouette from behind, with harbour hills in the background

What it means for the Wellington decider

India lead the five-match series 2-0 going into the third T20I and will be looking to seal a series win on Tuesday (Indian Express). The Hindu’s report likewise confirms India lead the five-match series 2-0 (The Hindu).

On the batting order, the immediate consequence is continuity rather than another reshuffle. Kishan’s continued absence possibly means that India will be sticking with 15-year-old Vaibhav Sooryavanshi in the No. 3 role (Indian Express). The Times of India reported the same shape to the decision: Kishan’s absence gave Sooryavanshi an opportunity in the playing XI for the second T20I, and India have won the first two matches to lead the five-match series 2-0, with the third T20I to be played in Wellington on October 27 (Times of India).

The balance of risk favours caution — and the schedule allows it. With a 2-0 lead, India can lose in Wellington and still lead the series; rushing an adductor strain back for a match they do not strictly need to win is how a low-grade problem becomes a tour-ending one. Morkel’s “just as a precaution” and the BCCI’s “yet to regain match fitness” point the same way: the decision was made by the calendar as much as by the scan.

The real test is No. 3. Sooryavanshi’s four off eight in Christchurch came in a new role, in overseas conditions, in a chase that was collapsing around him — context that argues for backing him again rather than judging him on one innings. But New Zealand now have a full match of footage of him at No. 3, and a series on the line. If India seal the series on Tuesday, the final two matches become the natural window for Kishan’s return — if the medical team clears him. If they do not, the question stops being about one teenager’s innings and becomes about whether India protect their first-choice wicketkeeper-batter for what comes after this tour. The BCCI’s statement, notably, promises nothing either way.

Leave a Reply

Your email address will not be published. Required fields are marked *