CRR is the current run rate, the runs a team has scored per over so far, and RRR is the required run rate, the runs per over a chasing side still needs to win. CRR looks back at what has happened and RRR looks ahead at what must happen. When RRR is higher than CRR, the chasing side has to score faster than it has been. Both figures are shown on most scoreboards and apps, usually as CRR and RRR or Req RR.
CRR and RRR at a Glance
| CRR | RRR | |
|---|---|---|
| Stands for | Current run rate | Required run rate (asking rate) |
| Looks at | Runs scored so far | Runs still needed |
| Formula | Runs × 6 ÷ balls faced | Runs needed × 6 ÷ balls left |
| Available | Either innings | Second innings of a limited-overs match |
| Changes when | Every ball bowled, and every extra | Every ball bowled, and every extra |
The Formulas
CRR = runs scored × 6 ÷ balls faced
RRR = runs needed × 6 ÷ balls left
You will also see them written as runs ÷ overs. That is the same sum as long as the overs are converted properly, which is where most mistakes start. Working in balls and multiplying by 6 at the end avoids the problem. For the full conversion rules see our net run rate guide, which uses the same arithmetic.
The part-over trap
Overs are written as overs.balls. 12.3 means 12 overs and 3 balls, which is 75 balls, or 12.5 overs. It does not mean 12.3 in decimal. A side on 87 after 12.3 overs has a CRR of 87 × 6 ÷ 75 = 6.96. Divide 87 by 12.3 instead and you get 7.07, which is wrong. The over to ball converter turns any scorebook figure into balls in one step.
A Worked Chase
The first side made 170, so the target is 171 in 20 overs. The chasing side is 82 for 3 after 11.2 overs.
- Balls faced: 11 overs and 2 balls is 11 × 6 + 2 = 68.
- CRR: 82 × 6 ÷ 68 = 492 ÷ 68 = 7.24.
- Runs needed: 171 − 82 = 89.
- Balls left: 120 − 68 = 52.
- RRR: 89 × 6 ÷ 52 = 534 ÷ 52 = 10.27.
The gap is 10.27 − 7.24 = 3.03 runs per over. The side must score about three runs an over faster than it has so far, which is a hard ask but a long way from impossible. Wickets in hand matter as much as the rate, and neither figure shows them, so treat the rate as one input.
What Each Delivery Does to RRR
From the same position, 89 needed from 52 balls (RRR 10.27):
| Next delivery | Needed | Balls left | New RRR |
|---|---|---|---|
| Dot ball | 89 | 51 | 10.47 |
| Wide, no other runs | 88 | 52 | 10.15 |
| Single | 88 | 51 | 10.35 |
| Four | 85 | 51 | 10.00 |
The wide is the one that surprises people: it reduces the runs needed but does not use a legal ball, so the RRR falls. The same goes for a no-ball, which adds the penalty run and any runs off the bat while the ball is re-bowled. Byes and leg byes do use a legal ball, so they behave like a single or a dot with runs added; see the guide to extras for how each is recorded.
Reading the Gap Between CRR and RRR
- RRR below CRR: the chasing side is ahead of the rate and can afford a few quiet overs.
- RRR roughly equal to CRR: the chase is on track if nothing changes.
- RRR above CRR: the side needs to speed up. The bigger the gap and the fewer the wickets in hand, the more risk it has to take.
There is no universal “danger” number, because it depends on the format, the pitch, the boundary size and the batters in. In T20 the powerplay and the last few overs usually carry quicker scoring than the middle, so a flat rate is not a realistic picture of how the innings will go. The chase ladder calculator turns the required rate into a score checkpoint for each over, and the T20 target analyzer and win probability calculator add context on difficulty.
CRR, RRR, Net Run Rate and Projected Score
| Measure | Scope | Used for |
|---|---|---|
| CRR | One innings, live | How fast a side is scoring now |
| RRR | Second innings, live | How fast the chase needs to go |
| Projected score | First innings, live | CRR × overs in the innings, a rough guide only |
| Net run rate | A whole tournament | Separating teams level on points |
Net run rate is runs per over scored across all matches minus runs per over conceded; the net run rate calculator does it for you. Projected score multiplies CRR by the overs in the innings, so a side on 6.96 over 20 overs projects to 139, but that ignores wickets in hand and the faster scoring at the end of an innings. The run rate calculator gives CRR, RRR and projected score together.
Rain, Reduced Overs and Revised Targets
If a match is shortened, RRR uses the revised target and the revised overs. The revised numbers come from the competition’s rules or a method such as Duckworth-Lewis-Stern; the DLS calculator shows how that works. Always use the target the umpires or the match referee give you, not one you worked out yourself, and check your own league’s playing conditions for how it handles reductions.
Why Scorers Care
Run rates are only as good as the ball count behind them. A missed wide, a ball counted twice after a no-ball or a part-over typed as a decimal all produce a wrong CRR and a wrong RRR, and the captain makes decisions from them. Our guide to reading a cricket scorecard shows where the figures come from, and T20 strategy covers how captains use them. Want to record this automatically during your next match? Score your match with CricPulse and the run rates update after every ball.
Frequently Asked Questions
What does CRR mean in cricket?
CRR is the current run rate: runs scored divided by overs faced, with balls counted as sixths. 120 after 20 overs is a CRR of 6.00.
What does RRR mean in cricket?
RRR is the required run rate, or asking rate: the runs a chasing side still needs divided by the overs it has left. Needing 80 from 10 overs is an RRR of 8.00.
How do you calculate required run rate with balls remaining?
Multiply the runs needed by 6 and divide by the balls left. 89 needed from 52 balls is 89 × 6 ÷ 52 = 10.27 runs per over.
Why is 12.3 overs not 12.3 in the formula?
The digit after the point counts balls. 12.3 overs is 75 balls, or 12.5 overs, so 87 runs is a CRR of 6.96, not 7.07.
Does a wide change the required run rate?
Yes. The runs needed fall by one but the balls left stay the same, so the RRR goes down. 89 from 52 becomes 88 from 52, or 10.15 instead of 10.27.
Is CRR the same as net run rate?
No. CRR is live and belongs to one innings. Net run rate is a tournament figure made from runs per over scored minus runs per over conceded across the matches played.
Is run rate used in Test cricket?
CRR is shown and useful for judging scoring speed and declarations, but RRR matters mainly in limited-overs chases with fixed overs. In a Test, time and overs left matter more.