Cricket Calculator

Strike rate is the number that tells you how fast a batter actually scores, not just how many runs end up next to their name. It's simply runs scored divided by balls faced, multiplied by a hundred. A batter with 45 off 30 balls has done more damage to a bowling attack than someone who ground out 45 off 60, even though the scorecard shows the same runs. That's why in T20 cricket a strike rate is almost as important as the score itself — a flashy 40 that eats 45 balls can actually hurt a team's chances more than it helps.

Batting average has been cricket's go-to yardstick for over a century, and for good reason — it captures consistency in a single number. You get it by dividing total runs scored by the number of times a batter has actually been dismissed, which is the part people often get wrong: not-out innings don't count as a dismissal, so they're left out of the divisor entirely. That's exactly why a player who finishes not-out several times can carry a much higher average than their raw run tally might suggest — those unbeaten knocks boost the number without adding to the count they're divided by.

Net run rate is the quiet tie-breaker that decides who tops a group when points are level, and it trips people up more than any other cricket stat because of one detail: it isn't just about one match. NRR is worked out across every game a team has played in a tournament — total runs scored per over faced, minus total runs conceded per over bowled. The twist most people miss is what happens when a team is bowled out early; instead of using the overs they actually faced, the rules count it as if they'd used every over available in that match. Get that wrong and your NRR maths will never match the official points table. Our dedicated NRR calculator handles this automatically, match by match.

Economy rate is a bowler's version of damage control — it tells you how many runs they leak per over, calculated as total runs conceded divided by overs bowled. A bowler who goes for 24 runs in 4 overs has an economy of 6, and whether that's good or bad depends entirely on the format and the phase of the innings. Conceding 6 an over in the tense final overs of a T20 chase is a fine result; conceding the same in the middle overs of a Test match would be a disaster. It's one of those numbers that only really means something once you factor in the context around it.

Rain has ended more cricket matches unfairly than almost anything else in the sport, which is exactly the problem the DLS method was built to solve. Instead of just chopping overs off the chasing team's innings and leaving them with an unreasonable target, DLS looks at how many run-scoring "resources" — a combination of overs left and wickets in hand — each side actually had available, and recalculates a fair target from that. It's the reason a rain-hit chase sometimes ends up with a target that looks oddly specific, like 187 off 32 overs; that number has been reverse-engineered from resource tables rather than simple arithmetic, and it's what keeps interrupted matches from turning into a coin flip.

Cricket overs look like decimals but they don't behave like them, and that catches out a lot of people doing quick maths on a scorecard. "14.3 overs" doesn't mean fourteen-and-three-tenths of an over — it means 14 complete overs plus 3 balls of the next one. Since every over is 6 legal balls, converting is just a matter of multiplying the whole overs by 6 and adding the leftover balls, so 14.3 overs becomes (14 × 6) + 3 = 87 balls. Skip that step and treat .3 as 0.3, and every run rate or NRR figure built on top of it comes out wrong.

Going the other way is just as common, especially when you're working from ball-by-ball data and need to know how many overs that translates to for a run rate or bowling figure. Take the total balls bowled, divide by 6, and whatever's left over after the whole number becomes the balls part in cricket notation. So 87 balls isn't 14.5 overs — it's 14 full overs with 3 balls left, written as 14.3. That one-digit difference between a real decimal and cricket's overs notation is a small thing, but it's exactly where most manual run-rate calculations quietly go wrong.