South Africa recently beat Sri Lanka by 10 wickets, and only needed two runs in the fourth innings to win the match. This made me wonder how often the side batting fourth had won a Test with so few runs. Turns out five Tests have been decided with the team batting fourth only needing one run. In four of those Tests a batsmen scored a single to stitch up the game, but in one, the Windies v. Indies Test at Bridgetown, the winning run was scored by No Ball.
Australia 1/0 South Africa Cape Town 26 Nov 1921 England 1/0 Australia Sydney 02 Dec 1932 Australia 1/0 South Africa Johannesburg 07 Feb 1958 West Indies 1/0 England Manchester 06 Jun 1963 West Indies 1/0 India Bridgetown 15 Apr 1983
Any chance we Strayans can get up a protest to turn the alien 1/0 into the earthbound 0/1.
Posted by: Tony | Thursday, January 12, 2012 at 03:25 PM
Australia has long since started compromising by being 1/1, 2/2, 3/3 etc.
Posted by: Russ | Thursday, January 12, 2012 at 03:30 PM
It's funny. As I was composing the post I was thinking about which Aussie batsmen would get out chasing such a daunting target as 1. Hughes obviously came to mind, as did Slatts.
Posted by: Tony | Thursday, January 12, 2012 at 03:34 PM
This list might also be of interest, being lead at the end of the 3rd innings in losses. There were also two instances of 1 run 4th innings chases being scored with boundaries, and 3 games where the team lost by an innings and 1. The worst loss of wickets chasing a total of 10 or under was Sri Lanka, who were 2/0 after 5 balls, and 2/10 after 11. On your last comment, the answer is Langer.
Posted by: Russ | Thursday, January 12, 2012 at 03:43 PM
There are two Tests that you missed, in which the chasing team hit a boundary when they only needed a single. Pak v NZ 1976/7, Eng v WI 2004.
Posted by: David Barry | Thursday, January 12, 2012 at 04:36 PM
You set me wondering who managed to get out chasing the lowest target. Turns out it was the BNG.
Posted by: Jonathan | Thursday, January 12, 2012 at 05:22 PM
That's a good spot, Dave. As it happens I started off wondering about sides facing a one run target to win, but half way changed to sides who only scored one run to win.
I was also looking for sides facing a one run target, who then scored a weird total like 5, courtesy of overthrows, hit helmet, or the like.
Posted by: Tony | Thursday, January 12, 2012 at 05:41 PM
Tony, my comment went awol, although Dave and Jonathan addressed the main points. It was full of links, no doubt typepad thinks I'm a spammer.
Posted by: Russ | Thursday, January 12, 2012 at 05:54 PM
Gnome B.N. is a trendsetter.
Posted by: m0nty | Thursday, January 12, 2012 at 06:13 PM
Russ, you were right. Consider it found, fished and published.
Posted by: Tony | Thursday, January 12, 2012 at 06:16 PM
For some reason - possibly even because it is true - I thought there was an instance in Australia where the Aussies, chasing 30-odd, lost three or four wickets.
By the way, my linked list does contain 27 such low chases.
Posted by: Tony | Thursday, January 12, 2012 at 07:34 PM
Another form of 'None for one'...
http://m.theage.com.au/sport/cricket/english-cricketer-guilty-of-matchfixing-20120113-1pxw6.html
Posted by: @TKYC | Friday, January 13, 2012 at 07:17 AM
There aren't a huge number of low chases with more than 3 wickets lost. Australia's worst recent effort was 64/3 against England in Perth. Doesn't hold a candle to NZ's 33/5 vs. West Indies in '87 or Pakistan's 66/7 vs. England in '84.
Posted by: Russ | Friday, January 13, 2012 at 09:12 AM
Reckon that 3/64 in Perth was the match I was thinking of, with both Slogger and Gnome B.N. being dismissed in the chase.
Posted by: Tony | Friday, January 13, 2012 at 12:27 PM
This match was unique in its own right though - a completed innings with no legitimate deliveries bowled! Apparently a first in Tests.
Posted by: Spark | Saturday, January 14, 2012 at 12:18 AM