GALAXY OF TOOLS

HEALTH SECTOR

DLS Calculator — Rain-Rule Target Estimator

Estimate a rain-revised cricket target and par scores with the Duckworth–Lewis method, for ODI or T20.

50 for ODIs, 20 for T20s.
Lower it if overs were lost between innings.
Team 1 stoppages

No stoppages.

Team 2 stoppages
1

Overs as overs.balls (20.3 = 20 overs 3 balls). “Overs per innings after” is the new length of that innings; set it equal to the overs bowled if no more play was possible.

Check Team 2’s position (optional)
Revised target for Team 2220Team 2 need 220 to win from 40 overs; 219 ties. Estimate — published D/L model fitted to open data, not the official DLS calculation.

R2 < R1: par = ⌊250 × 87.7 ÷ 100.0⌋ = 219; target = 219 + 1 = 220

  1. Team 1 starts with 50 overs: 100.0%
  2. Team 2 starts with 50 overs: 100.0%
  3. Team 2, stoppage 1 at 20 ov, 2 wkts: 30 ov left = 69.2%, 20 ov left = 56.9% → lost 12.3%
Par score sheet for Team 2 (after the last stoppage)
Overs0 down1 down2 down3 down4 down5 down6 down7 down8 down9 down
2165728194108125144167188207
2270778597110126145167188207
23768389101113128146168188207
24828894105116130147168188207
25889499109119132148168188207
269599105113123135150169188207
27101106110118127138151169189207
28108112116123131141153170189207
29116119122129135144155171189207
30123126129134140148158172189207
31131134136140145152161174189207
32139141143147151157164175190207
33148150151154157162168178190207
34157158159161164168172180191207
35166167168170171174178184193207
36176176177178179181184188195207
37186186187187188189191193198207
38197197197197197198199200203208
39207207208208208208208208209211

Estimate only. Official targets come from the ICC’s licensed DLS software and resource tables, which are not public. This page applies the published Standard Edition rules to resources from the published Duckworth–Lewis model form fitted to open ball-by-ball data (Cricsheet, ODC-BY), so results can differ from the official figure by several runs.

Runs entirely in your browser. Nothing you enter or upload is sent to a server.

A DLS calculator you can check line by line

When rain shortens a one-day or T20 match, the side batting second gets a revised target from the Duckworth–Lewis–Stern (DLS) method. This DLS calculator estimates that target and the par scores along the way. Enter Team 1’s total and when play stopped — overs bowled, wickets down and the new length of the innings — and it shows the resources each side had, the target, the working and a par score sheet for every over and wicket.

Be clear about what it is: an estimate. Official targets come from licensed DLS software and resource tables that are not public. This page applies the published “Standard Edition” rules to resources from the published Duckworth–Lewis model, fitted to open ball-by-ball data. If you have the official resource percentages, switch to the second mode and the arithmetic is exact.

How to use the DLS Target Estimator

  1. Enter Team 1 total (S) and choose G50: 245 for men’s internationals and first-class teams, 200 for women’s ODIs and associate matches.
  2. Set the overs per innings at the start (50 or 20) and Team 2’s overs at the start of their innings.
  3. For each stoppage, press Add stoppage and enter the overs bowled, wickets down and the overs per innings after the restart. If the innings ended, use the overs bowled.
  4. Read the revised target, R1 and R2 and the working. Open the par score sheet to follow the chase over by over.
  5. Use Check Team 2’s position to see whether the chasing side is ahead of par if no more play is possible.
  6. Have the official percentages? Choose I have official resource % and enter R1 and R2.

DLS Target Estimator features

Standard Edition rules

Resource lost per stoppage, R1 and R2, target = ⌊S × R2 ÷ R1⌋ + 1 or ⌊S + (R2 − R1) × G50 ÷ 100⌋ + 1, par = target − 1.

Multiple stoppages

Up to six stoppages in each innings, including overs lost before Team 2 start.

ODI and T20

Any innings length up to 50 overs: a 20-over innings starts with 63.8% of a full innings in this model.

Par score sheet

The par for every completed over and 0–9 wickets after the last stoppage.

Exact mode

Type official resource percentages and get the exact Standard Edition target.

How the revised target is worked out

Each side’s run-scoring resources depend on overs left and wickets lost. When a stoppage cuts overs, the resource lost is the resource remaining when play stopped minus the resource remaining at the restart, at the same number of wickets. R1 and R2 are the resources each side actually had, as a percentage of a full 50-over innings.

If R2 is less than R1, Team 2’s par is S × R2 ÷ R1, rounded down, and the target is par + 1. If R2 is greater, the Standard Edition adds runs instead of scaling: par = S + (R2 − R1) × G50 ÷ 100, rounded down. These rules, and the G50 values of 245 and 200, are set out in the England and Wales Cricket Board’s document Duckworth/Lewis/Stern methodology of re-calculating the target score in an interrupted match (March 2025). The same document notes that the full DLS method raises targets by the resource ratio rather than with G50, and the ICC’s software includes further refinements for high-scoring matches — another reason official figures can differ.

Where the resource percentages come from

Duckworth and Lewis modelled the average runs still to come with u overs left and w wickets down as Z(u, w) = Z0F(w)[1 − e−bu/F(w)] (Journal of the Operational Research Society, 1998 and 2004). They never published the fitted values. This calculator fits the same equation to Cricsheet’s open ball-by-ball data: the first innings of 2,206 completed, uninterrupted men’s 50-over internationals from June 2002 to October 2026. Resource = Z(u, w) ÷ Z(50, 0).

Because modern teams score faster late in an innings, this fit gives more resources to short innings than older published tables did, something Steven Stern’s revision of the method, adopted by the ICC in 2014, also reflects in its own way. Treat targets here as a well-founded guide for club scorers, fans and students, not as the umpires’ figure.

Overs left0 down2 down4 down6 down8 down
50100.080.555.031.912.2
4092.376.353.931.812.2
3080.969.251.231.512.2
2063.856.945.330.212.2
1038.235.931.524.411.9
521.020.419.016.510.4

Tips for scorers

  • Most playing conditions need a minimum number of overs for Team 2 — commonly 20 in ODIs and 5 in T20s — before a result can be decided on par. Check your competition’s rules.
  • Penalty runs and DLS results affect net run rate too; the net run rate calculator follows the ICC clause for rain-affected matches.
  • Planning a rain-hit tournament? Draw the knockout with the tournament bracket generator.

DLS Target Estimator FAQ

How is the DLS target calculated?

Work out the resources each team had — a percentage combining overs and wickets left — as R1 and R2. If Team 2 had fewer, scale Team 1’s score by R2 ÷ R1; if more, add (R2 − R1) × G50 ÷ 100 runs. Round down for par and add one for the target. This DLS calculator shows each step.

Is this the official DLS calculator?

No. The official DLS software and full resource tables are licensed by the ICC and are not public. This page gives an estimate from the published Duckworth–Lewis model, labelled as such. Use the exact mode if you have official resource percentages.

Does it work for T20 matches?

Yes. Set 20 overs per innings. As in the Standard Edition, the same resource table is used for any innings length, so a 20-over innings starts with less than 100% of a 50-over innings.

What is G50?

The average score in a full 50-over innings, used only when Team 2 have more resources than Team 1. The ECB document gives 245 for matches involving full ICC members, Under-19 internationals and first-class teams, and 200 for associates, women’s ODIs and Under-15 internationals.

What is a par score?

The score Team 2 need at a given point to be level if no more play is possible. One run more and they win; exactly par is a tie; less and Team 1 win.

Why does my result differ from the TV graphic?

Broadcasters show the official figure from the ICC’s DLS software, whose resource values differ from this estimate, so a gap of a few runs is expected.

You might also need