Duckworth-Lewis Calculator
Enter each team's overs, wickets, and score to estimate a revised target after a rain interruption.
Match Details
Team 1 (batted first, innings complete)
Team 2 (chasing, at point of interruption)
Wickets already down when the reduced overs figure was set. Use 0 if the reduction happened before Team 2 batted.
Advanced: average score constant (G50)
Used only when Team 2 has more resource than Team 1 had. Default 245 is a typical one-day average; lower it for T20.
Quick Examples
Enter both teams' details on the left to see the revised target
Score to Tie
Target to Win
How the Target Is Estimated
R1 and R2 are resource percentages read from a simplified overs-and-wickets table. Target to win is the par score rounded down, plus one run.
Summary
Enter each team's overs, wickets, and score to estimate a revised target after a rain interruption.
How it works
- Enter the overs Team 1 actually faced and the total runs they scored.
- Enter the overs available to Team 2 and how many wickets, if any, were already down when that number of overs was set.
- The calculator looks up each team's resource percentage from overs remaining and wickets lost.
- If Team 2 has fewer resources than Team 1 had, the target scales down proportionally.
- If Team 2 somehow has more resources, extra runs are added using an average-score constant (G50), which you can adjust.
- The revised target and the score needed to tie are shown side by side.
Use cases
- Estimate a fair chase target after rain interrupts a run chase.
- Understand how resource percentage changes with overs and wickets.
- Check a broadcast-quoted revised target against a rough independent estimate.
- Explore how big a difference losing wickets early makes to resource loss.
- Teach or learn the logic behind the Duckworth-Lewis method.
- Compare scenarios by adjusting overs and wickets lost.