NPL Season 3

Why NPL Teams Are Suddenly Batting First

For the first three weeks of NPL Season 3, the toss had only one answer. Win it, bowl first, and chase under the lights at Kirtipur. Then the answer changed. Captains have now chosen to bat first in six of the 25 matches played, including three in a row — and the results, the pitches and the captains' own words all point to the same reason: setting a total has started to look safer than chasing one.

Reading6 min
Words1270+
A wicketkeeper appeals during a night match at the TU International Cricket Ground in Kirtipur Photo: The Kathmandu Post
For the first three weeks of NPL Season 3, winning the toss meant bowling first. That has changed: captains have now chosen to bat first in six of the 25 matches played, including three in a row, because the slow Kirtipur pitches make setting a total safer than chasing one. The numbers, and the captains, explain why.

Advertisement

Quick Facts

The split
25 matches played: 19 field-first decisions (8 won, 11 lost), 6 bat-first decisions (2 won, 4 lost)
The last field-first win
Lumbini Lions beat Biratnagar Kings by four wickets, 14 November — the first field-first win since 5 November
The turning point
Pokhara Avengers 217 for 3 vs Karnali Yaks, 9 November — Yuvraj Samra 102 off 48 balls, won by 63 runs
A small total defended
Sudurpaschim Royals defended 120 for 9 against Janakpur Bolts, 10 November, winning by 27 runs
Latest
Janakpur batted first on 13 November and made 88 for 9; Chitwan chased 92 for 6 and won by four wickets

For the first three weeks of NPL Season 3, the toss had only one answer. Win it, bowl first, and chase under the lights at Kirtipur. Then the answer changed. Captains have now chosen to bat first in six of the 25 matches played, including three in a row — and the results, the pitches and the captains' own words all point to the same reason: setting a total has started to look safer than chasing one.

Advertisement

The numbers behind the flip

The split is stark. Across the 25 matches played so far — one fixture, between Chitwan Rhinos and Lumbini Lions on 31 October, was cancelled — the captain who won the toss has chosen to field 19 times and to bat six times. The field-first teams have won eight and lost 11. The bat-first teams have won two and lost four. The raw numbers still favour bowling first. The direction of travel does not.

The last time a team won a match after choosing to field first was 5 November, when Kathmandu Gorkhas bowled first against Biratnagar Kings and won by nine wickets. In the 11 matches since that night, the toss-winning captain has chosen to bat five times — and five teams that chose to field first in completed matches all lost. That run ended on Saturday, when Lumbini Lions won the toss against Biratnagar, chose to bowl, and chased down the Kings' 166 for 4 with four wickets in hand, reaching 168 for 6 with one ball to spare. The field-first win drought lasted nine days. The split now reads 19 field-first calls, eight won and 11 lost.

Advertisement

Three matches changed minds

The turn began on 9 November, in a match Pokhara Avengers had to win. Bottom of the table and playing Karnali Yaks in a do-or-die game, Pokhara chose to bat first — and posted 217 for 3, built on Yuvraj Samra's 102 off 48 balls and Kushal Bhurtel's 62 off 39. Karnali were bowled out for 154, and Pokhara won by 63 runs. It was the season's first century, and the first time in weeks that batting first had looked like the brave choice rather than the reckless one.

A day later, Sudurpaschim Royals took the same gamble against Janakpur Bolts and made it work with far less. They managed only 120 for 9 — and defended it, winning by 27 runs. Two days after that, the idea met its limit twice in one day: Pokhara batted first again and were bowled out for 132, losing to Biratnagar by four wickets with four balls to spare; Karnali batted first against Lumbini, were bowled out for 105 in 19.2 overs, and lost by four wickets with 20 balls to spare.

Advertisement

Friday tested the idea twice

Friday's double-header put the new thinking through two very different tests. In the first match, Kathmandu Gorkhas went back to the old way: they won the toss against Sudurpaschim, chose to bowl, and watched the Royals post 125 for 6 — Dipendra Singh Airee making 60 off 55 balls, his third fifty of the season — before falling seven runs short at 118 for 7. It was the fifth straight defeat for a team that chose to field first since 5 November.

In the second match of the day, Janakpur Bolts won the toss against Chitwan Rhinos and batted first — and were held to 88 for 9. Chitwan chased it down with four wickets and 16 balls to spare, reaching 92 for 6 behind Dawid Malan's unbeaten 35 off 39 balls. Janakpur's campaign ended with the defeat; Chitwan moved to seven points from six matches and stayed in the playoff race. The lesson of the day was not that batting first always works. It was that neither choice works without the runs to back it.

Advertisement

Why the pitch changed the maths

The captains are not guessing. They are reading the pitch at the TU ground, and the pitch has been the season's loudest argument. Chitwan batter Ravi Bopara, the leading run-scorer of the season, has played in all three editions of the league, and he has been blunt about the surfaces this year. He called them the worst he has seen in the tournament — then added that the pitch for his most recent match was nice, and a positive sign for the second half of the season.

The ground staff have had little time to work with. The pitches at the TU ground were repaired only in August, and the grass needs months to bind the soil properly — four months, by one estimate, for roots to reach four inches deep. The season began on 26 October, before that work could finish. Days in Kirtipur have been hot and bright, evenings cool, and the surfaces have stayed slow and low for much of the tournament — good for bowlers, hard for batters trying to force the pace, and harder still for a team chasing a total as the light fades.

That is the calculation behind the flip. On a slow pitch, a team that bats first can set its own pace, put a total on the board, and then let its bowlers defend it with the scoreboard on their side. A team that chases has to score at a required rate on the same surface, with the pressure rising with every dot ball. When a total of 120 has been enough to win — as Sudurpaschim showed against Janakpur — the risk of batting first starts to look smaller than the risk of chasing.

Advertisement

What the captains say

Karnali captain David Miller was frank after his side's defeat to Lumbini: his team had not batted well and had not posted the score it wanted. It was the same complaint, in different words, from Janakpur's Gulshan Jha, who said the wicket had been slow at first before getting better — and that his side had still not used its plan after winning the toss and batting first. Lumbini coach Shakti Gauchan, asked whether he would have bowled first had he won the toss, said it depended on the team's strength and planning — and that Karnali's plan with the bat had been real enough: had they scored 130 or more, he said, it would have been difficult for his side.

Gauchan added a point worth remembering as the playoffs approach: if results were decided by the toss, that would not be great for the game. The toss gives a team the first decision. It does not bat, bowl or field for them. The last three weeks have proved both halves of that — captains who bowled first and lost, and captains who batted first and lost, all on the same ground.

Advertisement

What it means for the playoffs

The playoffs begin on Tuesday, 17 November, and the toss will matter there as much as anywhere — perhaps more, with the season on the line in every match. But the trend of the last week suggests captains will think twice before taking the ball by default. Saturday's 26th match showed both sides of the argument at once. Lumbini won the toss and chose to bowl against Biratnagar — the 19th field-first call of the season — and this time the old habit worked: the Lions chased down 166 for 4 with four wickets in hand, the first field-first win since 5 November. The win also took Lumbini to the top of the table with 11 points from seven matches. Whether Saturday was a return to the old habit or a one-match judgement about the conditions will be clear soon enough. What is already clear is that the habit itself has broken. In this league, batting first is no longer the strange decision. It is the one every captain is now weighing.

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

FAQs

How many times have teams chosen to bat first in NPL Season 3?

Six times in the 25 matches played so far — Kathmandu against Janakpur on 29 October, Pokhara against Karnali on 9 November, Sudurpaschim against Janakpur on 10 November, Pokhara against Biratnagar and Karnali against Lumbini on 12 November, and Janakpur against Chitwan on 13 November. Two of those teams won and four lost.

Which team started the bat-first trend?

Pokhara Avengers started the recent run, choosing to bat first against Karnali Yaks on 9 November and posting 217 for 3, with Yuvraj Samra scoring 102 off 48 balls. Pokhara won by 63 runs. Kathmandu Gorkhas had batted first once earlier in the season, against Janakpur on 29 October, and lost by eight wickets.

Why are teams batting first at the TU ground?

The pitches have been slow and low, which makes setting a total and defending it attractive — totals as low as 120 have been defended. Chasing on the same surface, under lights, has proved harder, and captains have decided the risk of batting first is now smaller than the risk of chasing.

When was the last time a team won after choosing to field first?

On Saturday, 14 November, when Lumbini Lions won the toss against Biratnagar Kings, chose to bowl, and won by four wickets, chasing 168 for 6 with one ball to spare. Before that, the last field-first win was Kathmandu's nine-wicket win over Biratnagar on 5 November — five straight defeats in between.

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.