South Africa set 288 target for Australia in Test series decider
Summarised from 2 outlets · Updated 30 Oct, 21:45 · Archive
South Africa set Australia a target of 288 runs to win the decisive Test in Cape Town after batting out the fourth day.
South Africa batted throughout the fourth day of their decisive Test against Australia in Cape Town, recovering from a position where defeat looked likely to set up a real possibility of series victory. The hosts were 40-4 at the start of the day but built steadily on a surface that appeared increasingly flat for batting.
Ryan Rickelton made 101 and Wiaan Mulder scored a brilliant 115 in a final-wicket partnership that took South Africa to 387 in their second innings. They set Australia a target of 288 for victory on the final day.
CricViz's WinViz tool gives South Africa a 54 per cent chance of winning from this position. Should Australia chase the target successfully, it would be only the second-highest fourth-innings chase in the 62 previous Tests played at Cape Town's Newlands ground. The highest chase was Australia's own victory of 331 in 2002, when Ricky Ponting scored a brilliant 100 not out against South Africa. Five other scores above 288 in the fourth innings at the ground resulted in defeats or draws.
How it is being reported
- Series set for epic finale as Aussie batters must stand upAfter Rickelton and Mulder's heroics, Australia needs batting heroes to stand up on a decisive final day in Cape Town.ABC News Australia · 30 Oct, 21:21
- South Africa-Australia set for classic finale – what does history suggest could happen?South Africa set up an epic final day of their decisive Test against Australia by batting throughout the fourth day. What does history suggest could happen?BBC News · 30 Oct, 17:03
In this story: South Africa · Australia · Cape Town · Ryan Rickelton · Wiaan Mulder · Ricky Ponting
This summary was written by AI from the headlines and standfirsts above, and states as fact only what at least two outlets report. How we use AI · Report a problem · Corrections log
Comments (0)