How is the DLS revised target calculated?

DLS treats each innings as a stock of two resources, overs remaining and wickets in hand, read as a single percentage from the Standard Edition table. Team 1's resource is R1, Team 2's is R2. If R2 is less than R1, Team 2's target is Team 1's score scaled by R2/R1, truncated, plus one run: Target = floor(S × R2/R1) + 1.

What is the par score in cricket and how do I read it?

The par score is what the chasing side must have reached, at a given point, to be exactly level on DLS. If a rain-hit match is abandoned, the team ahead of par wins. If they are level it is a tie. So if par is 133 and Team 2 are 140, they win by 7 runs (DLS method); at 130 they lose by 3.

What is the difference between DLS Standard Edition and Professional Edition?

The Standard Edition uses one fixed, published resource table you can apply by hand. It is what club and school cricket uses, and it is what this calculator implements. The Professional Edition uses a licensed computer program with an undisclosed formula that adjusts for very high first-innings scores. Its algorithm is not public, so no free tool can reproduce it exactly.

Why does the team batting second sometimes get a target higher than the first team scored?

When Team 1's innings is cut short, they do not use all their resource (R1 falls below 100%). If Team 2 then bats their full innings, Team 2 has more resource (R2 greater than R1). DLS adds the extra expected runs using the G50 constant: Target = S + floor((R2 − R1) × G50/100) + 1. This is why a side chasing 200 can be set 264.

How many overs must be bowled for a DLS result to be valid?

Under standard ICC playing conditions the side batting second must face at least 20 overs in a 50-over match, or 5 overs in a T20, for a DLS result to stand. Below that the game is a no result. This calculator flags when the overs you enter fall below the minimum for the selected format.

What is the G50 value and when does it matter?

G50 is the average total a team is expected to score batting first in an uninterrupted 50-over innings. The ICC Standard Edition uses 245 for first-class teams. It only affects the answer when Team 2 has more resource than Team 1 (the excess branch). You can lower it in the advanced settings for school or club matches with lower scoring.

Does this handle T20 matches and reduced-overs games?

Yes. Pick the T20 (20 overs) or Custom format and enter the overs each side gets. DLS uses the same resource table for every format, a 20-over innings simply starts from a lower resource percentage than a 50-over one. The Standard Edition is applied identically across formats.

Is this the same method used in international matches?

International and top-flight matches use the DLS Professional Edition, which is a licensed program. This tool uses the Standard Edition, the officially published manual version. For scores in a normal range the two editions give very similar answers, but they can differ when the first innings total is very high. Treat this as an accurate Standard Edition calculator, not an exact replica of the broadcast figure.

Cricket · DLS Standard Edition

Duckworth-Lewis-Stern (DLS) Par Score & Revised Target Calculator

Rain stopped play? Enter the score, overs and wickets to get the DLS revised target or the live par score in seconds, with the exact resource percentages and full working shown. Uses the official ICC Standard Edition table. No signup, no ads.

By Induwara Ashinsana· Co-Founder, Ryzera TechnologiesUpdated Jul 8, 2026

DLS revised target & par score

ICC Standard Edition

Match format

Team 1 final score (runs)

Total runs the side batting first made.

Team 1's innings

Resource for Team 1 (R1): 100.0%

Team 2 overs available (revised allocation)

Overs the chasing side will get after the interruption.

Revised target to win

224

off 40 overs

Par (tie) score

223

reach this exactly = tie

Resource R2 / R1

89.3% / 100.0%

Formula branch

Scale down

Team 2 has less resource (R2 89.3% < R1 100.0%), so Team 1's score is scaled down.

Target = floor(250 × 89.3% ÷ 100.0%) + 1 = floor(223.25) + 1 = 224

Cross-check (runs per 1% of resource): 250 ÷ 100.0% × 89.3% → par 223 ✓ matches

Standard Edition table, cells in play

Overs left	0w	1w	2w	3w	4w	5w	6w	7w	8w	9w
50	100.0	93.4	85.1	74.9	62.7	49.0	34.9	22.0	11.9	4.7
40	89.3	84.2	77.8	69.6	59.5	47.6	34.6	22.0	11.9	4.7

Uses the official ICC/ECB Duckworth-Lewis-Stern Standard Edition resource table (G50 = 245). The Professional Edition is a licensed, undisclosed algorithm and cannot be reproduced. Sources are cited below the calculator.

How it works

The Duckworth-Lewis-Stern method measures each innings as a stock of two resources, the overs still to be bowled and the wickets still in hand. The ICC Standard Edition publishes a single lookup table giving the percentage of a full 50-over innings' resource that remains for every combination of overs remaining (0–50) and wickets lost (0–9). A fresh 50-over innings starts at 100%; the same table is used for every format, so a 20-over innings simply begins from a lower percentage.

Two resource figures drive every calculation: R1, the resource available to the side batting first, and R2, the resource available to the side batting second. For an uninterrupted 50-over innings R1 is 100%. If an innings is shortened, the resource lost to each stoppage is the table value when play stopped minus the value when it resumed; for an innings ended for good, the resource lost is simply the value remaining at that moment.

The revised target then follows three rules from the ICC/ECB regulations, truncating any decimals rather than rounding:

R2 < R1: Target = floor(S × R2 ÷ R1) + 1
R2 = R1: Target = S + 1
R2 > R1: Target = S + floor((R2 − R1) × G50 ÷ 100) + 1

Here S is Team 1's score and G50 = 245is the average total for a 50-over first innings between first-class teams. The par (tie) score is always one run below the target. During a chase that is interrupted, the par score at that instant is Team 1's score multiplied by the resource Team 2 has already used, divided by R1, the batting side is ahead if their score is above par. A DLS result is only valid once the side batting second has faced a minimum number of overs (20 in an ODI, 5 in a T20 under standard playing conditions); below that the game is a no result.

This calculator implements the Standard Edition only. The Professional Edition, used in international cricket, relies on a licensed program whose algorithm is not published and cannot be reproduced by any free tool. Every figure here is read straight from the transcribed Standard Edition table, last cross-checked against the ICC and ECB source documents on 2026-07-08.

Worked examples

Reduced chase set before Team 2 starts

R2 < R1, the everyday rain case

Team 1 makes 250 in a full 50 overs → R1 = 100.0%
Rain cuts Team 2 to 40 overs before they start, 0 wickets lost
R2 = resource(40 overs, 0 wkt) = 89.3%
Target = floor(250 × 89.3 ÷ 100) + 1 = floor(223.25) + 1 = 224
Par (tie) score = 223. Team 2 need 224 off 40 overs to win.

Live par score at an abandoned chase

Reading whether the batting side is ahead

Team 1 makes 280 (full 50 overs) → R1 = 100.0%
Team 2 are 2 down with 20 overs left when the match is abandoned
Resource remaining = resource(20 overs, 2 wkt) = 52.4%
Resource used = 100.0 − 52.4 = 47.6%
Par = floor(280 × 47.6 ÷ 100) = floor(133.28) = 133
At 140/2 Team 2 are 7 ahead → win by 7 (DLS); at 130/2 they lose by 3.

Target higher than Team 1's score

R2 > R1, Team 1's innings was cut short

Team 1's innings is ended by rain at 200, with 10 overs left and 5 down
Resource lost = resource(10 overs, 5 wkt) = 26.1% → R1 = 100 − 26.1 = 73.9%
Team 2 then bat a full 50 overs → R2 = 100.0%
Excess = floor((100.0 − 73.9) × 245 ÷ 100) = floor(63.945) = 63
Target = 200 + 63 + 1 = 264 (par 263), above Team 1's 200.

Frequently asked questions

Sources & references

The Standard Edition resource table used here was transcribed cell-by-cell from the ICC/ECB source documents and last cross-checked on 2026-07-08. Only the Standard Edition is implemented; the Professional Edition is a licensed, undisclosed algorithm.

Related tools

Utility

Required Run Rate Calc

Work out the live chase numbers in one entry, required run rate (asking rate), current run rate, runs still needed, overs remaining and the projected final score. Handles ODI, T20 and custom over limits with correct six-balls-per-over arithmetic, plus an over-by-over ask table. Runs in your browser, sources cited.

Open tool

Utility

Cricket Average Calculator

Work out batting average, batting strike rate, bowling average, economy rate and bowling strike rate from raw match numbers. Handles the two things people get wrong by hand, excluding not-outs from the batting-average denominator, and converting base-6 over notation (12.3 = 12 overs 3 balls) before dividing. Free, no signup, runs in your browser.

Open tool

Utility

Pregnancy Due Date

Estimate your due date from last menstrual period, conception date, or dating ultrasound. Naegele's rule with cycle adjustment, trimester progress, week-by-week milestones, ACOG-aligned, runs in your browser, no signup.

Open tool

Comments & feedback

Spotted a bug or want an improvement? Tell us, our team reviews every comment, and good ideas get built. Comments are public and anonymous.

Found a bug, edge case, or want to suggest an improvement?

Email me at [email protected] , most fixes ship within 24 hours.

Advanced, G50 constant

Standard Edition table, cells in play

How it works

Worked examples

Frequently asked questions

How is the DLS revised target calculated?

What is the par score in cricket and how do I read it?

What is the difference between DLS Standard Edition and Professional Edition?

Why does the team batting second sometimes get a target higher than the first team scored?

How many overs must be bowled for a DLS result to be valid?

What is the G50 value and when does it matter?

Does this handle T20 matches and reduced-overs games?

Is this the same method used in international matches?

Sources & references

Related tools

Required Run Rate Calc

Cricket Average Calculator

Pregnancy Due Date

Comments & feedback