Pokhara Avengers vs Sudurpaschim Royals Match Prediction

Match preview

Sudurpaschim Royals have the stronger historical case, but this is a narrow editorial lean rather than a winner guarantee. They have beaten Pokhara Avengers in both verified NPL meetings. Pokhara, meanwhile, are entering the 2026 season without a completed match to show what their new roster can do.

The counterweight is important. Sudurpaschim were bowled out for 87 in their only completed Season 3 match on 26 October. Kirtipur also has a rebuilt square, and neither team has a confirmed XI for this fixture. The prediction must therefore stay conditional. ^{[7] [8] [9] [10] [11]}

The best pre-match reading is Royals to have a small edge if their recent XI is largely retained and their batting execution improves. Pokhara can overturn that lean with all-round depth and effective new-ball bowling. See the cricket match prediction hub for wider context on how these previews weigh form, selection and venue evidence.

Key Takeaways

• Sudurpaschim lead the proper NPL head-to-head 2-0, with wins in 2024 and 2025. That is historical evidence, not a current team rating. ^{[9] [10]}
• Pokhara have no completed 2026 NPL match before this fixture. Sudurpaschim are 0-1 after losing to Lumbini Lions by seven wickets. ^{[7] [8]}
• The Royals' 26 October XI is a useful continuity reference, not a confirmed team for 28 October. Pokhara's XI is also unconfirmed.
• Kirtipur's square was rebuilt before Season 3. Early grass may aid seam, while a flatter surface can bring spin into the middle overs. ^[11]
• Editorial prediction: a narrow Sudurpaschim lean. The call is most vulnerable to a strong Pokhara debut XI or another Royals batting collapse.

Match details

This is the fourth match of Nepal Premier League Season 3. The approved working start is 10:45 GMT, 16:30 NPT and 16:15 IST on Wednesday, 28 October 2026. CAN's board-linked fixture listing and ESPN's match page agree on the 16:30 Nepal start. ^{[1] [2]}

The Pokhara Avengers fixtures page displays 17:00 NPT. It is an undated franchise-page conflict, and no explicit reschedule notice was found. CAN and ESPN remain the approved time sources. Viewers should still reconfirm the start on match day. ^[3]

This timing issue matters for practical planning. The article does not treat the franchise-page display as a new official change. It records the conflict so readers do not rely on one unverified time when following the match.

Recent tournament form

The teams arrive with very different amounts of 2026 evidence. Pokhara have completed no NPL Season 3 match before this fixture. Their record is 0-0 because their campaign has not started, not because they have established an unbeaten run. ESPN's season listing places Sudurpaschim at 0-1 after their opening match. ^{[7] [8]}

Sudurpaschim's only completed match was a heavy defeat to Lumbini Lions on 26 October at Kirtipur. The Royals made 87 all out in 17.2 overs. Lumbini reached 88/3 in only 9.5 overs and won by seven wickets with 61 balls remaining. ^[7]

That scoreline is the most important piece of fresh evidence in this preview. It shows that the Royals' batting can fail badly in these early conditions. It does not prove that the same XI will struggle again. It also does not establish 87 as a venue par score.

Dipendra Singh Airee was Sudurpaschim's leading scorer with 27 from 23 balls. Anil Kharel made 15 not out from 26, Saif Zaib scored 13 from 14, and Binod Bhandari added 9 from eight. These figures identify the players who offered resistance on the day. They are not forecasts for the next innings. ^[7]

Pokhara's lack of a completed match creates both uncertainty and opportunity. There is no 2026 batting pattern to project. There is also no scorecard-based bowling order. The available material does not prove that the full overseas group will be available together.

The form verdict is mixed. Sudurpaschim have the only current result, but it is a poor one. Pokhara have no result from which to build a positive case. That leaves the Royals with more current evidence, but not with a strong form advantage.

Proper head-to-head record

Sudurpaschim Royals lead the verified NPL head-to-head against Pokhara Avengers 2-0. The sample contains only two direct meetings. Both were played at Kirtipur, and both are historical matches from 2024 and 2025. ^{[9] [10]}

• On 15 December 2024 in Season 1, Sudurpaschim made 153/7. Pokhara were all out for 148, so the Royals won by five runs. ^[9]
• On 21 November 2025 in Season 2, Sudurpaschim scored 193/7. They defeated Pokhara 175/8 by 18 runs. ^[10]

This record supports a small Royals lean because the same matchup has gone their way twice at the same ground. It should not be converted into a probability. It should not be blended with wider historical league records either. A two-match sample cannot measure how the 2026 squads compare.

The head-to-head is best used as context. It gives Sudurpaschim evidence of having handled this opponent before. It does not cancel out the Royals' 87 all out or tell us how Pokhara's new roster will perform.

Current team news

No confirmed 28 October playing XI was located for either team. No reliable fixture-specific injury, withdrawal or registration bulletin was found. Shakib's reported arrival is a separate travel update discussed below.

Any team list published before the toss should therefore be treated as a selection forecast or continuity option. It should not be presented as a fact.

Pokhara's official 2026 roster lists 16 players across batting, wicketkeeping, all-round and bowling roles. It includes captain Kushal Bhurtel and international all-rounders Shakib Al Hasan, Dhananjaya Lakshan and Chamika Karunaratne. The roster is a candidate pool. It is not evidence that every player is available or selected. ^[4]

CricNepal reported on 25 October that Shakib had arrived and was expected to be available throughout the competition. That supports availability in principle. It does not confirm selection or role.

The same report mentioned Mahedi Hasan and Mohammad Saifuddin. They were absent from the current official roster page. They should therefore be treated as reported additions that still require confirmation. ^[5]

Sudurpaschim's official squad page exposes 13 named players. The list includes Airee, Bhandari, Aarif Sheikh, Ishan Pandey, Hemant Dhami, Abinash Bohara and Anil Kharel. ^[6]

The 26 October scorecard confirms that Saif Zaib, Brandon McMullen, Sherfane Rutherford and Scott Kuggeleijn also played. That is stronger evidence of recent availability than a static squad page. It still does not guarantee that all four will repeat in the next XI. ^[7]

The practical question is which combination the captains trust after inspection. The other question is whether the Royals respond to their opening batting failure without sacrificing balance.

Probable XI and selection options

Sudurpaschim Royals: conditional continuity reference

The following is not a confirmed XI. It is the 26 October actual XI, used as the most defensible continuity reference immediately before this fixture:

Saif Zaib, Binod Bhandari, Aarif Sheikh, Brandon McMullen, Dipendra Singh Airee, Ishan Pandey, Sherfane Rutherford, Scott Kuggeleijn, Anil Kharel, Hemant Dhami and Abinash Bohara. ^[7]

Keeping much of that group together would give Sudurpaschim a known combination. Changes could also address the 87 all-out batting display. The four added or overseas names in the scorecard actually played, even though not all appear on the official club squad page.

That source conflict is a reason to wait for the toss. It is not a reason to declare anyone unavailable. The scorecard shows who took part on 26 October. The toss sheet will show who is selected for this match.

Airee remains the clearest recent batting reference because he top-scored with 27 against Lumbini. Kharel's unbeaten 15 showed resistance rather than a high-scoring role. The wider selection question is balance.

The Royals need enough batting to avoid another collapse. They also need to preserve the bowling resources that made the combination viable on 26 October. A continuity decision can support familiarity, but it does not repair poor execution by itself.

Pokhara Avengers: role-based options, not a fixed XI

Pokhara do not have a previous 2026 scorecard from which to build a probable XI. The responsible approach is to describe options by role:

• Leadership and batting: Kushal Bhurtel is listed as captain and batter. Kiran Kumar Thagunna and Bibek Rana Magar are additional listed batting options.
• Wicketkeeping cover: Arjun Kumal is listed as a batter-wicketkeeper. Arjun Gharti Magar is listed as a wicketkeeper.
• All-round and bowling depth: Dinesh Kharel, Bipin Khatri, Sunny BK, Bipin Acharya, Shakib, Dhananjaya Lakshan and Chamika Karunaratne are listed as all-rounders. Akash Chand, Sagar Dhakal, Pratik Pokhrel and Sudip Aryal are listed as bowlers. ^[4]

These options do not establish the batting order. They also do not establish the overseas combination or the number of specialist bowlers. The final team should be described as “to be announced at the toss” unless a new official bulletin appears.

For historical context around Nepal's prominent power-hitting names, readers can also browse this six-ball, six-sixes record list. That background is not current NPL form and should not be used as a substitute for the team sheet.

Kirtipur pitch evidence

Kirtipur offers a changing surface rather than a fixed one-line pitch verdict. The square was rebuilt before Season 3. Damaged soil was stripped back, turf was relaid and grassing was completed.

CAN vice-president Roshan Kumar Singh said the grass could last roughly two weeks into the tournament before the surface flattened. The accompanying report linked earlier green conditions with pace and new-ball assistance. It then described spin as more influential once the grass disappeared. ^[11]

That description concerns seasonal wear across the tournament. It is not a guarantee of a within-innings change during this match.

The first completed 2026 match provides a live check, but not a par score. Sudurpaschim made 87 all out and Lumbini chased 88/3 in 9.5 overs on 26 October. ^[7] The low total may reflect batting errors and execution as well as the wicket. Therefore, 88 cannot be treated as a fixed target.

The useful match-day question is how much grass and pace remain during inspection. A lively surface may aid new-ball bowlers. A flatter surface could make spin a useful middle-overs option. The toss decision should follow what the teams see, not a rigid pre-match label.

The venue evidence also supports a measured approach to the cricket grounds hub. That link is a wider pitch-evidence resource, not a dedicated Kirtipur guide. Historical numbers provide context, but no mixed T20I aggregate or one-match total is a fixed 28 October par score.

Weather forecast for 28 October

Current match-period weather could not be verified consistently enough for publication. There is no dependable basis here for stating a temperature, rain probability, humidity level, wind condition or dew expectation.

Readers should recheck the weather close to the start. Any toss-choice discussion that depends on weather must remain conditional. It should not be presented as a forecast.

Tactical matchups

Can Pokhara attack the Royals before they settle?

The first tactical opportunity is the new ball. Sudurpaschim's 87 all out exposes a batting risk, but the innings total alone does not establish when the collapse began.

If grass remains, Pokhara should seek disciplined movement and pressure. Their aim would be to make the Royals' top order play enough controlled deliveries before it can settle. That is a tactical option, not a claim that the pitch will definitely assist seam.

The Royals need their top order to avoid allowing one difficult passage to become another collapse. A calm start would give Airee and the middle order a platform. It would also reduce the need for a late rescue effort from the lower order.

Airee and the Royals' middle-order response

Airee's 27 from 23 was the strongest batting contribution in the opening match. That makes him a player Pokhara must plan for if he is selected again. The evidence does not justify assigning him a fixed batting position or predicting another score.

The key issue is whether Sudurpaschim can keep wickets in hand if the surface plays flatter than it did in the opening match. Kharel's unbeaten 15 from 26 also shows how difficult recovery became against Lumbini.

A more productive recovery, rather than one isolated big over, may be the Royals' route back into the match. Pokhara should try to make that rebuilding phase costly through control and smart fields.

Pokhara's selection flexibility

Pokhara's listed all-rounders could help them adapt to the surface they find at inspection. A roster label does not confirm a player's final role, batting order or bowling workload.

That uncertainty can be useful if the selected players cover several phases of a T20. It can also become a weakness if the debut combination leaves too much responsibility with a few players. The toss sheet will matter more than a speculative fixed XI.

Fantasy selection considerations

Fantasy teams should wait for the toss because neither side has a confirmed XI. These are conditional candidates, not guaranteed selections or points predictions.

• Kushal Bhurtel: He is Pokhara's listed captain and batter. He is a candidate to monitor if selected, but neither his 2026 batting position nor an opening role is confirmed by the roster.
• Shakib Al Hasan: His arrival and reported competition availability make him a watch-list player if he is named. Selection is still unconfirmed, and the roster does not establish a guaranteed bowling workload.
• Dipendra Singh Airee: He scored 27 from 23 in the Royals' only completed 2026 match. That is a recent performance reference, not a promise of repeat value.
• Saif Zaib, Brandon McMullen, Sherfane Rutherford and Scott Kuggeleijn: All four played in Sudurpaschim's 26 October XI. Their appearance is useful evidence of recent availability, but their places in the 28 October team remain conditional because current squad pages and match evidence do not align perfectly.

Confirm the team sheet, wicketkeeper, top order and selected all-rounders. The previous scorecard does not prove future roles.

Conditional match prediction

Editorial prediction: narrow Sudurpaschim Royals lean. The case rests on two direct NPL wins over Pokhara, both at Kirtipur. It also rests on the possibility that the Royals retain much of their recent combination. The lean is deliberately modest.

Sudurpaschim's only 2026 result was an 87-all-out defeat. Pokhara's new-season ceiling is unknown. Those facts prevent the historical record from carrying the whole prediction. ^{[9] [10]}

The prediction changes in Pokhara's favour if their toss XI has reliable batting, their all-rounders provide balance and the new ball uses any remaining grass. A strong debut from Bhurtel or the international all-rounder group would quickly reduce the value of the historical head-to-head.

Another Royals collapse would do the same. The previous scorecard is evidence of a possible weakness, not proof that the next innings will follow the same pattern.

Toss analysis should also be conditional. If inspection shows visible grass or early seam, bowling first may be logical. If the wicket looks hard and flatter, batting first can be attractive.

That does not mean spin must become harder to attack later in the same innings. There is no basis for predicting the toss or saying its winner must chase.

Final verdict

Sudurpaschim Royals are the narrow editorial pick because they have won both verified NPL meetings with Pokhara and can draw on a recent XI baseline. That edge is fragile.

Their 87 all out against Lumbini exposes a major batting concern. Pokhara's untested 2026 roster could also produce a better combination than the evidence currently allows us to model.

The most responsible prediction is therefore a conditional Royals lean, not a definitive result claim. A deep Pokhara XI or another Royals batting failure can overturn it.