Illustrated graphic of stadium floodlights and a red cricket ball with the headline DLS method explained: how rain targets work

The Duckworth-Lewis-Stern (DLS) method is the system cricket uses to reset a target when rain or bad light cuts overs from a one-day or T20 match. It does not simply scale the target by overs lost. Instead, it measures how much of a team’s run-scoring “resources” — overs left and wickets in hand — has been taken away, and adjusts the target in proportion. That is why a chasing side 2 wickets down can be set a very different target from one 6 down, even when both lose the same number of overs.

Fans in India saw it in action this week. In the first ODI at Eden Park on November 4, 2026, New Zealand were bowled out for 185, but rain kept interrupting India’s chase and the target was revised to 143 in 32 overs. India won by five wickets “(DLS method)”. This guide explains exactly how a number like 143 is reached, what the “par score” on the big screen means, and why the system still causes arguments almost 30 years after it was born.

Key takeaways

  • DLS treats an innings as two resources — 300 balls and 10 wickets — and sets revised targets according to how much of those resources each side actually had.
  • The target is what the chasing side must reach after an interruption; the par score is the score they need to be ahead of if no more play is possible.
  • A result needs at least 20 overs per side in an ODI and 5 overs per side in a T20, unless a team is bowled out or the chase is completed earlier.
  • Wickets matter as much as overs: losing overs with plenty of wickets in hand costs a side far more “resource” than losing them when 7 or 8 down.

Why cricket needed DLS: the 1992 semi-final

Before DLS, rain rules were blunt. The most infamous example came in the 1992 World Cup semi-final in Sydney. South Africa were chasing England when a short shower arrived; under the “most productive overs” rule then in use, their equation was recalculated to 21 runs off one ball. The match was effectively over, and the cricket world agreed something had to change.

Two English statisticians, Frank Duckworth and Tony Lewis, built a model that recognised a simple truth every fan knows: a team with ten wickets in hand can attack in a way a team eight down cannot. Their method was first used in an international on January 1, 1997, in the second ODI between Zimbabwe and England, and the ICC adopted it as the standard for rain-shortened one-day games in 1999. After both men retired, Australian academic Steven Stern became the method’s custodian and it was renamed Duckworth-Lewis-Stern in late 2014.

The core idea: overs and wickets are “resources”

Think of a 50-over innings as a full tank: 300 balls and 10 wickets, which together equal 100% of a team’s resources. Every ball bowled and every wicket lost drains that tank. When rain removes overs, it removes a slice of resources too — and how big that slice is depends on when the overs are lost and how many wickets are down at the time.

Losing overs late in an innings usually hurts more, because the final overs are when sides score fastest. And the value of an over shrinks as wickets fall: 10 overs left with 9 wickets in hand is a launchpad, while 10 overs with 1 wicket in hand is a scramble. DLS captures both effects in a resource table.

The modern “Professional Edition” used in international cricket runs on software whose detailed figures are not published. But the older Standard Edition table is public and shows the logic clearly:

Overs remainingWickets in handResources remaining (Standard Edition)
5010100.0%
301075.1%
201056.6%
101032.1%
51017.2%
Illustrative values from the public Standard Edition table. International matches use the Professional Edition software, which can give slightly different numbers.

Notice the curve. A side with 20 overs left and all wickets intact still has well over half its resources — 56.6%, not 40%. That is exactly why a straight “runs per over” adjustment is unfair: wickets in hand are worth runs.

How the revised target is calculated

Call the first team’s score S, the resources the first team had R1, and the resources the second team has R2. The ECB’s published DLS methodology sets out three cases:

  • Second team has fewer resources (R2 < R1): target = S × R2 ÷ R1, plus 1, with decimals dropped. This is the most common case — the chasing side loses overs, so its target comes down.
  • Equal resources (R2 = R1): target = S + 1, exactly as in an uninterrupted game.
  • Second team has more resources (R2 > R1): the target goes up. Under the published formula, the extra resources are multiplied by G50 — the average first-innings score in a 50-over match, set at 245 for matches between ICC full members — and added on.

That third case surprises many fans. If the team batting first loses overs mid-innings, it bats for a while as if it had the full 50, scoring cautiously and protecting wickets. When the innings is then cut short, it has not been able to use its resources fully. The team chasing knows from ball one how many overs it has, so it can plan its innings — and DLS asks it to score more to compensate.

Reading the Eden Park example

New Zealand used up all their resources by being bowled out for 185 in 40.2 overs, so R1 is effectively 100%. India’s chase was reduced to 32 overs and their target became 143. Working backwards from the formula, that implies India were judged to have roughly 77% of a full innings’ resources — more than the 64% you would get by simply comparing 32 overs with 50. Put simply, losing 18 overs while having lots of wickets in hand did not cost them 18/50ths of their chance.

Par score vs target: the number on the big screen

During a rain-threatened chase, broadcasters show a “DLS par score”. This is not the target. It is the score the chasing side needs to be ahead of at that moment, given the wickets they have lost, if the match is abandoned and no further play is possible.

  • Above par when play is abandoned: the chasing side wins.
  • Exactly on par: the match is tied.
  • Below par: the side batting first wins, and the margin is given in runs relative to par.

The ECB document gives a neat example: a team chasing 201 in 50 overs is 115 for 4 after 30 overs when play is abandoned. Par at that point is 110, so they win by 5 runs (DLS method). Had they been 105 for 4, they would have lost by 5.

Par changes with every wicket. ESPNcricinfo’s explainer showed how sharply: in one washed-out game, Australia’s par after 20 overs ranged from 41 with no wickets down to 84 with four down. That is why captains in a rain-hit chase often tell batters to “stay ahead of par” rather than chase the full target — and why a wicket just before a shower can decide a match.

Misreading this distinction has cost teams dearly. At the 2003 World Cup in Durban, South Africa batted in the rain against Sri Lanka believing the figure they had been given was the winning target. It was the par score for a tie. The match was tied, and the hosts were knocked out of their own tournament.

Minimum overs and when DLS does not apply

DLS can only produce a result if enough cricket has been played to constitute a match. In international cricket the thresholds are:

FormatMinimum overs per side for a resultException
ODI (50 overs)20 oversFewer is fine if a side is bowled out or the chasing side reaches its target
T20 (20 overs)5 oversSame exceptions apply

If the minimum is not reached, the match is a no result. DLS also has nothing to do with Test cricket, where time lost to weather simply makes a draw more likely. Domestic competitions and leagues can set their own minimums, so always check the playing conditions for a particular tournament.

Common myths and fair criticisms

Myth: “DLS always favours the chasing team”

Not true. As shown above, an interruption in the first innings often pushes the chasing side’s target up. Whether DLS seems kind or harsh depends entirely on the timing of the rain and the wickets lost.

Myth: “Wickets lost after the rain don’t count”

The target is set using the wickets down at the moment of the interruption. Wickets that fall later do not change that fixed target, but they absolutely matter for the next par score if more rain arrives. In one ESPNcricinfo example, a side that was 67 for 1 at a stoppage left the opponents’ target unchanged at 292; had it been 67 for 4, the target would have dropped to 284.

Fair criticism: it ignores who is batting

DLS counts wickets, not names. Four wickets down with a set centurion and a big hitter at the crease is treated the same as four down with two tailenders in. Critics also point out that the model can be less reliable in T20 cricket, where a single over can swing a game, and that it does not explicitly account for powerplay restrictions. Alternatives have been proposed — India’s V. Jayadevan devised the VJD system, which has been used in some Indian domestic cricket — but DLS remains the ICC’s choice.

A fan’s cheat-sheet for rain-hit games

  1. Check the wickets column first. A chasing side that is two down is usually well placed against par; five down and it is often behind, even if the run rate looks healthy.
  2. Watch the par score over by over when dark clouds are around. Teams batting second will try to stay ahead of it at the end of every over.
  3. Remember the 20-over (ODI) and 5-over (T20) rule. Before those points, an abandonment means no result.
  4. First-innings rain can raise the target. Don’t assume the side batting second is getting a gift.
  5. Look for “(DLS method)” in the result. Margins under DLS are stated against the revised target or par, which is why you sometimes see odd-looking wins by a handful of runs.

With India’s five-match ODI series in New Zealand moving to Wellington, where coastal weather can change quickly, there is a decent chance DLS will be back on the screens soon. Our NZ vs IND 2nd ODI preview covers the conditions and the key battles.

What do you think? Join the discussion in our CricAmore forums and share your take with fellow fans.

Frequently asked questions

Who invented the DLS method?

English statisticians Frank Duckworth and Tony Lewis created the original Duckworth-Lewis method, first used in 1997. Australian statistician Steven Stern later took over its development, and it was renamed Duckworth-Lewis-Stern in late 2014.

What is the DLS par score?

It is the score the chasing team needs to be ahead of, for the wickets it has lost, if the match is abandoned at that point. Above par wins, equal ties, below par loses.

How many overs are needed for a DLS result?

In international cricket, at least 20 overs per side in an ODI and 5 overs per side in a T20I, unless a team is bowled out or the target is reached earlier.

Is DLS used in Test cricket?

No. DLS is only for limited-overs matches. In Tests, time lost to rain is not compensated with revised targets; it simply reduces the time available to force a result. (For a Law that applies in every format, see our LBW rule explainer.)

Sources: ECB – Duckworth Lewis Stern Methodology, ESPNcricinfo – How the DLS method works, Wikipedia – Duckworth-Lewis-Stern method, cricket.com.au – NZ vs India 1st ODI report, Outlook India

7 Comments

Comment

New Report

Close