South Africa vs Australia 2nd Test 2026: St George’s Park Preview
South Africa meet Australia in the second Test at St George’s Park, Gqeberha, from 18 to 22 October 2026. Day one starts at 1:30 PM IST. This guide separates the confirmed schedule, the first Test’s actual day-four score, named touring squads and selection questions from an unconfirmed playing XI or invented result.
South Africa vs Australia 2nd Test 2026: confirmed match details
South Africa vs Australia’s second Test is scheduled for Sunday, 18 October to Thursday, 22 October 2026 at Dafabet St George’s Park in Gqeberha, South Africa. Day one is scheduled to begin at 10:00 AM local time, which is 1:30 PM Indian Standard Time. The ICC match listing expresses the start as 08:00, or 1:30 PM IST after the UTC-to-India conversion. Cricket South Africa and the series match centre agree on the date, venue and five-day window.
This is a preview anchored to 13 October 2026. The first Test had not reached a final result in the latest scorecard available at that reference point: after day four in Durban, South Africa were 102 for 4 in the chase of 421 and still needed 319 runs. That live status matters. It is not a completed score, so this article does not invent a series score, a winner or a player-of-the-match award.
| Match item | Confirmed detail | India reader’s meaning |
|---|---|---|
| Match | South Africa vs Australia, 2nd Test | Second match of the three-Test series |
| Day one | Sunday, 18 October 2026 | 1:30 PM IST |
| Scheduled window | 18–22 October 2026 | Up to five days, subject to an earlier result |
| Venue | Dafabet St George’s Park, Gqeberha | 10:00 AM local start; 1:30 PM IST |
| Status at reference date | Upcoming fixture; first Test at day-four stumps | Do not treat a final series score or XI as known |
What time does the Gqeberha Test start in India?
For Indian viewers, the scheduled day-one start is 1:30 PM IST on Sunday, 18 October. St George’s Park is on South Africa Standard Time, UTC+2, while India is UTC+5:30. Adding three hours and 30 minutes to the local 10:00 start produces 1:30 PM IST. The same fixture is listed by the ICC at 08:00, which is the UTC expression of that start.
The five-day allocation is 18, 19, 20, 21 and 22 October. A Test can finish before day five, so those dates describe the maximum scheduled window rather than a promise that every day will be used. The daily close, session breaks and any lost-time adjustments are match-day information and should not be filled in from a generic schedule.
| Clock label | Start time | What it represents |
|---|---|---|
| Gqeberha local | 10:00 AM SAST | Scheduled first ball on day one |
| UTC listing | 08:00 | ICC’s displayed match-start reference |
| India | 1:30 PM IST | Local conversion for Indian readers |
| Dates | 18–22 October | Scheduled five-day Test window |
What is the current first-Test status before Gqeberha?
The latest actual Durban scorecard available on 13 October showed Australia 390 and 314 for 6 declared, with South Africa 284 and 102 for 4 after 41 overs. Australia had set a target of 421, leaving South Africa 319 runs short at the end of day four. Aiden Markram was unbeaten on 45 from 115 balls and Wiaan Mulder was 5 not out; Josh Hazlewood had taken 2 for 20, while Pat Cummins and Matt Renshaw had one wicket each.
That is a live match position, not an old pre-match snapshot and not a final score. Matt Renshaw’s 190 in Australia’s first innings and 82 in the second had driven the visitors’ total. The scorecard also records a meaningful tactical shift: Australia declared at 314 for 6 after scoring quickly, leaving time to attack, while South Africa’s chase was slowed by early wickets and a wearing surface with variable bounce and turn. The Durban result must be updated separately after play finishes; it is not folded into this Gqeberha preview.
| Innings | Score | Verified context |
|---|---|---|
| Australia first | 390 all out | Matt Renshaw 190; South Africa’s Marco Jansen took 3 wickets and Wiaan Mulder 4 |
| South Africa first | 284 all out | Australia led by 106; South Africa’s highest score was David Bedingham’s 49 |
| Australia second | 314/6 declared | Renshaw 82; declaration set a target of 421 |
| South Africa second at day-four stumps | 102/4 after 41 overs | Markram 45*, Mulder 5*; 319 still required |
Named squads are not the same as the playing XI
Australia announced a 16-player Test squad for the tour: Pat Cummins (captain), Scott Boland, Alex Carey, Cooper Connolly, Cameron Green, Josh Hazlewood, Travis Head, Josh Inglis, Matthew Kuhnemann, Marnus Labuschagne, Nathan Lyon, Michael Neser, Matthew Renshaw, Steve Smith, Mitchell Starc and Beau Webster. This is the named touring group, not confirmation that all 16 are available or that any particular combination will take the field in Gqeberha.
South Africa’s published 18-player preliminary squad for the first Test was Temba Bavuma, Marques Ackerman, David Bedingham, Corbin Bosch, Gerald Coetzee, Tony de Zorzi, Simon Harmer, Marco Jansen, Keshav Maharaj, Aiden Markram, Wiaan Mulder, Senuran Muthusamy, Anrich Nortje, Dane Paterson, Kagiso Rabada, Ryan Rickelton, Tristan Stubbs and Kyle Verreynne. The announcement was explicitly preliminary and first-Test specific. It cannot be presented as a confirmed second-Test XI. The match listing shows a squad pool, while the final XI normally arrives with the toss.
| Team | Named group available in published source | Selection limit |
|---|---|---|
| Australia | 16-player Test touring squad | No Gqeberha XI confirmed in the source set |
| South Africa | 18-player preliminary first-Test squad | Preliminary first-Test list, not a second-Test XI |
| Both | Captains and reserve options are identifiable | Toss-day XI, wicketkeeper and balance remain to be confirmed |
The distinctive selection questions for the second Test
Australia’s main question is how much of Durban’s winning or near-winning combination can be retained after a five-day workload. The announced group offers four seam options in Cummins, Hazlewood, Starc and Boland, plus all-round balance through Green, Webster and Connolly. The squad announcement says Matthew Kuhnemann was selected as a second spinner and notes that Gqeberha is the only South African venue since the pandemic where more wickets have fallen to spin than pace. That makes a Lyon-Kuhnemann discussion a real selection scenario, not a predicted XI.
The first-Test scorecard adds a second question: Australia’s batting order had to absorb an early collapse before Renshaw rebuilt the innings. Renshaw’s two big scores make him a central selection fact for the next match, but they do not automatically settle the opening order or remove questions around Head and Labuschagne. On the South African side, the first innings exposed the cost of Rickelton’s early dismissal and several middle-order scores below 50. The response could involve continuity, a batting adjustment or a bowling-balance change, but no such decision had been announced by the reference date.
Josh Inglis was named in Australia’s touring squad despite returning home after a fractured finger sustained in the preceding ODI series, according to the tour guide. The report does not establish a second-Test XI or a definitive medical clearance. Alex Carey appeared as wicketkeeper in Durban, so the correct wording is that wicketkeeping selection remains a watch point, not that a replacement is confirmed.
Recent verified results and the series record
The latest completed Test between these teams before the 2026 tour was the 2025 World Test Championship final at Lord’s. South Africa beat Australia by five wickets after scores of Australia 212 and 207, and South Africa 138 and 282 for 5. Aiden Markram was player of the match after scoring 136 in the chase. That result explains the WTC significance around this series, but it is historical context rather than evidence of what will happen at St George’s Park.
The recent head-to-head panel for the second-Test listing records South Africa’s five-wicket win in that 2025 final, a drawn Test in Sydney in January 2023, Australia’s innings-and-182-run win at Melbourne in December 2022, Australia’s six-wicket win at Brisbane in December 2022 and South Africa’s 492-run win at Johannesburg in March 2018. Listing the score and margin is more useful than saying one side has “momentum”; each match had a different venue, surface and team combination.
| Date | Match | Verified result |
|---|---|---|
| 11–14 June 2025 | WTC final, Lord’s | South Africa won by 5 wickets |
| 4–8 January 2023 | Third Test, Sydney | Match drawn |
| 26–29 December 2022 | Second Test, Melbourne | Australia won by an innings and 182 runs |
| 17–20 December 2022 | First Test, Brisbane | Australia won by 6 wickets |
| 30 March–3 April 2018 | Fourth Test, Johannesburg | South Africa won by 492 runs |
Tactical matchup: what St George’s Park can test
The strongest evidence for a tactical preview comes from the venue note in Australia’s squad announcement and the Durban scorecard. St George’s Park has produced more wickets to spin than pace since the pandemic, according to Cricket Australia’s selection report. If that trend is relevant again, the contest may turn on how quickly captains introduce spin and whether batters can disrupt a bowler’s control without offering a catching chance. That is a question to watch, not a forecast of the pitch or weather.
Australia’s attack has several ways to build pressure. Hazlewood’s two day-four wickets in Durban came while South Africa were chasing a large target; Cummins removed Tristan Stubbs; Renshaw supplied a surprise off-spin wicket. South Africa’s first-innings attack, meanwhile, showed that Jansen and Mulder could extract wickets from Australia’s top and middle order before Renshaw changed the match. At St George’s Park, the tactical test is whether South Africa can turn early movement or spin into sustained pressure before Australia’s lower order adds a second wave of runs.
At the crease, Markram’s 45 not out at day-four stumps and his 136 in the 2025 final make him a verified player to monitor against Australia. Renshaw’s 190 and 82 in Durban are the clearest current batting evidence on the other side. Neither record guarantees a repeat. It simply identifies the matchups that deserve attention when the confirmed XIs and first session arrive.
What to check when the second-Test match centre opens
The first check is the toss-day playing XI for both teams. Compare it with the named touring and preliminary squads rather than assuming the published squad is the XI. The second check is the wicketkeeper and spin balance, especially if Australia selects Lyon with Kuhnemann or if South Africa changes its combination after the Durban chase. The third check is any official update on players carrying a workload or injury question. Only a team announcement or match centre should settle those details.
The fourth check is the first-Test result. At the 13 October reference time, the verified status was day-four stumps, not a final. Once the Durban scorecard is complete, it can change the series context and the tactical reading of the Gqeberha fixture. Until then, the responsible preview is to state the live position, keep the second Test upcoming and avoid odds, projected winners, weather claims or a made-up broadcast listing.
What this South Africa vs Australia 2nd Test guide does not claim
This page confirms the date, complete match window, venue and India-time start, then reports the latest actual Durban scorecard position. It does not claim a final Durban result because that result was not available in the verified scorecard at the 13 October reference time. It also does not name a playing XI, add a weather forecast, publish betting odds, predict a winner or state a broadcast arrangement for Indian viewers.
The WTC context is factual: the ICC lists this as part of the 2025–27 championship cycle, and South Africa won the previous cycle’s 2025 final against Australia. A competition context is not a trading or investment recommendation. Readers should use the ICC, host-board and team match centres for any update that appears after this time-stamped preview.
Reader guide
Article questions, answered
Short answers to common reader questions based on the reporting above.
When is the South Africa vs Australia 2nd Test in 2026?
The second Test is scheduled from Sunday, 18 October to Thursday, 22 October 2026 at St George’s Park in Gqeberha, South Africa.
What time does South Africa vs Australia 2nd Test start in India?
Day one is scheduled for 1:30 PM IST on Sunday, 18 October 2026. That converts the 10:00 AM local start in Gqeberha, or the ICC listing of 08:00 UTC.
Where will the second Test be played?
The match is scheduled at Dafabet St George’s Park, Gqeberha, South Africa. The venue is also commonly called St George’s Park in the ICC and scorecard listings.
What was the latest South Africa-Australia first-Test score before this preview?
At day-four stumps in Durban, Australia had made 390 and 314 for 6 declared. South Africa were 284 and 102 for 4, chasing 421 and still needing 319 runs. That was a live score, not a final result.
Are the playing XIs confirmed for the Gqeberha Test?
No confirmed second-Test playing XI was available in the sources checked on 13 October 2026. Australia’s 16-player touring squad and South Africa’s preliminary first-Test squad are named groups, not match-day XIs.
Why is spin a selection question at St George’s Park?
Cricket Australia’s squad report says St George’s Park is the only South African venue since the pandemic where more wickets have fallen to spin than pace. That makes a second-spinner discussion a verified selection question, not a guarantee about the surface.
What was the latest completed South Africa-Australia Test?
The latest completed Test listed before this tour was the 2025 World Test Championship final at Lord’s. South Africa beat Australia by five wickets, with Aiden Markram named player of the match.
Sources and further reading
These references support the factual context used in this article. Links open the original publisher.