Officials

DLS Calculator

Work out the revised target and the over by over par score when rain has cost a limited overs match some of its overs.

Free, no account neededUmpiresScorersLeague officials
1

Which match is this?

It sets the overs and the minimum needed for a result.

2

Team 1's innings

What the side batting first finished on.

Interruptions during Team 1's innings

Overs and balls bowled when play stopped, the score at that moment, and the overs each side lost.

No interruptions in the first innings

Total overs available50
3

Team 2's innings

What the weather has cost the side chasing.

After any overs lost before Team 2 began.

Awarded while Team 2 are batting.

Interruptions during Team 2's innings

Add the score and wickets here and the result shows the par score at that moment, and whether Team 2 are ahead or behind it.

No interruptions yet in the chase

Total overs available40

Target

227

to win from 40 overs

Par score

226

a tie

Edition

Official DLS 5.0

Beyond the calculator

Umpires and scorers using Crickslab get the revised target, the par score and the over rate on screen, signed off and shared in seconds.

  • Rain rules applied as the match runs
  • Results and points posted automatically
  • Live streaming with the score on the picture
Request a demoExplore the ecosystem

How this was worked out

  1. 1Team 1250 off 50 overs
  2. 2Team 240 overs to bat
  3. 3The model is calibrated to Team 1's actual scorewhich is what separates DLS 5.0 from the printed chart, and why it is the figure used in licensed competition
  4. 4Targetpar 226 plus one run = 227
226 exactly is a tie. The target is always the par score plus one run.
This is the official Duckworth-Lewis-Stern 5.0 figure, the one that applies in licensed competition.
The DLS method and its parameters are the intellectual property of the International Cricket Council. Crickslab is not affiliated with the ICC and this is not an official ICC product.

Par score by overs remaining and wickets down. Level with par is a tie.

Overs left0123456789
40016365985115145175200219
39319376086115146175200219
38621396187115146175200219
37924416387116146175200219
361226436488116146175200219
351529466689117146175200219
341932486790117146175200219
332235506992118146175200219
322638537193118146175200219
312941557394119147175200219
303344587595120147175200219
293748617797120147175200219
284151647998121147175200219
2745556782100122148175200219
2650597084102123148175200219
2554637387104124149175200219
2459677790106125149175200219
2364718193108127150175200219
2268758496110128150175200219
2173808899113130151176200219
20798592102115131152176200219
19849097106118133153176200219
189095101110121135154176200219
1795100106114124137155177200219
16101105111118127140156177200219
15107111116122131142158178200219
14114117121127135145159178200219
13120123127132139148161179200219
12127129133137143152164180200219
11134136139143148155166181200219
10141143145149153159169182201219
9148150152155158164172184201219
8156157159161164169175186201219
7164165166168170174179188202219
6172172173175177179184191203219
5180181181182184186189194204219
4189189189190191192195198206219
3198198198198199200201203208219
2207207207207207208208210212219
1216216216216216216217217218221
0226226226226226226226226226226

How the number is worked out

The formula

Target = S x R2 / R1 + 1 when R2 is at or below R1
S
The score Team 1 actually made.
R1
The percentage of a full innings' resources Team 1 had. A side that batted its full quota without interruption had 100 per cent.
R2
The percentage Team 2 has. Fewer overs, or overs lost part way through, means a smaller number.
G50
The average first innings score in a full 50 over innings. Used only when Team 2 has more resources than Team 1 had. 245 for full members, 200 for associates, women's ODIs and under 15 cricket.

When Team 2 ends up with MORE resources than Team 1, which happens if Team 1's innings was cut short, scaling up in proportion would overstate the target. The excess is valued at G50 instead: Target = S + G50 x (R2 - R1) / 100 + 1.

The par score is the raw figure truncated. The target is one run more than that. Truncating and adding one is not the same as rounding up, and the difference decides matches.

A worked example: rain in the chase

Team 1 bats first and makes 250 in its full 50 overs, so it used 100 per cent of its resources.

Rain arrives before Team 2 starts, and the umpires cut the chase to 40 overs. Team 2 therefore begins with less than a full innings in hand.

  1. 1Team 1 resourcesR1 = 100.0 per cent, a full uninterrupted innings
  2. 2Team 2 resourcesR2 = 89.3 per cent, 40 overs with all ten wickets standing
  3. 3R2 is below R1, so scale in proportion250 x 89.3 / 100 = 223.25
  4. 4Truncate to get parfloor(223.25) = 223
  5. 5Add one run for the target223 + 1 = 224

Team 2 needs 224 from 40 overs. Exactly 223 is a tie, which is the part captains most often get wrong in the last over.

Rules and edge cases

The situations that change the answer, and the ones most calculators get wrong.

1

Resources are wickets as well as overs

Losing ten overs with all ten wickets standing costs far less than losing ten overs at eight down. The method values what a side has left to bat with, not just how long it has. That is why a par score always depends on wickets down as well as overs remaining, and why the par table has a column for each.

2

Par is a tie, not a win

If play is abandoned and the chasing side is exactly level with par, the match is tied. One run more and they have won. Reading par as the score needed to win is the single most common mistake made at the ground, and it costs sides matches.

3

Truncate, then add one. Never round up

The regulations truncate the raw par figure and then add one run. On an exact integer the two approaches diverge: the ICC's own worked Example 3 gives a par of 217.000 and an official target of 218. Rounding up returns 217 and is wrong. Any calculator that uses ceiling rather than floor will disagree with the umpire in precisely the situation where it matters.

4

Team 2 can end up with more resources than Team 1

This is legitimate, not a fault. It happens when Team 1's innings was interrupted and Team 2 gets a clean run at a known target. The method switches to the G50 branch here, valuing the extra resources at an average score rather than scaling the actual score up in proportion. Scaling up would reward Team 2 for a total Team 1 never had the chance to build.

5

The two editions give slightly different answers

The Standard Edition works from a fixed published table, which is what an umpire computes by hand when there is no computer. The Professional Edition calibrates to the score Team 1 actually made, so it handles very high totals better, and it is the figure that applies in licensed competition. On an ordinary total the two usually agree. On a first innings of 350 or more they can differ by several runs.

6

A minimum number of overs is needed for a result at all

Most playing conditions require each side to face a minimum, commonly 20 overs in a 50 over match and 5 in a Twenty20. Below that there is no result regardless of what the arithmetic says. Check your competition's regulations rather than assuming the international standard.

Frequently asked questions

Duckworth Lewis Stern is the system cricket uses to set a fair target when a limited overs match loses time to weather. It works on the idea that a batting side has two resources, overs and wickets, and it adjusts the target according to how much of each side actually had.

For officials and scorers

Crickslab applies DLS automatically while the match is being scored

No pausing to work out a revised target at the ground. Overs lost go in once, and the target, the par score and the live par comparison update for everyone watching, including the players and the scorers.

Talk to our team

Last reviewed 17 August 2026. Playing conditions change, so if your competition uses a different rule, its regulations take precedence over anything here.