Rain-Affected Overs Calculator

What This Calculator Does

When rain, bad light or any other stoppage costs playing time, umpires don’t touch the target first — they work out how many overs are actually left to bowl. That conversion, sometimes called an over calculation sheet in league playing conditions, turns minutes lost into overs lost using an agreed minutes-per-over rate. Only once the revised over count is known does a method like Duckworth-Lewis-Stern come in to work out a fair target from it.

This tool does that first step: enter the scheduled innings length, the minutes of playing time lost, and your league’s minutes-per-over rate, and it tells you the overs lost, the overs remaining, and whether the innings still meets the minimum overs most competitions require for a result.

The Formula

The result is always rounded down: a partial over’s worth of lost time below the next full increment isn’t deducted, under most playing conditions. Revised overs remaining is simply the scheduled overs minus overs lost, floored at zero.

Why the Rate Isn’t Fixed

There is no single worldwide minutes-per-over rate. Historic playing conditions often used a flat 4 minutes per over; a rate around 4.25 minutes per over is common in current white-ball guidance; and many club leagues simply default to 5 minutes per over for simplicity. Some leagues go further and set different rates for each innings — the Lancashire League, for instance, uses seven minutes per over for the first innings and three and a half for the second. None of these is universally “correct” — whichever figure your own competition’s playing conditions publish is the one that governs your match, which is why this calculator lets you pick or override the rate rather than hard-coding one.

Worked Example

A T20 innings (20 overs) loses 45 minutes to rain, and the league plays to a 4.25-minute-per-over rate. Overs lost = ⌊45 ÷ 4.25⌋ = ⌊10.59⌋ = 10 overs. Revised overs remaining = 20 − 10 = 10 overs. Since 10 overs is above the commonly applied 5-over minimum for a T20 result, the match can still produce one — and the next step is feeding those 10 revised overs into a DLS calculator to set the actual target.

What Happens Next

Once you know the revised overs, two different rulebooks take over depending on the level of cricket. Professional and representative matches apply the Duckworth-Lewis-Stern method to set a fair revised target. Many club and social matches instead just play out the reduced overs without a formal target-revision method at all, or apply a simpler league-specific rule — if your competition also runs cut-off times and over-rate penalties, see our guide to over rate penalties in club cricket for how those two, separate mechanisms interact.

Frequently Asked Questions

How do you calculate overs lost to a rain delay?

Divide the minutes of playing time actually lost by your league’s minutes-per-over rate, then round down to the nearest whole over. For example, a 45-minute delay at 4.25 minutes per over loses 10 overs (45 ÷ 4.25 = 10.58, rounded down to 10), not 11 — the partial over below the next full increment isn’t deducted.

What is a typical minutes-per-over rate for rain delays?

It varies by competition. Historic flat rates of 4 minutes per over are still used in some playing conditions, a rate around 4.25 minutes per over is common in current white-ball cricket, and many club leagues default to 5 minutes per over. Always check your own league’s published playing conditions rather than assuming a figure.

Is this the same as a DLS calculation?

No. This calculator answers a different, earlier question: how many overs are left to bowl after time is lost. Duckworth-Lewis-Stern (DLS) then uses that revised over count to work out a fair target or par score. The overs-lost conversion has to happen first — DLS cannot be applied without knowing the revised overs. Use our DLS calculator once you know the new overs figure.

What is the minimum number of overs needed for a result?

It depends on the competition’s own playing conditions, but a commonly applied figure in international white-ball cricket is 5 overs per side for a T20 and 20 overs per side for an ODI. Below that, a rain-shortened match is more likely to be declared no result. Many club and league formats set their own minimum, which can be different — check your competition’s rules.

Does every league use the same minutes-per-over rate?

No. Rates are set competition by competition. The Lancashire League, for example, uses different rates for each innings — seven minutes per over lost in the first innings and three and a half minutes per over in the second — rather than one flat figure. That is why this calculator lets you enter your own rate instead of assuming a single standard one.

Why does the calculator round the overs lost down rather than up?

Because that is how most playing conditions treat a partial over below the next full increment — time lost that doesn’t add up to one more full over at the agreed rate isn’t deducted. If your league rounds differently, check its specific wording before relying on the figure for an official decision.

Adjust Overs Mid-Match with CricPulse

Once your umpires agree the revised overs, CricPulse lets you update the total overs for the innings directly in the app — the required run rate and every projection recalculate immediately from the new figure. Free on iOS and Android.