De Kock ready to ‘bide’ time for Test cricket

Aims for consistency after scoring third consecutive ODI ton.


News Desk December 12, 2013
Quinton De Kock is level-headed despite his golden run in international cricket; he scored hundreds in each of the three ODIs against India and is now eyeing a Test call-up. PHOTO: AFP

South Africa’s batting sensation Quinton De Kock is not willing to rest on his laurels despite joining an elusive club of three consecutive centurions in One-Day International (ODI) cricket.

De Kock joined teammate and ODI captain AB De Villiers, Herschelle Gibbs and Pakistan duo of Saeed Anwar and Zaheer Abbas in the club of three successive century makers in the format.

According to ESPNcricinfo, the 20-year-old was admonished for playing recklessly by De Villiers as he closed in on his third consecutive ton against India in a rain-curtailed third ODI against India in the Centurion.

“I don’t remember what he said,” De Kock admitted, after the game had been washed out. De Villiers, who was sitting beside him, put on an expression of mock shock. “You don’t remember anything,” he joked. De Kock blushed a little while the people in the room laughed, and De Villiers explained what he had told the newest member of his team.

“I spoke to him twice,” said De Villiers. “I spoke to him before the start of the game today and I told him never to be satisfied. And then I spoke to him when he was in the 90s. Anyway, he can’t remember anything.”

De Kock was not picked for the two Tests against India despite his prolific run. However, the wicketkeeper-batsman is undeterred. “I’m sure anybody would love to be part of the Test squad, but I will have to go back to four-day cricket, bide my time and hopefully score some runs there.”

Published in The Express Tribune, December 13th, 2013.

Like Sports on Facebook, follow @ETribuneSports on Twitter to stay informed and join in the conversation.

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