Cricket Addictor
For fastest livescore in India
cricketaddictor.com

Ishan Kishan explains why Ravi Bishnoi's 29-run over wasn't the turning point

Published - 05 Jul 2026, 03:39 PM | Updated - 05 Jul 2026, 03:40 PM

Ishan Kishan And Ravi Bishnoi
Image Credits: X

India wicketkeeper-batter Ishan Kishan opened up on the costly over bowled by leg-spinner Ravi Bishnoi during the second T20I of the five-match series against England. Ishan said that the two free hits in the over helped England shift the momentum and reduced the pressure during a crucial stage of the run chase.

The Men in Blue lost the match by four wickets at Emirates Old Trafford in Manchester on Saturday, July 4. India posted 190 batting first, but England completed the chase with one over to spare and took a 1-0 lead in the five-match series. Bishnoi struggled throughout his spell and conceded 60 runs in four overs.

Free Hits Made It Easier for Him - Ishan Kishan on Ravi Bishnoi's Over

Ishan Kishan said that India felt they were in control before the costly 17th over changed the match. He admitted the free hits allowed England batter Jacob Bethell to play with more freedom and shift the momentum during the run chase.

“We were always in a situation where, we thought we had the game. But getting those free hits made it easier for him to get relief, get the pressure out of him. I think we bowled pretty well. We had our plans, but at the same time, we have to give that credit to Bethell because he took his time, he was in the middle for a very long time, and he understood when to charge the ball and who to charge.”

England needed 49 runs from the last four overs before Bishnoi's expensive over. Bethell stayed calm, settled into his innings, and attacked at the right time to put England in control after India had dominated most of the match.

We Could Have Done Better - Ishan Kishan on Costly Death Overs

Ishan Kishan admitted that India let the game slip by giving away easy scoring opportunities in the closing overs. He said that the free-hit deliveries allowed England to score big runs without the risk of losing a wicket.

Cricket Addictor — fastest live scores on Google Play

“We could have done better, maybe not just give him those free balls where he scored two sixes out of it. So, 12 runs and two balls without making any mistakes. It’s a big thing in these T20 games because it’s a very short format and we might not bowl those extra balls to him next time.”

Bishnoi conceded 29 runs in the 17th over, including two no-balls and one wide, as Bethell hit both free hits for sixes. England's equation dropped to 20 runs from 18 balls, and the hosts completed the chase in the 19th over. Shreyas Iyer blamed costly bowling errors after England defeat.

The Best Part Is We Are All Together - Ishan Kishan Backs Team India

Despite the defeat, Ishan Kishan said the dressing room remains united and focused on improving. He believes the team has played good cricket and will learn from its mistakes instead of letting one loss affect its confidence.

“Yes, we did not win but I think we have been playing good cricket. The most important thing is how we realise in each of these games where we can get better. The best part is we are all together. We are all trying to improve. Not winning makes a huge difference in your mindset as well. But I think all of us are mature here who will understand what’s going on and where we can get better as a group.”

India have now lost three of their last four completed T20Is, while captain Shreyas Iyer is still searching for his first win as India's full-time T20I captain. The visitors will look to level the series when they face England in the third T20I in Nottingham on Tuesday, July 7.

Sai Vaitla
Sai Vaitla

Sai Vaitla is an author at Cricketaddictor and he has been working since September 2022. Sai Vaitla...

Cricket Addictor — fastest live scores on Google Play
logo
Stay Updated with the Latest Cricket News from Cricket Addictor.

You will receive the latest updates on cricket news throughout the day. You can manage them whenever you need in browser settings.