New Zealand v South Africa, 1st Test, Dunedin, 4th day March 11, 2017

Lowest scoring rate in 19 years

Another sedate day in Dunedin meant that the scoring rate in the first Test is the slowest in New Zealand in the last 19 years

Dean Elgar became the first South African opener to face 200 or more ball in both innings of a Test © ESPNcricinfo Ltd

548 Balls faced by Dean Elgar in this Test - the most by an overseas batsman in Tests in New Zealand (where balls faced information is available). Elgar was dismissed after facing two more balls than Mike Atherton in Christchurch in 1996-97, where he had faced 546 balls in the Test, which was the previous highest.

3 Instances when a South Africa batsman has faced more deliveries in a Test match than Elgar in Dunedin (where balls faced information is available). The previous such instance was when Hashim Amla faced 560 deliveries in the Kolkata Test in 2009-10. Gary Kirsten leads this list with 673 balls against England in Durban in 1999-00. Jacques Kallis completes the top three with his 585-ball marathon against West Indies in Cape Town during the same season.

2.57 Scoring rate in this Test - the slowest in the last 19 years in Tests in New Zealand. Teams scored at a rate slower than this 79 matches ago in New Zealand, at the Basin Reserve, when the hosts and Zimbabwe combined to score 861 from 341 overs in the match. So far, 872 runs have been scored in 340.1 overs in Dunedin.

229 Runs made by Elgar in this Test - the fourth highest by a South Africa batsman against New Zealand. Daryll Cullinan leads this list: he made 275 not out in South Africa's first innings of the Auckland Test in 1998-99.

2013 Previous instance of a South Africa opener scoring 200 or more runs in a Test match. Graeme Smith had made 234 runs in the Dubai Test in 2013-14. Since then Elgar's is the first instance of an opener aggregating 200 runs in a Test.

0 Instances before Elgar when a South Africa opener had faced 200 or more balls in each innings of a Test match. Elgar faced 299 balls in the first innings and 249 in the second in this Test. Apart from Elgar, there are only five instances when any South Africa batsman has faced 200 balls in each innings of a Test. The previous instance was when Jacques Kallis faced 291 and 241 balls in the two innings of the Cape Town Test against India in 2010-11.

434 Dot balls played out by Elgar in this match. Since 2002, there are only four other instances when a South Africa batsman has faced more dots in a Test. Faf du Plessis' 450 dots in the Adelaide Test in 2012 leads this list.

4 Number of times Jeetan Patel has dismissed Quinton de Kock in just 25 deliveries in international cricket this month. In addition to dismissing the batsman in both innings of this Test, Patel got him for a first-ball duck in the Hamilton ODI and off his sixth ball at de Kock in the Auckland ODI. De Kock has made only 8 runs off Patel.

2012 Previous instance of a South Africa captain making two fifty-plus scores in a Test. Smith had 52 in both innings of the Leeds Test on that occasion. Du Plessis' is the first instance for South Africa in 42 Tests since then. Click here for instances when a South Africa captain has hit two fifty-plus scores in a Test.

345 The highest target successfully chased in Tests in New Zealand, which was by West Indies, in 1968-69. The highest target chased down in the last ten years in New Zealand is 217, by the hosts against Bangladesh with seven wickets to spare earlier this year. In four Tests at the University Oval that have spilled over to the fifth day in the last ten years, 32 wickets have fallen at an average of 22.72 runs apiece, which suggests a par target of 230 runs on the fifth day. South Africa are 191 runs ahead with four wickets in hand.

Shiva Jayaraman is a senior stats analyst at @shiva_cricinfo

Comments have now been closed for this article

  • mogots9181850 on March 14, 2017, 3:36 GMT

    Personally i don't like the way Dean Elgar play, he plays negative cricket. Look at his first innings run rate he was scoring at a chamelon rate it was like i was watching 1980 cricket match. I understand the first 50balls he was negotiating the new ball but after that he bored us to death even Misbah could've done better. Dean this is modern cricket boss don't put unnecessary pressure on your fellow batsman trying to inflat your average and pls stop this negative cricket. anyway i've never liked your playing style the likes of Makram must be called to replace our openers we don't have time this NZ bowling attack its weak our new players they would've adapted well. Look at

  • Avinash on March 13, 2017, 8:40 GMT

    oh my!! all of you lot that are complaining should not bother watching test cricket... just go and watch your pajama cricket and be content.

    some of us appreciate the toughness of a test match played on a difficult wicket!

    cricfan69564930 - I think that you should try batting in the rain against a fast bowler bowling at >140km/h

  • Hannes on March 12, 2017, 18:13 GMT

    Do you people even watch Test cricket regularly? That was a tough pitch to score on. Because it was virtually impossible to time the ball well for most the match, it made it risky to try and force the pace. South Africa threw away their best chance at a win when they tried to push the run rate and lost 6 for 79 on the second day. 400 would've been their target, and 350 par for an aggressive approach, but they ended more than 40 short of par, and then NZ batted well to take a 30+ run lead. That kind of lead was always going to make it difficult to set a good total for the chase. I'm not saying they couldn't have been more positive - there wasn't enough strike rotation, for example - but, frankly, that 4th day pitch was incredibly sluggish and just tricky enough to make life dangerous for the batsmen. And, critically, NZ, though not filled with fire and brimstone, bowled extremely well for most of the match. You take what the bowling gives you. They didn't give much.

  • daniel on March 12, 2017, 6:04 GMT

    BCG,,, it is a good pitch going into the fifth day anyone could win it. You want roads like india used to prepare, or a massive seemer like NZ used to have. There was and is something in it for everyone in this. 2 centuries seamers and spinners getting wickets. its a test not a T20.

  • Phillip on March 12, 2017, 5:01 GMT

    Produce good pitches NZL. Then watch the scoring rate ease up.

  •   cricfan69564930 on March 12, 2017, 3:21 GMT

    i don't know why cricketers will face up to a ball that can kill and break bones yet they won't play in any rain....

  • Jay on March 12, 2017, 2:52 GMT

    SA won the toss, elected to bat, and from the start looked like they were playing for a draw.

    And in the 2nd innings, SA looked like a team batting time and praying for rain. No intent to force a result.

    A gift of a draw to a NZ team reduced to 9 players. Some more bad weather and the Proteas could be facing a drawn series, because they won't win within 4 days playing like that.

    And a drawn series for NZ would be a good result for them against a heavily favoured SA team.

  •   cricfan69564930 on March 11, 2017, 22:48 GMT

    prime example of why tests should be 4 days with each team batting a maximum 180 overs in the game.....time to get result focused and rid cricket of negative batting tactics..

  • Steve on March 11, 2017, 17:38 GMT

    "Lowest scoring rate in 19 years". Utterly shameful batting by SA against a non-threatening NZ bowling. We are talking about two non-spinning spinners in Patel and Santner and medium pacer, one whom didn't play an entire session. The only way to prevent this kind batting that will surely kill test cricket is to award opposition free runs (difference of total for a 3 RPO) if the batting team doesn't maintain a minimum run rate of 3 at the end of each session.

  • No featured comments at the moment.