India T20I Lowest completed totals: Match Records
Written and checked by CricketTakenPublished Cricket in India9 min read
India's lowest completed total in a men's T20 international is 74, made in 17.3 overs against Australia at the Melbourne Cricket Ground on 1 February 2008. Australia knocked it off for the loss of one wicket in 11.2 overs. That was India's twenty-eighth T20 international; eighteen years and more than two hundred and fifty matches later, nobody has managed to take the record off it.
The nearest anyone has come was England at Trent Bridge on 7 July 2026, when India were bowled out for 76 in 11.4 overs chasing 202. That innings holds a different record — it is the fastest India have ever been dismissed in the format, and the 125-run defeat is the heaviest they have suffered by runs.
Seventeen India innings have finished under 130 runs. The full list of the lowest is below, followed by what the distribution across eras looks like once you account for how many more T20 internationals India now play.
India's lowest completed T20I totals
| Score | Overs | Innings | Opponent | Ground | Match date | Result |
|---|---|---|---|---|---|---|
| 74 | 17.3 | 1st | Australia | Melbourne | 1 Feb 2008 | Lost by 9 wickets |
| 76 | 11.4 | 2nd | England | Nottingham | 7 Jul 2026 | Lost by 125 runs |
| 79 | 18.1 | 2nd | New Zealand | Nagpur | 15 Mar 2016 | Lost by 47 runs |
| 81/8 | 20.0 | 1st | Sri Lanka | Colombo (RPS) | 29 Jul 2021 | Lost by 7 wickets |
| 92 | 17.2 | 1st | South Africa | Cuttack | 5 Oct 2015 | Lost by 6 wickets |
| 101 | 18.5 | 1st | Sri Lanka | Pune | 9 Feb 2016 | Lost by 5 wickets |
| 102 | 19.5 | 2nd | Zimbabwe | Harare | 6 Jul 2024 | Lost by 13 runs |
| 110/7 | 20.0 | 1st | New Zealand | Dubai (DICS) | 31 Oct 2021 | Lost by 8 wickets |
| 111 | 18.5 | 2nd | South Africa | Ahmedabad | 22 Feb 2026 | Lost by 76 runs |
| 118/8 | 20.0 | 2nd | South Africa | Nottingham | 16 Jun 2009 | Lost by 12 runs |
| 118 | 20.0 | 1st | Australia | Guwahati | 10 Oct 2017 | Lost by 8 wickets |
| 119 | 19.0 | 1st | Pakistan | New York | 9 Jun 2024 | Won by 6 runs |
| 120/9 | 20.0 | 1st | England | Eden Gardens | 29 Oct 2011 | Lost by 6 wickets |
| 124/7 | 20.0 | 1st | England | Ahmedabad | 12 Mar 2021 | Lost by 8 wickets |
| 124/6 | 20.0 | 1st | South Africa | Gqeberha | 10 Nov 2024 | Lost by 3 wickets |
| 125 | 18.4 | 1st | Australia | Melbourne | 31 Oct 2025 | Lost by 4 wickets |
| 126/7 | 20.0 | 1st | Australia | Visakhapatnam | 24 Feb 2019 | Lost by 3 wickets |
A completed innings means one that ended in all ten wickets falling or in the full twenty overs being bowled. Rain-shortened innings are excluded and discussed separately below.
Melbourne, February 2008
India were the reigning world Twenty20 champions and had just won the Commonwealth Bank Series one-day tri-series. The T20 international that followed at the MCG was the only one of the tour. Australia bowled first; Nathan Bracken took three for 11 in 2.3 overs and Adam Voges two for 5, and India slid to 20 for 4.
Irfan Pathan's 26 was the only score above ten. India hit three fours in the whole innings and not a single six, which dates the innings more precisely than the year does. In 2008 a Twenty20 side could be dismissed for 74 without clearing the rope once and nobody thought it strange; in 2026 that would read as a misprint.
Trent Bridge, July 2026
The Nottingham innings is the modern version of the same failure. England made 201 for 7, Phil Salt scoring 70 from 44 balls, and India lost their tenth wicket in the twelfth over of the reply. Josh Tongue took four for 28 and Jofra Archer three for 29.
Unlike Melbourne, this was not a low-scoring innings — it was a fast one. India hit five sixes and five fours in 70 balls, which works out at a boundary every seven deliveries and a strike rate above 100 for a side that scored 76. The dismissal pattern is what modern collapses look like: nobody defended, nobody survived, and the innings was over in less time than the powerplay plus five overs. It was also India's second sub-130 innings of 2026, following the 111 against South Africa at Ahmedabad five months earlier.
The rain-shortened exceptions
Three India innings have finished below 74 without being complete in the sense used here. India were 15 for 0 after two overs against West Indies at Lauderhill in August 2016 when the match was abandoned; 28 for 2 after 3.5 overs against South Africa at Bengaluru in June 2022, again abandoned; and 47 for 2 in 6.5 overs against Ireland at Malahide in August 2023, which India won by two runs on a revised target.
None of those is a low total in any meaningful sense, which is why the convention exists. The one genuinely small completed innings from a reduced match belongs in the record for a different reason: 67 for 5 in eight overs against New Zealand at Thiruvananthapuram in November 2017, which India defended, and which appears on the lowest totals India have defended page.
The only one they won
Sixteen of the seventeen totals in the table ended in defeat. One produced a win.
New York, 9 June 2024: India were bowled out for 119 in 19 overs, having been 89 for 4 before losing their last six wickets for 30. Rishabh Pant made 42; Naseem Shah and Haris Rauf took three wickets each. Pakistan, needing 120 on a Nassau County pitch that had already produced the lowest-scoring matches of the tournament, reached 80 for 4 and finished on 113 for 7. Jasprit Bumrah took three for 14 in four overs and Hardik Pandya two for 24.
It is the lowest total India have successfully defended in a full-length T20 international, and it happened in the group stage of a World Cup India went on to win. The match sits in both the India versus Pakistan T20I record and the account of the 2024 T20 World Cup.
Distribution by period
Counting India innings under 130 runs against the number of T20 internationals played in the same window:
| Period | Matches | Innings under 130 | Rate |
|---|---|---|---|
| 2006-2011 | 31 | 3 | 1 in 10 |
| 2012-2016 | 47 | 3 | 1 in 16 |
| 2017-2020 | 59 | 2 | 1 in 30 |
| 2021-2023 | 79 | 3 | 1 in 26 |
| 2024-2026 | 71 | 6 | 1 in 12 |
The last row is the one that resists explanation by scoring rates. India's average T20 international total is higher now than it has ever been, and their most recent period is also the period in which they have been bowled out cheaply most often. Six sub-130 innings in seventy-one matches is a worse rate than any window since 2011.
Two things are going on. The first is that India's batting method has changed: a side that attacks from the first over will occasionally be four down in the fourth, and the trade the modern order makes is a higher mean for a longer tail. The second is opponent quality — three of the six recent collapses came against England and South Africa, both of whom now field pace attacks built specifically for the powerplay.
Who has bowled India out cheaply
Among the seventeen entries, Australia and South Africa appear four times each, England three times, New Zealand and Sri Lanka twice each, and Zimbabwe and Pakistan once each.
There is nothing here against the West Indies, Bangladesh, Afghanistan or Ireland, which is what you would expect given the fixture list, and the two entries against opponents outside the top group are worth noting for opposite reasons. The 102 at Harare in July 2024 came against a Zimbabwe attack that had only 115 to defend: Tendai Chatara took three for 16, Sikandar Raza three for 25, and Shubman Gill's 31 was India's top score in a much-changed side playing days after the World Cup final. The 119 at New York against Pakistan is discussed above.
By ground, Melbourne and Nottingham each appear twice — the MCG for the record itself and for the 125 in October 2025, Trent Bridge for the 76 of 2026 and the 118 for 8 against South Africa in the 2009 World Twenty20.
Four things the list shows
Ten of the seventeen innings ended with India all out; seven ended with wickets in hand at the end of twenty overs. The distinction matters: 110 for 7 in twenty overs against New Zealand at Dubai in the 2021 World Cup was a batting failure of a different kind from 76 in 11.4, and the two are only comparable at all because both were completed.
Five of the seventeen came in the second innings, and only three of those were chases of a target under 135: the 79 at Nagpur, the 102 at Harare and the 118 for 8 at Trent Bridge in 2009. Low totals in this format overwhelmingly happen when a side bats first with nothing to aim at, or when the target is large enough that the innings falls apart under it.
The record itself has now stood for eighteen years and has never been within two runs of falling. India have come below 80 three times in 287 matches, and the two occasions since 2008 both came against teams who had just made more than 125.
Finally, low totals are not correlated with low match aggregates. Melbourne 2008 produced 149 runs across both innings; Trent Bridge 2026 produced 277, more than several matches India have won. The other end of that scale is on the highest T20I match aggregates page, and the reverse of this list — the totals India have piled up in the same era — runs through the most sixes in a T20I innings record. The story of how the format's scoring norms moved is set out in the history of India in T20 internationals, with the wider game covered across the cricket in India hub.
Sources and method
Totals are taken from India's men's T20 international scorecards and checked against ESPNcricinfo's Statsguru lowest-innings-totals record for India in T20 internationals, which applies the same completed-innings convention used here: an innings counts if all ten wickets fell or the full allotted overs were bowled.
The period table counts matches from the official result list, excluding the nine fixtures abandoned without a ball bowled, and counts innings under 130 from the ranked totals list. Rates are rounded to the nearest whole match and are descriptive rather than a test of anything.
Bowling figures, individual scores and margins are as recorded on the scorecards. Statements about why an innings collapsed, or about what a pitch was doing, are readings of contemporary reports rather than computed values. Figures are current to 19 August 2026 and cover matches completed before that date.