NPL Season 3

NPL Season 3 by the Numbers: Scoring Fell 10%

Twenty-eight matches produced two completely different seasons inside one. In one of them, 120 was enough to defend, 88 took more than 17 overs to chase, and four teams batting first failed to reach 100. In the other, Pokhara Avengers posted 217 and 224 in the final week, a Canadian opener scored the only century of the season, and a 17-year-old fast bowler finished joint-top of the wicket charts. The numbers below tell the story of the league stage better than any single match could: scoring fell by a tenth from last season, the review system overturned half the decisions it was asked to look at, and the record book was rewritten by a team that finished seventh.

Reading9 min
Words1768+
The TU International Cricket Ground in Kirtipur under lights at night during NPL Season 3 Photo: Cricnepal
NPL Season 3's league stage was defined by falling scores and rising records. First-innings scoring averaged 140.7 through Match 25, down 10.4% from 157 in 2025, while DRS overturned 11 of 22 reviews in the first six matches and Pokhara Avengers posted the highest total in league history, 224 for 3.

Advertisement

Quick Facts

League stage
28 matches, 27 results, one abandonment; ended Sunday 15 November 2026
Scoring
First-innings average 140.7 through Match 25, down 10.4% from 157 in 2025
DRS
11 of 22 team reviews overturned in the first six matches
Most runs / wickets
Yuvraj Samra, 294 runs in four innings; four bowlers tied on 12 wickets
Playoffs
Qualifier 1: Lumbini vs Sudurpaschim, Tuesday 17 November, 5:00 PM NST; final Saturday 21 November

Twenty-eight matches produced two completely different seasons inside one. In one of them, 120 was enough to defend, 88 took more than 17 overs to chase, and four teams batting first failed to reach 100. In the other, Pokhara Avengers posted 217 and 224 in the final week, a Canadian opener scored the only century of the season, and a 17-year-old fast bowler finished joint-top of the wicket charts. The numbers below tell the story of the league stage better than any single match could: scoring fell by a tenth from last season, the review system overturned half the decisions it was asked to look at, and the record book was rewritten by a team that finished seventh.

Scoring fell by a tenth from last season

The clearest fact of the season is how hard batting became at Kirtipur. Through the first 25 scheduled matches, teams batting first averaged 140.7 runs. At the same stage of last season the average was 157, and in the inaugural edition it was 146. That is a fall of 10.4% from 2025, and it came with a shape nobody had seen before: four first innings finished below 100, and neither previous edition had produced a single sub-100 first innings in its opening 25 fixtures.

The late-season run was the hardest stretch of all. Across Matches 21 to 25, first-innings totals were 120, 132, 105, 125 and 88, an average of 114. The same five-match window had averaged 145.6 in 2024 and 162.2 in 2025. Nine first innings ended below 130 this season; in the equivalent 2025 sample, the lowest first-innings total of all was 130.

The full league-stage picture, counting all 26 full-length matches and excluding the abandoned game and the five-over match, is only slightly kinder to batters. The average first innings was 145.3 and the median was 148. In 14 of those 26 matches, neither side reached 150. Teams batting first won 14 of the 26, and chasing sides won 12, with the five-over match taking the batting-first tally to 15 wins against 12 for the season as a whole. Low totals were not automatically easy to chase, either. Chitwan Rhinos fell to 37 for 5 pursuing Janakpur Bolts' 88 and needed an unbeaten 35 from Dawid Malan to get home in the 18th over. Lumbini Lions lost six wickets chasing Karnali Yaks' 105. Sudurpaschim Royals defended 120 against Janakpur and 125 against Kathmandu, winning the second of those by seven runs after recovering from 8 for 4.

A rebuilt square, and too little time to prepare it

The scoring record has a physical explanation sitting underneath it, even if the numbers alone cannot prove the cause. The Kirtipur square was rebuilt before the tournament for the first time since 2020, with damaged soil stripped down to the roots before turf was relaid. The curator's team ideally needed four months for the grass roots to reach the depth at which the soil binds and the surface holds together. Roughly two and a half months remained before the October 26 opener.

The work cost an estimated seven to eight million rupees across Kirtipur and Mulpani, funded by the Cricket Association of Nepal, and the association's own forecast before the season was that the grass might survive around two weeks into the tournament before the surface flattened out. What followed matched that warning closely enough to be noticed: a surface that stayed slow, offered turn, and made boundary-hitting difficult once the ball softened. Players said so repeatedly during the season. The scores alone cannot establish whether preparation time, strip selection, weather, batting approach or another factor caused the conditions, but nobody who batted at Kirtipur described an easy surface.

Spin played a central role in the low totals. Sandeep Lamichhane took six wickets for 27 against Pokhara, Chitwan's Ranjeet Kumar took three for two from three overs against Janakpur, and Sikandar Raza conceded ten runs from four overs while taking two wickets in the same match. The season did not belong exclusively to spinners, though. Scott Kuggeleijn's three for 13 helped Sudurpaschim defend 120, Jahandad Khan took three wickets against Sudurpaschim, and Kuggeleijn and Hemant Dhami delivered the final two overs of the chase when Kathmandu fell seven short of 126.

The review system overturned half the calls it saw

The other first of the season was the Decision Review System, used in Nepali cricket for the first time. An audit of ball-by-ball records from the opening six matches found 22 completed team reviews. Eleven decisions were overturned, nine reviews ended with the original decision upheld, and two remained unchanged on umpire's call, allowing the reviewing team to keep its review. All eight teams had used the system by the end of the sixth match.

Twenty of those 22 reviews involved leg-before-wicket decisions, with the other two concerning caught-behind appeals. The clearest early example came when Lokesh Bam was initially given out leg-before-wicket against Karnali Yaks. He reviewed successfully, continued to 87, and helped Biratnagar Kings reach 186 for 7. Without the review, his innings would have ended much earlier. The figures do not represent an overall umpiring error rate, because teams challenged only selected decisions, but they show how quickly the technology changed the relationship between players and major on-field calls. A batter or a captain could act on a doubt instead of carrying it back to the dressing room. The debate did not end there: the system produced the season's biggest flashpoint when a review overturned a not-out call in Chitwan's win over Janakpur, and the argument about how the technology is used has only just begun.

Pokhara rewrote the record book, too late to matter

Pokhara Avengers finished seventh, but no team produced more spectacular batting records. Yuvraj Samra scored 294 runs from only four innings to finish as the league stage's leading run-scorer, with a sequence of 19, 102, 84 and 89. His 102 from 48 balls against Karnali Yaks was the only century of the league stage, and it made him the fourth centurion in league history after Andries Gous, Mark Watt and Adam Rossington.

Samra then combined with Kushal Bhurtel for 186 from 96 balls against Kathmandu Gorkhas in the final league match. It was the highest partnership for any wicket in league history, passing the unbeaten 176 shared by Gous and Dinesh Kharel in 2024, and remarkably the second time in the season the pair had put on exactly 186 together. Bhurtel made 99 from 51 balls, with eight fours and eight sixes, surpassing Rohit Paudel's 95 as the highest score by a Nepali batter in the league, but falling one run short of the first hundred by a home batter.

Pokhara's 224 for 3 became the highest team total in league history, four runs above Biratnagar Kings' 220 for 6 in 2025, and it followed their 217 for 3 against Karnali, making the Avengers the first team to record two totals above 200 in one season. Their two victories came by 63 and 55 runs, the two largest margins of the league stage. The problem was timing. Pokhara had already lost their first four matches and were eliminated before their most destructive performances arrived.

The charts: Samra clear, four share the bowling lead

Samra's 294 placed him 52 runs ahead of Lokesh Bam, who finished second with 242. Bhurtel's late surge took him to 235, while Rashid Khan made 186 for Kathmandu Gorkhas and Ravi Bopara 183 for Chitwan Rhinos. Samra hit the most fours, 29, along with 16 sixes in just four outings. David Miller supplied one of the season's great losing innings on his Karnali debut, an unbeaten 93 from 55 balls while the rest of the batting order struggled against Sudurpaschim, but Karnali still lost by 39 runs.

The bowling table reflected the range of methods that worked at Kirtipur. Kamal Singh Airee, Rijan Dhakal, Rahul Yadav and Jahandad Khan each took 12 wickets, with Harmeet Singh next on 11. Kamal and Rijan gave Chitwan a reliable domestic pace combination, and their performances were central to the Rhinos reaching the playoffs despite winning only three of their seven matches. Rahul's rise carried a different significance. The 17-year-old, recruited through Janakpur's talent hunt, took 12 wickets in his first season, including four for 31 against Kathmandu, and finished joint-top of the charts. Sandeep Lamichhane produced the best figures of the league stage, six for 27 against Pokhara, including a hat-trick that removed Samra, Chamika Karunaratne and Kiran Thagunna from successive deliveries. Harmeet Singh took four for 17 against Janakpur, and Dinesh Kharel four for 18 in the final league match.

How the table finished

Lumbini Lions topped the table with 11 points from seven matches, five wins, one defeat and one no-result, with a net run rate of +1.256. Sudurpaschim Royals were second on 10 points at +0.135, Kathmandu Gorkhas third on 8 at +0.360, and Chitwan Rhinos fourth on 7 at +0.011. Biratnagar Kings and Karnali Yaks finished outside the playoffs with six points each, at -0.467 and -0.640, while Pokhara Avengers and Janakpur Bolts collected four points each, at -0.175 and -0.422. The defending champions did not depend on one dominant run-scorer; different batters handled different situations, and their lower order completed the league stage's most dramatic chase when 28 were needed from eight balls against Biratnagar. Sudurpaschim lost two of their first three matches before winning four in succession. Kathmandu followed an opening defeat with four consecutive wins before losing their final two games. Chitwan's route was built on bowling, with Kamal and Rijan sharing 24 wickets. Biratnagar's campaign contained some of the narrowest margins in the season: an eight-run loss to Chitwan, a failure to defend 186 against Karnali, and a two-run win over Janakpur. Karnali won their first two matches and then lost four in a row, while Janakpur finished bottom on net run rate after their bowlers, led by Rahul and Harmeet with 23 wickets between them, were repeatedly let down by the batting.

What the numbers mean for the playoffs

The league stage offered both extremes, and the playoffs will decide which team adapts best when the Kirtipur square can make 125 look sufficient one day and allow 224 on another. Qualifier 1 brings Lumbini Lions and Sudurpaschim Royals together again on Tuesday, 17 November, at 5:00 PM NST, with the winner straight through to Saturday's final and the loser getting a second chance. The Eliminator follows on Wednesday, 18 November, with Kathmandu Gorkhas against Chitwan Rhinos, the loser going home and the winner meeting the Qualifier 1 loser on Thursday for the last place in the final. Good T20 cricket does not require every match to produce 200, and the best bowlers deserve conditions in which their skills matter. But a competition also needs enough consistent pace and bounce for batters to trust their shots. The team that reads Kirtipur best over the next four matches will lift the trophy.

Read Also: Slow TU Pitch Turns NPL Into a Bowlers' League

FAQs

How much did scoring fall in NPL Season 3?

Through the first 25 scheduled matches, teams batting first averaged 140.7 runs, compared with 157 at the same stage in 2025 and 146 in the inaugural edition. That is a fall of 10.4% from last season, and four first innings finished below 100 for the first time in the league's history.

Why were scores so low at Kirtipur?

The Kirtipur square was rebuilt for the first time since 2020, but the curator's team had roughly two and a half months before the opener instead of the four months ideally needed for the roots to bind. The scores alone cannot prove the cause, but players repeatedly described surfaces that were slow, offered turn and made boundary-hitting difficult once the ball softened.

How did DRS perform in its first NPL season?

In the first six matches, teams completed 22 reviews. Eleven decisions were overturned, nine were upheld and two ended on umpire's call. Twenty of the 22 reviews involved leg-before-wicket decisions, and all eight teams had used the system by the end of the sixth match.

What records fell in the NPL Season 3 league stage?

Pokhara Avengers posted 224 for 3, the highest team total in league history, and became the first team with two totals above 200 in one season. Yuvraj Samra and Kushal Bhurtel shared 186, the highest partnership in league history, and Bhurtel's 99 passed Rohit Paudel's 95 as the highest score by a Nepali batter.

Advertisement

Comments

  1. No comments yet. Be the first to share your view.

Leave a comment

Your email is never shown publicly. Comments appear after approval.