Officials
Quotient Calculator
The runs per wicket ratio still used as a tie break across a great many club and school leagues.
Quotient
1.186
above par
Runs for
1240
Wickets lost
62
Runs against
1180
Wickets taken
70
Runs per wicket for
20.00
Runs per wicket against
16.86
Beyond the calculator
Umpires and scorers using Crickslab get the revised target, the par score and the over rate on screen, signed off and shared in seconds.
- Rain rules applied as the match runs
- Results and points posted automatically
- Live streaming with the score on the picture
How this was worked out
- 1Runs per wicket scored1240 / 62 = 20.00
- 2Runs per wicket conceded1180 / 70 = 16.86
- 3Divide one by the other20.00 / 16.86 = 1.186
How the number is worked out
The formula
Quotient = (runs for / wickets lost) / (runs against / wickets taken)- runs for
- Runs your side scored across the season.
- wickets lost
- Wickets your side lost across the season.
- runs against
- Runs conceded across the season.
- wickets taken
- Wickets your bowlers took across the season.
A quotient above 1 means you score more per wicket than you concede. Below 1 means the reverse.
Overs never appear. That is the whole point of quotient: it can be worked out straight from a scorebook.
A worked example: a full season
Across a season a club has scored 1240 for the loss of 62 wickets, and conceded 1180 while taking 70.
- 1Runs per wicket scored1240 / 62 = 20.00
- 2Runs per wicket conceded1180 / 70 = 16.86
- 3Divide one by the other20.00 / 16.86 = 1.186
A quotient of 1.186, comfortably above par. In a league that separates level teams on quotient, that is the number the committee will read.
Rules and edge cases
The situations that change the answer, and the ones most calculators get wrong.
Quotient is not net run rate
Net run rate measures runs per over. Quotient measures runs per wicket and ignores overs entirely. They answer different questions and they can rank the same two teams in opposite orders. A side bowled out cheaply is punished much harder by quotient.
A side that lost no wickets has no divisor
Dividing by zero wickets has no meaning. Most leagues substitute ten wickets in that case, but it is a local rule rather than a universal one, so check your regulations before applying it.
Declarations distort it
In competitions where sides declare, a team that declares on 250 for 4 records four wickets lost rather than ten, which inflates its runs per wicket. Leagues that use quotient usually have a rule covering declarations for exactly this reason.
Why leagues still use it
It can be worked out from a scorebook without converting a single over, which mattered a great deal before every club had a laptop. That is also why it survives in school and village cricket long after professional competitions moved to net run rate.
Frequently asked questions
Divide your runs scored by wickets lost, divide runs conceded by wickets taken, then divide the first figure by the second.
For league officials
Whichever tie break your competition uses, kept up to date on its own
Crickslab maintains standings with quotient, net run rate or head to head applied in whatever order your regulations set out, updated as each result is scored.
See tournament managementLast reviewed 17 August 2026. Playing conditions change, so if your competition uses a different rule, its regulations take precedence over anything here.