Duckworth-Lewis-Stern (DLS) Target Calculator

Why rain needs a formula

When rain shortens a limited overs cricket match, the two teams no longer have equal opportunity to score, so the target has to be adjusted fairly. The Duckworth Lewis Stern method, DLS, is the ICC approved way to do it. This calculator applies the official DLS equations: give it Team 1's score and each side's resource percentage, and it returns Team 2's revised target.

The key idea is resources. A team with 50 overs and 10 wickets has 100 percent of its resources; every over bowled and every wicket lost eats into that. The ICC publishes the resource table that converts overs remaining and wickets lost into a percentage. You look up the two percentages, enter them here, and the formula does the rest.

How to use the DLS calculator

Enter Team 1's completed total. Then find the resource percentages from the ICC DLS table: Team 1's resources used (100 percent minus resources remaining at each interruption, plus resources at resumption) and Team 2's resources available at the start of their innings. The calculator handles both cases: Team 2 with fewer resources than Team 1, and Team 2 with more.

Getting the resource numbers right is the whole job. Track each interruption: note overs remaining and wickets lost when play stops, and the same when it resumes. The difference is the resources lost to rain. Add those losses across multiple stoppages for the full picture.

The formulas and a worked example

When Team 2 has fewer resources than Team 1 used (R2 less than R1), the target scales down proportionally: target equals Team 1's score times R2 divided by R1, rounded up. When Team 2 has equal or greater resources, the target scales up using the average innings total G50, which is 245 for ODIs: target equals S plus G50 times (R2 minus R1) divided by 100, rounded up.

Worked example one: Team 1 scored 170 with 80.8 percent resources used; Team 2 has 91.7 percent available. Since 91.7 exceeds 80.8, target equals 170 plus 245 times 10.9 divided by 100, which is 196.71, rounded up to 197. Worked example two: Team 1 scored 240 with full resources and Team 2 has 30 overs, worth 75.1 percent. Target equals 240 times 75.1 divided by 100, which is 180.24, rounded up to 181 to win.

What changed from DL to DLS

The original Duckworth Lewis method used historical scoring patterns that, over time, undervalued teams batting second in high scoring modern games. Steven Stern's 2014 revision recalibrated the resource table to reflect how teams actually score today, with more aggressive batting through the middle overs. The ICC adopted the Stern revision, hence DLS.

For most club and fan calculations the difference is a few runs either way, but in professional cricket those runs decide tournaments. This calculator uses the Stern era G50 value of 245 for one day internationals, matching the current professional standard.

Common DLS scenarios, decoded

Second innings delayed before it starts: Team 2's resources come straight from the table for the reduced overs, and Team 1 used 100 percent. First innings interrupted: compute Team 1's resources used by subtracting the resource value at each stoppage and adding back the value at resumption. Multiple interruptions just repeat the bookkeeping.

Remember the minimum overs rule: in ODIs, generally at least 20 overs must be possible for Team 2 for a DLS result to stand, unless the chase finishes earlier or a side is bowled out. T20s use their own resource table and a G50 of around 145, so do not apply this ODI calculator to a T20 game.

Why DLS sometimes feels unfair

Every rain affected classic produces the same argument: one set of fans insists the target was too high, the other that it was too low. The method is statistically fair on average, but any single match can feel wrong because DLS assumes an average team. A side stacked with finishers is genuinely more dangerous with 5 overs left than the table assumes, while a side of accumulators is less dangerous. The table cannot know your lineup.

The par score confusion drives most of the anger. Fans see Team 2 ahead of par when rain ends the game and call it a stolen win, but par is simply the score that would tie given resources used. Being ahead of par means Team 2 was winning the game as it stood. The frustration is real but it belongs to the weather, not the arithmetic.

There is also the G50 problem. The constant 245 represents an average ODI innings, but scoring conditions vary wildly: a 245 par on a slow turner is a mountain, on a flat batting deck it is below par. The method trades precision for universality, and most of the time the trade is worth it. When your team loses to DLS, remember the alternative is a coin toss or a shared trophy, and the formula beats both.

Worked Example: Rain in a 50-Over Match

Team 1 scores 280 in their full 50 overs (100 percent resources used, R1 = 100). Rain cuts Team 2's innings to 30 overs. The resource table says 30 overs remaining at the start of an innings is worth 75.1 percent resources, so R2 = 75.1. Since R2 is less than R1, target = 280 x 75.1 / 100 = 210.3, rounded up to 211 to win. Team 2 needs 211 off 30 overs, a required rate of 7.03 per over versus the 5.6 Team 1 managed. The system prices the lost overs as the expensive late-innings overs they are.

Now a mid-innings interruption: Team 2 is 120 for 2 after 20 overs when rain stops play for good with 15 overs lost. Resources remaining at suspension (30 overs left, 2 wickets down) minus resources remaining at resumption (15 overs left, 2 wickets down) is the lost resource. From the table: 75.1 minus 51.1 = 24.0 percent lost, so R2 = 100 - 24.0 = 76.0. Target = 280 x 76 / 100 = 212.8, rounded to 213. Losing middle overs costs less than losing the death overs, and the table knows the difference.

What Changed From DL to DLS

The original Duckworth-Lewis used scoring patterns from the 1990s, when 250 was a big ODI total. By the 2010s, teams scored faster, especially with wickets in hand late in the innings, so the old tables underpriced remaining resources and set targets too low. The Stern update recalibrated the resource table against modern scoring data and introduced the G50 constant of 245 for ODIs. Same structure, sharper numbers: the upgrade was a data refresh, not a new theory.

The most misunderstood part is that DLS measures resources, not fairness of outcome. It answers "what would an average team score with these overs and wickets left," using historical data. It does not account for the specific batsmen at the crease or the match situation. A team cruising at 200 for 1 when rain comes gets the same target as a team stumbling at 200 for 8, because the resource table counts wickets lost, not who is batting. That is a known limitation, and every alternative proposed so far has a worse one.

Why Fans Argue About It Anyway

Every controversial DLS decision follows the same script: a team dominating the match loses to the rain-adjusted target and calls the system broken. The 2003 World Cup gave the famous case when South Africa, needing one run to tie under D/L, blocked the last ball thinking a tie was enough and went out on the miscalculation, not the math. The system priced their resources correctly; the batsmen misread the sheet. DLS cannot fix misreading, and no formula can price momentum, which is what the losing side always believes was stolen. The ICC keeps it because every proposed replacement prices resources worse.