DLS Calculator (Duckworth-Lewis-Stern Method)
Calculate revised targets using the official DLS method for rain-affected cricket matches
Comprehensive Guide: How is DLS Calculated in Cricket?
The Duckworth-Lewis-Stern (DLS) method is the official mathematical formulation used to calculate revised targets in rain-affected limited-overs cricket matches. Developed by statisticians Frank Duckworth and Tony Lewis (later refined by Steven Stern), this method has become the standard for all international and major domestic cricket competitions since its introduction in 1997.
Understanding the Core Principles of DLS
The DLS method operates on two fundamental concepts:
- Resource Percentage: Represents the combination of overs and wickets remaining as a percentage of total available resources
- Par Score: The score that would be exactly equal to the resources used by both teams at any point in the match
Unlike simple run-rate comparisons, DLS accounts for the fact that:
- Wickets in hand are valuable resources (more wickets = more aggressive batting possible)
- Overs remaining allow for different scoring strategies
- The value of resources changes non-linearly throughout an innings
The Mathematical Foundation
The current DLS system uses a complex table of resource percentages that vary based on:
| Overs Remaining | Wickets in Hand (10) | Wickets in Hand (5) | Wickets in Hand (1) |
|---|---|---|---|
| 50 | 100.0% | 90.3% | 75.1% |
| 40 | 75.1% | 65.7% | 50.2% |
| 30 | 50.2% | 41.7% | 27.5% |
| 20 | 27.5% | 20.9% | 11.9% |
| 10 | 11.9% | 8.2% | 3.5% |
The complete DLS table contains values for every combination of overs (from 1 to 50) and wickets (from 0 to 10). The key formula for calculating revised targets is:
Revised Target = Team 1 Score × (Team 2 Resources / Team 1 Resources) + 1
Where:
- Team 1 Resources = Resources available at start – Resources used when Team 1 batted
- Team 2 Resources = Resources available at interruption point
Step-by-Step Calculation Process
-
Determine Team 1’s Resource Usage:
Calculate what percentage of resources Team 1 used during their innings based on overs faced and wickets lost. For example, if Team 1 batted 40 overs and lost 4 wickets, they used approximately 55% of their resources (leaving 45% unused).
-
Assess Team 2’s Available Resources:
When play is interrupted, determine how many overs and wickets Team 2 will have available when play resumes. The DLS table provides the exact resource percentage for this combination.
-
Calculate the Ratio:
Divide Team 2’s available resources by Team 1’s remaining resources to get the adjustment factor.
-
Compute Revised Target:
Multiply Team 1’s total score by this ratio and add 1 run (to ensure the chasing team must actually surpass the target).
-
Determine Required Run Rate:
Calculate how many runs Team 2 needs to score per over to achieve the revised target in their remaining overs.
Practical Example Calculation
Let’s work through a real-world scenario:
Match Situation: In a 50-over ODI, Team A scores 280/6 in their 50 overs. Team B is 45/2 after 10 overs when rain stops play. After a 2-hour delay, the match is reduced to 30 overs for Team B.
Step 1: Team A’s resource usage
- Batted full 50 overs with 4 wickets remaining (6 lost)
- From DLS table: 50 overs with 4 wickets = 90.3% resources used
- Therefore, Team A had 9.7% resources remaining (100% – 90.3%)
Step 2: Team B’s available resources
- Will have 30 overs total (already played 10, so 20 remaining)
- Currently has 8 wickets in hand
- From DLS table: 20 overs with 8 wickets = 45.6% resources
Step 3: Calculate revised target
- Ratio = Team B resources / Team A remaining resources = 45.6% / 9.7% ≈ 4.70
- Revised target = 280 × 4.70 + 1 ≈ 1316 + 1 = 1317 runs
- But this can’t be right – let’s correct the approach
- Actual calculation: Team B’s target = (Team A score × Team B resources) / Team A resources
- Team A used 90.3% resources to score 280
- Team B has 45.6% resources available
- Revised target = (280 × 45.6%) / 90.3% ≈ 141 runs in 30 overs
- But they’ve already scored 45 in 10 overs, so need 96 more in 20 overs
- Final revised target: 141 runs in 30 overs (required RR: 4.7)
Common Misconceptions About DLS
| Misconception | Reality |
|---|---|
| DLS favors the team batting first | The method is mathematically balanced to be fair to both teams based on resources |
| DLS is just about run rates | It considers both overs AND wickets as resources |
| The “+1 run” is arbitrary | It ensures the chasing team must actually win rather than tie |
| DLS tables are the same for all formats | Different tables exist for ODIs, T20s, and different match conditions |
Historical Evolution of Rain Rules in Cricket
Before DLS, cricket used several different methods to handle rain interruptions:
-
Average Run Rate (Pre-1992):
The simplest method where the target was adjusted based on the ratio of overs. If Team A scored 250 in 50 overs and Team B got 30 overs, their target would be (250 × 30)/50 = 150. This ignored wickets completely.
-
Most Productive Overs (1992-1996):
Introduced the concept of counting only the highest scoring overs from Team A’s innings to set a target. Still didn’t account for wickets properly.
-
Duckworth-Lewis (1997-2014):
The original version that revolutionized rain rules by introducing resource percentages. First used in the 1997 England vs Zimbabwe ODI.
-
DLS (2014-Present):
Refined by Steven Stern to improve accuracy, especially for T20 matches. The current standard used by ICC.
Controversies and Famous DLS Incidents
While generally accepted as the fairest system, DLS has been involved in several controversial moments:
-
1999 World Cup Semi-Final (Australia vs South Africa):
The most famous DLS controversy where South Africa needed 21 runs from 4 balls when rain stopped play. The DLS calculation (which was less sophisticated then) gave Australia a tie and passage to the final, eliminating South Africa. This led to significant refinements in the method.
-
2015 World Cup (Ireland vs Zimbabwe):
Ireland were set a revised target of 239 from 47 overs after rain. They reached 237/7 when rain returned with 3 balls left. The match was declared a tie, with many arguing Ireland should have won as they were ahead of the DLS par score.
-
2019 World Cup Final (England vs New Zealand):
While not strictly a DLS controversy, the super over result (where England won on boundary count) led to calls for DLS to be used in super overs as well.
How DLS Handles Different Match Scenarios
The DLS method is designed to handle various interruption scenarios:
-
Single Interruption:
The most common case where play stops once and then resumes with reduced overs. The calculation is straightforward as described above.
-
Multiple Interruptions:
If play stops and starts multiple times, DLS recalculates the target each time based on the new resource availability. Each interruption creates a new “mini-match” scenario.
-
Match Abandoned:
If insufficient overs remain to constitute a match (minimum 20 overs per side in ODIs, 5 in T20s), the match is abandoned with no result.
-
First Innings Interruption:
If rain interrupts the first innings, DLS calculates what the score would have been at the interruption point if the innings had been uninterrupted, then sets this as the target for the second innings (adjusted for any overs lost).
DLS in T20 Cricket: Special Considerations
While the principles remain the same, T20 matches require some adjustments:
-
Different Resource Tables:
T20s use different resource percentage tables that account for the more aggressive scoring patterns in the shortest format.
-
Minimum Overs:
A T20 match requires each team to face at least 5 overs to constitute a result (compared to 20 in ODIs).
-
Powerplay Adjustments:
The DLS tables for T20s account for the mandatory powerplay overs where scoring is typically higher.
-
Super Over Integration:
In some competitions, if a rain-affected T20 ends in a tie, a super over is used instead of further DLS calculations.
How to Read a DLS Par Score Sheet
During broadcasts, you’ll often see a DLS par score sheet that shows:
- Overs: The over number being considered
- Par Score: The score that would be exactly equal to the resources used by both teams at that point
- Required RR: The run rate needed to reach the par score from the current position
- Resources: The percentage of resources used/remaining
For example, if the sheet shows:
After 20 overs: Par Score = 120, Required RR = 6.00, Resources = 50%
This means that at the 20-over mark, a score of 120 would mean both teams have used exactly 50% of their resources, making the match evenly balanced at that point.
Limitations and Criticisms of DLS
While DLS is the most sophisticated system available, it does have some limitations:
-
Assumes Linear Resource Usage:
The method assumes teams use resources at a consistent rate, which isn’t always true in modern cricket where teams often “save” wickets for late assaults.
-
Doesn’t Account for Match Context:
DLS doesn’t consider the match situation (e.g., a team might bat differently if they’re 200/2 vs 200/8 even with the same resources).
-
Complexity for Fans:
The calculations are complex and not easily understandable by casual fans, leading to confusion during rain-affected matches.
-
Data Dependency:
The accuracy depends on the historical data used to create the resource tables, which may not perfectly match current playing styles.
Alternative Methods Proposed
Several alternatives to DLS have been proposed over the years:
-
VJD Method (V Jayadevan):
Developed by Indian engineer V Jayadevan, this method claims to be more accurate by using a different resource calculation approach. It’s used in some Indian domestic competitions.
-
Average Run Rate Plus (ARRP):
A modified version of the old average run rate method that attempts to account for wickets lost.
-
Machine Learning Models:
Some researchers have proposed using AI to predict match outcomes based on real-time data rather than pre-calculated tables.
Official Resources and Further Reading
For those interested in the technical details of DLS calculations:
- ICC Playing Conditions (Official DLS Rules)
- Marylebone Cricket Club (MCC) DLS Explanation
- ESPNcricinfo DLS Explainer
The Future of Rain Rules in Cricket
As cricket evolves, so too must the methods for handling interruptions. Potential future developments include:
-
Real-time Dynamic Calculations:
Using live ball-tracking data and player statistics to adjust resource values dynamically during a match.
-
Format-Specific Optimizations:
Developing separate DLS variants optimized for The Hundred, T10, and other emerging formats.
-
Enhanced Fan Communication:
Better visualizations and explanations during broadcasts to help fans understand DLS decisions.
-
Integration with Other Technologies:
Combining DLS with Hawk-Eye and other tracking systems for more precise resource assessment.
While no system will ever be perfect, the DLS method represents the most sophisticated attempt to date to ensure fair results in rain-affected cricket matches. Its continued refinement by statisticians and cricket administrators helps maintain the integrity of the game in the face of unpredictable weather conditions.