DLS Calculator
Calculate revised targets using the Duckworth-Lewis-Stern method
DLS Calculator
Calculate revised targets using the Duckworth-Lewis-Stern method
What is the Duckworth-Lewis-Stern (DLS) Method?
The Duckworth-Lewis-Stern (DLS) method is the official ICC system for working out a new target when a cricket match is interrupted by rain, bad light, or any other delay. Before DLS, rain-affected matches used simpler methods that were widely criticised as unfair, because they ignored how many wickets a team had lost.
Worked scenario: Team 1 scores 280/6 in a full 50-over match. Rain then cuts Team 2's innings down to 30 overs before they even start batting. A simple method might just scale the target down: 280 × (30/50) = 168. DLS works differently — it knows Team 2 is losing their most valuable overs, the high-scoring ones near the end, so the DLS target usually comes out higher, often around 190-210 depending on the exact numbers.
The core idea is simple: a batting team has two things to spend — overs left and wickets left. Both run out as the innings goes on. When overs are lost to rain, DLS looks at what resources are left and sets a fair new target, instead of just cutting the runs down in a straight line.
How to Use This Calculator
Why DLS Matters in Cricket
DLS decides the outcome of countless rain-hit matches, including major tournament games and finals. A team can be batting comfortably and still lose because the DLS target moved against them after an interruption, which is why every fan following a match on a rainy day needs to understand roughly how it works.
Captains change their approach the moment rain becomes a real threat. A team batting first might push much harder for quick runs if bad weather is forecast, since a bigger score protects them better under DLS if the second innings gets cut short. This tactical shift is something you only notice if you understand what DLS is trying to do.
It also explains a moment that confuses a lot of casual viewers: the "par score" shown on screen during a delay is not the actual target. It is just what the chasing team would need at that exact moment to be level under DLS — it keeps changing as the delay goes on, and only becomes the real target once the final number of overs is confirmed.
?Frequently Asked Questions
DLS looks at both things a batting team has left — overs and wickets. Older methods only looked at overs lost, ignoring that a team with 9 wickets and 5 overs left has a lot more chance than a team with 1 wicket and 5 overs left. DLS treats these two together, which gives a fairer target.
In T20 internationals, each side needs at least 5 overs. In ODIs, each side needs at least 20 overs. If rain doesn't allow even that much play, the match is called a no-result.
When Team 2's innings gets cut short mid-chase, DLS can set a target that looks higher than what Team 1 actually scored. This is because Team 2 hasn't had the chance yet to use their own big-scoring overs near the end — DLS treats those lost overs as a real loss and adjusts for it.
No — and this is one of the most common mix-ups. The "par score" shown during a rain delay is just what the chasing team needs at that moment to be level. It changes over by over. The real, final target is only locked in once the total overs for the innings are confirmed.
A simple scale-down only looks at overs and ignores wickets completely. It also doesn't account for the fact that the overs lost are usually the highest-scoring ones near the end of the innings. That's why a straight percentage cut is usually lower than the actual DLS target.
Yes, sometimes. Even though DLS is more fair than older methods, it can still produce targets that feel harsh in specific situations, especially when a match is interrupted more than once. Some players have called for improvements over the years, though no better system has replaced it since DLS came in.
Yes. DLS is used across nearly all limited-overs formats, including domestic T20 leagues, as long as the match has a minimum number of overs completed per the rules. The same overs-and-wickets idea applies, just scaled for a shorter 20-over match instead of a 50-over one.