West Indies Beat Nepal by 9 Wickets in Mumbai
West Indies beat Nepal comfortably in Mumbai, chasing 134 in 15.2 overs as Shai Hope’s 60 and Holder’s 4/27 sealed a big win.
West Indies Beat Nepal at Wankhede
At Wankhede Stadium, West Indies beat Nepal by 9 wickets, and the margin clearly reflected how the match unfolded. Nepal fought hard in patches, but their innings never found a smooth rhythm. They ended on 133/8 in 20 overs, mainly because Dipendra Singh Airee played a brave knock when wickets kept falling around him. West Indies then made the chase look simple, reaching 134/1 in 15.2 overs, with 28 balls still unused.
This win was built on two clear phases. First, West Indies controlled Nepal’s scoring options through disciplined powerplay bowling and smart match-ups. Then, with the bat, they avoided panic, took the singles that were available, and waited for Nepal’s bowlers to miss their lengths. At a venue like Wankhede, chasing can become a race. West Indies turned it into a routine.
Match Details Snapshot
- Match: Nepal vs West Indies, 25th Match, Group C
- Venue: Wankhede Stadium, Mumbai
- Result: West Indies won by 9 wickets (28 balls remaining)
- Scores: Nepal 133/8 (20), West Indies 134/1 (15.2)
- Toss: West Indies elected to bowl
Why West Indies Beat Nepal: The Story in One Line
West Indies beat Nepal by 9 wickets because they won the powerplay battle twice—first with the ball by forcing early damage, and then with the bat by staying ahead without taking risks.
Nepal needed a clean start to set a defendable total. Instead, they lost early wickets and had to rebuild under pressure. West Indies, on the other hand, kept their chase stable and never let the required rate squeeze them. When a chase stays calm, the bowling side feels the match slipping even if they bowl a few good overs.
West Indies Beat Nepal: Nepal’s Innings
Nepal’s total of 133 looked competitive for a moment, but the start made the rest of the innings heavier than it needed to be. They lost Kushal Bhurtel for 1, and soon after, more wickets followed.
The biggest problem was timing. Nepal kept losing wickets just as they tried to lift the pace. That meant new batters had to begin against a hard ball and an attack that was sticking to a plan.
West Indies Beat Nepal: Powerplay Damage
In T20 cricket, the powerplay is often where the match direction is decided. Nepal were pushed into survival mode early, and that usually reduces a team’s options later.
- Kushal Bhurtel fell for 1 (3 balls), bowled by Akeal Hosein.
- Aasif Sheikh made 11 (10) but could not convert.
- Captain Rohit Paudel was out for 5 (7), leaving Nepal searching for stability.
At 17/3, Nepal were already fighting two battles: rebuilding and keeping the total moving. That is a tough combination, because any attempt to accelerate risks another wicket.
West Indies Beat Nepal: A Knock With Responsibility
If Nepal had one clear positive, it was Dipendra Singh Airee’s 58 off 47 balls. He hit 3 fours and 3 sixes, and he carried Nepal through the longest period of their innings.
This was not a flashy innings built only on boundaries. It was built on problem-solving.
He had to do three things at once:
- Stop the collapse.
- Keep enough rotation so the total did not freeze.
- Pick moments to attack so Nepal could reach something near 130.
He did all three for a while. The issue was support. When partners cannot stay long, a batter has to keep resetting. That drains momentum. It also gives the bowling side confidence because every over feels like a small win.
Airee’s strike rate (123+) was decent, but the innings needed one more batter to stay with him through the middle overs. Without that, Nepal were always at risk of ending 10–15 short.
West Indies Beat Nepal: Middle Overs
Nepal’s key dismissals in the middle overs came when they tried to change gears. Lokesh Bam played a short cameo, but he couldn’t stretch it into a match-shaping stand.
- Lokesh Bam scored 13 (15) before falling.
- Gulshan Jha added 11 (14) with a six, but again, the stay was brief.
The fall of wickets shows the pattern: small rebuilds, then another wicket, then another reset.
At Wankhede, you want at least one partnership that crosses 40 or 50. Not because the number is magical, but because it forces bowlers to change their plan. It makes captains move fielders. It creates pressure. Nepal never fully created that pressure.
West Indies Beat Nepal: Sompal Kami’s Late Push
When Nepal needed late acceleration, Sompal Kami delivered the cleanest hitting of their innings. He finished 26 off 15 balls* with 4 fours, giving Nepal a lift in the final phase.
These runs mattered because they turned a struggling innings into a total that at least asked a question. Without Sompal’s late push, Nepal might have finished near 115–120, which is rarely enough against a deep West Indies batting line-up.
Still, a late push works best when the platform is solid. Here, the platform was shaky. Sompal’s cameo improved the look of the score, but it could not erase the pressure created by the early collapse.
Nepal ended on 133/8, with Airee dismissed late (at 19.2 overs) after doing the heavy lifting.
West Indies Beat Nepal: West Indies Bowling
West Indies beat Nepal by 9 wickets, and the win began with their bowling control. The standout was Jason Holder, who produced a match-defining spell of 4 overs, 27 runs, 4 wickets.
Holder’s wickets weren’t random. He removed key batters and kept Nepal from building a stable middle.
Holder’s 4-Wicket Spell: Momentum Killer
In T20s, a wicket at the right time is worth more than a wicket at any time. Holder struck when Nepal were trying to recover.
He dismissed:
- Aasif Sheikh
- Dipendra Singh Airee
- Aarif Sheikh
- Karan KC
Removing Airee late was especially important because Airee was the one batter who looked capable of taking Nepal beyond 140.
Matthew Forde’s Control: The Quiet Over That Changes an Innings
Matthew Forde gave West Indies something every captain wants: control. His figures of 4-1-10-1 show how hard it was to score off him.
A single tight over can force a batting side to attack the next bowler. That is often where wickets fall. Forde’s economy (2.50) did more than save runs—it shaped Nepal’s decisions.
Akeal Hosein Starts the Tone
Akeal Hosein took the early wicket of Bhurtel and finished with 1/30 in 4 overs.
Even when he conceded, he kept the pressure by making batters hit to the longer boundaries and by varying his pace. Early wickets at the top remove a chasing plan before it even begins.
West Indies Beat Nepal: Calm, Structured, and Ruthless
In pursuit of 134, the chase never demanded reckless hitting. Instead, composure and smart shot selection shaped the innings. The batting unit stayed disciplined and followed a clear plan.
Only one breakthrough came during the reply. Brandon King contributed 22 off 17 balls before falling to Nandan Yadav, offering Nepal a brief opening.
From that point onward, control returned quickly. The partnership that followed absorbed any pressure and guided the team smoothly toward the target.
Shai Hope’s 60*: The Anchor That Removes Fear
Shai Hope played a proper chase captain’s innings: 60 off 42* with 5 fours and 3 sixes.
This knock mattered because it kept West Indies ahead without taking unnecessary risks. Hope’s tempo was perfect for a chase of this size. He didn’t try to finish the match in five overs. He ensured Nepal had no opening.
In chases like these, the bowling side waits for a mistake. Hope did not offer one.
Shimron Hetmyer’s 46*: The Finisher Without Chaos
Shimron Hetmyer stayed unbeaten on 46 off 32*, hitting 4 fours and 2 sixes.
Hetmyer’s value is his ability to turn “under control” into “out of reach” quickly. Once he settled, the boundary options opened. When a batter like Hetmyer is set, even decent deliveries can disappear.
Hope and Hetmyer made sure there was no drama. They made sure West Indies crossed the line early, which also helps net run rate in tournament cricket.
Overs That Defined the Chase
Even without ball-by-ball, the scoreboard tells the key moments.
- West Indies reached 43/1 by 5.3 overs (King’s wicket fell there).
- After that, Hope and Hetmyer finished it with an unbeaten partnership.
- The chase ended at 15.2 overs, which is a big net-run-rate boost.
When you win with 28 balls remaining, you didn’t just win. You dominated the time and pressure of the match.
Nepal’s Bowling: Effort, But Not Enough Threat
Nepal’s bowlers tried to mix pace and spin, but they lacked a consistent wicket threat once King was dismissed.
- Nandan Yadav took the only wicket: 1/24 in 3 overs.
- Sandeep Lamichhane conceded 38 in 3 without a wicket.
- Sompal Kami was expensive: 23 in 2 (with a no-ball and wide).
Against a chase, wickets are the fastest way to create pressure. Nepal didn’t get them.
At Wankhede, lengths must be sharp. If the ball sits up, it goes. If it’s too full, it becomes a driving ball. Hope and Hetmyer are exactly the kind of batters who punish small errors.
Nepal did have some decent economy from Karan KC (2-0-12-0) and Dipendra Airee (3-0-18-0), but without breakthroughs, economy only delays a loss.
Key Turning Points
1) Early Damage in the Powerplay
Momentum shifted quickly when Nepal slipped to 17/3 inside the powerplay. Losing three wickets so early forced a complete rethink of their batting approach. Instead of building toward a strong finish, the middle order had to focus on recovery. That defensive adjustment reduced scoring freedom and kept the total below par.
2) Holder’s Impact in the Middle Overs
Jason Holder ensured Nepal never rebuilt properly. Each of his breakthroughs arrived at moments when a partnership was beginning to settle. His spell of 4/27 dismantled any hopes of a late surge and removed the set batters who were trying to anchor the innings. With those dismissals, the possibility of a 150-plus total disappeared.
3) Hope and Hetmyer Shut the Door
After Brandon King’s wicket offered a brief opening, Nepal required immediate strikes to stay alive in the contest. Instead, Shai Hope and Shimron Hetmyer combined for a calm and unbeaten stand. Their partnership erased pressure, rotated strike smartly, and accelerated at the right moments to seal the chase well before the final overs.
What This Result Means for Group C
In tournament cricket, the manner of victory often matters as much as the points earned. A convincing finish strengthens confidence and improves net run rate — both vital factors in tight group stages.
With this dominant chase completed in just 15.2 overs, West Indies beat Nepal by 9 wickets and significantly boosted their standing in Group C. Such margins can become decisive if qualification scenarios come down to net run rate.
From Nepal’s perspective, the contest highlighted small but costly gaps. Their bowling unit showed discipline in phases, yet the top order must provide stronger starts. Frequent early collapses leave too much responsibility on the middle order, turning competitive matches into recovery efforts. At the World Cup level, consistent stability at the top is essential to post winning totals.
Lessons for Nepal: What Must Improve Next Match
A steadier top order
Bhurtel’s early dismissal put pressure on everyone else. Nepal need at least one of the top three to bat into the 12th or 14th over regularly. That is how middle-order hitters get freedom.
Build one long partnership
Even if the strike rate is not explosive, one 50-run stand changes everything. It allows the death overs to become an attack phase rather than damage control.
Wickets during chases
Nepal must find ways to take wickets in the powerplay. One wicket is not enough against experienced batting units.
Lessons for West Indies: Why This Looked Like a Complete Team
West Indies will be happy because this win had structure.
- Bowl first, take early wickets, and keep the middle overs disciplined.
- Chase without panic, keep the required rate low, and finish early.
Holder’s spell gave the bowling unit a clear leader, and Hope’s chase showed composure. When your senior players do the basics well, the team looks hard to beat.
Final Word
West Indies beat Nepal by 9 wickets at Wankhede because they played the match in the simplest way. They forced Nepal into mistakes early, kept the scoring under control, and then chased with a calm plan led by Shai Hope’s 60* and Shimron Hetmyer’s 46*. Nepal had a fighter in Dipendra Singh Airee (58) and a late push from *Sompal Kami (26)**, but the early collapse and lack of wickets in the chase left them with too much to fix inside one game.
Play Live Cricket
Stay tuned with Play Live Cricket for fast match results, human-style analysis, and daily cricket updates—covering the T20 World Cup and everything trending in the cricket world.
Disclaimer
This match report is based on publicly available score information and match data. Team line-ups, stats, and figures are credited to official sources and may be updated if revisions are published later.
