The Sikkim Cricket Team vs Mumbai Cricket Team Match Scorecard from the Vijay Hazare Trophy Elite 2025‑26 looks respectable at first glance: Sikkim fighting to 236/7, Mumbai replying with 237/2. The scoreboard alone doesn’t show the gulf in intent, skill, and tactical clarity that unfolded in Jaipur. Rohit Sharma’s 94‑ball 155* didn’t just win a match, it rewrote the balance of the group, tore apart Sikkim’s bowling confidence, and highlighted exactly how top domestic sides convert opportunities into net run rate gold. This long‑form scorecard article gives you something most competitors don’t: complete reference data plus phase‑wise analysis, turning points, boundary and dot‑ball insight, and tournament context.

Match Overview – Result, Venue, and Stakes

Sikkim Cricket Team vs Mumbai Cricket Team Match Scorecard, they want clarity first: who won, by how much, and under what conditions. Before diving into tables and tactical layers, you anchor those basics.

Match Snapshot

• Fixture: Sikkim vs Mumbai, Vijay Hazare Trophy Elite 2025‑26, Group C
• Venue: Sawai Mansingh Stadium, Jaipur
• Date: 24 December 2025
• Format: List A, 50 overs per side
• Toss: Sikkim won the toss, elected to bat first
• Sikkim total: 236/7 (50 overs)
• Mumbai total: 237/2 (30.3 overs)
• Result: Mumbai won by 8 wickets, with 117 balls remaining
• Points: Mumbai 4 points, Sikkim 0 points
• Player of the Match: Rohit Sharma (155 off 94 balls)

Read More: UP Warriorz vs Royal Challengers Bangalore Cricket Match Scorecard

Snippet‑Friendly Summary

In the Sikkim Cricket Team vs Mumbai Cricket Team Match Scorecard, Sikkim posted 236/7 after choosing to bat, built around a solid innings from Ashish Thapa. Mumbai responded with a dominant chase, reaching 237/2 in 30.3 overs thanks to Rohit Sharma’s 155‑run blitz, securing an eight‑wicket win and a crucial boost to their net runrate in Group C.

Full Sikkim Batting Scorecard – How 236/7 Was Constructed

Most “scorecard” pages stop at numbers. To beat them, you start with full tables and tell readers what those tables actually mean.

Sikkim Innings – Batting Card

Batter	Dismissal	Runs	Balls	4s	6s	SR
Amit Rajera	c wicketkeeper b Deshpande	0	2	0	0	0.00
K Sai Satwik	b Kotian	34	55	4	0	61.82
Ashish Thapa †	c fielder b Thakur	79	87	8	0	90.80
Kranthi Kumar	lbw b Thakur	34	52	2	0	65.38
Gurinder Singh	lbw b Mulani	17	35	0	0	48.57
Palzor Tamang	c fielder b Musheer Khan	10	15	1	0	66.67
Ankur Malik	run‑out	9	11	0	0	81.82
Lee Yong Lepcha (c)	not out	1	2	0	0	50.00
Extras		21	–	–	–	–
Total	236/7 (50 overs)					RR 4.72

Snippet‑Style Explanation of Sikkim’s Total

Sikkim’s 236/7 came from a mix of resilience and missed opportunity. Ashish Thapa’s 79 off 87 balls held the innings together, while K Sai Satwik and Kranthi Kumar added 34 each. The overall run rate of 4.72 showed controlled batting, but a lack of boundary bursts in the final overs meant the total landed in Mumbai’s comfort range rather than stretching the favourites.

Boundary and Dot‑Ball Patterns – Sikkim

Looking at the Sikkim Cricket Team vs Mumbai Cricket Team Match Scorecard closely, you can see where Sikkim’s innings stalled:

• Thapa’s boundaries: 8 fours in 87 balls means just under 10% of his deliveries went to the rope. That’s solid, but not destructive.
• Satwik’s role: His 34 off 55 was more about soaking pressure, with 4 boundaries and a strike rate touch above 60.
• Dot‑ball impact: Both batters faced long stretches of dots against Mumbai’s spinners and disciplined pace, especially after the 25th over, forcing Sikkim into survival mode instead of targeted acceleration.

Mumbai Bowling Figures – How the Attack Controlled the Game

The bowling half of the Sikkim Cricket Team vs Mumbai Cricket Team Match Scorecard shows how Mumbai’s attack took control after an early wobble. They didn’t rely on mystery spin or express pace, they used lengths, angles, and sustained discipline.

Mumbai Bowling Scorecard

Bowler	Overs	Maidens	Runs	Wickets	Econ
Shardul Thakur	6	0	19	2	3.17
Tushar Deshpande	8	0	32	1	4.00
Tanush Kotian	9	0	63	1	7.00
Shams Mulani	10	0	35	1	3.50
Musheer Khan	10	1	37	1	3.70
Sylvester D’Souza	7	0	50	0	7.14

Snippet – Ready Bowling Insight

Mumbai restricted Sikkim to 236/7 largely through Shardul Thakur’s 2 for 19 and tight spells from Shams Mulani and Musheer Khan. While Tanush Kotian and Sylvester D’Souza went for more than seven runs an over, Mumbai’s captain rotated them around the more economical options, ensuring Sikkim never sustained scoring bursts long enough to push past 250.

Phase‑Wise Bowling Control

To give your Sikkim Cricket Team vs Mumbai Cricket Team Match Scorecard more depth, break the bowling effort into phases:

• Powerplay (0-10 overs):
  Deshpande and Thakur attacked the stumps and hard length. The early dismissal of Rajera at 5/1 set the tone, limiting Sikkim to cautious shots and keeping them under 45 runs in the first 10 overs.
• Middle Overs (11-35 overs):
  Mulani and Musheer Khan squeezed the scoring by hitting the same channel repeatedly-just outside off, full enough to invite risk but tight enough to punish mis‑hits. Thapa and Kumar kept Sikkim afloat but couldn’t break free.
• Death Overs (36-50 overs):
  Mumbai’s plan here was simple: protect straight boundaries, force cross‑bat hitting, and accept singles. That’s why Sikkim’s last 14 overs produced only a modest increase in run rate, leaving the final total below “scary” territory.

Fall of Wickets and Key Partnerships – Sikkim’s Turning Points

Where did Sikkim’s innings truly shift? The fall‑of‑wickets table in the Sikkim Cricket Team vs Mumbai Cricket Team Match Scorecard shows this clearly.

Fall of Wickets – Sikkim

Score	Wicket	Over	Context
5/1	Amit Rajera	1.2	Early edge, immediate pressure
56/2	K Sai Satwik	12.5	First rebuild ended, forced reset
162/3	Ashish Thapa	31.5	Set batter removed at launch window
165/4	Kranthi Kumar	33.4	Two wickets in two overs, momentum lost
190/5	Gurinder Singh	41.5	Middle‑order squeeze completed
210/6	Palzor Tamang	45.4	No base left for finishing surge
232/7	Ankur Malik	49.1	Late run‑out stalls any late dash

Partnership Summary – Sikkim

You can add a simple partnership table to give structure on the Sikkim Cricket Team vs Mumbai Cricket Team Match Scorecard.

Read More: Andhra Cricket Team vs Delhi Cricket Team Match Scorecard

Wickets	Partners	Runs	Overs	Role
1-2	Rajera, Satwik	51	~11	Powerplay rebuild
2-3	Satwik, Thapa	106	~19	Backbone of total
3-4	Thapa, Kumar	3	~2	Collapse after set batter
4-5	Kumar, Gurinder	25	~8	Slow, defensive rebuilding
5-6	Gurinder, Tamang	20	~4	Attempted late push
6-7	Tamang, Malik	22	~4	Short burst, then stall

Only one partnership truly pushed Sikkim forward-the Thapa–Satwik stand. Everything after that was damage control, not scoreboard pressure.

Full Mumbai Batting Scorecard – 237/2 in 30.3 Overs

Now the second half of the Sikkim Cricket Team vs Mumbai Cricket Team Match Scorecard: the chase. This is where Mumbai showed why they’re a heavyweight in Indian domestic cricket.

Mumbai Innings – Batting Card

Batter	Dismissal	Runs	Balls	4s	6s	SR
Angkrish Raghuvanshi	c fielder b Gurinder Singh	38	58	3	0	65.51
Rohit Sharma	c fielder b Kranthi Kumar	155	94	18	9	164.89
Hardik Tamore †	lbw b Purna Chhetri	2	7	0	0	28.57
Musheer Khan	not out	27	26	2	1	103.84
Extras		15	–	–	–	–
Total	237/2 (30.3 overs)					RR 7.77

Snippet‑Ready Chase Summary

Mumbai chased down 237 for the loss of just two wickets, led by Rohit Sharma’s 155 off 94 balls. With a strike rate near 165 and 27 boundaries, Rohit turned the target into a formality, ensuring the game ended in the 31st over and transforming the Sikkim Cricket Team vs Mumbai Cricket Team Match Scorecard into a showcase of aggressive List A batting.

Rohit Sharma Innings Breakdown – Boundaries, Milestones, and Strategy

If you want a high‑authority cricket blog, you can’t stay generic about an innings like this. You break Rohit’s knock down like a coach and an analyst would.

Rohit’s Numbers

• Runs: 155
• Balls: 94
• Strike Rate: 164.89
• Fours: 18
• Sixes: 9
• Total boundaries: 27
• Boundary balls: 27 out of 94
• Boundary percentage: 28.7% of his balls faced resulted in boundaries
• Fifty: reached in the low‑40 ball range, balancing risk and control
• Hundred: completed in 62 balls, the fastest List A century of his career

Why His Innings Broke Sikkim

Rohit’s approach in the Sikkim Cricket Team vs Mumbai Cricket Team Match Scorecard was deliberately ruthless:

1. Early assessment:
   The first 20 balls were about reading pace and bounce. Singles, twos, and a few controlled boundaries kept the rate healthy without exposing him to early dismissal.
2. Middle‑overs expansion:
   Once comfortable, he targeted weaker match‑ups-medium‑pacers without sharp movement and spinners whose length he could manipulate. This phase saw his strike rate jump toward 150+.
3. Death‑overs mentality in middle overs:
   Rohit used the middle overs like death overs: field spread, but pace predictable. He hit over mid‑off, through extra cover, and over mid‑wicket. Boundaries at the start and end of overs broke any pressure.
4. Partnership with Angkrish:
   Their 140+ stand meant Mumbai never had to think about risk management. Angkrish could play at 65 SR, Rohit covered the required rate alone.

Sikkim Bowling Figures – Structural Weaknesses Exposed

The bowling card on the Sikkim Cricket Team vs Mumbai Cricket Team Match Scorecard isn’t just about runs conceded. It reveals the structural challenges Sikkim faces against elite batting.

Sikkim Bowling Scorecard

Bowler	Overs	Maidens	Runs	Wickets	Econ
Amit Rajera	7	0	54	0	7.71
K Sai Satwik	4	0	32	0	8.00
Gurinder Singh	6	0	37	1	6.16
Purna Chhetri	4	0	17	1	4.25
Ankur Malik	3	0	26	0	8.66
Kranthi Kumar	3	0	37	1	12.33
Lee Yong Lepcha	3.3	0	34	0	9.71

Tactical Problems

• No strike bowler with pace or mystery:
  Every over Rohit faced felt like a calculated risk, not genuine danger. Without a bowler who could consistently challenge both edges at high speed, Sikkim were stuck hoping for mistakes rather than creating them.
• Inconsistent lengths:
  Too many half‑volleys and short‑of‑length balls in Rohit’s arc. When you bowl that way to someone in this kind of form, he will hit at will.
• Reactive captaincy:
  Field changes often followed boundaries instead of anticipating shot selection. Once Rohit spotted patterns, he simply hit where the field wasn’t.

Match Timeline – Chronological Highlights for AI Overviews

Your Sikkim Cricket Team vs Mumbai Cricket Team Match Scorecard needs a chronological narrative section.

Sikkim Innings – Timeline

• Over 1: Rajera edges behind early, Sikkim 5/1, forced into damage control.
• Overs 2-10: Satwik and Thapa rebuild quietly, moving Sikkim to around 40–45/1, run rate around 4.5.
• Over 13: Satwik bowled at 56/2, partnership broken just as they approached stability.
• Overs 14-31: Thapa and Kumar build the main stand, pushing the score to 162/2. This is Sikkim’s best phase, yet scoring remains more “steady” than “explosive”.
• Over 32: Thapa dismissed at 162/3, the key turning point in the innings.
• Over 34: Kumar lbw, Sikkim tumble from 162/2 to 165/4, momentum gone.
• Overs 35-42: Gurinder and Tamang attempt a rebuild but are held around 5 RPO.
• Overs 43-50: Late wickets and limited boundaries restrict Sikkim to 236/7.

Mumbai Innings – Timeline

• Overs 1-5: Rohit and Angkrish play watchfully, picking singles and occasional boundaries, score around 30/0.
• Overs 6-10: Intent rises, Mumbai cross 60 with no wicket, chase fully under control.
• Overs 11-20: Rohit accelerates aggressively, by the 20th over, Mumbai sit near 140/1.
• Rohit’s hundred: He reaches his century in 62 balls, pushing the required rate into irrelevance.
• Overs 21-29: Continued hitting, Mumbai surge past 220 with plenty of overs left.
• Over 29: Rohit finally dismissed at 155, the match is already practically decided.
• Over 30.3: Musheer finishes the chase, Mumbai end at 237/2, win by eight wickets.

Phase‑Wise Sikkim Scoring – Powerplay, Middle, and Death Overs

Phase	Overs	Approx. Runs	Wickets	Run Rate	Comment
Powerplay	0-10	~40-45	1	~4.2-4.5	Conservative, field restrictions underused
Middle	11-35	~120	3	~4.8-5.0	Backbone built, but no major spike
Death	36-50	~70	3-4	~5.0	Below par for modern List A finishing

Mumbai Scoring Phases

Phase	Overs	Approx. Runs	Wickets	Run Rate	Comment
Powerplay	0–10	~60	0	~6.0	Calm, efficient, zero pressure
Middle	11-25	~135	2	>8.0	Rohit’s acceleration kills tension
Death	26-31	~40+	0	>8.0	Chase finished before actual death phase

Sikkim’s phases show survival and limited intent, Mumbai’s phases show controlled aggression and a conscious net run rate strategy.

Boundary Analysis and Run‑Rate Progression

This is where you add the stats‑nerd layer to your Sikkim Cricket Team vs Mumbai Cricket Team Match Scorecard.

Sikkim Boundary Analysis

• Top‑order boundaries: around 16–18 fours in total.
• Boundary clustering: most boundaries came in safe overs-after big risks were taken, not when the bowlers were under pressure.
• Run‑rate pattern: gentle climb, occasional stalls, rarely did they push above 6 RPO for multiple overs.

Mumbai Boundary Analysis

• Rohit alone: 18 fours and 9 sixes, 27 boundaries off 94 balls.
• Boundary distribution: early boundaries build confidence, mid‑innings hitting breaks Sikkim’s plans, late boundaries ensure rapid finish.
• Run‑rate progression: from around 6 in the Powerplay to above 8 in the middle phase, staying high enough that the target becomes irrelevant long before the final overs.

Tournament Context – What This Match Did to Group C

Scorecards that rank well don’t treat the match as isolated, they tie it into series narratives.

In Group C of the Vijay Hazare Trophy Elite 2025‑26, this match had clear consequences:

• Mumbai:
  • Gain four points, rising near the top of the group.
  • Massive net run rate boost thanks to a chase inside 31 overs.
  • Batting confidence surges, Rohit’s form becomes a talking point for both domestic fans and national selectors.
• Sikkim:
  • Stay at the bottom end of the table.
  • Net run rate suffers from heavy defeat.
  • The gap between their batting discipline and finishing power becomes obvious, raising questions about death‑overs strategy and bowling resources.

Frequently Asked Questions: