How to Use This DLS Calculator

Our free DLS calculator lets you compute revised targets in three simple steps. Whether you are a commentator, a fantasy cricket player, or just a curious fan watching a rain-interrupted match, here is exactly how to use it.

1. Enter match details. Start by selecting the match format (ODI or T20), entering the total overs originally allotted to each team, and the score of the team batting first. If the first innings was also interrupted, enter the overs and wickets at the point of interruption so the calculator can adjust the first team's resource percentage accurately.
2. Enter interruption details. Input the over number at which play was stopped, the number of wickets that had fallen, and the revised number of overs now available to the chasing team. You can add multiple interruptions if rain stopped play more than once during the innings.
3. Read the revised target. The calculator instantly displays the DLS par score and the revised target. The par score is what the chasing team needs to be level at any given point, while the revised target is the final score needed to win. A step-by-step breakdown shows you exactly which resource percentages were used so you can verify the maths yourself.

What Is the DLS Method?

The Duckworth-Lewis-Stern (DLS) method is the internationally accepted mathematical formula used to calculate fair revised targets in rain-affected or otherwise interrupted limited-overs cricket matches. It was created by English statisticians Frank Duckworth and Tony Lewis in 1997 and later refined by Australian professor Steven Stern, who became its custodian in 2014. The ICC renamed it from "D/L method" to "DLS method" in Stern's honour. At its core, DLS treats each combination of overs remaining and wickets in hand as a "resource" and uses a detailed percentage table to ensure both teams have an equivalent opportunity to win, regardless of interruptions. Read our full guide to the DLS method in cricket.

When Is DLS Applied in Cricket?

The DLS method is activated whenever the number of overs available to either or both teams is reduced after the match has started. Common scenarios include:

• Rain delays — the most frequent reason. If rain stops play and overs are lost, DLS recalculates the target for the chasing team.
• Bad light — when fading light forces the umpires to call off play early, especially in day-night matches without floodlights at full capacity.
• Wet outfield or ground conditions — even without active rain, a waterlogged outfield can cause delays that shorten the match.
• Floodlight failure — rare, but if stadium lights malfunction and play cannot resume, DLS is used to determine the result.
• Multiple interruptions — DLS handles any number of stoppages within a single innings, recalculating resources after each resumption.

DLS Method Examples

Example 1: 2019 World Cup Semi-Final — India vs New Zealand

In one of the most dramatic World Cup matches in history, the semi-final at Old Trafford was spread across two days due to rain. New Zealand batted first and posted 239/8 in their full 50 overs. There was no interruption during the first innings, so New Zealand used 100% of their resources.

India's chase began on the reserve day with the full 50 overs available. No DLS revision was needed in this case because both teams received their complete allocation. However, had rain interrupted India's innings at, say, 30 overs with 3 wickets down, here is how DLS would have worked:

• Resources remaining at 30 overs, 3 wickets down: approximately 34.9%
• Resources used by India: 100% - 34.9% = 65.1%
• New Zealand used 100% of resources to score 239
• DLS par score for India at that point: 239 x 65.1% = approximately 156
• If India were at 156 or above when rain ended play, they would have won via DLS

Example 2: IPL Rain-Affected Match — CSK vs MI

Consider a typical IPL scenario: Mumbai Indians bat first and score 185/5 in 20 overs, using 100% of their resources. Rain arrives during the innings break, and Chennai Super Kings are given only 14 overs to chase.

• Resources available for 20 overs, 0 wickets: 100%
• Resources available for 14 overs, 0 wickets: approximately 78.1%
• CSK have fewer resources (78.1% vs 100%), so the target is scaled down
• Revised target: 185 x (78.1 / 100) + 1 = approximately 146 runs from 14 overs
• CSK need 146 to win — a required rate of 10.43 per over instead of the original 9.30

Notice that even though the target came down from 186 to 146, the required run rate actually went up. This is a common source of confusion for fans, but it reflects the fact that CSK lost more batting resources (overs) than the raw score reduction might suggest.

Why Do DLS Targets Sometimes Feel Unfair?

The key concept in DLS is resources. A team's resources are the combination of overs remaining and wickets in hand — and they are not linear. Losing 5 overs when you have 10 wickets in hand costs far fewer resources than losing 5 overs when you have only 4 wickets left, because a team with more wickets can accelerate more aggressively later.

This means the chasing team sometimes gets a target that feels too low or too high. For example, if a team has lost early wickets before rain arrives, the DLS target may actually increase because the interruption saved them from losing more wickets during a difficult spell. Conversely, a team cruising at 2 wickets down may feel the revised target is harsh because it does not fully account for their momentum. The maths, however, is statistically validated across thousands of matches and remains the fairest system available.

DLS vs VJD Method

The VJD (V. Jayadevan) method was proposed by Indian civil engineer V. Jayadevan as an alternative to DLS. It uses a different mathematical model that plots separate curves for the "normal" and "target" innings, claiming to handle certain scenarios — like shortened first innings — more accurately. The BCCI briefly used VJD in domestic cricket. However, in 2012 the ICC conducted a formal evaluation and chose to retain the DLS method as its official standard, citing its proven track record, wider testing across international matches, and the continuous refinements made by Steven Stern. As of 2026, DLS remains the only ICC-approved method for calculating revised targets in all international and franchise cricket.

Frequently Asked Questions About DLS

What does DLS stand for?

DLS stands for Duckworth-Lewis-Stern. It is named after its three architects: Frank Duckworth and Tony Lewis, who created the original formula in 1997, and Steven Stern, who took over as the method's custodian and refined the resource tables. The ICC officially added Stern's name in 2014, changing the abbreviation from D/L to DLS.

Who invented the DLS method?

The method was invented by Frank Duckworth, a statistician, and Tony Lewis, a mathematician — both from England. They developed it in response to the infamous 1992 World Cup semi-final between England and South Africa, where the existing rain rule produced an absurdly unfair target. After their retirement, Professor Steven Stern of Bond University, Australia, became the method's custodian and updated the underlying mathematical model.

Is DLS used in T20 cricket?

Yes, DLS is fully applicable in T20 cricket. It is used in the IPL, T20 World Cup, Big Bash League, and all ICC-sanctioned T20I matches. The same resource percentage tables are used, but because T20 matches have only 20 overs, even a small reduction in overs has a proportionally larger impact on the revised target. A minimum of 5 overs per side is required for a valid DLS result in T20s.

Can DLS give a higher target than the original score?

Yes, this can happen. If the team batting second has more resources available than the team that batted first — for example, if the first innings was curtailed by rain but the second innings gets full overs — the DLS target will be higher than what the first team actually scored. This ensures fairness: the team with more overs and wickets at their disposal is expected to score proportionally more.

Why was the DLS method introduced?

Before DLS, cricket used the "average run rate" and "most productive overs" methods to set revised targets. Both were deeply flawed. The average run rate method ignored wickets entirely, while the most productive overs method could produce bizarre results — as seen in the 1992 World Cup semi-final where South Africa needed 22 runs off 13 balls, and after a rain delay, their target became 22 off just 1 ball. DLS was introduced to replace these methods with a statistically rigorous formula that accounts for both overs and wickets as combined "resources," providing fairer outcomes in interrupted matches.