DLS Calculator

What is the Duckworth-Lewis-Stern (DLS) method?

The Duckworth-Lewis-Stern (DLS) method is the official mathematical model used in limited-overs cricket to set fair revised targets when a match is interrupted, most commonly by rain. It treats each batting team as starting with two finite resources — overs remaining and wickets in hand — and assigns a resource percentage to every combination of the two.

When a chase is interrupted, the DLS engine measures the resources Team 2 lost to the stoppage, compares Team 2’s available resources (R₂) to Team 1’s available resources (R₁), and rescales (or boosts) the target accordingly.

How this calculator works

This is an advanced, live DLS workspace. Anything you change on the form recomputes the answer in real time — no Calculate button required. The calculator supports four working modes via tabs:

• Innings 2 Rain Reduction — the classic case: Team 1 batted normally, rain hit during Team 2’s chase, and overs were cut. Use the rain simulator slider to stress-test more rain.
• Innings 1 Shortened — rain ended Team 1’s innings early and it never resumed; Team 2 has a fresh allotted-overs chase. For a delayed start, just set Format to the reduced overs. If Team 1’s innings restarted after a break, use Multi-Interruption.
• Multi-Interruption — supports any number of stoppages across either innings. Add interruptions in chronological order with the situation at each break.
• Resource Table — a heatmap of the DLS Standard Edition table for reference and learning.

Custom over formats (12, 16, 25 overs and the rest)

Club, school and corporate cricket is rarely 20 or 50 overs — six-a-side, sixteens, the 12-over evening league at your local club, all of it works here. Pick Custom… in the Format dropdown and type any value from 5 to 50 overs per side.

There is no separate table for shorter games. The DLS regulations are explicit about this: “the same table and the same method of calculation are used whatever the number of overs per innings”. What changes is where you start reading it. A 20-over innings begins on 56.6% of a full 50-over innings rather than 100%, and a 10-over innings on 32.1%. Because both sides are measured on that one scale, the R₂/R₁ ratio that sets the target still comes out right.

For the same reason G50 stays a 50-over number — 245, or 200 for associate, women’s ODI and U15 cricket. It is only used when Team 2 ends up with more resources than Team 1, and it converts a surplus expressed in 50-over resource points into runs. Override it if your league’s own 50-over average is different, but do not scale it down because you are playing a T20.

The DLS formula, step by step

The calculator shows the working on every recompute. The numbered breakdown panel walks through:

1. How R₁ was computed (Team 1’s available resources, accounting for any interruptions during their innings).
2. How R₂ was computed (Team 2’s available resources, less anything lost to rain).
3. Which formula branch applied — Target = S₁ × R₂ ÷ R₁ + 1 when R₂ < R₁, or Target = S₁ + G50 × (R₂ − R₁) ÷ 100 + 1 when R₂ > R₁.

Rain simulator

The rain-simulator slider in the standard tab lets you remove additional overs from Team 2’s revised total on the fly. The target, par score, win probability and resource bars all update instantly — useful for contingency planning and tournament directors trying to anticipate cut-offs.

Win-probability insight

Once a revised target is in place, the calculator overlays a chase win-probability estimate. The model factors in required run rate vs the format baseline, wickets in hand, and the phase of innings. It is calibrated for fan-level intuition — broadcast win-probability charts use more sophisticated proprietary models with venue, player and ball-by-ball features.

Par-score curve

The par-score curve plots the score Team 2 needs to be on at each over to be exactly on the DLS line, given the current wickets lost. A point above the line means Team 2 is ahead of the chase; a point below means they need to recover.

Resource table

The Resource Table tab renders the official DLS Standard Edition lookup as a colour-coded heatmap. Reading is intuitive: pick the row matching your overs remaining (normalised to a 50-over equivalent for T20/T10 matches), then the column matching wickets lost. The intersection is the resource percentage available to that team.

History of the DLS method

Before the DLS method, cricket used the “most productive overs” method, criticised after the 1992 World Cup semi-final between England and South Africa, when South Africa were left to score 22 off 1 ball after a brief rain delay. Frank Duckworth and Tony Lewis introduced their model in 1997, the ICC adopted it in 1999, and Professor Steven Stern updated the parameters in 2014 — giving us the present-day DLS.

When DLS is used

• Rain or hail delays during a match.
• Bad light causing an early end to an innings.
• Any other interruption that reduces overs in a limited-overs game.
• Multiple interruptions in the same match — use the Multi-Interruption tab.

DLS in domestic and grass-roots cricket

The DLS Standard Edition (what this tool uses) is open and can be worked by hand, which is why it is the usual fallback when no computer is available. International cricket, and ECB competitions down to club leagues, use the Professional Edition through the ICC’s software (built into scoring apps such as Play-Cricket), which additionally scales the resource curves by Team 1’s actual score. Its parameters are unpublished and it runs as official ICC software, so this calculator deliberately does not try to imitate it — where the first innings was well above or below par, a broadcast target will sit a few runs away from the one here.