South Africa thrash Sri Lanka to complete series whitewash

Defeat Islanders by innings and 118 runs on third day to win three-match series 3-0


Afp January 14, 2017
Photo: AFP

JOHANNESBURG: Sri Lanka lost 16 wickets in a day as South Africa's fast bowlers sent them crashing to defeat by an innings and 118 runs in the third Test at the Wanderers Stadium on Saturday.

Sri Lanka were bowled out for 131 and 177 as South Africa's four pacemen tore the batting apart handing the home side a 3-0 series whitewash.

Scrap T20Is to save ODIs, advises Arthur


In a dismal third day of the final Test for the tourists, Sri Lanka were able to add only 51 runs to their overnight first innings total of 80 for four and seldom looked like providing sustained resistance in the second innings, despite a fighting 50 by opening batsman Dimuth Karunaratne.

Vernon Philander and Kagiso Rabada both took three wickets in the first innings, while new cap Duanne Olivier and left-armer Wayne Parnell took two apiece.

Parnell took four wickets in the second innings, Olivier three, Rabada two and Philander one.

Sharing the new ball with Philander in the second innings, Rabada took a wicket with his first ball when Kaushal Silva gloved a catch to wicketkeeper Quinton de Kock. He added the wicket of Karunaratne, who was bowled shortly before tea.

Amla hits ton in 100th Test as South Africa reach 338-3 against Sri Lanka


Parnell bowled Kusal Mendis before Olivier dismissed Dhanajaya de Silva and captain Angelo Mathews, both with the help of catches at second slip by South African captain Faf du Plessis, the second a spectacular one-handed leaping effort.

Philander took his only wicket of the innings when Dinesh Chandimal was caught at first slip.

Suranga Lakmal hit out to make 31 as he and Upul Tharanga (26) added 43 for the eighth wicket before the last three wickets fell for no runs in ten balls.

Our Publications

Most Read

COMMENTS

Replying to X

Comments are moderated and generally will be posted if they are on-topic and not abusive.

For more information, please see our Comments FAQ