Nepal vs Ned 1st ODI 2026: Rain-Curtailed DLS Walk-Through

The cover squad jogged on at the 32-over mark. Nepal were 142 for 4, chasing Netherlands' 251 in 50 overs, and the par score on the broadcast graphic showed them 5 runs ahead. By the time the rain stopped — 27 minutes later — the umpires had revised the chase to 43 overs. The DLS table was about to do work that the umpires alone could not. Nepal needed a new target. The crowd at Tribhuvan University Cricket Ground waited. The maths started.

This walk-through tracks the curtailed-overs scenario, the par-score evolution, the wickets-down adjustment, and what the result means for Nepal's CWC qualification pathway. The series itself is recapped in the Nepal tour Netherlands 2026 ODI series recap.

The Curtailed-Overs Scenario

Netherlands batted first and posted 251 all out in 49.4 overs. Nepal's chase began conventionally. They reached 142 for 4 in 32 overs. The rain came. Twenty-seven minutes were lost. The umpires revised the chase to 43 overs total — meaning Nepal would have 11 overs to bat once play resumed.

The Par-Score At The Stoppage

Under the DLS method, par-scores depend on the resources used (overs bowled, wickets remaining). Nepal's resources at the stoppage: 36% (32 overs faced of 50, 6 wickets in hand of 10). The DLS table converted this into a target adjustment.

Element	Value
NED 1st innings	251 (49.4 overs)
Nepal at stoppage	142/4 (32 overs)
Nepal resources used	64%
Nepal resources remaining (initial)	36%
Resources after curtailment	22% (11 overs, 6 wickets)
Resources lost to rain	14%

The 14% resource loss requires a target adjustment.

The Par-Score Evolution

The DLS table reduces the target proportionally to the resources available. With Nepal's revised chase being 43 overs total instead of 50 — a 14% resource reduction — the target shifts.

Stage	Target
Original target	252
Revised target after curtailment	217
Runs Nepal had at stoppage	142
Runs needed off remaining 11 overs	75
Required RPO	6.82

The chase had become harder. Nepal's par-RPO had been 5.30. The new RPO of 6.82 was a meaningful jump.

The Wickets-Down Adjustment

This is where DLS detail matters. The same 11-over chase looks very different depending on wickets in hand.

Wickets In Hand	Effective Resources	Realistic Strike Rate
6 (actual)	22%	Around 6.50 RPO
4	18%	Around 5.80 RPO
2	12%	Around 4.40 RPO

Nepal had six wickets in hand. The 22% resource read was favourable. They had Rohit Paudel and Kushal Bhurtel both at the crease. The chase was challenging but not unreasonable.

The wider lessons of DLS underpinnings — how the par-score table works in different scenarios — are in the DRS / decision review system complete guide, which despite the DRS-focused name covers the broader umpire-rule conversation Nepal's coaching staff would have referenced.

The Chase After The Rain

When play resumed, Nepal were chasing 75 off 66 deliveries with 6 wickets in hand. Bhurtel hit the second ball of the resumed innings for four. Paudel followed with a calmly worked single. The required-rate ticker started to drop.

Phase Breakdown

Phase	Runs Added	Wickets Lost	RPO
Overs 32.1-37 (first 5 after resume)	38	1	7.60
Overs 37.1-43 (last 6)	41	1	6.83

Total chase output across the 11 revised overs: 79 runs for 2 wickets. Nepal won by 4 wickets and 4 balls remaining.

Qualification Implications

Nepal's win in this 1st ODI was significant for their CWC 2027 pathway. The match counted toward the Cricket World Cup League 2 standings — Nepal's position before the game was 6th of 8, and the win moved them to 5th, within striking distance of the qualifying tier.

Team	Played	Wins	Points
Scotland	14	9	18
Oman	14	8	16
USA	14	7	14
UAE	14	6	12
Nepal (post-win)	13	6	12
Netherlands (post-loss)	13	6	12

The win made Nepal's CWC qualification pathway significantly more competitive. The full pathway is detailed in the ODI World Cup 2027 qualification pathway explained.

Paudel's Anchor Role

Rohit Paudel batted through the rain delay's mental disruption — finishing the chase with 47 not out. The kind of anchor performance that lined up neatly with the Paudel-Airee anchor-finisher split Nepal vs Ned 2026 ODI series pattern that runs through all three games.

His captaincy detail in the rain-resume phase — calling Bhurtel through for a tight single early to settle nerves, refusing the swung pull-shot at the start — is the kind of read that doesn't make scoreboards but turns DLS chases into wins.

Coach Quote

Monty Desai, Nepal's head coach, told the post-match presser: "DLS is a math game once the rain comes. We were ahead at the stoppage. We knew the resources lost would tighten things. Six wickets in hand was the key. Rohit and Kushal stayed calm. The chase was always going to be uncomfortable, but we'd have backed ourselves at 75 off 66 with six in hand on any day."

What This Tells Us About DLS In Pathway Cricket

Three observations:

1. DLS slightly favours the batting team in mid-innings curtailment when wickets are in hand. Nepal's 22% resource read was favourable.
2. Six wickets in hand is the inflection point. Below that, the par-score becomes punishing. Above, it's navigable.
3. The required-RPO jump from 5.30 to 6.82 is the kind of mid-chase cliff that coaching staff drill in nets. Nepal handled it. Many sides don't.

The Takeaway

A rain-curtailed chase. A 14% resource adjustment. A 75-off-66 finish. Nepal's 1st ODI win against Netherlands was a clean DLS chase from a side that had read the tables before walking out — and the qualification points it secured matter for their 2027 World Cup pathway. The math is dry. The cricket was anything but.