India beat New Zealand by five wickets under the Duckworth–Lewis–Stern method at Eden Park on 4 November 2026. The Board of Control for Cricket in India's match centre shows New Zealand's 185 in 40.2 overs and India's 143 for five in 22.4 overs. Those totals can look contradictory at first. The result makes sense once you read the score for each innings separately from the target that applied after the interruption.
The same match centre had earlier shown India needing 186 at the innings break. A later in-progress display showed India at 124 for four after 20 overs, needing 19 runs from 12 more overs. That later update implies a winning target of 143 and an allocation of 32 overs at that stage. The final result identifies DLS as the method. The number of runs already scored by New Zealand remained on the card. The task India faced in the chase changed.
Check which New Zealand–India match you are reading
Start with the date, venue and format. The ICC fixture page identifies this as the first ODI of a five-match series at Eden Park in Auckland. New Zealand Cricket's summer schedule lists a T20 international at the same ground on 30 October, followed by the last T20 in Hamilton on 1 November and the ODI opener back in Auckland. Searching for the same two teams and stadium can therefore turn up two different matches from the tour.
The format matters because it sets the framework for the innings and any revised playing conditions. A T20 scorecard belongs to a shorter form of the game, with a different original allocation. A Test has a different structure again. This match was a men's ODI, so the ICC's men's ODI playing conditions are the relevant starting point for understanding the target. Follow the match centre for the target actually communicated for this fixture.
The search interest also included Virat Kohli. The ICC fixture page lists him in India's squad, and a BCCI photograph caption documents him on the field at Eden Park. Those details establish different things. A squad listing identifies players available for selection. The match caption documents participation in the game. A batting score requires the batting entry or a report that explicitly records it. This article follows the team chase and the target, for which the official match centre provides the relevant figures.
Read the first innings without treating 40.2 as a decimal
The BCCI match details report that India won the toss and chose to field. New Zealand's total was 185 in 40.2 overs. In a cricket score, 40.2 means 40 completed overs plus two legal balls. With six legal balls per over, that is 242 legal deliveries. The digit after the point counts balls in the unfinished over. It does not represent two tenths of an over.
This notation matters if you are calculating a rate or comparing how long two innings lasted. A batter can score runs on deliveries that do not advance the count of legal balls, depending on the type of delivery and scoring event. The total runs and the overs shown answer different questions. If you divide runs by overs, first translate the ball count into the appropriate fraction or work from the number of legal balls.
You can use India's final line to see the same thing. At 22.4 overs, 22 full overs account for 132 legal deliveries and four more make 136. That is the amount of the innings played. It does not say the chase was scheduled to last 22.4 overs. The result can be reached before the full allocation is used. In a shortened chase, the allocation is a separate figure from the time at which the winning run is recorded.
Follow the target from one match state to the next
At the innings break, the BCCI display reported that India needed 186. One run above the first innings total is the ordinary winning target if no adjustment changes it. It was the number shown at that stage, and it helps explain why someone who checked early might remember a different figure from the one that decided the match.
The later live display is a useful cross-check. It showed India at 124 for four after 20 overs and needing 19 more from 12 overs. Add 19 to 124 and you get 143. Add 12 overs to the 20 already played and you get an allocation of 32. These sums read the match centre's status. They do not independently reproduce a DLS calculation. The final display then shows 143 for five in 22.4 overs and a five-wicket victory under DLS.
This is a case where two screenshots can both be faithful to the source and describe different stages. A capture at the break can show 186. Another during the chase can show 19 still needed, while a final scorecard can show India winning with fewer runs than New Zealand. When sharing one of those captures, include the innings and whether the match was live, interrupted or complete. Otherwise, a reader may put an early target beside the final result and think one source has to be wrong.
The point also applies when several feeds are open. A page headed “match details” can retain an earlier summary while a main match page has updated to the result. For a result that has just changed, refresh the official match centre and look for a completed-result line that agrees with the final scores. A headline that says one team leads the chase is different from a result that the organisers have posted as final.
What DLS adjusts and what stays on the scorecard
In an interrupted limited-overs game, the DLS method is used to calculate a target or determine a result under the applicable conditions. The available batting resources depend on time left in the form of overs or balls and on wickets in hand. Those quantities matter together. A team with most of its wickets remaining can approach a short stretch differently from a team with only one wicket left, even if both have the same number of deliveries available. The ICC playing conditions index links to the applicable ODI document.
Consider a purely hypothetical chase interrupted with 15 overs left. In one version, the batting side has lost one wicket. In another, it has lost seven. The time remaining is identical, while the cost of a dismissal and the batting options are very different. A calculation based only on the fraction of overs lost would treat those positions alike. DLS incorporates the changing balance of time and wickets. This example illustrates the inputs without supplying an unofficial target.
The method adjusts what is required to win. It does not rewrite the runs actually scored in the first innings. At Eden Park, New Zealand's 185 remained on the scorecard. India's result line showed that the chase ended when the revised winning target was reached. Reading both facts together explains the outcome without changing either innings total. It also explains why simply subtracting 143 from 185 gives no useful winning margin.
A target and a par score are related but answer different questions. The target is the score needed to win under the applicable calculation if play continues to the relevant point. A par score is used as the comparison level at a particular point in a chase under the rules. When a match is still being played, look for the target and overs remaining rather than treating an on-screen par figure as a permanent winning target. When it is over, use the result line.
The wickets margin describes the end of the chase
India finished on 143 for five. Five wickets had fallen when the target was reached. Five wickets were therefore still available, which explains the reported winning margin. The result is expressed in wickets because the chasing side reached its target. The difference between the two innings totals would only confuse that explanation because the winning target was adjusted.
The later live checkpoint lets you follow the last stretch without inventing a ball-by-ball account. India were 124 for four, so reaching 143 for five meant adding 19 runs and losing one more wicket from that checkpoint to the finish. The overs notation moved from 20.0 to 22.4. That is 16 more legal balls. These calculations describe the change between two official displays. They do not identify who scored each run or assign the remaining deliveries to individual batters.
For someone reading the game after the event, it is helpful to keep three columns in a short timeline. Put the match state in one, the score in the next and the target information in the last. The innings break gets 185 for New Zealand and the early chase target of 186. The later live checkpoint gets India's 124 for four with 19 needed. The completed match gets 143 for five and the official DLS result. This is enough to reconcile the apparent discrepancy without pretending that every update was seen.
A method for reading the next rain-affected scorecard
First, locate the match by its format, date and venue. Then identify which team batted first and write down its actual score. Find the current chase target and check whether the innings has a revised allocation. Finally, check whether the chase ended by reaching that target or whether the result was decided when play stopped. Those two endings can produce different kinds of result lines, even though both can refer to DLS.
If you are comparing a live graphic with a scorecard, preserve the two versions rather than copying numbers from each into one sentence. A live panel can say a team needs 19 from 12 overs. A completed card can say the same team won with time unused. Both can be true. Use the clock or overs figure to locate each statement in the match. A change in the displayed number of runs needed is more informative when you know the score and the allocation at the same moment.
The tour schedule provides a separate reference for what follows. New Zealand Cricket listed the second ODI for Wellington on 7 November. A schedule confirms the fixture as published, while the match centre is the place to check the result of the Auckland game. Keeping those records separate helps avoid mixing a report about the earlier T20 series with the opening ODI or treating a future fixture as a completed event.
One other comparison can help when reading a shortened chase. Suppose two teams each need 19 runs from 12 overs. One still has six wickets available and the other has one. The runs and balls tell you how quickly each team needs to score. The wickets tell you how much room each has to absorb a dismissal. Looking at all three helps explain why the same required rate can produce different decisions. An individual shot can be affordable in one position and costly in another.
Also check whether a graphic reports the number of wickets lost or remaining. A line of 124 for four gives the score and wickets already lost. The text in the Auckland match centre described the same position with six wickets remaining. The two displays refer to the same situation from opposite directions. When working out a margin or comparing stages of an innings, keep the label next to the number.
Conclusion
The Auckland scorecard records two innings and one revised chase. New Zealand made 185 in 40.2 overs. India's winning target was 143 in the later chase state, and the final result was 143 for five in 22.4 overs, a five-wicket win under DLS. To see why those numbers fit, read the match status and target alongside the scores. The target explains what India had to reach, while the innings totals show what each side actually scored.
This New Zealand Google Trends selection followed two higher-ranked searches about U.S. midterms already covered.
For another example of how sporting records use different clocks, see the Winnipeg–Montreal game analysis.
Sources consulted 4 November 2026 include BCCI's match centre, the ICC fixture page, the ICC playing conditions index and New Zealand Cricket's schedule.