🏏DLS Par Score Calculator
Detailed Guide Coming Soon
We're working on a comprehensive educational guide for the Duckworth-Lewis-Stern Calculator in your language. The content below is shown in English.
What is Duckworth-Lewis-Stern Calculator?
▾
Imagine you are hosting a weekend backyard cricket match and a sudden downpour cuts your game short. How do you decide who wins fairly when one team got to bat for 20 overs, but the other only got 10? In professional cricket, they don't just guess—they use the Duckworth-Lewis-Stern (DLS) method. It is the ultimate mathematical referee, designed to solve the age-old headache of rain-interrupted matches. Instead of using outdated, unfair rules that ruined games for decades, DLS uses smart math to calculate a fair, adjusted target so everyone goes home happy (or at least, feeling treated fairly). At its heart, DLS works like managing a household budget. In cricket, a batting team has two main "currencies" or resources: the number of overs they have left to play, and the number of wickets (or outs) they still have in hand. If you have plenty of time and all your wickets, you can afford to take big risks and score quickly. But if you lose wickets early, you have to play defensively. When rain cuts a game short, DLS looks at how much of these two resources each team had left when play stopped. It then adjusts the target score so both teams face an equally difficult challenge, regardless of how much time the weather stole from them. Why does this matter to you? If you are a casual fan watching a big match on TV, a fantasy sports enthusiast tracking player points, or a local club player trying to figure out if your team won the weekend league game before the storm rolled in, understanding DLS keeps you in the loop. Instead of scratching your head when the scoreboard suddenly changes from needing 150 runs to needing 132, you will know exactly how the math leveled the playing field. It turns a confusing statistical black box into a clear, logical tool that helps you enjoy the game and settle friendly debates over a cold drink.
DigiCalcs delivers precision-engineered tools for engineers and STEM professionals.
Формула
▾
The core idea behind the DLS target calculation is surprisingly simple: we compare the resources available to both teams.
Here is the basic formula:
Team 2 Target = [Team 1 Score × (R2 / R1)] + 1 run (rounded down to the nearest whole number, then add 1 to win)
Where:
S1 = The total runs scored by Team 1
R1 = The resource percentage available to Team 1 (this is 100% if they got to play their full 50 overs without any interruption)
R2 = The resource percentage available to Team 2 after taking into account any rain delays, lost overs, or mid-innings stops
How do we find R1 and R2? They come from the official DLS resource tables, which look at how many overs are left and how many wickets have been lost. For example, if Team 1 scores 300 runs in a full 50 overs (R1 = 100%), and rain reduces Team 2's innings to just 30 overs before they even start batting (R2 = 75.1%), their revised target is calculated as:
Target = [300 × (75.1 / 100)] + 1 = 225.3 + 1 → 225 (rounded down) + 1 = 226 runs to win in 30 overs.Variable Legend
▾
| Symbol | Ime | Единица | Опис |
|---|---|---|---|
| R1 | Team 1's Starting Capital (Resources) | % | The total batting resources Team 1 has at their disposal (starts at 100% for a full, uninterrupted game). |
| R2 | Team 2's Remaining Capital (Resources) | % | The resource percentage left for Team 2 after taking into account any lost overs or rain delays. |
| S1 | Team 1's Raw Score | runs | The actual number of runs scored by the first team during their innings. |
| T | The New Adjusted Target | runs | The exact number of runs Team 2 must score to win the match, rounded up to keep things fair. |
| Z(u,w) | The Resource Curve | % | A smart mathematical function that calculates how much batting power you have left based on overs remaining (u) and wickets lost (w). |
| G50 | The Ground Average Benchmark | runs | A setting used to adjust the calculations for high-scoring or low-scoring pitches, ensuring the math fits the day's playing conditions. |
How to Duckworth-Lewis-Stern Calculator
▾
- 1Both teams start the match with a full bank account of resources: 100% of their overs (50 for ODIs, 20 for T20s) and all 10 wickets intact.
- 2If rain pauses the game, the scorers check the official DLS resource table to see exactly how much 'currency' (overs and wickets remaining) is lost.
- 3If Team 1's batting is cut short, their final score is scaled up mathematically to estimate what they would have scored if they had their full resources.
- 4If Team 2's chase is interrupted, the calculator constantly updates a 'par score'—the exact number of runs they need to be at right now to be considered safe.
- 5The final target is always rounded up to the next whole run, ensuring Team 2 must actually beat Team 1's adjusted performance rather than just matching it.
- 6For shorter formats like T20s, a specialized resource table is used because teams play much faster and value wickets slightly differently than in longer games.
- 7Local clubs and professional leagues alike use computerized versions of these tables to instantly spit out the new targets, saving captains from doing complex math in the middle of a muddy field.
Worked Examples
▾
When the sun is shining and no rain stops play, both teams have 100% of their resources. Team 1 plays all 50 overs, and Team 2 gets the exact same opportunity. No adjustments are needed, so Team 2 simply needs one more run than Team 1's score of 250 to win the game.
Team 1 scored a solid 280 runs using 100% of their resources. Then, a heavy downpour delayed the start of the second innings, cutting Team 2's time down to 40 overs. According to the DLS table, 40 overs with 0 wickets lost equals 89.3% of full resources. We multiply Team 1's score by this resource ratio: 280 × 0.893 = 250.04. We round this down to 250 and add 1, giving Team 2 a fair target of 251 runs to chase in their 40 overs.
Imagine Team 2 is cruising at 185 runs for 3 wickets after 30 overs while chasing a massive target of 300. Suddenly, the heavens open up and the game is called off. To find out who won, we calculate the DLS 'par score' for this exact moment. Based on having 20 overs left and 3 wickets down, Team 2 needed to be at 196 runs to be on track. Since they are at 185 (11 runs short of par), Team 1 is declared the winner of this damp duel.
In a fast-paced T20 match, Team 1 sets a target by scoring 160. A sudden storm limits Team 2's reply to just 12 overs. Using the T20-specific DLS resource curve, 12 overs with all 10 wickets in hand gives Team 2 71.0% of their resources. To find the new target, we calculate 160 × 0.71 = 113.6. We round this down to 113 and add 1, meaning Team 2 needs to smash 114 runs in their 12 overs to secure the victory.
Real-World Applications
▾
Local club captains use DLS calculators on their phones during cloudy Saturday afternoon matches to figure out if they need to speed up their scoring before the storm hits.
Fantasy cricket players monitor live DLS par scores during rain delays to predict which players will get more batting time and adjust their lineups accordingly.
TV commentators and sports journalists use live DLS data to explain the game's shifting momentum to viewers at home, turning complex math into an exciting narrative.
Amateur league organizers use simplified DLS tables to resolve rain-shortened tournament matches fairly, preventing heated arguments at the post-game barbecue.
Special Cases
▾
If Team 1 gets cut short while batting
If Team 1 gets cut short while batting, we have to estimate what they would have scored if they had their full 50 overs. This is called calculating a 'notional' score. It prevents Team 2 from getting an easy ride just because Team 1 didn't get to finish their innings.
Extremely low-scoring games
In games where the pitch is tough and scores are incredibly low (like under 100 runs), the DLS calculation can sometimes set a target that is higher than what Team 1 actually scored. This happens because the math assumes any normal team with 10 wickets left would easily score more. If you hit this weird edge case in backyard or local games, common sense and a friendly agreement usually work best!
The stop-and-start rain dance
When rain stops and starts multiple times, the calculations pile up. Every single stoppage requires a new calculation of remaining resources. Don't worry if the target keeps changing every time the players walk back onto the field—the calculator is just keeping the balance of power perfectly level after each delay.
Quick Guide: How Batting Resources Decay (Standard 50-Over Match)
▾
| Overs Remaining | 0 Wickets Lost | 2 Wickets Lost | 5 Wickets Lost | 7 Wickets Lost | 9 Wickets Lost |
|---|---|---|---|---|---|
| 50 | 100.0% | 83.8% | 49.5% | 26.1% | 7.6% |
| 40 | 89.3% | 75.1% | 44.6% | 23.5% | 6.9% |
| 30 | 75.1% | 63.4% | 37.6% | 19.8% | 5.8% |
| 20 | 56.6% | 47.6% | 28.2% | 14.9% | 4.3% |
| 10 | 32.1% | 26.9% | 16.0% | 8.4% | 2.4% |
| 5 | 17.2% | 14.4% | 8.5% | 4.5% | 1.3% |
| 1 | 3.6% | 3.0% | 1.8% | 0.9% | 0.3% |
Frequently Asked Questions
▾
What actually is the DLS method in simple terms?
Think of DLS as a fair-play calculator for when rain ruins a cricket match. It looks at how many overs a team has left and how many wickets (outs) they have left to figure out a fair revised target. Instead of just guessing or using simple averages, it treats overs and wickets like valuable resources. This ensures neither team gets cheated by a sudden change in the weather.
Why can't we just use a simple percentage of overs to change the target?
If you lose 20% of your overs, you might think you should just lose 20% of your target score. But cricket doesn't work that way because having 10 wickets to use over 40 overs is much easier than having 10 wickets over 50 overs—you can play much more aggressively! DLS understands that wickets are just as valuable as overs. A simple percentage split would make chases far too easy for the team batting second.
What is the difference between a 'target' and a 'par score'?
The target is the final score Team 2 must reach to win the match once the total number of overs has been locked in. The par score, on the other hand, is a moving target that changes with every single ball and wicket lost during a chase. It tells you exactly how many runs the chasing team needs to have scored at any specific second if the rain suddenly stops the game for good. It's like a real-time safety line.
Why does the target sometimes go UP when overs are cut?
This is one of the most confusing parts of cricket, but it actually makes perfect sense! If Team 1 bats first and gets interrupted by rain, they might have played cautiously expecting to bat for 50 overs, only to have their innings cut short. Because they didn't get to launch a late-innings attack with their remaining wickets, DLS boosts their score to a 'what-if' total. This means Team 2 has to chase a slightly higher, fairer target to make up for Team 1's lost opportunity.
Does this rule apply to our local weekend T20 games?
Absolutely, though you'll want to make sure you're using the specific T20 version of the resource tables. Because T20 cricket is much shorter and faster, players value their wickets differently than in a 50-over match. Many local club leagues use simplified mobile apps or online calculators to run these numbers so players don't have to carry printed math sheets in their kit bags.
How many overs do we need to play for a DLS result to count?
You can't just play one over and call it a game! For a match to have an official result under DLS, both teams must bat for a minimum number of overs. In international 50-over matches, that minimum is 20 overs per side, while in quick T20 matches, it's just 5 overs per side. If the rain doesn't let you reach these limits, the match is declared a 'no result' and everyone shares the points.
Who actually came up with this system, and is it still updated?
The system was originally invented by two British statisticians, Frank Duckworth and Tony Lewis, after a famously unfair rain rule ruined a 1992 World Cup semi-final. Later, in 2014, an Australian professor named Steven Stern updated the math to handle modern, high-scoring matches. That is why it's now officially called the Duckworth-Lewis-Stern (DLS) method, and it's managed globally to keep up with how fast modern batsmen score.
Common Mistakes to Avoid
▾
- !Mixing up the target with the par score. The target is what you need to win by the end of the game, while the par score is your real-time 'survival' line if the match ended right this second.
- !Thinking a 20% cut in overs means a 20% cut in target runs. This ignores the fact that you still have all your wickets left, which lets you play much more aggressively over those remaining overs!
- !Forgetting to check if you've played the minimum number of overs. If you haven't hit the 5-over mark in T20s or 20-over mark in ODIs, the DLS math doesn't apply and the game is a draw/no-result.
Pro Tip
Keep an eye on the wickets column! In a tight rain-affected chase, losing a single wicket can instantly boost the DLS par score by 10 or 15 runs. If you're the batting captain, keeping wickets in hand is your absolute best insurance policy against a sudden downpour.
Did you know?
Did you know the DLS method was born out of pure frustration? During the 1992 World Cup semi-final, South Africa needed a very doable 22 runs from 13 balls. After a brief rain delay, the old rule recalculated their target to an absolutely impossible 21 runs from just 1 ball! This absurd moment outraged fans worldwide and inspired Frank Duckworth and Tony Lewis to create the fair system we use today.
References
Добијте неделни математички совети
Придружете се на 12.000+ претплатници кои добиваат совети за калкулатори секоја недела.