India ODI Highest successful chases: Match Records

Australia made 359 for 5 at Jaipur on 16 October 2013 and it was not close. India passed the target of 360 in 43.3 overs for the loss of one wicket, Rohit Sharma finishing on 141 not out and Virat Kohli reaching a hundred off 52 balls, which was then the fastest ODI century by an Indian. The final score, 362 for 1, is the largest total India have made batting second in a match they won, and no side has bettered it against Australia since.

Chasing is the part of the fifty-over game India have been best at for longest. That is partly a matter of personnel — a batting order built around players who prefer a number on the board to a blank slate — and partly a matter of where India play. A target is easier to calculate on a dry surface under lights than it is at Headingley in May.

Eighteen times India have chased down 300 or more and won. The first came in January 1998; seven of the eighteen have come since 2016. Below is the full set, ranked by the score India made rather than by the target, which is the convention ESPNcricinfo uses and which puts a chase completed with a boundary above one completed with a single.

The eighteen biggest chases India have completed

#	India	Overs	Target	Balls to spare	Opponent	Venue	Date	Won by
1	362/1	43.3	360	39	Australia	Jaipur	16 Oct 2013	9 wickets
2	356/7	48.1	351	11	England	Pune	15 Jan 2017	3 wickets
3	351/4	49.3	351	3	Australia	Nagpur	30 Oct 2013	6 wickets
4	331/4	49.4	331	2	Australia	Sydney	23 Jan 2016	6 wickets
5	330/4	47.5	330	13	Pakistan	Mirpur	18 Mar 2012	6 wickets
6	326/8	49.3	326	3	England	Lord's	13 Jul 2002	2 wickets
7	326/2	42.1	323	47	West Indies	Guwahati	21 Oct 2018	8 wickets
8	325/5	47.4	325	14	West Indies	Ahmedabad	15 Nov 2002	5 wickets
9	321/5	48.5	316	7	New Zealand	Bengaluru	7 Dec 2010	5 wickets
10	321/3	36.4	321	80	Sri Lanka	Hobart	28 Feb 2012	7 wickets
11	317/8	49.4	317	2	England	The Oval	5 Sep 2007	2 wickets
12	317/3	48.1	316	11	Sri Lanka	Eden Gardens	24 Dec 2009	7 wickets
13	316/7	47.5	315	1	Pakistan	Dhaka	18 Jan 1998	3 wickets
14	316/6	48.4	316	8	West Indies	Cuttack	22 Dec 2019	4 wickets
15	312/8	49.4	312	2	West Indies	Port of Spain	24 Jul 2022	2 wickets
16	310/4	46.5	309	19	Sri Lanka	Karachi	3 Jul 2008	6 wickets
17	308/6	44.3	305	33	England	Cuttack	9 Feb 2025	4 wickets
18	306/6	49.0	301	6	New Zealand	Vadodara	11 Jan 2026	4 wickets

The Dhaka match was played over 48 overs a side after a delay, so the balls-to-spare figure there is measured against 288 deliveries rather than 300. Every other row is a full fifty-over contest.

Jaipur, 16 October 2013

The Sawai Mansingh Stadium innings is the outlier in every direction. India lost Shikhar Dhawan early, and then Rohit and Kohli batted for the rest of the evening. Kohli's fifty came off 32 balls and his hundred off 52. India needed 360 and had 39 balls left when they got there. Only one larger target had been chased down in ODI cricket at that point, and that was the 438 at the Wanderers in 2006.

What made it possible was the rule set of that season: two new balls, five fielders inside the circle for most of the innings, and no compulsory catching positions. Every Indian chase of 350 or more comes from that window. The three biggest were all completed between October 2013 and January 2017, and nothing above 331 has been chased since. Kohli's record in this specific discipline is set out in more detail in the account of his batting in run chases.

The three targets of 350 or more

Only three of the eighteen involved a target in the 350s: 360 at Jaipur, and 351 twice — at Pune against England in January 2017 and at Nagpur against Australia a fortnight after the Jaipur game.

Pune was the harder of the two. England made 350 for 7, India lost three wickets for 63, and Kohli and Kedar Jadhav then added the bulk of the runs, Kohli making 122 and Jadhav 120. India got home with eleven balls to spare and three wickets standing. The Nagpur chase was tighter still in one sense — India needed the last of the 351 with three balls left — but they never lost more than six wickets.

Australia are the opponent in three of the top four. That is not a coincidence: the fixtures of 2013 and 2016 were played on some of the flattest surfaces of the decade and the India–Australia one-day rivalry has produced more 300-plus totals than any other India match-up.

Dhaka 1998, and the first time India chased 300

Before 18 January 1998, India had never made 300 batting second in a completed one-day international. In the deciding final of the Independence Cup at Dhaka they made 316 for 7 in 47.5 overs to beat Pakistan, who had posted 314 for 5 with Saeed Anwar making 140 and Ijaz Ahmed 117.

Sourav Ganguly made 124 and added 179 with Robin Singh, who made 82. India still needed nine off the last over from Saqlain Mushtaq, and Hrishikesh Kanitkar hit the boundary that settled it with one ball remaining. It was, at the time, the highest successful run chase in all one-day international cricket, and it is the oldest entry on this list by four and a half years.

The mark has only moved four times

Because a chase stops the moment the target is passed, the record for India's largest successful chase moves far less often than the record for their largest total. It has been reset four times in twenty-eight years.

India	Target	Opponent	Venue	Date
316/7	315	Pakistan	Dhaka	18 Jan 1998
326/8	326	England	Lord's	13 Jul 2002
330/4	330	Pakistan	Mirpur	18 Mar 2012
362/1	360	Australia	Jaipur	16 Oct 2013

The near-decade between Lord's and Mirpur is the interesting gap. India chased 321 at Bengaluru in 2010, 321 at Hobart three weeks before Mirpur, 317 at The Oval in 2007 and 317 at Eden Gardens in 2009, and none of those got past 326. Then the mark moved twice inside nineteen months and has stood ever since. Two of the four resets came against Pakistan, which is more than the India–Pakistan record in fifty-over cricket generally would lead you to expect.

Two wins by two wickets, five years apart

Three of the eighteen were won with two wickets in hand, and two of those were at English grounds. At Lord's in July 2002, in the NatWest Series final, England made 325 for 5 and India were 146 for 5 before Mohammad Kaif and Yuvraj Singh put the chase back together; India won with three balls to spare. At The Oval in September 2007 they needed 317 and got there with two balls left. The third, at Port of Spain in July 2022, also finished with two balls unused.

These are the matches that show why ranking chases by runs scored rather than by target can mislead. A chase completed off the penultimate delivery and a chase completed with 47 balls in hand are the same size on the table and nothing alike to watch.

Balls to spare, and the Hobart exception

The balls-to-spare column has a wide spread: from one at Dhaka to eighty at Hobart.

The Hobart match, on 28 February 2012, is the strangest entry here. India had to chase 321 inside 40 overs to keep a bonus point and stay alive in the tri-series, and did it in 36.4, Kohli making 133 not out off 86 balls. It is by some distance the fastest 300-plus chase India have completed, at 8.75 an over, and it stands slightly outside the logic of the rest of the list because the target that mattered was not the one on the scoreboard.

At the other end, six of the eighteen were completed with eight balls or fewer remaining. Chasing 300 in a fifty-over match remains, on this evidence, a thing India do successfully but rarely comfortably.

Where the chases happened

Ten of the eighteen were at home, five away and three at neutral venues. The five away wins came at Sydney, Lord's, Hobart, The Oval and Port of Spain — all grounds where the ball comes through at a predictable height. None came in South Africa, none in New Zealand, and none in Pakistan or Sri Lanka in daylight.

That distribution is the reverse of what happens when India bat first: India's highest ODI team totals are seventeen-twentieths a home record, while nearly half of the big chases were made outside India. Setting a huge total needs a pitch. Chasing one needs a target, and a target can be handed to you anywhere.

The mirror image of this page — the smallest scores India have managed to protect — is at India's lowest ODI totals defended, and the same discipline in twenty overs is covered at India's highest T20I chases. India's record against England across formats, including the Pune and Cuttack chases, is traced in the India–England rivalry, and the Asia Cup context for the Mirpur and Karachi wins is in the Asia Cup history. The country hub is at cricket in India.

Sources and method

Scores, overs, opponents, venues, dates and results come from ESPNcricinfo Statsguru, filtered to India's second-innings team totals in matches India won, cross-checked against the site's smallest-margin-of-victory records for the matches decided in the last over. Individual scores and match narrative come from published match reports and scorecards. Data checked in August 2026.

Two columns are computed rather than quoted. The winning margin in wickets is derived arithmetically from the wickets India lost, since a side chasing successfully wins by ten minus that figure. Balls to spare is derived from the overs India used against the length of the innings — 300 deliveries in every match here except Dhaka in 1998, which was reduced to 48 overs a side. Both derivations were spot-checked against ESPNcricinfo's own margin figures for the six matches where those figures are published, and agreed in each case. Where a target could not be established from the opposition's completed first innings, the match has been left off the table rather than listed with a gap; the ranking is therefore complete down to 306 and no further.