Nepal Premier League 2026 · ARCHIVED PRE-MATCH ANALYSIS

Archived pre-match analysis: Lumbini Lions vs Pokhara Avengers Match Prediction: NPL Match 13

Lumbini Lions bring one win and one abandonment into NPL Match 13, while Pokhara Avengers have two completed defeats. Direct match listings support 4:15 PM IST, although another schedule listing shows 4:45 PM IST.

By CricWin24 editorialPublished Facts checked
A conceptual AI-generated cricket-equipment illustration for this match preview, not a player or venue photograph.
AI-generated cricket-equipment illustration; not a player or venue photograph. Photo credits.
Scheduled start has passed. This is an archived pre-match opinion, not a live score, a current toss result or a confirmed playing XI. The analysis is dated 2 Nov 2026, 1:16 PM IST.

A prediction is not a result

These are pre-match editorial estimates. Neither the toss nor the starting XIs were confirmed at the stated editorial check; the actual match can unfold differently.

THE QUICK READ · 3 NOV 2026

What you need to know first

  • Match: Lumbini Lions vs Pokhara Avengers
  • Start: 4:15 PM IST / 10:45 UTC / 4:30 PM NPT
  • Venue: Tribhuvan University International Cricket Ground, Kirtipur
  • Conditional lean: Lumbini have the cleaner current record, but the two-match sample, unconfirmed XIs, clock conflict and unavailable dated forecast prevent a guaranteed pick.
01 / MATCH DESK

Match preview and early verdict

Lumbini Lions vs Pokhara Avengers is scheduled for Tuesday, 3 November 2026, in Nepal Premier League Match 13. The best early reading is a cautious Lumbini lean: Lumbini have one completed win and one abandoned fixture, while Pokhara have lost both of their completed matches. That is a useful form contrast, but it is not a large enough sample to justify a percentage prediction or a confident playing-XI call. The fixture appears on the NPL 2026 overview, and the direct match record still showed it as upcoming when the research was checked. 1

The central question is whether Lumbini can turn an interrupted start into another completed result, or whether Pokhara can convert two competitive innings into a first win. ESPNcricinfo displays 03/11 at 05:45 AM EST, which converts to 10:45 UTC, 4:30 PM NPT and 4:15 PM IST; Pokhara's club fixture page and an independent schedule page show 5:00 PM NPT, or 4:45 PM IST. 1 3 This article uses the direct-record clock while keeping the alternative visible.

AdvertisementVedik Exchange: Your Cricket ID Guide. Account access, security and eligibility. Read the guide. Information-only resource.

An external information guide from Vedik Exchange. Opens in a new tab.

Key Takeaways

  • Lumbini enter Match 13 with one win, one abandonment, three points and no completed loss; Pokhara are 0-2 after defeats by six wickets and nine runs.
  • The working start time is 4:15 PM IST / 10:45 UTC / 4:30 PM NPT, but Pokhara Avengers and an independent listing attribute 5:00 PM NPT / 4:45 PM IST to the fixture.
  • The only prior Lumbini-Pokhara meeting in the available record was in 2025, when Lumbini chased 150 and won by three wickets. It is historical context, not 2026 team evidence.
  • No confirmed Match 13 XI, injury report, replacement list or dated match-time forecast was available at the research cut-off.
  • The conditional winner lean is Lumbini because of the current points position and cleaner completed record, not because the result is guaranteed.
02 / MATCH DESK

Lumbini Lions vs Pokhara Avengers: match details

Detail Information
Fixture Lumbini Lions vs Pokhara Avengers
Competition Nepal Premier League 2026, labelled 2026/27 on ESPNcricinfo
Match 13th Match, league stage
Format Twenty20, day/night, 20 overs per side
Date Tuesday, 3 November 2026
Working start 4:15 PM IST / 10:45 UTC / 4:30 PM NPT
Alternative listing 5:00 PM NPT / 4:45 PM IST on the Pokhara club page and independent schedule
Venue Tribhuvan University International Cricket Ground, Kirtipur
Status at research cut-off Scheduled/upcoming; no toss, result or confirmed XI

ESPNcricinfo identifies the same teams, date, venue and 20-over day/night format and displays 03/11 at 05:45 AM EST. This converts to 10:45 UTC and 4:30 PM NPT / 4:15 PM IST. 1 The unresolved point is the alternative 5:00 PM NPT listing, not an ordinary time-zone calculation.

Readers checking the NPL 2026 schedule should compare the displayed local time with the direct match records close to the fixture. No organizer notice resolving the conflict was found in the sources checked.

03 / MATCH DESK

The match preview: an interruption-reset versus a two-loss test

This is not a straightforward meeting between a settled leader and a settled struggler. Lumbini's points position looks strong because the team won its opener and received a point from an abandoned game. Pokhara's record is more damaging because both of its matches reached a result. Yet Pokhara have not been blown away in either completed innings: they made 145/7 in the opener and 138/9 while chasing 147 against Janakpur. The problem is closing the match, not finding every ingredient for a competitive contest.

ESPNcricinfo's table snapshot had Lumbini at two matches, one win, no losses, three points and a net run rate of +4.599. Pokhara were at two matches, no wins, two losses, no points and a net run rate of -0.934. 1 Those numbers describe the table at the check, not a stable performance rate. Lumbini have only completed one match, and one Pokhara defeat was decided by nine runs.

The unique angle for this Lumbini Lions vs Pokhara Avengers prediction is therefore completion under pressure. Lumbini need to show that the sharp opening chase was more than a favourable low target. Pokhara need to show that the final overs of a chase can be managed with enough wickets and boundary options left. The side that answers its specific question better should control the match, even if the raw table creates a bigger gap than the evidence supports.

04 / MATCH DESK

Current form and preceding results

Lumbini Lions: one emphatic chase, then no result

Lumbini began the campaign by beating Sudur Paschim Royals by seven wickets on 26 October. Sudur Paschim were dismissed for 87 in 17.2 overs, and Lumbini reached 88/3 in only 9.5 overs. D'Arcy Short scored 40 from 18 balls and Aasif Sheikh made 32 from 25 in that match. 4 Those are direct match contributions, not season averages and not a promise that either batter will be selected against Pokhara.

Lumbini's next listed match, against Chitwan Rhinos on 31 October, was abandoned without a ball bowled. ESPNcricinfo records the abandonment without a ball bowled and one point for each side. 5 That distinction matters for the prediction. Lumbini have not lost, but they also have not completed a second match in which their batting depth, bowling changes and death-over execution could be tested.

The positive reading is that Lumbini's first chase was controlled rather than merely survived. The caution is that an 87-run target tells us little about how they would respond to a 150-plus chase or how they would defend a total late in a full innings.

Pokhara Avengers: competitive totals without a completed win

Pokhara's opener against Sudur Paschim Royals ended in a six-wicket defeat. Pokhara made 145/7 in 20 overs, but Sudur Paschim reached 148/4 in 16.5 overs. 6 The scoreline points to two connected issues: Pokhara found enough runs to make a match of it, but the defence did not create enough pressure once the chase gathered pace.

The latest completed result was a nine-run loss to Janakpur Bolts on 1 November. Janakpur made 147/7, and Pokhara finished on 138/9 after 20 overs. ESPNcricinfo records that Pokhara chose to field. 16 8

Pokhara's bowling contributions from that game are worth separating from Janakpur's defence. Shakib Al Hasan's 3/15 and Chamika Karunaratne's 2/23 were Pokhara bowling figures in Janakpur's first innings, not Janakpur wickets. Both also appeared as Pokhara batters in the chase. The full scorecard records Janakpur's defending bowlers as Moeen Ali, 3/13, and Harmeet Singh, 2/20. 16 The tactical distinction matters: Pokhara have shown they can take wickets, but still need a stronger batting finish and more control when defending or chasing a close total.

05 / MATCH DESK

Head-to-head record: one 2025 meeting only

There was no completed Lumbini-Pokhara meeting in the 2026 NPL record before this scheduled Match 13. The available historical record contains one 2025 league meeting at Kirtipur: Pokhara made 150/5, Lumbini replied with 151/7 in 19.4 overs and won by three wickets with two balls remaining. 9

That result is useful as a reminder that this fixture can become a close chase. It cannot be used as current NPL 2026 form, a venue average or a reason to carry 2025 players into the 2026 selection. The available evidence does not support a larger historical head-to-head table, so this prediction keeps the comparison narrow rather than presenting an incomplete number as a trend.

06 / MATCH DESK

Venue, pitch report and weather: what can be said responsibly

Tribhuvan University International Cricket Ground, Kirtipur is the listed venue in the ESPNcricinfo direct fixture record. 1 The assigned venue source is a general listing, not a current pitch report with trustworthy measurements or a verified ground-wide scoring baseline. 11

The clearest recent interruption evidence is an abandonment, not a verified pitch or weather forecast. ESPNcricinfo records that the Lumbini-Chitwan match at the same ground was abandoned without a ball bowled. The cited scorecard does not establish the weather cause. 5 That supports a practical decision rule: readers should check the official match status and toss information close to the start, because recent disruption is real, while the surface behaviour for Match 13 remains unverified.

A usable dated 3 November match-window forecast was not available at the check. No reliable match-hour temperature, wind, rain probability, humidity or dew value can therefore be given. The recent abandonment is relevant interruption context, but it does not establish tomorrow's weather or a pitch-drying prediction.

07 / MATCH DESK

Availability and probable playing XI limitations

A confirmed Match 13 squad and playing XI were not available at the research cut-off. The direct Cricbuzz squads page states that squads data was not available. 10 A 2026 Match 7 scorecard reference for Lumbini includes Rohit Paudel as captain, Niroshan Dickwella as wicketkeeper, D'Arcy Short, Aasif Sheikh, Shamim Hossain, Sundeep Jora, Shadley van Schalkwyk and Sher Malla among the players seen around that fixture. 5 That is a current-season match reference, not a confirmed XI for Tuesday.

Pokhara's completed Match 9 scorecard identifies Shakib Al Hasan and Chamika Karunaratne as Pokhara bowlers and batters against Janakpur. 16 This is current-season match evidence, not a confirmed Match 13 squad. It does not establish Tuesday's availability, batting order, overseas participation or final XI; neither player is guaranteed to be selected again.

For that reason, a responsible Lumbini Lions vs Pokhara Avengers playing 11 preview should stop at the evidence boundary. Do not treat a fan or club roster as a confirmed squad, do not carry 2025 names forward and do not label any player injured or available without a current team-sheet source. The final fantasy and tactical decisions should be made after the toss and announced XIs.

08 / MATCH DESK

Strengths and weaknesses of both teams

Lumbini Lions

Strengths: Lumbini's opener showed fast, low-risk chase control. They dismissed Sudur Paschim for 87 and reached the target at 9.5 overs with only three wickets down. The direct scorecard also gives them a clear top-order evidence point through D'Arcy Short's 40 from 18 and Aasif Sheikh's 32 from 25. 4 Their current table position gives them more margin than Pokhara, provided the no-result is not mistaken for another completed win.

Weaknesses: Lumbini have only one completed match in the sample. There is no recent completed innings showing how they defend a total, absorb a middle-overs slowdown or recover after early wickets. The abandoned Chitwan fixture also means their last match action did not test their combination under pressure.

Pokhara Avengers

Strengths: Pokhara have produced totals of 145/7 and 138/9 in their two completed matches, so the batting has not disappeared. The latest game also produced genuine bowling contributions from Shakib and Chamika, who took 3/15 and 2/23 respectively against Janakpur. 16

Weaknesses: The team has not yet completed a winning chase or defence. Sudur Paschim reached 148/4 in 16.5 overs after Pokhara posted 145/7, and Janakpur held a nine-run margin after Pokhara reached 138/9. 6 16 The next step is not simply scoring more; it is preserving wickets and creating decisive overs at the end.

09 / MATCH DESK

Key players and battles to watch

The first key battle is Lumbini's proven opening-chase intent against Pokhara's ability to take early wickets. D'Arcy Short and Aasif Sheikh were the most visible batting contributors in Lumbini's first match, but neither is a guaranteed Match 13 selection. If they are named, Pokhara's new-ball plan should aim to deny the same rapid start rather than wait for pressure to build later.

The second is Pokhara's all-round balance. Shakib Al Hasan and Chamika Karunaratne produced important bowling figures in the Janakpur first innings and also batted in Pokhara's reply. The team attribution matters here: those were Pokhara contributions, not evidence of Janakpur's attack. Their value in Match 13 depends on selection and role, neither of which was confirmed at the check.

The third is the final five overs of each innings. Pokhara's two losses show why this is the decisive area: a chase can remain alive at 138/9 but still fall nine runs short, while a 145/7 total can be chased with 19 balls unused. Lumbini, meanwhile, have not yet supplied a completed defence to compare. The team that handles wickets, strike rotation and boundary options after the 15th over will have the clearest tactical edge.

10 / MATCH DESK

Informational fantasy and Dream11 considerations

This is an informational fantasy cricket section, not a confirmed Dream11 team. There is no responsible basis for publishing a locked combination before the Match 13 XI is announced. The direct squads page was unavailable, and the current-season roster references do not settle availability.

Once the XIs are released, prioritise roles over reputation:

  • A confirmed top-order batter has more opportunity than a player whose batting position is unknown. D'Arcy Short and Aasif Sheikh are watchlist names because of their opening-match scores, not automatic picks. 4
  • An all-rounder who is confirmed to bat and bowl can offer two routes to fantasy points. Shakib Al Hasan and Chamika Karunaratne have current scorecard evidence for both disciplines, but their Match 13 roles must be checked first. 16
  • A wicketkeeper should be considered only after confirming selection and batting position. The Lumbini Match 7 reference identifies Niroshan Dickwella as wicketkeeper, but that match reference is not a final team sheet for this fixture. 5
  • Captain and vice-captain choices should follow confirmed involvement. A genuine two-skill role or a top-order player with a clear workload is a better evidence-based starting point than a famous name who may not play.

Avoid using the 2025 head-to-head as a fantasy player pool. It is historical context only, and the article has no confirmed Match 13 XI to support a player-by-player recommendation.

11 / MATCH DESK

Toss, chase and innings scenarios

No toss preference can be verified before the toss. The absence of a dated forecast and current pitch report also means there is no evidence-based reason to declare that batting first or chasing is automatically superior.

If Lumbini bat first, Pokhara need wickets and dot-ball pressure before the closing overs, then enough wickets in hand for their own chase. Their last pursuit finished on 138/9, nine runs short of Janakpur. 16 That is the relevant chasing warning, rather than their earlier unsuccessful defence.

If Pokhara bat first, they need to set a target with a more demanding finish than the 145/7 Sudur Paschim chased in 16.5 overs. 6 Lumbini's recent evidence is a fast chase of a much smaller target, so it cannot prove how they would pursue a substantially larger total. Bowling roles and late-overs execution must be assessed from the confirmed XIs, not an invented matchup statistic.

If rain delays the start or reduces the overs, the analysis must be reset rather than scaled mechanically. The recent abandonment supports checking the live status, covers and revised playing conditions, but it does not supply a score band or a rain probability for this match. Any prediction should therefore remain scenario-based until the toss, team sheets and official playing conditions are known.

12 / MATCH DESK

Match winner prediction and final verdict

The conditional winner lean is Lumbini Lions. They have the cleaner current record, three points, a positive table position and an opening chase won by seven wickets. Pokhara's two defeats are close enough to show competitiveness, but they still point to an unfinished team problem: either the defence has not held or the chase has not reached the line.

That lean is deliberately modest. Lumbini have only one completed match, their second fixture was abandoned, the Match 13 XI is unconfirmed, the dated match-time forecast is unavailable and the start-time conflict has not been resolved by an organizer notice. Pokhara can overturn the lean if their batting preserves wickets deeper into the chase and their bowlers reproduce the control shown by Shakib and Chamika against Janakpur.

So the answer to “who will win?” is not a guaranteed Lumbini result. It is a conditional Lumbini preference based on the evidence available on 2 November for a match scheduled on 3 November. Reassess it after the toss and confirmed XIs, especially if the clock, weather status or player availability changes.

13 / MATCH DESK

Frequently Asked Questions

What time is Lumbini Lions vs Pokhara Avengers Match 13?

The working time is 4:15 PM IST, 10:45 UTC and 4:30 PM NPT on Tuesday, 3 November 2026. ESPNcricinfo's direct fixture record displays 03/11 at 05:45 AM EST, equivalent to 10:45 UTC / 4:30 PM NPT / 4:15 PM IST. 1 Pokhara's club fixture page and an independent schedule instead show 5:00 PM NPT, or 4:45 PM IST. 3 15 No official organizer notice resolving the difference was found in the sources checked.

Where will the NPL Match 13 be played?

The match is scheduled at Tribhuvan University International Cricket Ground, Kirtipur. ESPNcricinfo lists the match at Tribhuvan University International Cricket Ground, Kirtipur. 1

Is the match confirmed, and has the toss happened?

It was listed as scheduled and upcoming at the 2 November research cut-off. No toss, result or confirmed Match 13 XI was available. The status can change on match day, so readers should use the direct match centre and official team-sheet information for the final update.

Did Lumbini lose to Chitwan Rhinos in their previous match?

No. The Lumbini-Chitwan fixture on 31 October was abandoned without a ball bowled, with one point for each side. 5 Lumbini therefore entered Match 13 with one win, no completed loss and one no-result, not two wins and not a defeat.

What was Pokhara Avengers' latest result?

Janakpur Bolts beat Pokhara by nine runs on 1 November. Janakpur made 147/7 and Pokhara finished on 138/9 in 20 overs. 16 Pokhara's earlier result was a six-wicket loss to Sudur Paschim Royals after posting 145/7. 6

What is the Lumbini Lions vs Pokhara Avengers head-to-head record?

The available record contains one completed meeting before this fixture, in the 2025 NPL. Pokhara made 150/5, Lumbini chased 151/7 in 19.4 overs and won by three wickets with two balls remaining. 9 It should not be treated as 2026 form or as confirmation of any 2026 player selection.

Are the playing XIs and weather forecast confirmed?

No. The direct Match 13 squads page reported that squads data was unavailable. 10 A usable dated 3 November match-window forecast was unavailable at the check. Do not treat current-season roster pages or stale weather output as a confirmed XI or match forecast.

14 / MATCH DESK

Sources and fact-check

Research was checked on 2 November 2026 at 13:16:55 +05:30. The source register below identifies the direct pages used for fixture, form, player attribution, availability, venue and weather-limit claims. The cover is a conceptual AI-generated cricket-equipment illustration, not a player or venue photograph.

Archived pre-match analysis. The scheduled start has passed; this page is not a live score or an updated result. Confirmed lineups, the toss and match conditions can change the outlook; the actual result may differ.

← More match previews