DLS Calculator: Revised Target for Rain-Hit Matches

Work out the Duckworth-Lewis-Stern target for any rain-affected match, with as many stoppages as you need in either innings. Every result shows its full working, using the ICC Standard Edition table.

Match

Match shortened before it began? Keep the format and type the overs it started with, such as 40 for an ODI. The format sets the minimum overs for a result: 20 in an ODI, 5 in a T20, and 10 in knockouts that ask for it, such as the ICC Men's T20 World Cup semi-finals and final.

G50 is set by the playing conditions of your competition. The ICC uses 245 for matches involving full members and between first-class teams, and 200 for women's, associate, Under-19 and Under-15 internationals; the ECB's 2026 methodology uses 245 for Under-19 internationals. Local leagues may set their own value.

Team 1 stoppages

Add one row per stoppage. If rain ended the innings, enter all the overs that were left as overs lost. Write overs as 32.4 for 32 overs and 4 balls.

Team 2 innings

Penalty runs given to the fielding side while Team 2 bats raise the target and every par score by the same number (ICC DLS rules, section 6). Penalty runs Team 1 earned while batting are part of its score, and penalty runs to Team 2 go on Team 2's score without changing the target.

How this target was worked out

Every number comes from the ICC Standard Edition resource table, ball by ball.

  1. Team 1 starts with 20 overs and 10 wickets: 56.6% of resources.
  2. Team 1 resources, R1 = 56.6%.
  3. Team 2 starts with 20 overs and 10 wickets: 56.6% of resources.
  4. Team 2 stoppage at 7 overs, 0 down: 13 overs left = 40.2%. After losing 4 overs, 9 left = 29.3%. Resources lost: 10.9%.
  5. Team 2 resources, R2 = 45.7%.
  6. R2 is not more than R1, so par = 184 × 45.7 ÷ 56.6 = 148.57, rounded down to 148. Target = 148 + 1 = 149.

Par score for the rest of the chase

Par after each completed over from here, for 0 to 9 wickets down. If play ends for good, Team 2 wins when it is above par.

DLS par score for Team 2 by completed overs and wickets down
Overs0 wkt1 wkt2 wkt3 wkt4 wkt5 wkt6 wkt7 wkt8 wkt9 wkt
75354565963697892112133
86264656771768395113133
97273747678838999114133
1082838485879095103115133
11929393949698102107118133
12103103104104105107109113121133
13114114114115115116117120125134
14125125125125125126127128130136
15136136136136136137137137138140

Add this DLS calculator to your website

Free for club, league and cricket blog sites. Paste this code where the calculator should appear. It works on any site, including WordPress (use a Custom HTML block).

How do you use this DLS calculator?

Choose the format, enter Team 1's final score, then add a row for every stoppage. Each row needs the overs bowled when play stopped, the wickets down at that moment and the overs lost. Enter the overs Team 2 had at the start of its chase, and the revised target appears straight away.

  1. Match. Pick ODI, T20, T10 or custom overs. Type the overs per side as they were when the match started, not after any rain.
  2. Team 1 score. Enter the runs Team 1 finished on, whether they batted all their overs, were bowled out or were stopped by rain.
  3. Team 1 stoppages. Leave this empty if Team 1 batted without a break. If rain ended Team 1's innings early, add a stoppage and put every remaining over in "overs lost".
  4. Team 2 overs. Enter the overs Team 2 was given when its innings began. This is often the same as Team 1's overs, or fewer if overs were lost during the break.
  5. Team 2 stoppages. Add a row for each break in the chase. If the match is abandoned, put all the remaining overs in "overs lost" and the result panel switches to the par score that decides the match.

Write overs the way a scorer does: 32.4 means 32 overs and 4 balls, so the number after the point is always 0 to 5. The result panel, the working and the par table update as you type, and the page address changes with your inputs, so you can share or bookmark the exact result.

What does the DLS calculator show?

It shows Team 2's revised target and the overs to get it in, the par score that ties the match, and the resources each team had, called R1 and R2. Below that is every step of the working and a par table for each remaining over and wicket of the chase.

The target is what Team 2 must reach to win. The par to tie is one run less. R1 and R2 are the share of a full 50-over, 10-wicket innings that each team had, after taking away what the stoppages cost. If Team 2 cannot face the minimum overs for a result, a warning appears above the numbers: pick the format and type the overs the match started with, so a 40-over ODI still needs 20 overs for Team 2. If play cannot restart, enter the last stoppage with every remaining over lost and the par score at that moment decides the match; the DLS method guide explains the minimum overs and abandoned matches.

The par table answers the question scorers get asked every time the covers come on: "where do we stand if it does not stop raining?" Find the completed overs on the left and the wickets down across the top. If play ends for good at that point, Team 2 wins when its score is above the number in the cell.

How does the calculator work out the target?

It reads each team's resources from the ICC Standard Edition table, using overs left and wickets lost, and takes away the resources lost in every stoppage. If Team 2 had fewer resources than Team 1, Team 1's score is scaled down by R2 ÷ R1. The result is rounded down, then one run is added.

If Team 2 had more resources than Team 1, which happens when Team 1's innings was cut short, the extra resources are worth G50 runs per 100%. The par score becomes Team 1's score + G50 × (R2 − R1) ÷ 100. In both cases the target is the par score rounded down, plus one.

Line chart of DLS resources remaining against overs left, from 0 to 50 overs, with one line each for 0, 2, 4, 6 and 8 wickets lost. With no wickets lost, 50 overs left is 100%, 20 overs is 56.6% and 10 overs is 32.1%. The lines flatten as wickets fall.
Resources remaining from the ICC Standard Edition table. The more wickets lost, the less the remaining overs are worth.

Rain during the chase cuts the target by the share of resources lost, not the share of overs. In a 40-over match where Team 1 makes 230 and Team 2 loses 8 overs at 15.3 overs with 2 down, Team 2 loses a fifth of its overs but the target falls by only 37 runs, from 231 to 194 in 32 overs, because those overs came with eight wickets in hand. The worked examples in the DLS method guide go through cases like this step by step.

Resources are rounded to one decimal place after each innings, and every stoppage in the same innings is added up. That is exactly how the ICC playing conditions describe the Standard Edition, so the working on this page can be checked line by line against the table. For the background to resources and why wickets matter as much as overs, read the DLS method explained.

Does this calculator match the ICC's own examples?

Yes. The ICC playing conditions include six worked examples of the Standard Edition, and this calculator gives the same resources, par scores and targets for all six. The buttons above the calculator load four of them. "Rain during chase" is Example 3: Team 1 scores 250 in 50 overs and Team 2 loses 10 overs when it is 1 down after 12.

The six ICC worked examples, with G50 = 245
ExampleWhat happenedICC resultThis calculator
150 overs. Team 1 stopped at 20 overs, 3 down, 10 overs lost, ends on 180. Team 2 gets 40 overs.R1 87.5, R2 89.3, target 185185
245 overs. Team 1 scores 212. Team 2 gets 35 overs.R1 95.0, R2 82.7, target 185185
350 overs. Team 1 scores 250. Team 2 stopped at 12 overs, 1 down, 10 lost.R2 86.8, target 218 in 40 overs218
4As Example 3, then a stop at 22 overs, 3 down, 2 lost, and the match ends at 30.2 overs, 6 down.R2 63.8, par 159159
550 overs. Team 1 ended at 47.1 overs, 8 down, on 226. Team 2 gets 33 overs.R1 93.1, R2 79.8, target 194194
6As Example 5, plus a Team 2 stop at 25 overs, 2 down, 5 lost.R2 64.7, target 158158

Each example is part of the test suite that runs before any change to this site goes live, in both the browser code and the server code that prints the first result on the page.

Why can the target be higher than Team 1's score?

When Team 1 loses overs in the middle of its innings, it batted those early overs without knowing the innings would be shorter. If Team 2 then gets the same reduced overs from the start, Team 2 has more resources than Team 1, so the target is raised above Team 1's score to make up for it.

This is ICC Example 1. In a 50-over match, Team 1 is 3 down after 20 overs when 10 overs are lost. It finishes on 180 from 40 overs:

  • R1 = 100 − (61.6 − 49.1) = 87.5%. Team 2 starts with 40 overs and 10 wickets, so R2 = 89.3%.
  • R2 is more than R1, so par = 180 + 245 × (89.3 − 87.5) ÷ 100 = 184.41, rounded down to 184.
  • The target is 185 in 40 overs, five more than Team 1 scored.

What is G50 and which value should you use?

G50 is the average score expected in a full 50-over first innings. It is only used when Team 2 has more resources than Team 1. The ICC sets 245 for matches involving full-member nations and between first-class teams, and 200 for women's internationals, Under-19 and Under-15 internationals and matches between associate members, but competitions can choose their own value.

The ECB's 2026 methodology lists 245 for Under-19 internationals, so the right value for a youth match depends on who runs it. For club and school cricket, a league can set G50 to a typical first-innings score at its level and use the custom option here. When Team 2 has fewer resources than Team 1, as in most chases cut short by rain, G50 does not change the target at all.

Why can an official target differ from this calculator?

International matches and the major T20 leagues use the DLS Professional Edition, which runs on ICC software and adjusts for high-scoring matches. Its formulas are not published. This calculator uses the Standard Edition, the published table the ICC names as the method when the software is not available.

How close are they? We checked 33 recent rain-hit internationals and league matches (35 targets and par scores). All 17 T20 figures came within 3 runs of this calculator. In ODIs, 11 of 18 were within 5 runs, but the gap reached 9 to 23 runs in six matches, nearly all after Team 1 scored 300 or more or rain cut a long stretch of either innings: the Professional Edition assumes a different pace of scoring in those games. The full comparison lists the biggest gaps. Local leagues, school cricket and tournaments without the ICC software usually use the Standard Edition, since it needs nothing but the table, and this page is built for exactly that. Check your competition's playing conditions for the edition it names.

DLS calculator FAQ

Is this the official ICC DLS calculator?

No. DLSCalc is an independent calculator, not an ICC product. It uses the DLS Standard Edition resource table and formulas that the ICC publishes in its playing conditions, the official method when the ICC's Professional Edition software is not available. International matches use that software, so an official target can differ from ours. In 35 checks from 33 recent rain-hit matches, every T20 target and par came within 3 runs of this calculator, while ODIs differed by up to 23 runs after a big first innings.

Is this a Duckworth-Lewis calculator or a DLS method calculator?

Both. The Duckworth-Lewis (D/L) method became Duckworth-Lewis-Stern in 2014, when Steven Stern updated it, so a Duckworth-Lewis calculator, a D/L calculator and a DLS method calculator all mean a tool like this one. It uses the current DLS Standard Edition table, not the old D/L figures.

How many overs are needed for a DLS result?

Team 2 must be able to face at least 20 overs in an ODI and 5 overs in a T20, even if the match started with fewer overs. If fewer are possible, there is no result, unless Team 2 has already passed the target or been bowled out. Some knockout matches ask for more: at the ICC Men's T20 World Cup, the semi-finals and the final need at least 10 overs a side. The calculator warns you when the chase falls below the usual minimum for the format you pick.

Can I add more than one rain break?

Yes. Add a row for every stoppage in either innings, up to ten per innings. The resources lost in each stoppage are added together, which is how the ICC playing conditions handle several interruptions.

Why can my answer differ from the official target?

International matches and big franchise leagues use the DLS Professional Edition, which runs on ICC software and is not published. This calculator uses the published Standard Edition table, the ICC's official fallback, so targets usually match or come close. In 35 checks from 33 recent rain-hit matches, every T20 target and par came within 3 runs of this calculator, while ODIs differed by up to 23 runs after a big first innings. See how close it comes in famous rain-hit matches.

What is the par to tie?

It is one run less than the target. If the match ends with Team 2 exactly on the par score, the match is tied. When Team 2's innings is cut short for good, the par score decides the winner.

Which G50 should I use?

Use 245 for men's matches between full-member nations or first-class teams, and 200 for women's internationals, associate matches and Under-15 internationals: those are the ICC's values. For Under-19 internationals the ICC says 200 but the ECB's 2026 methodology lists 245, so check your competition's rules. Local leagues may set their own average first-innings score.

How do penalty runs change the DLS target?

Only penalty runs given to Team 1 while Team 2 is batting change it: the target and every par score go up by that many runs, with no new calculation (ICC DLS rules, section 6). Enter them in the penalty runs box. Penalty runs Team 1 earned while batting are already in its score, and penalty runs to Team 2 at any time go on Team 2's score without changing the target.

What if rain ends Team 1's innings early?

Add a Team 1 stoppage at the overs bowled when play stopped, with the wickets down, and enter every remaining over as overs lost. The calculator then treats Team 1's innings as finished and usually sets Team 2 a target above Team 1's score.

Can I save or share a result?

Yes. The page address updates with your inputs, so the link reproduces the same result. Use the WhatsApp button, copy the link, or print the page with the par table for the scorers.

Is there a DLS calculator app?

You do not need to install one. Open DLSCalc once with a connection and your phone keeps the calculators, so they work offline at the ground. On most phones you can also add DLSCalc to the home screen from the browser menu, and it opens like an app.

Sources

The resource table, formulas and worked examples come from the ICC playing conditions. G50 values are cross-checked against the ECB's published methodology.

Cricketer and tournament organiser

I played club cricket for 20 years at National Cricket Club (NCC), a city-level club registered with the PCB, and now organise tournaments. I built these calculators because I needed accurate rain targets during live matches. Every tool shows its working.