Duckworth Lewis Calculator - DLS Target and Par Score

The duckworth lewis calculator is a cricket decision tool that recalculates the target score for the team batting second in a rain-affected limited-overs match using the official Duckworth-Lewis-Stern (DLS) method. You enter the first-innings total, the overs available to each side, and any wickets lost, and the calculator reads the Standard Edition resource table to return a par score, the target to win, the score to tie, and a match-result verdict when Team 2's score is supplied.

• • Scorers and statisticians: Recalculate the target after a rain delay without flipping through the printed DLS resource table.
• • Coaches and captains: Decide whether to bat first or chase when a coin toss is moved indoors by a wet outfield.
• • Commentators and broadcasters: Quote the revised target live as soon as the umpires announce the overs reduction.
• • Cricket fans and students: Learn how overs and wickets drive target recalculation by running real match scenarios through the calculator.

The Duckworth-Lewis method was first used in international cricket on 1 January 1997 and adopted officially by the ICC in 1999. It was created by English statisticians Frank Duckworth and Tony Lewis after the 1992 World Cup semi-final, where the older Most Productive Overs method left South Africa needing 21 runs from one ball. After they retired, Australian statistician Steven Stern became custodian and the method was renamed Duckworth-Lewis-Stern in November 2014. The Professional Edition runs in international one-day cricket; the Standard Edition is used at lower levels.

This calculator implements the Standard Edition and uses the published resource table to map combinations of overs and wickets into a single percentage of run-scoring resources, so a club scorer gets the same par score an international computer would.

The calculator reads the Standard Edition resource table to find the percentage of run-scoring resources each team has, then plugs those percentages into the DLS par-score formula. If Team 2 has fewer resources than Team 1, the target is scaled down in proportion. If Team 2 has more resources, the target is lifted by adding G50 times the resource surplus.

• S: Team 1's final score, in runs. The single most important input because every target adjustment starts from this number.
• R1: Percentage of run-scoring resources Team 1 used, read from the Standard Edition table.
• R2: Percentage of run-scoring resources Team 2 has, read from the same table.
• G50: Average score expected from the team batting first in an uninterrupted 50-over match. 245 is the international default.

The reduced-target branch is the most common DLS calculation. Team 1 plays a full innings, rain reduces Team 2's overs, and the target is scaled down by the resource ratio. The increased-target branch matters when rain interrupts Team 1's innings; Team 1 saved wicket resource for overs they did not get, so Team 2 should chase a higher score than Team 1 managed. Targets are rounded up to give the win number, and the par score is rounded down to give the tie number.

According to International Cricket Council - Duckworth-Lewis-Stern methodology, the DLS method is the formula the ICC formally adopted to fairly calculate the winning side when rain interrupts a limited-overs match by re-scaling targets based on each team's resources.

The team-1 score that drives DLS is the same per-player batting-card data the cricket batting average calculator works from, so a 231 team total reflects 300-plus decisions the average tool sorts.

Four ideas explain almost every DLS recalculation: the two resources that drive the formula, the Standard Edition resource table, the G50 constant, and the difference between editions.

These four ideas are enough to read any DLS adjustment on a scorecard or broadcast. Once you can name the resources, the table, G50, and the edition in play, the rest is arithmetic.

Resource-based scaling is not unique to cricket. The nfl passer rating calculator combines four capped rate components into a single 0 to 158.3 rating, applying the same resource-scaling idea in a different sport.

The duckworth lewis calculator is built for the innings break or the rain delay, so it expects the first-innings total, the overs available to each side, and the wickets Team 2 has lost.

1. 1 Pick the interruption scenario: Choose 'Team 2 innings reduced' for the common case of a delayed, cut short, or interrupted chase.
2. 2 Enter Team 1 maximum overs: Type the scheduled overs for Team 1. For a 50-over ODI this stays at 50; for a T20 it is 20.
3. 3 Enter Team 1 final score: Type the runs scored by the team batting first. This is the score S that drives every target adjustment.
4. 4 Enter Team 2 maximum overs: Type the maximum overs Team 2 will have for the chase, after any rain reduction.
5. 5 Enter Team 2 wickets lost: Type the wickets Team 2 has already lost at the moment of interruption.
6. 6 Set G50 and review: Leave G50 at 245 for international and county cricket. Read the par score, target to win, and par score to tie.

A 50-over ODI is reduced to 30 overs each before the toss. Team 1 closes on 231. Open the calculator, choose 'Team 2 innings reduced', enter Team 1 maximum overs 50, Team 1 final score 231, Team 2 maximum overs 30, Team 2 wickets lost 0, and leave G50 at 245. Read the verdict: par 173.48, target 174, par to tie 173.

The percentage readouts in this calculator use the same single-percentage style as other sports stat tools. The save percentage calculator reports goalie efficiency from saves and shots on goal in the same one-number format this page uses for resources.

The duckworth lewis calculator replaces a printed resource table and a hand-held DLS computer with one screen that the scorer, captain, and broadcaster can all read at the same time.

• • Standard Edition resource lookup: Reads the published Standard Edition table at every 5 overs from 5 to 50 and every wicket in hand from 1 to 10.
• • Both target branches covered: Handles reduced-target and increased-target scenarios using the G50 constant.
• • Match result verdict: Compares Team 2's actual runs so the scorer can call Won, Lost, Tied, or Below Par.
• • Cricket-side consistency: Uses the first-innings totals and wickets counts scorers already track.
• • Studying real matches: Lets fans rerun famous DLS decisions from the 1992 World Cup or the 2023 IPL final.

These benefits show up most during a rain delay, when the umpires announce the overs reduction and the scoreboard needs a new number within seconds.

Across a tournament, the Won, Lost, Tied, Below Par verdict rolls up naturally into the win-loss-tie count that the winning percentage calculator uses to turn a stack of DLS results into a season win rate.

The calculator returns the DLS number, but the on-field captain must weigh five match-state factors that sit on top of the formula.

• • This calculator uses the publicly published Standard Edition resource table. The Professional Edition used by the ICC runs only on the official DLS computer.
• • G50 is set to the international and county default of 245. Lower-league matches should adjust G50 to reflect local scoring levels.
• • The match-result verdict assumes the innings has ended. Live matches should only use the target to win and par score to tie.

These factors sit on top of the calculator's verdict. A captain who sees a target of 174 from 30 overs still has to read the pitch, the bowlers' workloads, and the light.

According to England and Wales Cricket Board - Duckworth/Lewis/Stern Regulations 2023, G50 for international and county cricket is 245 runs, and the Standard Edition resource table provides percentage values for each combination of overs remaining and wickets lost.