Rohan Sawant
(Rohan A. Sawant is a reporter for CricketCountry. He loves Cricket, Football and is a die-hard Arsenal fan. You can follow him on Twitter @iswandering)
Written by Rohan Sawant
Published: Mar 10, 2017, 08:26 AM (IST)
Edited: Mar 10, 2017, 08:28 AM (IST)
New Zealand reached a total of 304 for 8 at the end of second session trailing South Africa by 4 runs in the first Test at Dunedin. Kane Williamson, the Kiwi skipper was dismissed early in the second innings on (130 off 241) after he achieved the milestone of scoring 16th Test century of his career. Since then wicketkeeper-batsman BJ Watling (50) and bowling all-rounder Mitchell Santner (4) frustrated the South Africa pacers throughout the second session with a cautious approach. It was towards the end of the session that Santner and Watling departed one after the other. Prior to this, both forged a 20 run-partnership in 76 deliveries. LIVE CRICKET SCORECARD, New Zealand vs South Africa, 1st Test at Dunedin
Resuming from the score of 247 for 5, Williamson and Watling began the third session on a positive note. They knocked the ball into the gaps very well dealing in easy 1s and 2s and kept the momentum going with come cracking boundaries on whatever was pitched too full or outside off. Having lost 2 wickets in the morning session – nightwatchman Jeetan Patel (16) and Jimmy Neesham (7), New Zealand desperately needed a partnership which would ensure some quality runs on the board stopping the batting collapse.
Watling batted sensibly with his skipper changed their batting gears scoring runs in a flurry in the second session. Faf du Plessis persisted bowling with the old ball for a certain period in the second session hoping for some breakthrough but only to be disappointed. Finally, du Plessis opted for the new ball after 5.5 overs it was available and straightaway handed it to Kagiso Rabada and Vernon Philander. Both used the new ball to the best of their ability but bowling against well-settled Williamson and Watling became a stiff task for the Protea quicks. But Rabada’s patience paid off and rewarded with Williamson’s wicket.
Rabada pitched a fullish delivery which sprung up on Williamson (130) taking a healthy edge and settling into wicketkeeper Quinton de Kock’s gloves. There was extra bounce and pace due to the new ball which did the trick for Rabada.
When Williamson departed, New Zealand were still trailing by 31 runs and Santner had walked in. The visitors had a good chance to capitalise on Williamson’s wicket, but Watling continued to play sturdy cricket not allowing South Africa any chance to dominate. Santer, too played sanely avoiding any rash shots.
Watling and Santner played with the clear intentions of occupying the crease for the maximum they could for the majority of the second session. But towards the end of the session, when runs were hard to come, the visitors came up with the ploy of making Santner the scapegoat. They got Santner on strike and Morne Morkel bowled a fuller one well outside off; enough for Santner to drive the ball which he did to find Keshav Maharaj at covers. Just a few deliveries later, Watling made his maiden fifty only to be clean bowled by Maharaj soon.
South Africa have a slender lead of 4 runs while New Zealand have Neil Broom (4) and Trent Boult (0) at the crease who may go all guns blazing in the last session of the day to attain lead over the Proteas if any at all.
Brief scores:
South Africa: 308 (Dean Elgar 140, Temba Bavuma 64; Trent Boult 4 for 64, Neil Wagner 3 for 88) lead New Zealand: 304 for 8 (Jeet Raval 52, Kane Williamson 130, BJ Watling 50; Keshav Maharaj 3 for 82, Vernon Philander 2 for 48) trail by 4 runs.
This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.
Strictly Necessary Cookie should be enabled at all times so that we can save your preferences for cookie settings.
If you disable this cookie, we will not be able to save your preferences. This means that every time you visit this website you will need to enable or disable cookies again.