Article -> Article Details

Introduction: That Number Flashes on Screen and Nobody Explains It

Pakistan needs 47 off 5 overs. Rain falls. Play stops. Ten minutes later, a completely different number appears on your screen: Revised target: 38 off 4 overs.

Where did that come from? Who calculated it? Is it fair?

Or worse, you are watching India chase 290 in an ODI. Rain hits at the 22nd over. India are sailing at 130 for 2. Play resumes and the revised target after rain in cricket suddenly reads 251 from 40 overs. Why did the target barely change when they lost 10 whole overs?

If either scenario has ever left you confused, frustrated, or arguing in the comments section, this guide is built for you. By the end, you will understand exactly how the revised target after rain in cricket is calculated, why it sometimes barely moves and other times shifts dramatically, and how smart teams use this knowledge to win matches while rain is still falling.

What Is the Revised Target After Rain in Cricket?

The revised target after rain in cricket is the new score the chasing team must reach to win, recalculated by the Duckworth-Lewis-Stern (DLS) method after any weather interruption reduces the overs available.

It is not a guess, not a compromise, and not a simple proportion of the original score. It is a mathematically derived number based on one foundational idea: every batting team possesses two resources simultaneously, and any fair revised target must account for both.

Those two resources are:

• Overs remaining at any point in the innings
• Wickets in hand at any point in the innings

Original Definition (Citable): The revised target after rain in cricket is the minimum score Team 2 must achieve to win, calculated by comparing the proportion of batting resources available to each team. It is always one run more than the DLS par score. The par score is the tie number; the target is the win number.

The Core Formula: How DLS Calculates the Revised Target

The DLS formula looks intimidating in its full mathematical form, but its logic is clean and learnable. Here is the plain-English version:

Step 1: At the start of the innings, every team has 100% of their resources (all overs, all 10 wickets).

Step 2: As overs are bowled and wickets fall, the resource percentage depletes. Each combination of overs remaining and wickets lost maps to a specific resource percentage in the ICC's DLS table.

Step 3: When rain interrupts or cuts short an innings, the calculator compares the resources each team has (or had) available. The revised target is set so that each team faces an equally challenging task given their respective resources.

The formula: Revised Target = Team A's Score x (Team B's Resources / Team A's Resources) + 1

The "+1" is because the par score is a tie. Team B needs one more than par to win outright.

Quick example: Team A scores 260 in 50 overs (100% resources used). Rain reduces Team B to 40 overs before they start batting. From the DLS table, 40 overs, 0 wickets lost = 89.3% resources. Revised Target = 260 x (89.3 / 100) + 1 = 233 + 1 = 234 runs from 40 overs.

Simple proportion would have given 208. DLS gives 234. The difference? Wickets. Team B still has all 10 wickets. They can bat aggressively in fewer overs. The DLS method accounts for that scoring potential.

The Moment Competitors Stop Explaining: When Does the Revised Target Go UP?

Every article you will find on Google explains why the revised target goes down after rain. Almost none of them explain clearly when and why the revised target after rain in cricket goes UP.

This happens in one specific, critically important scenario: when rain cuts short Team A's first innings, and Team B still receives more over resources than Team A used.

If Team 2 has more resources than Team 1, the extra runs are calculated using the extra resource percentage multiplied by the average total score for a 50-over innings (G50), and the target is raised accordingly.

Worked Example: Team A is batting in a 50-over ODI and scores 180 for 5 in 40 overs when rain permanently ends their innings. Team A's resources used: approximately 75.5% (40 overs consumed, 5 wickets lost) Team B still receives: full 50 overs, 10 wickets = 100% resources

Since Team B has MORE resources than Team A used, the target goes UP: 180 x (100 / 75.5) + 1 = 238 + 1 = 239 runs from 50 overs.

Team A scored 180. Team B must chase 239. Rain fell on Team A. Yet Team B's target is higher than what Team A actually scored. This is not a bug in the DLS system. It is fairness in action. Team B has the structural advantage of knowing the target from ball one. Team A never knew their innings would end at over 40. DLS corrects for that information asymmetry.

Par Score vs Revised Target: The Distinction That Wins Matches

These two terms sound similar. They are fundamentally different. Most fans, and some coaches, confuse them, and that confusion has cost teams matches.

Par score is the total that a chasing team should have reached, when they are "X" wickets down, at the time of an interruption. Target is the revised score that a team is required to get after an interruption. The target is one fixed number, while the par score changes according to the number of wickets lost.

Why this distinction matters life and death in a match:

If rain terminates play without resuming, the result is decided by the par score, not the revised target. If Team B is at 145 for 3 and the par score for 3 wickets at that point is 143, Team B wins by two runs even though no further ball was bowled.

In a 2009 ODI against England, the West Indies coach called his players in for bad light, believing his team would win by one run under the DLS method, not realising that the loss of a wicket with the last ball had altered the DLS score. The match referee confirmed that West Indies were two runs short, giving victory to England.

The wicket changed the par score. The coach tracked the total, not the par relative to wickets lost. England won.

How the Revised Target Affects NRR: The Hidden Consequence

One of the most completely ignored aspects of the revised target after rain in cricket is its impact on Net Run Rate (NRR), the tiebreaker that decides playoff qualification in every major tournament.

In matches affected by DLS, the score for the team batting first is taken as the par score at the time of the interruption (if no further play is possible), or as one run less than the target (in case a revised target is set). The logic is simple: the NRR of the winning team should always be greater than zero and higher than the losing team in that game.

What this means for fans tracking NRR:

When a rain-affected match is won via DLS, neither team's runs-per-over score from the full match is used. Instead, the DLS-adjusted figures are used. This means:

• A team that wins with 10 overs to spare in a DLS chase does not bank the full surplus of those unused overs in their NRR
• The losing team's NRR is not destroyed by the full margin, since DLS already equalized the resource allocation
• Fans who use raw scorecards to estimate NRR after rain-affected games are almost always calculating incorrectly

Three Rain Scenarios: How the Revised Target Changes Each Time

Scenario 1: Rain Reduces Team B's Chase Before It Begins

Team A has batted. Rain falls during the innings break. Team B loses overs before facing a ball.

The revised target after rain in cricket here is calculated simply: Team B's available resources (fewer overs, still 10 wickets) versus Team A's 100% resources. The target goes down, but rarely as much as fans expect, because Team B still has all wickets, which carries enormous resource value.

Scenario 2: Rain Interrupts Team B's Chase Mid-Innings (Play Resumes)

Rain arrives, play stops, then resumes with fewer overs remaining. This is the most common scenario during live matches.

Resources at the point rain arrives minus resources when play resumes equals the resources lost. The target drops by the proportion of resources lost. Losing overs in the later stages of an innings will usually impact a team more than losing the same number of overs earlier in an innings, as those overs are more productive. This is why rain in the death overs hurts the chasing team far more than rain at the powerplay.

Scenario 3: Rain Terminates Team B's Chase (No Resumption)

No revised target is announced. Instead, the par score at the exact moment of termination determines the winner. Team B wins if their score equals or exceeds their par score (adjusted for wickets lost at that moment). Below par, they lose.

This is where wickets become the most critical variable. A team at 5 wickets down has a lower par score threshold to clear than a team at 0 wickets down, because they have already surrendered significant batting resources.

Real Match Examples: Revised Targets That Shaped Cricket History

2023 IPL Final: CSK vs GT

The DLS method was used after the rain disruption in the 2023 IPL Final, when Chennai Super Kings had scored 4/0 (0.3 overs) and Gujarat Titans had scored 214/4 (20 overs). The target was reduced from 215 runs in 20 overs to 171 runs from 15 overs. CSK won by 5 wickets.

The critical detail here: CSK had lost zero wickets when rain arrived. Their resource percentage was still near maximum, meaning the revised target dropped substantially because they had used almost none of their resource allocation before the interruption.

2017 ICC Champions Trophy Final: India vs Pakistan

Pakistan batted first and scored 338/4 in 50 overs. India's innings was interrupted multiple times by rain. India's target was first revised to 289 in 41 overs, and then to 158 in 22 overs after another shower.

Multiple interruptions to the same innings stack on top of each other. Each time rain arrives, the calculator freezes the resource percentage at that moment and recalculates from the new resumption point. This is why two brief interruptions can produce a final target that feels dramatically different from the original.

2025 India Women vs Australia Women ODI (Perth)

Multiple rain breaks resulted in India scoring 136/9 in 26 overs. DLS revised Australia's target to 131 in 26 overs, because India lost wickets rapidly late in their innings. Australia won easily, sparking debate but statistically the result was correct.

This example illustrates the wicket penalty clearly: India's rapid late wicket loss dramatically reduced their resource percentage, which reduced the target that Australia needed. Fans who argued the target was too low were not wrong to be frustrated, but the DLS system correctly reflected that India's batting resources had been severely depleted before the interruption.

Live Tactics: How Smart Teams Use the Revised Target in Real Time

The revised target after rain in cricket is not just a post-interruption announcement. It reshapes in-match strategy from the first cloud in the sky.

Batting team's DLS-aware strategy:

• Monitor the par score displayed on broadcast continuously
• Prioritise wicket preservation when rain is likely, because every wicket lost reduces the team's par score protection
• If significantly above par with rain threatening, consider accelerating to build a bigger buffer
• Captains now play DLS-aware cricket, accelerating if rain is around to stay ahead of par.

Bowling team's counter-strategy:

• Target wickets aggressively when rain is forecast, because wickets dramatically shift the par score calculation against the batting side
• Bowl to maiden overs in the powerplay when the batting team is running near par, forcing them to either take risks or fall behind
• Know the exact over at which the minimum overs threshold is crossed, because rain after that threshold cannot stop a result

The toss decision in a rain-threatened match:

Conventional wisdom says bat second in uncertain weather, because you know the revised target. But this is not universally true. If rain is likely to interrupt the first innings specifically, batting first can be advantageous, because a curtailed first innings often results in a higher DLS target for the chasing team.

Key Takeaways

• The revised target after rain in cricket is always one more than the DLS par score. The par score ties. The target wins.
• The revised target can go UP when Team A's innings is curtailed and Team B receives more resources than Team A used.
• Par score and revised target are different: par changes ball by ball with wickets; the revised target is a fixed number set after overs are confirmed.
• Rain in the death overs causes larger target reductions than rain in the powerplay, because later overs carry higher resource value.
• The revised target after rain in cricket affects NRR calculations. Raw scorecard figures cannot be used to estimate NRR in DLS matches.
• Multiple interruptions to the same innings stack. Each recalculation begins from the new resumption point, not the original innings start.
• DLS studies show the method predicts the correct winner approximately 75 to 85% of the time when over 25 overs have been played.

Quotable Insight: "The revised target after rain in cricket is not the original target adjusted for fewer overs. It is the original target adjusted for fewer resources. Overs and wickets together constitute resources. Treat them separately and you will misread every rain-affected match you ever watch."

Conclusion: Read the Target, Then Read the Resources Behind It

The revised target after rain in cricket is the visible output of an invisible calculation that balances overs, wickets, run rates, and scoring patterns across decades of historical match data. The number that flashes on your screen did not appear arbitrarily. It emerged from a system that Frank Duckworth, Tony Lewis, and Steven Stern spent decades refining.