Wikipedia

Net run rate: Difference between revisions

Browse history interactively
← Previous edit
Content deleted Content added
VisualWikitext
Tags: Mobile edit Mobile web edit
Undid revision 1248576766 by 103.131.215.211 (talk)
 
(77 intermediate revisions by 46 users not shown)
Line 1:
{{Short description|Tie-breaking formula in limited overs Cricket}}
{{EngvarB|date=JulyJune 20162024}}
{{Use dmy dates|date=July 2016}}
'''Net Runrun Raterate''' ('''NRR''') is a statistical method used in analysing teamwork and/or performance in [[cricket]].<ref>[https://papers.ssrn.com/sol3/papers.cfm?abstract_id=3415979 The Net Run Rate System: Calculus and Critique.] Social Science Research Network (SSRN). Accessed June 7, 2019.</ref> It is the most commonly used method of ranking teams with equal points in [[Limited overs cricket|limited overs]] league competitions, analogoussimilar to [[goal difference]] in [[association football|football]].
 
The NRR in a single game is the [[arithmetic mean|average]] runs per [[Over (cricket)|over]] that team scores, minus the average runs per over that is scored against them. The NRR in a tournament is the average runs per over that a team scores across the whole tournament, minus the average runs per over that is scored against them across the whole tournament.<ref name="ICCPH">{{cite web|url=http://icc-live.s3.amazonaws.com/cms/media/about_docs/526958a73c839-Playing%20Handbook.pdf|title=ICC Playing Handbook 2013/14 Paragraph 21.9.2|website=Icc-live.s3.amazonaws.com|accessdateaccess-date=30 April 2019}}</ref><ref name="espn1">{{cite web|url=http://www.espncricinfo.com/ci/content/page/429305.html|title=Net Run Rate explained |website=Espncricinfo.com|accessdateaccess-date=30 April 2019}}</ref> This is the same as the [[Weighted arithmetic mean|weighted average]] of the run rates scored in each match (weighted by the lengths of the innings batted compared to the other innings batted), minus the weighted average of the run rates conceded in each match (weighted by the lengths of the innings bowled compared to the other innings bowled). This is ''not'' usually the same as the total or average of the NRRs from the individual matches in the tournament.
 
A positive NRR means a team is scoring faster than its opposition overall, while a negative NRR means a team is scoring slower than the teams it has come up against.<ref>{{cite web|url=https://www.thoughtco.com/net-run-rate-nrr-962178|title=How To Calculate Net Run Rate in Cricket|author=Barnaby Haszard Morris|website=Thoughtco.com|accessdateaccess-date=30 April 2019}}</ref> It is therefore desirable for the NRR to be as high as possible.
 
NRR has been criticised as hard to understand, and 'often misunderstood'.<ref name="espn1"/> It also does not accurately reflect true margins of victoryAlso, aswhile it measures how quickly teams score and concede runs, butthis takesis nonot accountat ofall wicketsthe takensame as how big the teams' margins of victory or lost,defeat soare a(as teamit withignores a[[Dismissal narrow(cricket)|wickets victorylost]]), canand haveso aranking highersides by NRR thandoes anot teamrank withthem aby comfortablesize of victory. This means a team which progresses in a tournament at the expense of another team, due to a higher NRR, may not have actuallytruly hadperformed better victoriesthan their opponents.<ref>{{cite web |title=How is Net Run Rate (NRR) Calculated? |url=https://www.sportskeeda.com/amp/cricket/how-is-net-run-rate-nrr-calculate-in-cricket |website=www.sportskeeda.com |access-date=22 June 2019 |language=en |date=22 March 2016}}</ref>
 
In the [[Cricket World Cup]], the first use of NRR was in the [[1992 Cricket World Cup|1992 tournament]].<ref>{{cite news |url=https://news.google.com/newspapers?id=bpBlAAAAIBAJ&sjid=lJ4NAAAAIBAJ&pg=420%2C3190547 |title=Leander fires out Malik |first=H. |last=Natarajan |publisher=The Indian Express |page=15 |date=19 March 1992 |access-date=15 November 2020 }}</ref> Earlier tournaments used [[run rate]] instead as the tie-breaker.<ref>{{cite news |url=https://news.google.com/newspapers?id=FX5VAAAAIBAJ&sjid=-5YDAAAAIBAJ&pg=3010%2C387454 |title=Border's men face a daunting semi task |first=Martin |last=Blake |date=2 November 1987 |publisher=The Age |access-date=15 November 2020 }}</ref>
 
==Step by step explanation==
Line 14 ⟶ 17:
<math>\text{run rate }=\frac{\text{total runs scored}}{\text{total overs faced}}</math>.
 
So if a team scores 250481 runs off 50 overs then their RR is <math>\frac{250481}{50} = 59.62</math>. Note that as an over is made up of six balls, each ball is 1/6 of an over, despite being normally written in cricket's notation as .1 of an over. So if they got that same score off 4748.51 overs, their RR would be <math>\frac{250481}{47+48\frac{1}{5/6}} = 59.23986</math>.
 
The concept of net run rate involves [[subtraction|subtracting]] the opponents' run rate from the team's run rate, i.e.
<math>\text{match net run rate }=\frac{\text{total runs scored}}{\text{total overs faced}}-\frac{\text{total runs conceded }}{\text{total overs bowled}} </math>.
 
For two teams which have just played, the winning side will have a positive Match NRR, and the losing side will have the [[negative number|negative]] of this (i.e. the Match NRRs will be [[additive inverse|additive inverses]]s, summing to zero). A single match's NRR is used very rarely, perhaps only after a team has played one match in a tournament, so their tournament NRR is the same as the match NRR.
 
Usually, runs and overs are summed together throughout a season to compare teams in a league table. A team's overall NRR for a tournament is not defined as the sum or average of the NRR's from the individual matches, but as:
Line 31 ⟶ 34:
*If a match is '''abandoned but a result decided''' by retrospectively applying Duckworth-Lewis, the number of overs assigned to each team for this calculation is the number of overs actually faced by Team 2. Team 1 is credited with Team 2's Par Score (the number of runs they would need to have reached from this number of overs and wickets lost if they were going to match Team 1's score), and the actual runs scored are used by Team 2 for Team 2's innings.<ref name="ICCPH"/>
 
==ScenariosPermutations==
All scenarios assume [[One Day International]] rules with 50 overs per side.
 
Line 46 ⟶ 49:
 
===3. Side that bats first is bowled out, side batting second wins===
* Team A bat first and are bowled out for 127108 off 2519.42 overs. Despite their run rate for the balls they faced being 127 / 25.667 = 4.95, because they were bowled out the entire 5020 overs are added to their total overs faced tally for the tournament, and Team B are credited with having bowled 5020 overs.
* Team B reach the target off 3014.51 overs, ending with 128–4109–3. Team B actually scored at a slower pace (128/30.833 = 4.15), however they managed to protect their wickets and win. Thus, only the 30.833 overs are added to the seasonal tally.
* Team A's NRR for this game is <math>\frac{127}{50}-\frac{128}{30\frac{5}{6}} = -1.61</math>.
* Team B's NRR for this game is <math>\frac{128}{30\frac{5}{6}}-\frac{127}{50} = +1.61</math>.
Line 57 ⟶ 60:
 
===5. Both sides are bowled out, side batting first therefore wins===
* Team A bat first, and manage 117108 off 2419.2 overs on a difficult playing surface. Team B fall agonizingly short, reaching 112105 off 2314.31 overs.
* In this case, both teams get 50 overs both faced and bowled in the overs column for the season, just as in example 1.
 
Line 66 ⟶ 69:
* In matches where [[Duckworth-Lewis]] revised targets are set due to interruptions which reduce the number of overs bowled, those revised targets and revised overs are used to calculate the NRR for both teams.
* For example, Team A are dismissed for 165 in 33.5 overs. Team B progresses to 120–0, but play is halted after 18 overs due to rain.
* Six overs are lost, and the target is reset to 150 from 44 overs, which Team B reach comfortably after 26.2 overs.
* Because the target was revised to 150 runs from 44 overs, Team A's total is reset to 149 from 44 overs, thus their RR <math>=
\frac{149}{44} \approx 3.39</math>. Team B's RR, however, is computed as normal: <math>\frac{150}{26.33} \approx 5.70</math>.
Line 84 ⟶ 87:
Most of the time, in limited overs cricket tournaments, there are round-robin groups among several teams, where each team plays all of the others. Just as explained in the scenarios above, the NRR is not the average of the NRRs of all the matches played, it is calculated considering the overall rate at which runs are scored for and against, within the whole group.
 
Let'sHere take asis an example South Africa's net run rate in the [[1999 Cricket World Cup#Group A Table|1999 World Cup]].
 
'''FOR'''
Line 149 ⟶ 152:
==Criticisms==
===NRR does not accurately reflect margins of victory, as it takes no account of wickets lost===
In the language of [[Duckworth-LewisDuckworth–Lewis–Stern method|Duckworth-Lewis-Stern]], teams have two resources with which to score runs − overs and wickets. However, NRR takes into account only one of these − overs faced; it takes no account of wickets lost. Therefore, a team regarded as having a narrow victory can haveproduce a higher NRR than a team regarded as having a comfortable victory. For example, a team which just manages to win a close game with many overs to spare but with only one wicket in hand is likely to have a higher NRR than a team which paces itself to win comfortably with only a few overs in hand but many wickets.<ref>{{cite web|url=http://www.espncricinfo.com/icc-champions-trophy-2013/content/story/640383.html|title=Why net run rate doesn't work|date=10 June 2013|website=Espncricinfo.com|accessdateaccess-date=30 April 2019}}</ref> For example, in the [[2013 ICC Champions Trophy#Group A|2013 Champions Trophy Group A]]:
*New Zealand justnarrowly beat Sri Lanka by bowling them out for 138, then reaching 139–9 from 36.3 overs, giving them match NRR = (139/36.5) − (138/50) = '''1.05'''. ▼
*Sri Lanka comfortably beat England by restricting them to 293–7 from 50 overs, then reaching 297–3 from 47.1 overs, giving them match NRR = (297/47.167) − (293/50) = '''0.44'''. ▼
 
This fact can encourage a team to play in an overly aggressive manner, to maximise NRR by batting with next to no regard for preserving wickets, when the required run rate alone seems low, which can then put the team in danger of losing.<ref>{{cite web|url=http://www.espncricinfo.com/icc-cricket-world-cup-2015/content/story/833193.html|title=NZ stutter to win after dominant bowling|date=16 February 2015|website=Espncricinfo.com|accessdateaccess-date=30 April 2019}}</ref>▼
For example, in the [[2013 ICC Champions Trophy#Group A|2013 Champions Trophy Group A]]:
▲*New Zealand just beat Sri Lanka by bowling them out for 138, then reaching 139–9 from 36.3 overs, giving them match NRR = (139/36.5) − (138/50) = '''1.05'''.
▲*Sri Lanka comfortably beat England by restricting them to 293–7 from 50 overs, then reaching 297–3 from 47.1 overs, giving them match NRR = (297/47.167) − (293/50) = '''0.44'''.
*England comfortably beat Australia by 48 runs by scoring 269–6 in 50 overs, then restricting Australia to 221–9 in 50 overs, giving them match NRR = (269/50) − (221/50) = '''0.96'''.
 
▲This fact can encourage a team to play in an overly aggressive manner, to maximise NRR by batting with next to no regard for preserving wickets, when the required run rate alone seems low, which can then put the team in danger of losing.<ref>{{cite web|url=http://www.espncricinfo.com/icc-cricket-world-cup-2015/content/story/833193.html|title=NZ stutter to win after dominant bowling|date=16 February 2015|website=Espncricinfo.com|accessdate=30 April 2019}}</ref>
 
===Tournament NRR calculation===
'''A team's batted and bowled overs in a match count differently to tournament NRR'''
 
All overs batted in a tournament are given equal weighting when finding tournament NRR, and all overs bowled in a tournament are also given equal weighting. However, when the total number of overs batted is different from the total number of overs bowled, the weight for each over batted is different from the weight for each over bowled. This means that batted overs and bowled overs in the same match count differently towards tournament NRR.
 
For example, in the [[2009 ICC World Twenty20#Group D|2009 World Twenty20 Group D]], as New Zealand had batted 6 overs and bowled 7 overs against Scotland, the runs they scored in each of the 20 overs batted against South Africa contributed 1/26th to their tournament NRR, while the runs conceded in each of the 20 overs bowled against South Africa contributed only 1/27th. In fact, the effect of the higher weight for the batting overs was so strong that despite scoring fewer runs than South Africa from the same number of overs, and hence having a negative match NRR and losing the match, the net contribution of this match to New Zealand's tournament NRR was actually positive (127/26 − 128/27 is positive).
 
'''Each over in a match counts differently for the two teams'''
 
Moreover, if two teams in a tournament have different total numbers of overs batted or bowled, then each innings in the match(es) between them will contribute differently towards their tournament NRRs. For example, in the [[2009 ICC World Twenty20#Group D|2009 World Twenty20 Group D]], South Africa batted for 40 overs in total in their two matches, so their score of 128 from 20 overs against New Zealand contributed 128/40 = 3.20 to their tournament NRR, whereas New Zealand bowled for 27 overs in total in their two matches, so South Africa's score of 128 from 20 overs against them contributed −128/27 = −4.74 to New Zealand's tournament NRR.
 
As a team's NRR measures how many more runs it scores per over than it concedes, the NRRs of all the teams in a league table should [[zero-sum game|sum to zero]]. However, because of this fact of each innings usually counting differently to the two teams' tournament NRRs, this rarely happens. If the sum is positive, this implies that overall more runs were scored per over than were conceded, which is obviously impossible. (And if the sum is negative that less were scored than conceded). The teams' tournament NRRs will all sum to zero if all the teams have played one or zero matches, or if every innings had exactly the same number of overs. This happens sometimes with small league tables. For example, Group B in the [[2009 ICC World Twenty20#Group B|2009 World Twenty20]] featured three matches. Five of the six innings had the full complement of 20 overs, and in the sixth innings the team was bowled out, which counts as the full complement of 20 overs.
 
'''The same score by two teams counts differently to tournament NRR'''
 
If two teams make the same score from the same number of overs (either in the same match or different matches), this will count differently to their respective tournament NRR's if they have different total numbers of overs batted across the whole tournament. For example, in the [[2007 ICC World Twenty20#Group B|2007 World Twenty20 Group B]], Australia and Zimbabwe each scored 138 from 20 overs in one of their matches. However, as Australia batted for 14.5 overs in their other match, this contributed 138/34.833 = 3.96 to their tournament NRR, whereas as Zimbabwe batted for 19.5 overs in their other match, this contributed 138/39.833 = 3.46 to their tournament NRR.
 
This is also the case if two teams concede the same score in the same match or different matches, but have different total numbers of overs bowled in the tournament.
 
'''Tournament NRR can penalise teams which win batting second rather than first'''
 
If one team, batting first, scores 250 from their 50 overs, and another team, batting second, is set a target of 100 which it easily reaches in 20 overs, then both sides have a batting run rate of 5. Therefore, both sides will have the same match NRR, all else being equal, and should have the same contribution to tournament NRR. However, when it comes to calculating tournament NRR, the first team's innings will count more heavily than the second team's as it was longer, even though the second team achieved the same run rate and could potentially have reached the same total if it could have completed its 50 overs.
 
===NRR may be manipulated===
A team may choose to artificially reduce their margin of victory, as measured by NRR, to gain an additional advantage by not disadvantaging their opponent too much. For example, in the final round of matches in the [[1999 Cricket World Cup#Group B Tablestage|1999 World Cup Group B]], Australia needed to beat West Indies to progress to the Super Six stage, but wanted to carry West Indies through with them to the Super Six, rather than New Zealand. This is because Australia would then have the additional points in the Super Six stage from beating West Indies in the group stage, whereas they had lost to New Zealand in the group stage. It was therefore to Australia's advantage to reduce their scoring rate and reduce their margin of victory, as measured by NRR, to minimise the negative impact of the match on West Indies' NRR, and therefore maximise West Indies' chance of going through with them.<ref>{{cite web|url=https://www.theguardian.com/sport/1999/may/31/cricketworldcup1999.cricketworldcup5|title=Australia pull fast one with go-slow|first=Matthew|last=Engel|date=31 May 1999|accessdateaccess-date=30 April 2019|website=Theguardian.com}}</ref>
 
However, this is also likely to be a possibility with alternatives to NRR.
 
This is similar to the way a narrow victory for one side in a game of [[association football|football]] may enable both sides to progress to the next stage, e.g. [[West Germany 1–0 Austria (1982 FIFA World Cup)|West Germany v Austria in the 1982 World Cup]].
 
===NRR can be hard to understand===
NRR can be hard to understand, and is 'often misunderstood'.<ref name="espn1"/> For example, Tournament NRR has been incorrectly explained as the sum of the NRRs from each match.<ref>[http://www.bigbash.com.au/the-league/rules] {{dead link|date=April 2019}}</ref>
 
==Alternatives to NRR==
A number of alternatives or modifications done to NRR have beenis suggested. below as following -
===Duckworth–Lewis–Stern===
UseDuckworth Lewis Stern method in used Tournament NRR as present, but when a side batting second successfully completes the run chase, use the [[Duckworth-Lewis method|Duckworth−Lewis method]] to predict how many runs they would have scored with a full innings. This means the calculation would be done on the basis of all innings being complete, and so would remove the criticisms of NRR penalising teams which bat second, and NRR not taking into account wickets lost. However, this does nothing to alter the fact that when matches are rain-affected, different matches and even two complete innings in one match, can be different lengths long (in terms of overs), and so does nothing about some of the other criticisms above.▼
 
Therefore, alternatively, use Duckworth−LewisDuckworth–Lewis–Stern to predict the 50-over total for ''every'' innings less than this,<ref>{{cite web|url=http://www.sporttaco.com/rec.sport.cricket/Net_Run_Rate_alternative_3979.html|title=Net Run Rate alternative|website=Sporttaco.com|accessdateaccess-date=30 April 2019}}</ref> even, for example, if a match is reduced to 40 overs each, and a side completes their 40 overs. This would make every innings in the tournament the same length, so would remove all the criticisms above. However, a side will bat differently (less conservatively) in a 40-over innings compared to a 50-over innings, and so it is quite unfair to use their 40-over total to predict how many runs they could have scored in 50 overs.▼
===Duckworth−Lewis===
▲Use Tournament NRR as present, but when a side batting second successfully completes the run chase, use the [[Duckworth-Lewis method|Duckworth−Lewis method]] to predict how many runs they would have scored with a full innings. This means the calculation would be done on the basis of all innings being complete, and so would remove the criticisms of NRR penalising teams which bat second, and NRR not taking into account wickets lost. However, this does nothing to alter the fact that when matches are rain-affected, different matches and even two complete innings in one match, can be different lengths long (in terms of overs), and so does nothing about some of the other criticisms above.
 
▲Therefore, alternatively, use Duckworth−Lewis to predict the 50-over total for ''every'' innings less than this,<ref>{{cite web|url=http://www.sporttaco.com/rec.sport.cricket/Net_Run_Rate_alternative_3979.html|title=Net Run Rate alternative|website=Sporttaco.com|accessdate=30 April 2019}}</ref> even, for example, if a match is reduced to 40 overs each, and a side completes their 40 overs. This would make every innings in the tournament the same length, so would remove all the criticisms above. However, a side will bat differently (less conservatively) in a 40-over innings compared to a 50-over innings, and so it is quite unfair to use their 40-over total to predict how many runs they could have scored in 50 overs.
 
Either way, using Duckworth−Lewis would mean relying on subjective modelling predictions, which are opinions, rather than actual performances, which are facts.
 
===Average of the match NRRs===
Calculate tournament NRR as the total or average of the individual match NRRs. This would mean all matches have equal weighting, no matter how long they were, (rather than all batted overs across the tournament having equal weighting, and all bowled overs across the tournament having equal weighting). This would remove the criticisms under the 'Tournament NRR calculation' subheading above. For example, the different teams' tournament NRRs would always sum to zero if the total of the individual match NRRs were used, or if the average of the individual match NRRs were used and all teams had played the same number of games.
 
An example of when using this would have made a difference was the [[1999 Cricket World Cup#Group B Tablestage|1999 Cricket World Cup Group B]]. New Zealand and West Indies finished level on points. Having scored a total of 723 runs from 201 overs, and conceded 746 runs from 240.4 overs, West Indies' tournament NRR was (723/201) − (746/240.6667) = '''0.50'''. However, New Zealand had scored 817 runs from 196.1 overs, and conceded 877 runs from 244.2 overs, so their tournament NRR was (817/196.167) − (877/244.333) = '''0.58'''. Therefore, New Zealand progressed to the Super Six stage and West Indies were eliminated. However, with individual match NRRs of −0.540, 0.295, 0.444, 5.525 and −0.530, the West Indies' average match NRR was '''1.04''', and with individual match NRRs of 1.225, 0.461, −0.444, −1.240 and 4.477, New Zealand's average match NRR was '''0.90'''. Therefore, West Indies' average NRR was better than New Zealand's.
 
===Ball difference===
Ball difference (BD) is the number of balls remaining at the point of victory.<ref>{{cite web|url=https://pandimi.wordpress.com/2011/02/19/bd/|title=Ball Difference|date=19 February 2011|website=Pandimi.wordpress.com|accessdate=30 April 2019}}</ref> For a team winning batting second, BD would be the number of balls remaining. For a team winning having batted first, BD would be the number of balls between the precise delivery when the beaten team was outscored and the end of their innings (either the end of the overs or until the team were all out).<ref>{{cite web|url=https://pandimi.wordpress.com/balldiff/|title=Ball Difference|date=15 April 2012|website=Pandimi.wordpress.com|accessdate=30 April 2019}}</ref><ref>{{cite web|url=http://testmatchsofa.com/Forum/yaf_postst22_A-simple-alternative-to-Net-Run-Rate.aspx|title=Test Match Sofa A simple alternative to Net Run Rate|website=Testmatchsofa.com|accessdate=30 April 2019}}</ref> For the losing team, BD is the negative of the winning team's BD.
 
However, like the current NRR calculation, BD takes no account of wickets lost, so can produce similarly unjust results. In the example above from the 2013 Champions Trophy Group A, New Zealand's narrow victory over Sri Lanka would have a BD of +81, whereas Sri Lanka's comfortable victory over England would have a BD of only +17.
 
Also, if a match is affected by the weather, a side batting first can win having scored fewer runs, if Duckworth-Lewis increases the target for the team batting second, and they overtake the first team's score, but fail to reach the target. It's not clear what BD would be in this scenario.
 
===Head-to-head record or stage a play-off match===
Split teams level on points using the results from the matches between them. However, this unfairly increases the importance of that one match and reduces the importance of other matches in the league, when all matches in a league should be of equal value − the team with the better head-to-head record will have a worse record against other teams. Also, the head-to-head record will not decide it if the game between them was a No result, or if they played each other twice, and won one game each.<ref>{{cite web |last1=Madhavan |first1=M. J. |title=How Net Run Rate is calculated in IPL |url=https://www.thehindubusinessline.com/news/sports/how-net-run-rate-is-calculated-in-ipl/article23941359.ece/amp/ |website=businessline |date=20 May 2018 |access-date=22 June 2019 |language=en}}</ref><ref>{{cite web |title=IPL 2019: How Net Run Rate (NRR) is calculated |url=https://cricket.yahoo.net/news/ipl-2019-net-run-rate-104520452 |website=Yahoo Cricket |access-date=22 June 2019 |date=26 March 2019}}</ref>
An example of where a team progressed further because of a head-to-head result taken into account, was in the 1999 World Cup semi-finals when South Africa vs Australia played to a tie but Australia progressed due to them beating South Africa in the group stages, even though South Africa won more matches.
 
Alternatively, stage a play-off match between the teams level on points. However, organising this at very short notice may be difficult, or the teams may be in the middle of a league table with no promotion or relegation or progression at stake, so there may be no appetite for a play-off match.
Line 226 ⟶ 191:
 
[[Category:Cricket terminology]]
[[Category:Tie-breaking in group tournaments]]
Retrieved from "https://en.wikipedia.org/wiki/Net_run_rate"