The DLS Method in Cricket: How Rain-Hit Targets Are Set
How does the DLS method set a new target when rain cuts a cricket match short? A plain guide to resources, overs, wickets and why targets can look strange.
seo.test404 
Few things confuse cricket fans more than a rain delay followed by a new target that seems to come from nowhere. Why does a team chasing 250 suddenly need 198 from 34 overs instead of a simple fraction? The answer is the Duckworth-Lewis-Stern method, usually shortened to DLS. This guide explains the idea behind it without the heavy maths.
Where DLS came from
The method was created by two English statisticians, Frank Duckworth and Tony Lewis, and was first used in international cricket in the late 1990s. Australian statistician Steven Stern later updated it to match modern scoring patterns, and his name was added, giving us DLS. The International Cricket Council uses it for rain-affected limited-overs matches.
The key idea: resources
DLS is built on one simple insight. A batting team has two resources to make runs: overs remaining and wickets in hand. Losing overs reduces your chance to score, but so does losing wickets. A team with 10 overs left and 8 wickets in hand can attack hard. A team with 10 overs left and 2 wickets in hand must be careful.
DLS uses a table that gives a percentage of total resources for every combination of overs left and wickets lost. When overs are taken away by rain, the method calculates how much of each team's resources were used, and adjusts the target so that both sides are compared fairly.
Why old methods failed
Before DLS, targets were often set by average run rate. If a team scored 250 in 50 overs, the chasing side might need 5 runs per over for however many overs remained. This ignored wickets completely. A famous example was the 1992 World Cup semi-final, when South Africa were left needing 22 runs from 1 ball after a rain break under a different system. That result pushed the game to find a fairer method.
A simple example
Imagine Team A bats first and scores 250 in a full 50 overs. Team B starts its chase, rain stops play, and 16 overs are lost. Team B now has 34 overs in total. Because it has lost overs but still has wickets in hand, DLS gives it a target lower than 250 but higher than a straight run-rate fraction might suggest, since 34 overs with 10 wickets is a powerful combination. The exact figure comes from the official tables and software used by match officials.
Minimum overs for a result
A match can only be decided by DLS if both teams have had the chance to face a minimum number of overs. In One Day Internationals, that minimum is 20 overs per side. In T20 internationals, it is 5 overs per side. If rain prevents this, the match is a no result.
Common questions fans ask
- Is DLS perfect? No method is, but it is widely accepted as the fairest available.
- Does DLS favour the chasing side? Not by design. It aims to keep both teams' chances balanced.
- Why is the par score shown during a chase? It tells fans which team would win if play stopped at that moment.
Watching matches with DLS in mind
When rain clouds gather, watch the par score shown on the broadcast. Captains do the same. A team slightly ahead of par may push for quick runs before the rain arrives, while a team behind par may slow down to protect wickets. Fans who follow agents and platforms for match updates can find the verified list on the 9wicketsbd24 agent list.
Final thought
DLS looks complicated, but the idea is simple: overs and wickets together decide how many runs a team can realistically score. Understand that, and rain-hit targets suddenly make sense. More cricket explainers are on the 9wicketsbd24 homepage.
