NPL Season 3

Bat First Is the New Habit in NPL Season 3

For the first fortnight of Nepal Premier League Season 3, the toss at the TU International Cricket Ground in Kirtipur settled into a routine so fixed it barely seemed like a decision at all. The captain who called correctly sent the opposition in to bat, walked back to his fielders, and waited for the chase. Thirteen of the first 14 completed matches went that way. Then, inside a week, the routine broke. The last three tosses have all chosen to bat first, and the team that wins the coin on Friday will be watched more closely than usual.

Reading7 min
Words1480+
A wicketkeeper appeals under lights during a Nepal Premier League night match at the TU International Cricket Ground in Kirtipur Photo: The Kathmandu Post
NPL captains have flipped from fielding first to batting first: after the toss-winner chose to bowl in 13 of the first 14 completed matches, the last three tosses all chose to bat. Through 22 matches, teams batting first have won twice and lost three times — the toss still guarantees nothing.

Advertisement

Quick Facts

The split
22 matches played: toss-winners fielded first 17 times (7 wins, 10 losses) and batted first 5 times (2 wins, 3 losses)
The flip
The last three matches — 10 and 12 November — all saw the toss-winner choose to bat first
Last field-first win
Kathmandu Gorkhas beat Biratnagar Kings in Match 15 on 5 November, bowling them out for 83
Run chart
Lokesh Bam leads with 227 runs, ahead of Yuvraj Samra on 205 and Ravi Bopara on 171
Next matches
Kathmandu vs Sudurpaschim at 12:30 PM NST and Janakpur vs Chitwan at 5:00 PM NST on Friday, 13 November

For the first fortnight of Nepal Premier League Season 3, the toss at the TU International Cricket Ground in Kirtipur settled into a routine so fixed it barely seemed like a decision at all. The captain who called correctly sent the opposition in to bat, walked back to his fielders, and waited for the chase. Thirteen of the first 14 completed matches went that way. Then, inside a week, the routine broke. The last three tosses have all chosen to bat first, and the team that wins the coin on Friday will be watched more closely than usual.

Advertisement

The numbers behind the turn

The numbers behind the turn are stark. Twenty-two matches have been played, leaving out the abandoned fixture between Chitwan Rhinos and Lumbini Lions on 31 October, which never reached a toss. In 17 of them, the side that won the toss elected to field first. Seven of those sides went on to win, and 10 lost. In the five matches where the toss-winner chose to bat first, two won and three lost. Put another way, winning the toss has produced only two wins from the last eight matches — and both of them came from teams that batted first.

Kathmandu Gorkhas were the last team to win a match after deciding to field first. That was the 15th match of the season, against Biratnagar Kings on 5 November, when Biratnagar were bowled out for 83 in 18.3 overs and Kathmandu chased the target down in 9.4 overs, David Warner unbeaten on 44 off 24 balls. Since then, four captains have won the toss and sent the opposition in — Karnali Yaks against Sudurpaschim Royals, Pokhara Avengers against Chitwan Rhinos, Lumbini Lions against Kathmandu, and Chitwan Rhinos against Kathmandu — and all four lost.

Advertisement

The one warning nobody forgot

The reason the habit held for so long sits in the fifth match of the season, and every captain in the league seems to have remembered it. On 29 October, Kathmandu won the toss against Janakpur Bolts and chose to bat first, the only time any captain had done so up to that point. They were bowled out for 115 in 19.3 overs, with 17-year-old Rahul Yadav taking four for 31, including both openers. Janakpur knocked off the target with 16 balls to spare, winning by eight wickets. One match, one defeat — and nobody tried it again for 11 days.

It is easy to see why the lesson stuck. The pitches at Kirtipur have been the hardest part of this season to read, and a captain who bats first and posts a small total hands the match away before the second innings starts. Under floodlights, dew makes the ball harder to grip as the evening wears on, and the side bowling second feels it most. Captains also like the look of a fresh pitch in the first innings: overnight fog leaves residual moisture in the surface, the ball moves early, and the pitch flattens out as the afternoon sun bakes it. Chasing, in that picture, looks like the safe choice.

Advertisement

The innings that broke the freeze

What broke the freeze was not a theory but an innings. On 9 November, Pokhara Avengers, bottom of the table and playing a do-or-die match against Karnali Yaks, won the toss and batted first. Yuvraj Samra struck 102 off 48 balls, Kushal Bhurtel made 62 off 39, and Pokhara posted 217 for 3 — the biggest total of the season — before bowling Karnali out for 154 in 18.3 overs to win by 63 runs. It was Pokhara's first win of the season, and it showed the whole league what a first-innings total could do on this ground.

The next day, Sudurpaschim Royals took the same chance. They won the toss against Janakpur Bolts, batted first, and managed only 120 for 9 — a total that looked well short. They defended it anyway, winning by 27 runs. Two matches, two wins for the side batting first, and the second of them proved the point better than the first: it was not only about posting a huge score. A modest total, defended with discipline, could win too.

Advertisement

Thursday corrected the idea before it could harden into a new orthodoxy. Pokhara won the toss against Biratnagar Kings in the first match of the day and batted first again. This time it backfired: they were bundled out for 132 in 17.5 overs, Sandeep Lamichhane taking six for 27 including a hat-trick, and Biratnagar chased the target down with four wickets and four balls to spare. In the evening match, Karnali won the toss against the defending champions, Lumbini Lions, and chose to bat first. They were bowled out for 105 in 19.2 overs, and Lumbini chased it down with 20 balls and four wickets to spare, D'Arcy Short making 46 off 34 balls and taking two for 13. Batting first is the new habit. It is not a guarantee.

Advertisement

Why the pitches changed minds

The captains who have made the switch talk less about the toss itself than about the surface underneath it. Ravi Bopara, who has played in all three seasons for Chitwan Rhinos, has been the bluntest. He said the pitches have not been the best this season, and called them probably the worst he has seen at the ground — then added that the pitch for the match against Kathmandu on 9 November was nice, and that there were positive signs moving into the second half. He also noticed the weather turning on the surface: hot during the day, cool in the evenings, a pattern he compared to playing in England, and one he was not sure had affected the pitches or not. His own form underlines the point that batting first is no free gift: he is third on the run chart with 171 runs from four matches, behind Lokesh Bam on 227 and Yuvraj Samra on 205, and his 55 off 35 balls in the defeat to Kathmandu showed how hard runs have been to come by.

Advertisement

The background to the pitches goes back to August, when the surfaces at the TU Ground were repaired. The cricket association's vice-president, Roshan Kumar Singh, explained at the time that everything depends on how long the grass stays on the wicket: while the grass lives, the pitch holds together, and once it dies off the surface turns flat. For the roots to grip four inches deep and bind the soil, the work typically needs four months. The pitches did not get that time, with the league starting on 26 October.

Lumbini's consultant coach, Shakti Gauchan, put the decision the way a coach would: it depends on the team's strength and planning. Karnali, he said, had a plan with the bat, and had they scored 130 or more it would have been difficult for his side. Lumbini wanted to bowl, and used that strength. He also made the wider point that if results were decided by the toss, it would not be great for the game — teams have to perform the role the game demands of them. Karnali's Gulshan Kumar Jha agreed with the reading of the surface, saying the wicket was slow at first and then started getting better, and that his side could not use its plan despite winning the toss and batting first. His side had hoped for 130 or more, and fell 25 short. Rohit Kumar Paudel, the Lumbini captain, said he would have bowled first had he won the toss. The two captains looked at the same pitch and wanted opposite things from it.

Advertisement

What it means for the run-in

The flip matters because the league has reached the stage where every toss carries weight. Lumbini are the first team into the playoffs, top of the table with nine points from six matches after the win over Karnali. Kathmandu and Sudurpaschim sit behind them on eight points each, and the chasing pack is close enough that one result changes the shape of the race. Friday brings two more matches: Kathmandu against Sudurpaschim at 12:30 PM NST, and Janakpur against Chitwan at 5:00 PM NST. Both tosses will be read as a signal — whether captains still trust the bat-first turn, or whether Thursday's two defeats have already cooled it.

The honest reading of the season is that the toss has never decided much at Kirtipur, in either direction. The side that won the toss has won nine of the 22 matches played, and the side that lost it has won 13. Fielding first won seven and lost 10. Batting first won two and lost three. What has decided matches is the quality of the bowling, the nerve of the chase, and the fielding — the same things Janakpur's captain pointed to after his side's defeat to Lumbini, when misfields and dropped catches cost them runs they could not afford. The habit has flipped, and that is a story. But the next captain who wins the toss will still have to do the hard part himself.

Read Also: Winning the Toss Is Not Winning Matches in NPL Season 3

FAQs

How many times have teams batted first after winning the toss in NPL Season 3?

Five times in 22 matches. Kathmandu were the first, against Janakpur on 29 October, and lost. The other four came in the last five days: Pokhara against Karnali on 9 November, Sudurpaschim against Janakpur on 10 November, Pokhara against Biratnagar on 12 November, and Karnali against Lumbini on 12 November. Two of the five won, three lost.

When did NPL captains start batting first?

The turn came on 9 November, when Pokhara Avengers won the toss against Karnali Yaks and batted first, posting 217 for 3 and winning by 63 runs. Sudurpaschim Royals did the same the next day, and the last three matches of the season — against Janakpur, Biratnagar and Lumbini — have all seen the toss-winner bat first.

Who was the last team to win after choosing to field first?

Kathmandu Gorkhas, in the 15th match against Biratnagar Kings on 5 November. They bowled Biratnagar out for 83 in 18.3 overs and chased the target in 9.4 overs, with David Warner unbeaten on 44 off 24 balls. Every captain who has fielded first since then has lost.

Do the pitches explain why teams are batting first now?

Partly. Ravi Bopara, who has played all three seasons, called this season's pitches probably the worst he has seen at the ground, though he said the surface for the match against Kathmandu on 9 November was nice. The pitches were repaired in August, but the grass roots needed about four months to bind the soil, and the league began on 26 October. Captains also weigh the opposition, the match situation and the weather.

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.