Skip to content
CricketTaken

India's Highest Successful T20I Chase: 211 & Full List

By CricketTaken EditorialPublished Cricket in India9 min read

How this is written and checkedReport an error

Sri Lanka made 206 for 7 at Mohali on 12 December 2009 and India passed it with five balls unused, Virender Sehwag making 64 from 36 and Yuvraj Singh finishing on 60. Their 211 for 4 was then the largest total any side had chased down in a Twenty20 international. Seventeen years later it is still India's largest, which is a strange thing to be able to say about a format that has otherwise been rewritten twice over since.

A ranking of chases is not the same as a ranking of scores. A chase stops the moment the target is passed, so the number in the first column is set by the opposition rather than by India, and the interesting information sits in the two columns beside it: how many overs were used, and how many wickets were left. Those two figures separate a stroll from an escape, and this list contains both.

Twenty India chases have reached 173. Six of them came against Australia. Ten of the twenty finished with exactly six wickets in hand, one finished with two, and one with nine.

India's twenty largest completed T20I chases

# India Overs Opponent Venue Date Won by
1 211/4 19.1 Sri Lanka Mohali 12 Dec 2009 6 wickets
2 209/4 18.4 West Indies Hyderabad 6 Dec 2019 6 wickets
3 209/8 19.5 Australia Visakhapatnam 23 Nov 2023 2 wickets
4 209/3 15.2 New Zealand Raipur 23 Jan 2026 7 wickets
5 204/4 19.0 New Zealand Auckland 24 Jan 2020 6 wickets
6 202/4 19.4 Australia Rajkot 10 Oct 2013 6 wickets
7 201/3 18.4 England Bristol 8 Jul 2018 7 wickets
8 200/3 20.0 Australia Sydney 31 Jan 2016 7 wickets
9 199/5 19.2 West Indies Eden Gardens 1 Mar 2026 5 wickets
10 195/4 19.4 Australia Sydney 6 Dec 2020 6 wickets
11 188/5 18.3 Australia Hobart 2 Nov 2025 5 wickets
12 187/4 19.5 Australia Hyderabad 25 Sep 2022 6 wickets
13 186/3 17.1 Sri Lanka Dharamsala 26 Feb 2022 7 wickets
14 182/4 20.0 West Indies Chennai 11 Nov 2018 6 wickets
15 179/1 17.0 West Indies Lauderhill 12 Aug 2023 9 wickets
16 176/4 19.1 South Africa Mirpur 4 Apr 2014 6 wickets
17 174/7 19.2 Sri Lanka Colombo (RPS) 10 Feb 2009 3 wickets
18 174/3 19.2 Sri Lanka Colombo (RPS) 6 Sep 2017 7 wickets
19 174/4 18.5 Pakistan Dubai (DICS) 21 Sep 2025 6 wickets
20 173/4 15.4 Afghanistan Indore 14 Jan 2024 6 wickets

Australia in six of the twenty

No other opponent comes close. Australia have set India a target of 175 or more and lost the match six times: at Rajkot in October 2013, at Sydney in January 2016 and December 2020, at Hyderabad in September 2022, at Visakhapatnam in November 2023 and at Hobart in November 2025. Three of those were in Australia.

Sri Lanka and West Indies appear four times each, New Zealand twice, and England, South Africa, Pakistan and Afghanistan once each. The absence of anything against Bangladesh, Zimbabwe or Ireland is a reminder of what this list actually measures — it needs a large target, and only a strong batting side sets one.

The Australia cluster also has a shape. Five of the six came after 2015, and the two at Sydney are separated by almost five years and produced the same outcome from very different positions. What the pattern says about the fixture more generally is set out in the India-Australia rivalry.

Visakhapatnam, and the chase that nearly wasn't

The third entry is the tightest. Australia made 208 for 3 at the ACA-VDCA Stadium on 23 November 2023, Josh Inglis reaching 110 from 50 balls. Suryakumar Yadav made 80 from 42 for India, but three wickets fell in three balls in the final over and India needed one from the last delivery with two wickets standing. Rinku Singh hit a six off a no-ball to finish it.

Two wickets and one ball is the narrowest margin on the list by both measures. The next-tightest are the 187 for 4 at Hyderabad in September 2022, also completed with a ball to spare, and the two chases finished in the twentieth over at Sydney in 2016 and Chennai in 2018.

The three that were never in doubt

At the other end are the chases that ended early. India passed a target above 200 at Raipur on 23 January 2026 with twenty-eight balls unused, reaching 209 for 3 in 15.2 overs — the fastest chase of that size they have completed. At Indore on 14 January 2024 they took 15.4 overs to make 173 for 4 against Afghanistan, and at Lauderhill on 12 August 2023 they reached 179 for 1 in seventeen overs against West Indies, losing a single wicket.

The Lauderhill match is the only nine-wicket win on the list. It was built on an opening stand of 165 between Yashasvi Jaiswal and Shubman Gill, which is among the largest in the record of India's biggest T20I opening partnerships.

Mohali 2009, and why the top of the list is old

The 211 at Mohali has now stood for more than sixteen years, which sits oddly against everything else about Indian T20 batting in that time. The highest totals India have made batting first have climbed from 218 to 297 in the same period.

The explanation is arithmetic rather than ability. To break a chasing record India need the opposition to set them a target above 211, and to then get it. Targets of that size are set against India rarely, and when they have been the match has usually ended in a defeat rather than a record chase. The very biggest Indian run-scoring days have come batting first, where nothing stops the innings early.

That asymmetry applies to every country and it is why chasing records move so much more slowly than totals. The same effect is visible in the fifty-over game, where India's largest completed ODI chases also sit well below their highest first-innings scores.

Home and away, split down the middle

Ten of the twenty were made in India and ten away or at neutral grounds — Auckland, Sydney twice, Bristol, Hobart, Lauderhill, Mirpur, Colombo twice and Dubai. That is a much more even split than any other Indian batting record of this kind, and it reflects the plain fact that a chase depends on a target rather than on a surface prepared to suit the home batting order.

The two Colombo entries, both at the R Premadasa and both against Sri Lanka, came eight and a half years apart and were both completed in 19.2 overs, one with three wickets in hand and one with seven. The India-Sri Lanka T20I head-to-head has more of that kind of repetition than any other fixture India play.

The Dubai entry from September 2025 came against Pakistan in the Asia Cup, and the Eden Gardens chase on 1 March 2026 came in the T20 World Cup India won at home.

Nine of the twenty since 2022

Two of the twenty are from 2009, one each from 2013, 2014, 2016 and 2017, two from 2018, one from 2019, two from 2020, and nine from 2022 onwards.

The recent concentration is the expected shape for a batting record in this format, but it is milder than it looks. Chasing 175 was already normal by 2013, and the top of the list has not moved at all in that time. What has changed is the frequency: nine qualifying chases in five years against eleven in the thirteen years before them.

What has not changed is the comfort level. Eighteen of the twenty finished with at least five wickets standing, and that ratio is the same in the recent group as in the older one. A chase of this size, for India, has almost always been either straightforward or a one-ball finish, with very little in between. The broader account of how the side came to bat this way is in the guide to India's T20 international history, and the country's game as a whole in the guide to cricket in India.

Three readings

The first is that ten of the twenty ended on exactly four wickets down. That is a coincidence of sample size rather than a fact about batting, but it does show how narrow the normal band is: a successful chase of this size almost always costs three, four or five wickets, and anything outside that range is a story.

The second is that the wickets column and the overs column disagree more often than they agree. The 199 for 5 at Eden Gardens used 19.2 overs and cost five wickets; the 179 for 1 at Lauderhill used seventeen and cost one. Between them sit fourteen matches in which one measure looked comfortable and the other did not.

The third is what the list leaves out. India have chased successfully many times in matches shortened by rain, and those innings are excluded because a total of 130 in eleven overs is not comparable to 211 in nineteen. Lost chases do not appear here either, however large the total India made in them — the 244 for 4 that fell one run short at Lauderhill in 2016 is the obvious case, and it is the reason the top of this list looks smaller than it should. The mirror image of this page, India's biggest T20I wins by runs, covers the matches where the batting happened first, and the T20I record against South Africa covers the one opponent who appears here only once.

Sources and method

The ranking was assembled with ESPNcricinfo's Statsguru, filtering India's Twenty20 international team innings to those batted second in a match India won, then ordering by runs. Scores, overs, opponents, venues and dates are as returned by that query, checked in August 2026 and covering all men's T20 internationals to that date. No records page publishes "highest successful chases" for a single country, so this is a derived list rather than a quoted one.

The "Won by" column is calculated, not quoted: a side that completes a chase wins by ten minus the number of wickets it has lost, so 211 for 4 is a six-wicket win and 209 for 8 a two-wicket win. Balls remaining are calculated the same way from the overs figure and were verified against scorecards for Mohali 2009, Hyderabad 2019, Auckland 2020 and Visakhapatnam 2023. Targets, individual scores and match detail are quoted only for those four matches and for the Lauderhill opening stand, each of which was checked against a published scorecard; elsewhere the page describes what the table shows rather than adding numbers that were not confirmed. Rain-affected chases in which the innings was reduced are included by the query only where India batted second and won, and no adjustment has been made for revised targets.