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.
- Match. Pick ODI, T20, T10 or custom overs. Type the overs per side as they were when the match started, not after any rain.
- Team 1 score. Enter the runs Team 1 finished on, whether they batted all their overs, were bowled out or were stopped by rain.
- 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".
- 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.
- 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.
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.
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 default numbers when the page opens are Example 3: Team 1 scores 250 in 50 overs and Team 2 loses 10 overs at 40 for 1 after 12.
| Example | What happened | ICC result | This calculator |
|---|---|---|---|
| 1 | 50 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 185 | 185 |
| 2 | 45 overs. Team 1 scores 212. Team 2 gets 35 overs. | R1 95.0, R2 82.7, target 185 | 185 |
| 3 | 50 overs. Team 1 scores 250. Team 2 stopped at 12 overs, 1 down, 10 lost. | R2 86.8, target 218 in 40 overs | 218 |
| 4 | As 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 159 | 159 |
| 5 | 50 overs. Team 1 ended at 47.1 overs, 8 down, on 226. Team 2 gets 33 overs. | R1 93.1, R2 79.8, target 194 | 194 |
| 6 | As Example 5, plus a Team 2 stop at 25 overs, 2 down, 5 lost. | R2 64.7, target 158 | 158 |
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.
What is the DLS target when rain interrupts the chase?
When rain stops Team 2 mid-chase, the target drops by the share of resources Team 2 lost, not by the share of overs. Losing overs with plenty of wickets in hand costs a lot of resources, while losing overs late in an innings, with many wickets down, costs far less.
Take a 40-over match. Team 1 makes 230, so R1 is 89.3%, the value for 40 full overs. Rain arrives with Team 2 on 15.3 overs, 2 down, and 8 overs are lost:
- 24.3 overs were left with 2 down, worth 59.8%. After the break, 16.3 overs are left, worth 45.7%. Team 2 lost 14.1%.
- R2 = 89.3 − 14.1 = 75.2%.
- Par = 230 × 75.2 ÷ 89.3 = 193.68, rounded down to 193. The target is 194 in 32 overs.
Team 2 lost a fifth of its overs but the target fell by only 36 runs, about 16%, because the overs it lost came with eight wickets still in hand.
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.
How is a match decided if it cannot be finished?
If Team 2 has faced the minimum overs and play cannot restart, the match goes to the par score at the moment play ended. Team 2 wins with more runs than the par score, loses with fewer and ties on exactly the par. Enter the last stoppage with every remaining over lost to get it.
Say Team 1 makes 260 in a 50-over match and the rain sets in for good with Team 2 at 30 overs, 5 down. The 20 overs left with 5 down were worth 38.6%, so R2 = 100 − 38.6 = 61.4%. The par score is 260 × 61.4 ÷ 100 = 159.64, rounded down to 159. On 160 or more Team 2 wins, on 159 the match is tied and on 158 or fewer Team 1 wins.
The minimum is 20 overs for Team 2 in a 50-over match and 5 overs in a 20-over match. Below that there is no result, unless Team 2 has already passed the target or been bowled out. The calculator shows a warning when the chase falls below these limits.
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 men's internationals and first-class teams, and 200 for women's, associate and Under-19 matches, 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.
For most matches the two editions agree or are within a few runs. The gap grows in very high-scoring games, where the Professional Edition assumes a different pace of scoring. For local leagues, school cricket and tournaments without the ICC software, the Standard Edition is the official method, and this page is built for exactly that.
DLS calculator FAQ
How many overs are needed for a DLS result?
Team 2 must be able to face at least 20 overs in a 50-over match and 5 overs in a 20-over match. If fewer are possible, there is no result, unless Team 2 has already passed the target or been bowled out. The calculator warns you when the chase falls below that minimum.
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 and sometimes differ by a few runs.
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 internationals and first-class teams. The ICC sets 200 for women's, associate and Under-19 matches, but the ECB's 2026 methodology lists 245 for Under-19 internationals, so check your competition's rules. Local leagues may set their own average first-innings score.
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.
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.