Both teams scored identical powerplays: 34/2 and 34/4 respectively. Same runs, six wickets difference. That is the match in one line. GT survived their early collapse, built through patience and partnerships, posted 168. SRH never found a method once the powerplay damage was done. Sixty-one percent dot balls, 86 all out in 14.5 overs, and GT record their largest ever IPL win.

Match Pulse: Rabada's double strike in over 2 of the SRH chase, Abhishek Sharma and Ishan Kishan both gone for a combined 17 runs, collapsed SRH to 6/2 inside nine balls and the game was effectively over by over 4.

Phase Breakdown

Phase	GT Runs/Wkts	GT RPO	SRH Runs/Wkts	SRH RPO	Verdict
Powerplay (1-6)	34/2	5.67	34/4	5.67	Identical runs, SRH lost twice the wickets
Early Mid (7-11)	44/1	8.8	26/3	5.2	GT rebuilt, SRH kept losing
Late Mid (12-16)	45/0	9.0	26/3 partial	6.78	GT no wickets, SRH three more
Death (17-20)	45/2	11.25	DNB	—	SRH bowled out at 14.5
Reality check	SRH: 54 dot balls from 89 faced	—	61% dots on a surface GT scored 8.8 RPO on	—	Not conditions, just capitulation

SRH's best partnership in the entire innings was Klaasen-Arora for 24 off 23 balls at 6.26 RPO. That was the high-water mark of their chase.

Impact Match-Up

Rabada and Holder bowled 8 overs between them for 48 runs and 6 wickets combined. Rabada went 4-0-28-3 at 7.0 RPO with two powerplay strikes that broke the chase before it started. Holder then systematically dismantled the middle order: 4-0-20-3 at 5.0 RPO, clinical, relentless, no width, no room. Siraj opened with a wicket maiden and finished 3-1-11-1 at 3.67 RPO. With the bat, the Sudharsan-Washington stand of 60 off 41 balls at 8.78 RPO was where GT turned 26/2 into something defendable, both batters rotating strike, hitting gaps, refusing to force it on a surface that punished aggression.

The Over That Broke It

Over 2 in the chase. Rabada targeted hard lengths at Abhishek, got him for 6, then removed Ishan Kishan two balls later. SRH were 6/2 after nine balls of their chase, Head already gone from over 1, and three of their top four back in the hutch before the powerplay had even settled. From that point the required rate was already asking for something SRH simply did not have the batting depth to produce.

The Over That Closed It

Over 11, Holder bowling. Two wickets in the over, Klaasen at 56/6 and NKR at 60/7 in the same over. SRH's last genuine hope of a fighting total disappeared when Klaasen went for 14, the match effectively reduced from a chase to damage limitation in six balls. Rashid finished it in over 15 off five deliveries.

Player Ratings

#	Name	Team	Role	Label	Descriptor
1	Kagiso Rabada	GT	Bowler	Destroyer	3 wickets, chase-killer
2	Jason Holder	GT	Allrounder	Enforcer	3 wickets, suffocating
3	Sai Sudharsan	GT	Batter	Anchor	61 off 44, calm under pressure
4	Washington Sundar	GT	Allrounder	Builder	50 off 33, rebuilt the innings
5	Mohammed Siraj	GT	Bowler	Opener	Wicket maiden, tone-setter
6	Pat Cummins	SRH	Bowler	Lone Fighter	19 off 9 batting, best SRH had

Trivia

• GT's 82-run win is their largest margin of victory in IPL history, beating their previous best of 77 runs against Rajasthan Royals.
• The match aggregate of 254 runs (168 + 86) is the lowest in any IPL match involving GT and SRH.
• Jos Buttler took 5 dismissals behind the stumps in the GT innings, a new GT record breaking Wriddhiman Saha's previous best of 4

Simulation Verdict

GT won this in two phases: over 2 of the chase when Rabada took Abhishek and Kishan, and over 11 when Holder took Klaasen and NKR off consecutive balls.

Hot Take

• SRH scored 61% dot balls chasing 169 on a surface where GT's middle overs went at 8.8 and 9.0 RPO. This was not a difficult surface. SRH's top order simply had no answer to hard lengths and froze completely. Their powerplay batting approach, which has powered them all season, has no plan B when conditions do not suit it.

"Rhythm is everything for a fast bowler and you have to find a way to click depending on the conditions rather than looking too far ahead." ~ Kagiso Rabada, Player of the Match

"The way we bowled in the powerplay set the tone and gave us control of the game early on." ~ Shubman Gill, GT Captain

"These things happen in T20 cricket and it is about how you respond." ~ Pat Cummins, SRH Captain

SRH scored 61% dot balls chasing 169 on a surface GT scored at 9 RPO in the middle overs. Is this a one-off or does SRH have a structural problem when their powerplay attack plan fails?

Written with authoritative precision for r/CricketBriefing*.* Rabada removing Abhishek and Ishan off consecutive balls in over 2 while Head was already back in the pavilion from over 1 is the image that defines this match: SRH's entire top order gone before the powerplay found its footing.

This IPL 2026 post-match report covers GT vs SRH, Match 56, at Narendra Modi Stadium, Ahmedabad on 12 May 2026. Phase analysis, bowling breakdown, and partnership data for Gujarat Titans' 82-run win over Sunrisers Hyderabad. GT move to 16 points and top of the table after Match 56, SRH drop to 14 points on third place behind RCB on NRR.

Sri Lanka A swept New Zealand A 3-0 at Hambantota last month. Dambulla now, with thunderstorms threatening the entire day.

Match Intel: New Zealand A Women vs Sri Lanka A Women | Rangiri Dambulla International Stadium, Dambulla | Tue, 12 May 2026 | 10:00 AM IST | 04:30 AM GMT | 10:00 AM Local | Format: Unofficial ODI - 1st Match

Weather

• Thunderstorms from late morning; High to Very High rain risk first innings
• Rain risk High into second innings; DLS is not a possibility but a probability
• Temperature 29-31°C; humidity 80-90%
• Covers deployed multiple times; match completion not guaranteed

Market Volatility and Toss Index

Factor	Statistical Impact	Tactical Recommendation
Venue toss field	Toss field winners won 7/8 completed here	Bowl first
H2H toss bat	Both times toss winner chose to bat, they won	Bat first
SLA-W batting	4 wins batting first in last 10	Bat first
DLS context	Early aggressive batting maximises DLS par	Bat first

Pitch and Ground

Square	Straight	Avg 1st Inn	Avg 2nd Inn	Bat first wins	Chase wins
65m	72m	240	205	5/8 (63%)	3/8 (37%)

• Slow, dry Dambulla surface; early moisture could assist seamers in the first 10 overs
• Spinners dominate as match progresses; 57% of wickets here by spin
• Pitch slows between rain breaks; second innings batting gets harder
• Wet outfield reduces boundary speed; first-innings scoring suppressed

Vishmi Gunaratne vs Fran Jonas

Gunaratne returns from injury; senior international experience on her own surfaces. Jonas is NZA-W's primary slow left-arm threat. How Jonas handles Gunaratne in overs 20-35 shapes whether SLA-W build or collapse.

Predicted Playing XIs

Jess Watkin (c), Bella James, Prue Catton, Bella Armstrong, Tash Wakelin, Marama Downes, Hannah Rowe, Xara Jetly, Fran Jonas, Emma Black, Kate Gaging (wk)

Sathya Sandeepani (c), Vishmi Gunaratne, Sanjana Kavindi, Limansa Thilakarathna, Vimoksha Balasuriya, Rashmika Sewwandi, Piumi Wathsala, Dewmi Vihanga, Sachini Nisansala (wk), Chamudi Praboda, Rashmi Silva

All names verified against official squad lists.

Injury and Availability

No injury concerns for either squad.

Form and H2H

Team	Form (Oldest to Newest)	Reading
NZA-W	L W L L L	Three straight losses; swept at Hambantota
SLA-W	L L W W W	Three straight wins; dominant recent H2H run

SLA-W lead H2H 3-2 in completed meetings; won all three recent encounters.

Batting First Dominance in This H2H

Teams batting first won 4 of 5 completed H2H matches. Both times the toss winner chose to bat, they won. The H2H record is clear: the team that sets a total wins.

Venue Scoring Patterns

• Batting first won 5 of 8 completed here
• Toss field winners won 7/8; most batting-first wins came from toss losers
• Spin took 57% of wickets; conditions get harder for second-innings batters

Win Probability

SLA-W 62%, NZA-W 38%; home conditions, H2H momentum, spin familiarity.

Hot Take

Heavy rain cuts this to 20 overs; Xara Jetly produces an explosive knock and NZA-W win on DLS.

Trivia Nuggets

• This is the first time these two A-sides have met at Dambulla; NZA-W have never played a recorded match at this ground
• SLA-W's three April wins at Hambantota included a 140-run victory; Dambulla is a different surface

Community Challenge

With thunderstorms expected all day and DLS likely, does the toss winner today effectively win the match before a ball is bowled?

Written with authoritative precision for r/CricketBriefing. Always verify local toss updates and radar before the first ball.

This unofficial ODI series preview covers toss analysis, H2H batting-first dominance, and rain impact for New Zealand A Women vs Sri Lanka A Women at Rangiri Dambulla International Stadium.

The NZA-W vs SLA-W 1st Unofficial ODI preview includes venue spin dominance data, weather impact analysis, and H2H context following Sri Lanka A's 3-0 sweep at Hambantota.

Rangiri Dambulla International Stadium's slow pitch and 57% spin-wicket rate make it one of the most challenging surfaces for visiting teams in Asian women's cricket, particularly when rain interruptions further dry and grip the surface between innings.

Bhuvi took 4 for 23 with the ball then hit the six that broke the game open in the final over. Bosch took 4 for 26 and nearly won it for MI anyway. RCB conceded 16 extras including 11 wides and still won by one run off the last ball. On a two-paced Raipur surface where 166 felt competitive, composure in the final over was the only thing that separated these two sides.

Match Pulse: Bhuvi's six off the first ball of over 20, RCB needing 15 off six, turned a near-impossible equation into a manageable one and swung the momentum irreversibly.

Phase Breakdown

Phase	MI Runs/Wkts	MI RPO	RCB Runs/Wkts	RCB RPO	Edge
Powerplay (1-6)	53/3	8.83	47/3	7.83	MI ahead, same wicket cost
Early Mid (7-11)	38/0	7.6	35/0	7.0	Both grinding, no wickets
Late Mid (12-16)	45/2	9.0	49/3	9.8	RCB scored more, lost more
Death (17-20)	30/2	7.5	36/2	9.0	RCB pulled it out
Chaos row	Dropped Krunal at 17.2, 73 off 46	—	16 extras including 11 wides	—	MI gifted runs, then dropped the chance to end it

RCB's 16 extras vs MI's 6: that 10-run gap in a 1-run match is the single number that explains the result.

Impact Match-Up

Two spells defined the night. Bhuvi went 4-0-23-4 at 5.75 RPO on a pitch that let bowlers who hit good lengths repeatedly. He removed Rickelton in over 1, then came back in over 3 to take Rohit and SKY off consecutive balls, leaving MI at 28/3 inside three overs. Bosch replied in the chase: 4-1-26-4 at 6.5 RPO, removing Patidar in over 6, Bethell in over 13, then Jitesh and David off back-to-back deliveries in over 16 to leave RCB at 131/6. Against that, Krunal's pull shot produced 20 runs at 77% control. He came in at 39/3 and was still there at 149/7, scoring 110 of the 110 runs added while he batted. The Krunal-Jitesh stand of 37 off 22 balls at 10.09 RPO was the partnership that kept RCB alive after Bosch's first burst.

The Over That Broke It

Over 3 in the MI innings. Bhuvi to Rohit, clean bowled. Next ball, SKY first ball duck. 28 for 3 in 18 balls on a surface where settling in was everything, and MI's entire top order was gone before the fourth over started. Tilak and Dhir rescued it but the damage set the ceiling at 166.

The Over That Closed It

Over 20, Bawa bowling, RCB needing 15. First ball, Bhuvi hit a six. That single shot off a number nine batter changed the equation from 15 off 6 to 9 off 5 and the crowd and the dressing room felt it instantly. RCB scrambled the rest off the final ball to seal it.

Player Ratings

#	Name	Team	Role	Label	Descriptor
1	Bhuvneshwar Kumar	RCB	Bowler	Match-Winner	4 wickets, match-sealing six
2	Krunal Pandya	RCB	Allrounder	Lone Fighter	Cramps, pressure, 73 off 46
3	Corbin Bosch	MI	Bowler	Disruptor	4 wickets, almost enough
4	Tilak Varma	MI	Batter	Anchor	57 off 42, 77% control
5	Naman Dhir	MI	Batter	Builder	47 off 32, rebuilt from 28/3
6	Jitesh Sharma	RCB	Keeper-Batter	Catalyst	37-run stand, shifted momentum

Trivia

• MI conceded 16 extras in the chase including 11 wides. Bawa bowled 5 of those wides across his 3 overs. In a match decided by 1 run off the final ball, the extra gap of 10 runs between the two sides is the difference.
• Bhuvi dismissed four MI batters across two separate spells: over 1, over 3 twice, over 18. His victims were Rickelton, Rohit, SKY and Tilak, three of MI's top four and their second-highest scorer.
• RCB's win officially eliminated both Mumbai Indians and Lucknow Super Giants from playoff contention. Both sides finish on 6 points with no mathematical path to the top four.

Simulation Verdict

Bhuvi won this match twice: once with the ball in the first innings and once with the bat in the final over.

Hot Take

• Bawa conceded 39 off 3 overs at 13.0 RPO including 5 wides and was then handed the final over with 15 needed. SKY backed him and said so publicly after the game. That is either loyalty or a selection blindspot; the numbers don't make a strong case for it.

"For me, motivation is overrated because it fades quickly, whereas discipline is what really keeps you going day after day." ~ Bhuvneshwar Kumar, Player of the Match

"Players like Krunal bring a lot of experience and that is why they perform in big games under pressure." ~ Rajat Patidar, RCB Captain

"It is a hard pill to swallow right now but we will come back stronger as a group going forward." ~ Suryakumar Yadav, MI Captain

Bawa conceded 39 off 3 overs and was given the final over anyway. Was that the wrong call from SKY or does he deserve more credit for nearly pulling it off?

Written with authoritative precision for r/CricketBriefing*.* Bhuvi Kumar hitting a six off Bawa at number nine with 15 needed off six balls is the image of this IPL 2026 season so far: the old guard doing the unexpected when it matters most.

This IPL 2026 post-match report covers RCB vs MI, Match 54, at Shaheed Veer Narayan Singh International Stadium, Raipur on 10 May 2026. Full phase analysis, bowling breakdown and partnership data for Royal Challengers Bengaluru's two-wicket win over Mumbai Indians. RCB move to the top of the table on 14 points with NRR 1.103 after Match 54, while MI and LSG are officially eliminated from playoff contention.

Both teams scored 90-plus in their powerplays. Both had a batter go absolutely berserk in the first six overs. The difference was Inglis made 84.6% of LSG's powerplay runs himself and then got out. Urvil Patel made 65 off 23 at 16.96 RPO and left CSK needing 111 off 84 with eight wickets standing. One powerplay built pressure. The other broke a 203-run chase open before the halfway point.

Match Pulse: Urvil Patel's 13-ball fifty in overs 5 and 6, 50 runs at 25.0 RPO across those two overs alone, turned a difficult 204-run chase into a run chase CSK were ahead of from over seven onwards.

Phase Dissection

Phase	LSG Runs/Wkts	LSG RPO	CSK Runs/Wkts	CSK RPO	Shift
Powerplay (1-6)	91/1	15.17	97/1	16.17	CSK marginally ahead, same wicket cost
Early Middle (7-11)	32/3	6.4	39/1	7.8	LSG collapsed here, CSK held shape
Late Middle (12-16)	36/2	7.2	33/2	6.6	Both teams grinding, roughly even
Death (17-end)	44/2	11.0	39/1	10.64	CSK finished it, four balls remaining
Chaos row	Overton: 3 wkts, 9.0 RPO across 4 overs	—	Markram: 14 runs in 2 balls	42.0 RPO	Last over nearly got interesting

The 59-run powerplay gap in the middle overs tells the story: LSG lost 3 wickets for 32 runs (6.4 RPO) right after Inglis fell, CSK lost just 1 for 39 (7.8 RPO) in the same phase.

Impact Match-Up

Overton and Noor Ahmad were the two bowlers who won this for CSK with the ball. Noor went 4-0-24-1 at 6.0 RPO on a surface where every other CSK bowler went above 9.0. Overton took 3 for 36 across 4 overs, including Inglis at 112/3 in over 9, and his spell between overs 8 and 15 produced ten dot balls in his first 18 deliveries per the AI context. With the bat, Urvil's on drive produced 18 runs at 71% control. The Gaikwad-Urvil stand of 81 off 34 balls at 14.29 RPO was the match compressed into one partnership.

The Over That Broke It

Overs 5 and 6 in the CSK chase. Avesh Khan conceded 25 in over 5, Rathi conceded 25 in over 6. Back to back 25-run overs, 50 runs off 12 balls at 25.0 RPO, and Urvil Patel hit six sixes across those two overs alone. At the end of over 6, CSK were 97/1 chasing 204. The match was effectively settled before the powerplay ended.

The Over That Closed It

Over 20, CSK needing 15 off the last over. Markram got the ball. Two wides, then two sixes from Dube and Veer. 14 runs off 4 legitimate balls, chase done with 4 balls remaining, and Markram's 42.0 RPO from his 2-ball over is the single most expensive figure of the match by any bowler. Pant called that one wrong.

Player Ratings

#	Name	Team	Role	Label	Descriptor
1	Jamie Overton	CSK	Bowler	Disruptor	3 wickets, match-turning
2	Urvil Patel	CSK	Batter	Destroyer	13-ball fifty, brutal
3	Noor Ahmad	CSK	Bowler	Strangler	6.0 RPO, metronomic
4	Josh Inglis	LSG	Keeper-Batter	Lone Enforcer	84.6% of PP runs, not enough
5	Shahbaz Ahmed	LSG	Allrounder	Resistance	43 late, 2 wickets
6	Shivam Dube	CSK	Batter	Finisher	Six off last over, clean

Trivia

• Inglis scored 77 of LSG's 91 powerplay runs, 84.6% of the total, the highest individual share of a team's powerplay by any batter in this match. Once he was dismissed at 112/3, LSG lost 3 wickets for 32 in the next five overs at 6.4 RPO. (Source: B. Scorecard / D. O2O)
• LSG used 6 DRS reviews in the CSK innings, 5 unsuccessful. Four of those came in overs 13 to 19 as they chased wickets desperately. They found one legitimate breakthrough but wasted resources on the others. (Source: D. O2O)
• Markram bowled just 2 balls in the final over and conceded 14 runs including 2 wides, a figure of 42.0 RPO. It is the most expensive bowling contribution of the match. (Source: B. Scorecard)

Simulation Verdict

Urvil's 50 overs 5 and 6 made this a 160-run chase from over 7 onwards; LSG never had the bowling to close that down.

Hot Take

• Pant threw the ball to Markram for the last over with 15 needed and it cost him the match in 4 balls. Shahbaz had already taken 2 wickets and was available. The data on left-handers he mentioned after the game is a fair point but Markram conceding 14 off 2 balls makes it a very hard call to defend.

"As long as I stick to my plans, the rest takes care of itself, and right now I am feeling good and I just want to keep improving." ~ Jamie Overton, Player of the Match

"Going forward, the focus is simple, stay calm, keep things uncomplicated and take it one game at a time with three matches still to play." ~ Ruturaj Gaikwad, CSK Captain

"In T20 cricket, fielding standards have to be very high and dropping too many catches made it difficult for us to stay on top." ~ Rishabh Pant, LSG Captain

Pant gave the last over to Markram instead of Shahbaz with 15 needed. Was that the moment LSG lost the match or had it already gone by over 6?

Written with authoritative precision for r/CricketBriefing*.* Urvil Patel hitting six sixes before over 7 on a surface that got harder to bat on as the match went on is the single image that defines this game.

This IPL 2026 post-match report covers CSK vs LSG, Match 53, at MA Chidambaram Stadium, Chennai on 10 May 2026. Full phase breakdown, bowling analysis, and partnership data for Chennai Super Kings' five-wicket win over Lucknow Super Giants. CSK move to 12 points after Match 53, level with RCB on points but with a lower NRR of 0.185.

England Women won 8 of 9 ODIs against New Zealand, every one chasing. New Zealand arrive as IWC leaders.

Match Intel: England Women vs New Zealand Women | Riverside Ground, Chester-le-Street | Sun, 10 May 2026 | 03:30 PM IST | 10:00 AM GMT | 11:00 AM Local | Format: ODI - 1st Match

Series Information and Team Standings

Team	M	W	L	PTS	NRR
New Zealand Women	6	5	1	10	+2.229
England Women	0	0	0	0	0.000

Weather

• Mostly cloudy; 0-14% rain risk
• Temperature 10-13°C; cool conditions favour early seam
• Full match expected

Market Volatility and Toss Index

Factor	Statistical Impact	Tactical Recommendation
H2H toss	Toss winner won 8/9 H2H meetings	Toss critical here
H2H chasing	ENG-W won 8 of 9 H2H, all 8 chasing	Bowl first
ENG-W at venue	0 wins batting first in 6 here	Bowl first
NZ-W at venue	2 of 3 wins batting first here	Bat first

Pitch and Ground

Square	Straight	Avg 1st Inn	Avg 2nd Inn	Bat first wins	Chase wins
64m	70m	113	111	3/5 (60%)	2/5 (40%)

• Green surface; cloud cover assists swing in the first 15 overs
• Chester-le-Street is among England's lowest-scoring venues; 113 average first innings
• Spinners dominate middle overs; seamers rule early
• Conflict: H2H says bowl first; venue says bat first — H2H recent trend wins out

Sophie Ecclestone vs Amelia Kerr

Ecclestone: 20 wickets, 3.92 economy. Kerr: 22 wickets, 4.64 economy, 435 runs. Both control middle overs. Whoever uses their spinner better wins it.

Predicted Playing XIs

Charlie Dean (c), Heather Knight, Amy Jones (wk), Maia Bouchier, Emma Lamb, Freya Kemp, Dani Gibson, Ecclestone, Lauren Bell, Lauren Filer, Linsey Smith

Amelia Kerr (c), Suzie Bates, Maddy Green, Georgia Plimmer, Brooke Halliday, Gaze (wk), Jess Kerr, Rosemary Mair, Molly Penfold, Bree Illing, Nensi Patel

All names verified against official squads.

Injury and Availability

Nat Sciver-Brunt: calf injury, out. Alice Capsey: illness, out for ODI leg. No other concerns.

Form and H2H

Team	Form (Oldest to Newest)	Reading
ENG-W	W L W W L	Mixed; World Cup semi-final loss to SA
NZ-W	W W L W W	Four wins from last five; strong form

England lead H2H 8-1; all 8 wins came chasing.

Phase by Phase: Where Matches Are Won

Phase	H2H 1st Inn RPO	H2H 2nd Inn RPO
0-15	4.20	4.60
16-30	4.47	4.53
31-40	4.10	3.40
41-50	3.40	1.20

The 1.20 RPO death figure reflects older matches; England's recent chasing wins all came with balls to spare.

Venue Scoring Patterns

• Venue avg 113 first innings, 111 second
• Batting first won 3 of last 5 here
• NZ-W's 2 wins here: batting first. England's 2 wins: chasing.

Win Probability

England Women 58%, New Zealand Women 42%; H2H dominance and home conditions tip it.

Hot Take

Maddy Green scores a match-defining fifty; 77.17 average makes her the most dangerous batter on the pitch.

Trivia Nuggets

• England won 8 of 9 H2H ODIs vs New Zealand; all 8 while chasing
• Toss winner won 8 of 9 H2H meetings; tonight's toss matters

Community Challenge

England won every recent H2H ODI by chasing: does New Zealand finally defend tonight?

Written with authoritative precision for r/CricketBriefing. Always verify local toss updates and radar before the first ball.

This ICC Women's Championship 2026 match preview covers H2H chasing dominance, phase analysis, and win probability for England Women vs New Zealand Women at Riverside Ground, Chester-le-Street.

The ENG-W vs NZ-W 1st ODI preview includes toss impact data, venue scoring patterns, and key player matchups including the Ecclestone vs Amelia Kerr middle-overs battle.

Riverside Ground, Chester-le-Street averages just 113 in the first innings across recent ODIs, making it one of the most bowler-friendly venues in England's home schedule.

Pakistan Women won the series; 374-run aggregate margin. Tonight: clean sweep.

Match Intel: Pakistan Women vs Zimbabwe Women | National Stadium, Karachi | Sat, 09 May 2026 | 04:00 PM IST | 10:30 AM GMT | 03:30 PM Local | Format: ODI - 3rd Match

Series Information and Team Standings

Team	M	W	L	PTS	NRR
Pakistan Women	5	3	2	6	+1.826
Zimbabwe Women	5	0	5	0	-3.926

Weather

• Clear skies; zero rain risk
• Temperature 31-33°C first innings, 29-30°C second
• Humidity 55-70%; slight dew possible late in second innings

Market Volatility and Toss Index

Factor	Statistical Impact	Tactical Recommendation
H2H batting first	Every H2H ODI won by batting side (3/3)	Bat first
H2H at venue	Both Karachi meetings won by Pakistan batting	Pattern set
Venue	Batting first won 6/10 here	Reinforces bat-first approach
Pakistan recent wins	Both series wins came batting first (330, 343)	Bat first confirmed

Pitch and Ground

Square	Straight	Avg 1st Inn	Avg 2nd Inn	Bat first wins	Chase wins
62m	70m	242	165	6/10 (60%)	4/10 (40%)

• Hard, flat surface; excellent early batting, scores here are high
• Spinners effective from overs 25 onward as surface dries
• Square 62m is Target Zone; straight 70m needs real power
• Pakistan's death-over batting here: 10.30 RPO; Zimbabwe's chasing death average: 1.50 RPO

Sadaf Shamas vs Zimbabwe's New-Ball Pair

Shamas: 362 runs, 60.33 average, century in ODI 2. Mabhero: Zimbabwe's best at 3.93 economy. If Shamas and Amin build again, Zimbabwe have no answer.

Predicted Playing XIs

Sadaf Shamas, Sidra Amin, Gull Feroza, Najiha Alvi, Aliya Riaz, Natalia Pervaiz, Aroob Shah, Fatima Sana (c), Nashra Sandhu, Diana Baig, Tasmia Rubab

Kelis Ndhlovu, Beloved Biza, Kelly Ndiraya, Natasha Mtomba, Pasipanodya, Christine Mutasa, Michelle Mavunga, Nomvelo Sibanda (c), Precious Marange, Mabhero, Adel Zimunu

All names verified against official squads.

Injury and Availability

No injury concerns for either squad.

Form and H2H

Team	Form (Oldest to Newest)	Reading
PAK-W	L L W W W	Three straight wins; dominant in this series
ZIM-W	L L L L L	Five straight losses; no answers found

Pakistan Women lead H2H 3-0; all wins by 100-plus.

Phase by Phase: Where Matches Are Won

Phase	H2H at Venue 1st Inn RPO	H2H at Venue 2nd Inn RPO
0-15	5.87	4.20
16-30	5.93	3.27
31-40	4.90	3.30
41-50	10.30	N/A

Zimbabwe bowled out before over 40 both times; 41-50 is blank — they never got there.

Venue Scoring Patterns

• Venue avg 242 first innings, 165 second; 77-run batting-first advantage
• Pakistan scored 330 and 343 in the two previous matches here
• Zimbabwe bowled out before over 40 both times; never reached 50

Win Probability

Pakistan Women 90%, Zimbabwe Women 10%.

Hot Take

Zimbabwe need early powerplay wickets; they have taken zero in 100 overs of Pakistan batting this series.

Trivia Nuggets

• Pakistan Women won all three H2H ODIs: by 168, 206, and 114 runs; aggregate 488 runs
• Zimbabwe bowled out before over 40 in both Karachi matches

Community Challenge

Pakistan scored 330 then 343 in this series: does Zimbabwe restrict them below 300 tonight or is another massive total coming?

Written with authoritative precision for r/CricketBriefing. Always verify local toss updates and radar before the first ball.

This ICC Women's Championship 2026 match preview covers phase analysis, death-over data, and win probability for Pakistan Women vs Zimbabwe Women at National Stadium, Karachi.

The PAK-W vs ZIM-W 3rd ODI preview includes H2H phase averages, venue scoring patterns, and series context as Pakistan chase a clean sweep in the final ODI.

National Stadium Karachi's 62m square boundaries and high-scoring surface have produced 330 and 343 in this series; Zimbabwe have been bowled out in both matches before reaching over 40.

Bangladesh vs Pakistan | Pakistan tour of Bangladesh | Test - 1st Test, Day 2

Pakistan chose to field at Mirpur, where batting first wins every BAN vs PAK Test. Bangladesh 301/4 overnight; Shanto's century said it all.

Match Intel: Bangladesh vs Pakistan | Shere Bangla National Stadium, Mirpur | Sat, 09 May 2026 | 09:30 AM IST | 04:00 AM GMT | 10:00 AM Local | Format: Test - 1st Test, Day 2

Series Information and Team Standings

Team	M	W	L	D	N/R	PTS	PCT
Pakistan	2	1	1	0	0	12	50.00
Bangladesh	2	0	1	1	0	4	16.67

Weather

Day 2 — Sat 09 May: 0% rain, full play strongly favoured. Morning 33-35°C, afternoon 37°C. Extreme heat only.

Day 3 — Sun 10 May: Morning dry. Thunderstorms ~50% after tea; short interruptions possible.

Day 4 — Mon 11 May: Highest risk. Morning ~60%, afternoon ~75% thunderstorm chance; overs likely lost.

Day 5 — Tue 12 May: Mainly dry. Isolated showers ~25%; on-time start favoured.

🟡 Reserve Day Notice: No reserve day.

Market Volatility and Toss Index

Factor	Statistical Impact	Tactical Implication
BAN vs PAK at Mirpur	Batting side won all 3 here	Field-first is high-risk
H2H chasing	Pakistan 0 wins chasing in 10 H2H Tests	No template without batting first
Venue batting first	6 of 10 wins batting first here	Historical weight firmly against the call
Toss winner H2H	Toss winner won 7/10 H2H Tests	Pakistan won; now prove it

Pitch and Ground

Square	Straight	Pitch Type	Spin from	Forecast Day 5
64m	69m	Red-soil, slow	Day 3	Mainly dry

• Surface starts decent for batting, flattens under heat
• Mehidy and Taijul take over Day 3 as turn increases
• Pakistan's pacers face a long second-innings bowl on a dead pitch
• Babar Azam ruled out; Pakistan's batting depth hit hard

The Toss Gamble: Pakistan's Only Path

Shaheen took 1/67 Day 1. Bangladesh 301/4; Mushfiqur and Litton still to come. The collapse Pakistan needed did not arrive. Pakistan must dismiss the tail and lead before spin arrives. First session is critical.

Playing XIs

Bangladesh: Mahmudul Joy, Shadman Islam, Mominul Haque, Shanto (c), Mushfiqur Rahim, Litton Das (wk), Mehidy Hasan Miraz, Taijul Islam, Taskin Ahmed, Nahid Rana, Ebadot Hossain

Pakistan: Imam-ul-Haq, Azan Awais, Abdullah Fazal, Shan Masood (c), Saud Shakeel, Rizwan (wk), Salman Agha, Shaheen Afridi, Noman Ali, Hasan Ali, Mohammad Abbas

All names verified against official squads.

Injury and Availability

Babar Azam (Pakistan): left knee injury, out. No other concerns.

Form and H2H

Team	Form (Oldest to Newest)	Reading
BAN	L D W L W	Won both 2024 Tests vs Pakistan in Rawalpindi
PAK	W L W L L	Alternating wins and losses; lost last Test vs SA

Pakistan lead H2H 7-2 last 10; Bangladesh won both 2024 Tests.

Venue Scoring Patterns

• Batting first won 6 of last 10 here; first innings is critical
• Bangladesh home wins here: 217 runs, 546 runs, an innings
• Pakistan won all three previous Tests here batting first

Win Probability

Bangladesh 62%, Pakistan 38%; 301/4 overnight and Day 3 spin tips it heavily.

Hot Take

Pakistan need 350-plus; possible but requires perfection from a side missing Babar.

Trivia Nuggets

• Pakistan: zero wins chasing across 10 H2H Tests against Bangladesh
• Every BAN vs PAK Test at Mirpur won by the batting side; Pakistan fielded

Community Challenge

Pakistan fielded despite every BAN vs PAK Test at Mirpur being won by the batting side: bold gamble or mistake?

Written with authoritative precision for r/CricketBriefing. Always verify local toss updates and radar before the first ball.

This 1st Test preview covers toss analysis, day-by-day weather risk, and win probability for Bangladesh vs Pakistan at Shere Bangla National Stadium, Mirpur.

The BAN vs PAK 1st Test 2026 match analysis includes H2H chasing records, venue batting-first patterns, and pitch progression forecasts for all five days.

Shere Bangla National Stadium's red-soil surface and spin-friendly conditions from Day 3 onward make first-innings batting runs worth more here than almost any other Test venue in Asia.

Mitchell Marsh hit 111 off 56 balls at 11.89 RPO on a surface RCB should have dominated with the ball. They dropped him twice. They dropped Pant. They dropped Pooran. Four catches grassed in one innings and LSG waltzed to 209. RCB then got to 203 in reply and still lost by 6 runs. That is a very specific kind of painful.

Match Pulse: Prince Yadav's double-strike in over 11, removing Padikkal and Jitesh off consecutive balls, turned a chase RCB were running at 10.40 RPO into sudden, desperate scramble.

Phase Diagnostic

Phase	LSG Runs/Wkts	LSG RPO	RCB Runs/Wkts	RCB RPO	Who Owned It
Powerplay (1-6)	68/0	11.33	45/2	7.94	LSG, not even close
Early Mid (7-11)	41/1	8.2	67/2	10.86	RCB clawed back
Late Mid (12-16)	56/0	11.2	59/2	11.8	Roughly even, but RCB losing wickets
Death (17-19)	44/2	14.67	37/0	12.33	LSG pulled away late
Chaos moment	4 drops in LSG innings	—	104/2 to 112/5 in 13 balls	—	Both teams made this messy

Prince Yadav's 3 wickets at 8.25 RPO across 4 overs is the single number that explains why 209 held.

Impact Match-Up

Prince Yadav and Shahbaz Ahmed finished with 5 wickets between them at a combined cost of 66 runs across 7 overs. Prince's 8.25 RPO in a 200-plus chase is genuinely tight bowling. He went back to back at over 11, slower ball to dismiss Padikkal (104/3), then sharp bouncer for Jitesh (106/4), and suddenly a chase that felt very much alive was at 112/5 two overs later. On the batting side, Marsh's off drive produced 22 runs at 75% control. He was reading the surface better than any RCB bowler managed all night, and the Marsh-Pooran stand of 70 off 41 balls at 10.24 RPO in the middle overs is what pushed LSG past 200.

The Over That Broke It

Over 11 in the chase is the match in six balls. Prince Yadav came back, Padikkal gone for 34, Jitesh gone for 1, and RCB went from cruising at 104/2 to suddenly 106/4 with Patidar also falling at 112/5 in the next two overs. Three wickets in 13 balls on a flat pitch. The game turned completely in that passage.

The Over That Closed It

Last over, 10 needed, Rathi bowling. Pant backed him against Shepherd and Krunal. Rathi conceded just 10 off the final over, one boundary, and LSG held on by 6 runs after nearly letting it slip from 209. The trust in a young spinner at the death on a batting surface is the kind of captaincy call that looks brilliant only when it works.

Player Ratings

#	Name	Team	Role	Label	Descriptor
1	Mitchell Marsh	LSG	Allrounder	Destroyer	Brutal, clean, unstoppable
2	Prince Yadav	LSG	Bowler	Disruptor	Three wickets, match-turning
3	Rishabh Pant	LSG	Keeper-Batter	Finisher	19.2 RPO, 10 balls
4	Rajat Patidar	RCB	Batter	Lone Fighter	61 off 31, not enough
5	Tim David	RCB	Batter	Enforcer	Too late, too little
6	Shahbaz Ahmed	LSG	Bowler	Support Act	Two key wickets quietly

Trivia

• RCB dropped four catches in LSG's innings, overs 2.3, 15.5, 16.5 and 17.4, all off different fielders. Marsh was dropped twice directly and went on to score 111. (Source: D. O2O)
• Kohli and Bethell were both dismissed inside the first two overs for a combined 4 runs off 7 balls, the joint-second-lowest opening partnership of IPL 2026. (Source: B. Scorecard / C. Stats)
• Pant's 32 off 10 balls at 19.2 RPO is the highest RPO innings of this match by any batter from either side. (Source: B. Scorecard)

Simulation Verdict

LSG won this with Marsh's bat and Prince's arm; RCB lost it with four drops and one catastrophic over.

Hot Take

• Rathi going for 50 off 4 overs at 12.5 RPO in the chase and then being trusted with the final over tells you everything about how Pant reads match-ups. Most captains don't make that call. It worked. But if Shepherd hits one more boundary in that last over nobody is calling it genius.

"There is still a lot to play for and we want to finish strong." ~ Mitchell Marsh, Player of the Match

"This felt like one of those games where both our batting and bowling clicked together which is exactly what we have been aiming for." ~ Rishabh Pant, LSG Captain

"With four games still to go, the focus is on taking it one step at a time and improving where needed." ~ Rajat Patidar, RCB Captain

Four dropped catches, a six-run loss for RCB. Which drop hurt the most and does this cost them a top-two finish?

Written with authoritative precision for r/CricketBriefing*.* Marsh getting dropped at 15.5 by Padikkal, already past his century, with 30 off the last three overs still to come, is the single image that defines this match.

This IPL 2026 post-match report covers LSG vs RCB, Match 50 at Ekana Stadium, Lucknow on 07 May 2026. Full phase analysis, bowling breakdown, and partnership data for Lucknow Super Giants' six-run win over Royal Challengers Bengaluru. LSG move to 6 points, RCB stay on 12 but their NRR drops to 1.234 after Match 50.

Delhi's 155 looked competitive at halfway. It wasn't. CSK's spinners strangled the first innings on a slow surface, then Sanju Samson ran a clinic in the second, finishing 87* off 52 balls at 10.04 RPO as CSK chased it down with 15 balls to spare.

Match Pulse: Noor Ahmad's double-strike through overs 8 and 10 cut Delhi from 45/2 to 62/4, killing any chance of a defendable total.

Phase Diagnostic

Phase	DC Output	CSK Output	Ball Control	Verdict
Powerplay (1-6)	37/2 · 6.17 RPO	44/1 · 7.33 RPO	DC 38% dots	CSK started cleaner
Middle (7-15)	72/3 · 8.0 RPO	94/1 · 8.55 RPO	CSK ran it away here	DC never recovered from 62/4
Death (16-20)	46/2 · 9.2 RPO	21/0 · 7.0 RPO	DC scraped late	CSK didn't need to accelerate
Chaos over	Over 11: DC 69/5	—	Dropped catch kept Stubbs alive	Could've been 60/6

The 114-run unbeaten Samson-Kartik stand at 10.36 RPO made the death overs irrelevant before they started.

Impact Match-Up

Akeal Hosein (4-0-19-1, 4.75 RPO) and Noor Ahmad (3-0-22-2, 7.33 RPO) turned the first innings into a dot-ball grind through the powerplay and middle overs. Delhi managed just 6.17 RPO in the first six, with two early wickets stranding the middle order before it settled. In the chase, Samson's off drive was the productive weapon: 23 runs through that channel against both pace and spin, at 74% control. The Samson-Kartik partnership of 114* off 66 balls at 10.36 RPO was the match decided in one passage of play.

The Over That Broke It

Over 10 told the story of Delhi's innings. Noor Ahmad had already removed Karun Nair in over 8. Now he came back and got Nitish Rana, leaving DC at 62/4 with the innings at 10.04 overs. From 29/1 after four overs, Delhi lost four wickets for 33 runs across seven overs; the game was gone before the powerplay spinners had finished their quota.

The Over That Closed It

Over 15 in the chase. Natarajan conceded 20 runs, including two sixes from Samson, pushing CSK to 126/2 with the required rate already below four. Samson went from 46 to 66 in that single over; Kartik was 23 not out and growing; nothing Delhi had left could stop it.

Player Ratings

#	Name	Team	Role	Label	Descriptor
1	Sanju Samson	CSK	Keeper-Batter	Architect	Calm, clinical, unstoppable
2	Akeal Hosein	CSK	Bowler	Strangler	Tight, dry, miserly
3	Kartik Sharma	CSK	Batter	Anchor	Steady, unflappable, 78% control
4	Sameer Rizvi	DC	Batter	Lone Fighter	Late, brave, too late
5	Noor Ahmad	CSK	Bowler	Disruptor	Two wickets, match-turning
6	Tristan Stubbs	DC	Batter	Resistance	Survived drop, top-scored

Trivia

• Natarajan conceded 39 runs off 2.3 overs at 15.6 RPO, the worst economy figure by any bowler in this match by a margin of over 3 RPO. (Source: C. Stats)
• Delhi lost five wickets between overs 4 and 11, scoring just 40 runs across that stretch at 5.0 RPO. (Source: B. Scorecard / D. O2O)
• Hosein's 4-0-19-1 is the most economical four-over spell of the match, 2.5 RPO below the next best CSK bowler. (Source: C. Stats)

Simulation Verdict

CSK's bowling unit removed the contest by over 11; the batting unit was just collecting the paperwork.

Hot Take

• Delhi's impact sub Sameer Rizvi (40 off 24, 10.0 RPO) outscored every DC batter who started the innings. The XI that took the field didn't bat as well as the player brought on to fix it.

"A hundred is always special but winning the game brings more happiness and confidence, and with a few matches still to come, we will see if it happens." ~ Sanju Samson

"On the batting side we are very grateful to have Sanju after the World Cup he had, he is a backbone for us, but more often it is the bowlers who win you games." ~ Ruturaj Gaikwad

"From here, there is no margin for error and we know we have to win all our remaining five matches to stay alive." ~ Axar Patel

After CSK win Match 48, where do they finish in the playoffs: top two or squeezed out at the bubble?

Written with authoritative precision for r/CricketBriefing*.* Samson's off drive through the covers off Kuldeep in over 12, three sixes in the same over, was the moment Delhi's dressing room stopped believing.

This IPL 2026 post-match report covers DC vs CSK, Match 48, at Arun Jaitley Stadium, Delhi on 05 May 2026. Full phase analysis, player ratings, and partnership data for Chennai Super Kings' eight-wicket win over Delhi Capitals. CSK move to 10 points after Match 48, Delhi remain on 8 with five games left and no margin remaining.

Mumbai chased 229 in 18.4 overs, six wickets down, eight balls to spare. Rickelton (83 off 32, 15.56 RPO) and Rohit (84 off 44, 11.45 RPO) opened with 143 in 65 balls. LSG posted 90 in six overs, looked set for 250, then scored 36 in their last four. Bosch took both wickets that killed the innings. Death overs decided this match: 9.00 RPO for LSG, 14.62 RPO for MI.

Match Pulse: Bosch's over 9 removed Pooran and Marsh in four deliveries, collapsing LSG from 123/1 to 125/3 and cutting the final total by 15 runs.

Phase Breakdown

Overs	LSG runs/wkts	LSG RPO	MI runs/wkts	MI RPO	Edge
1-6	90/1	15.00	71/0	11.83	LSG launched, MI absorbed
7-16	102/4	10.20	119/3	11.90	MI flipped every number
17-20 / 17-18.4	36/0	9.00	39/1	14.62	Match decided here

LSG's death-over RPO was 9.00. MI's was 14.62. One over, two very different campaigns.

Impact Match-Up

Bosch's two overs cost 20 runs and took 2 wickets at 10.00 RPO: Pooran caught for 63, Marsh for 44, both in over 9. In the chase, Rohit's flick produced 25 runs at 70% control, Rickelton's flick 21 runs at 66%. Average control across the 143-run stand: 68%. That control figure at 13.20 RPO is not luck, it is selection and execution.

The Over That Broke It & The Over That Closed It

LSG were 123/1 after eight overs. Another 130 felt possible.

Over 9, Bosch: two wickets, four runs. LSG's innings never recovered.

Siddharth's ninth over in the chase went for 23 runs, three sixes, one four.

82 off 66 balls with all ten wickets standing. Chase was done there.

Player Ratings

#	Name	Team	Role	Label	Descriptor
1	Ryan Rickelton	MI	Keeper-Batter	Destroyer	Fast, precise, relentless
2	Rohit Sharma	MI	Batter	Anchor-Enforcer	Controlled then ruthless
3	Corbin Bosch	MI	Allrounder	Executioner	Two wickets, twenty runs
4	Nicholas Pooran	LSG	Batter	Lone Cannon	18.00 RPO, no support
5	Himmat Singh	LSG	Batter	Lone Fighter	40 off 31, steadied the wreckage
6	Manimaran Siddharth	LSG	Bowler	Wicket-Taker	2 wickets, costly finish

Trivia

• Mumbai's 229/4 in 18.4 overs is the highest successful chase at Wankhede.
• Pooran's 63 off 21 (18.00 RPO) is the fastest fifty by a number-three batter in IPL 2026, reaching 50 in 16 balls.
• LSG have lost seven of nine this season, NRR at -1.076.

Simulation Verdict

MI's opening stand delivered 31 runs above par across 65 balls; the chase was done before the middle overs started.

Hot Take

• LSG have posted 190-plus three times this season and lost all three. Pooran is not the problem. Thirty-six runs in the last four overs is.

"With the class and depth in this team, my role becomes very clear and it helps me play with freedom." -- Ryan Rickelton, Player of the Match

"They were always in control once they got that solid start, and credit to them for the way they executed with the ball." -- Suryakumar Yadav, MI Captain

"We were probably short by ten to fifteen runs on what felt like a two hundred and twenty to two hundred and thirty wicket." -- Rishabh Pant, LSG Captain

LSG have lost seven of nine. Rohit is back and Rickelton is at 15.56 RPO at Wankhede. Is a Mumbai playoff push still mathematically alive?

Written with authoritative precision for r/CricketBriefing*.* Rickelton and Rohit made 229 look like a net session, and LSG's death-overs template told the same story it has told all season.

Full IPL 2026 post-match report covering MI vs LSG Match 47 at Wankhede, including Rickelton's 83 off 32, Rohit's 84 off 44, Pooran's 63 off 21 and Bosch's 2/20. Searching for MI vs LSG scorecard, Ryan Rickelton IPL 2026, Wankhede highest chase IPL 2026 or Lucknow Super Giants season review, this is your complete breakdown. MI move to 6 points, NRR -0.649; LSG stay on 4 points, NRR -1.076, seven losses from nine in IPL 2026.

MI posted 159 on a slow Chepauk surface, 20-30 runs short by Hardik's own admission. CSK chased it in 18.1 overs with eight wickets to spare. Gaikwad anchored with 67 not out off 48, Kartik Sharma made a maiden IPL fifty of 54 not out off 40, their unbroken 98-run stand closing the game out without alarm. Kamboj took 3/32, Noor 2/26. Four dropped catches by MI across the match. CSK move to 8 points and sixth. MI fall to seventh on 4 points with seven losses from nine.

Match Pulse: MI's middle overs produced only 67 runs for 3 wickets between overs 7 and 16, allowing CSK to contain the total to 159 and chase it comfortably on a surface that rewarded patience.

Phase Diagnostic

Overs	MI runs/wkts	CSK runs/wkts	What it meant
1-6	57/1	62/2	CSK scored 5 more in powerplay, MI lost one fewer wicket
7-12	43/2	45/0	CSK's middle phase dominant, MI leaked wickets
13-16	24/1	30/0	CSK stayed ahead of required rate throughout
17-20	35/3	23/0	MI's death surge came too late, CSK strolled home

MI's dot ball rate was 44% against CSK's 31%. MI hit more sixes (10 vs 7) but CSK hit more fours (13 vs 10). CSK rotated strike and found gaps; MI hit boundaries but blocked between them.

Impact Match-Up

Kamboj and Noor vs MI's middle and lower order: Kamboj took 3/32 at 8.00 ECO including Rickelton and two in the death. Noor took 2/26 at 6.50 ECO, removing the dangerous Rickelton first and Tilak later. Together they conceded 58 runs and took 5 wickets across 8 overs. Dube dropped Dhir twice and Tilak once off their bowling, which cost MI dearly in their final total.

Gaikwad's flick brought 23 runs, control 88%, the highest control figure for any batter in the match. His 98-run unbroken stand with Kartik off 75 balls was built on rotation and smart targeting of Boult and Ghazanfar, not slogging. Dhir's 57 off 37 was MI's only innings of quality, his flick bringing 21 runs, control 65%, the lower control reflecting how difficult the pitch was.

The Over That Broke It & The Over That Closed It

Over 7: Noor removed Rickelton for 37 just after the powerplay. MI were 63 for 2 with Dhir and Suryakumar together but the momentum Rickelton had built was gone, and the pitch began to grip more as the innings progressed. From overs 7 to 16, MI scored 67 runs and lost 3 wickets, a scoring rate of 6.70 RPO when they needed 9-plus.

Over 17: Ghazanfar's over went for 14 runs including a Gaikwad six and two fours. CSK needed 8 off 12, game done. Gaikwad finished it with a four off Boult first ball of over 19. Kartik's maiden fifty came in the same over and CSK won with 11 balls to spare.

Player Ratings

#	Name	Team	Role	Label	Descriptor
1	Ruturaj Gaikwad	CSK	Batter	Anchor	67* off 48, 88% control, win sealed
2	Kartik Sharma	CSK	Batter	Breakthrough Knock	54* off 40, maiden IPL fifty
3	Anshul Kamboj	CSK	Bowler	Death Specialist	3/32, smart and reliable
4	Noor Ahmad	CSK	Bowler	Enforcer	2/26, applied pressure at right time
5	Naman Dhir	MI	Batter	Lone Fighter	57 off 37, only one who competed
6	Hardik Pandya	MI	Batter	Poor Return	18 off 23, pitch got the better of him

Trivia

1. MI have now lost seven of nine games this season, their worst ever IPL campaign at this stage of a tournament*.*
2. CSK have won the El Clasico double over MI this season, winning both meetings in 2026*.*
3. Gaikwad's 67 not out is his second consecutive fifty, both coming in successful CSK chases this season*.*

Simulation Verdict: MI's 44% dot ball rate and middle-over scoring rate of 6.70 RPO left a total 20-30 runs short on a pitch where CSK's patience and rotation made 160 look comfortable from over 10 onwards.

Hot Take: Dube dropped Dhir twice and Tilak once in the same innings. Those three drops alone cost MI at least 20 runs and potentially two extra wickets. MI's fielding has been a persistent problem all season and it is now a significant factor in why they are seventh on the table.

Ruturaj Gaikwad: "The plan while chasing was simple: get a good start and then ensure one batter bats deep till the end. Personally, it felt good to bat till the end, and even though T20 cricket can be cruel at times, the support from my family, teammates and management gave me confidence to see it through."

Hardik Pandya: "It was not just about tonight; it has been the season where we have fallen short because Chennai played better than us in all three departments. With the bat, we were eyeing something around one eighty or one ninety at one stage, but after the first ten overs, we lost momentum and could not get the finish we wanted."

CSK have won three of their last four. MI have lost seven of nine. Is MI's IPL 2026 season mathematically over or can they still make a miraculous run?

Written with authoritative precision for r/CricketBriefing*.* Gaikwad batted through to 67 not out and Kartik made a maiden fifty as CSK chased 160 with 11 balls to spare: CSK complete the El Clasico double over MI this season and move to 8 points while Mumbai's playoff hopes are almost entirely gone.

Full IPL 2026 match report covering CSK vs MI Match 44 at Chepauk, including Gaikwad's 67 not out, Kartik's 54 not out, Kamboj's 3/32 and CSK's eight-wicket win. Searching for CSK vs MI scorecard, Ruturaj Gaikwad IPL 2026 form, Mumbai Indians season review 2026 or Chennai Super Kings points table climb, this is your complete breakdown. CSK move to 8 points and sixth place while MI sit seventh on 4 points with just three games remaining in IPL 2026.

RR posted 225 after being 12 for 2 inside two overs. Parag's 90 off 50 and Ferreira's 47 off 14 rebuilt and exploded the innings. DC chased it in 19.1 overs with seven wickets to spare. Nissanka hit 62 off 33 in a powerplay-defining 110-run opening stand with Rahul. Starc took 3 wickets on his comeback. Parag picked up a hamstring issue during RR's innings. DC move to 8 points. RR stay on 12 but their Jaipur record defending high totals continues to concern.

Match Pulse: DC's powerplay of 70 for 0 against RR's 56 for 2 set the entire tone; DC were never behind in the chase from ball one.

Phase Diagnostic

Overs	RR runs/wkts	DC runs/wkts	What it meant
1-6	56/2	70/0	DC hit 14 more with no wickets lost, chase ahead from ball one
7-12	60/1	68/1	Both teams built, DC's required rate never climbed
13-16	46/2	46/2	RR surged late, DC lost Nissanka and Rahul but never panicked
17-20	63/1	42/0	Ferreira blitz gave RR 225, Stubbs-Sharma finished DC's chase cleanly

Both teams had identical dot ball rates of 28% and 27%. Both hit similar boundary counts. The difference was entirely in the powerplay: DC's 70 for 0 versus RR's 56 for 2 made 226 feel like 190.

Impact Match-Up

Nissanka and Rahul vs RR's powerplay bowling: 110 together off 57 balls, DC's highest opening stand of IPL 2026. Nissanka hit 52 in the powerplay alone. Rahul's cover drive brought 13 runs, control 83%, and his acceleration in the middle overs kept the required rate firmly below 10. After Nissanka fell in over 9, Rana hit 33 off 17 including two sixes off Bishnoi in over 9. Stubbs and Sharma finished without alarm.

Parag's flick brought 20 runs, control 78%, and his 102-run stand with Jurel off 59 balls was RR's recovery phase done properly. Ferreira's 47 off 14 with six sixes in the final three overs was breathtaking but Axar dropped him on the final ball of over 19, costing RR at least 8-10 runs at the death.

The Over That Broke It & The Over That Closed It

Overs 1-2: Starc got Jaiswal first over, Jamieson got Sooryavanshi second over. RR were 12 for 2 before Parag had faced a single ball. DC's bowlers created the pressure that their batters then capitalised on fully. The conditions were seaming but DC's batters never faced them at their toughest.

Over 16: Archer dismissed Rahul for 75. DC were 184 for 3 needing 42 off 24 with Stubbs and Sharma incoming. Both handled it calmly, the 49-run unbeaten stand off 24 balls never looking like it would slip, DC crossing the line with four balls remaining.

Player Ratings

#	Name	Team	Role	Label	Descriptor
1	KL Rahul	DC	Keeper-Batter	Chase Anchor	75 off 40, controlled from first to last
2	Pathum Nissanka	DC	Batter	Powerplay Weapon	62 off 33, 52 in powerplay alone
3	Riyan Parag	RR	Batter	Captain's Knock	90 off 50, rebuilt from 12 for 2
4	Donovan Ferreira	RR	Batter	Late Blitz	47 off 14, six sixes, too late
5	Mitchell Starc	DC	Bowler	Comeback Performance	3/40, first game back, set the tone
6	Nitish Rana	DC	Batter	Bridge	33 off 17, kept required rate down after Nissanka fell

Trivia

1. DC's 226 for 3 is their highest successful chase of IPL 2026*.*
2. Ferreira's 47 off 14 balls includes six sixes, the most sixes in a single innings by any RR batter in IPL 2026.
3. RR have now lost four of their last five matches after starting the season with four straight wins*.*

Simulation Verdict: DC's 70-run powerplay without a wicket removed all scoreboard pressure before the chase had started; even when Rahul and Rana fell in quick succession, the required rate never crossed a threatening threshold.

Hot Take: Axar dropped Ferreira on the final ball of over 19 when RR needed every run. Ferreira was on 31 at that point and hit 16 off the final four balls as a result. Drop catches continue to cost DC and RR in equal measure this season.

KL Rahul: "We play this game to win, and after being around for so many years, the results and points matter more than personal numbers. Batting with Nissanka was about reminding each other to play proper cricket shots and stay composed. Strike rate was spoken about for a long time, and I am happy that I have worked on it because modern T20 cricket demands that evolution."

Axar Patel: "You have to turn up every single day and give your best and I am really happy with the way the boys performed with both bat and ball. I want to especially mention Starc because after three months away he came back and delivered a performance that shows why he is considered a legend."

Riyan Parag: "I felt the score was competitive and around two hundred was par on this surface. The call not to promote Ferreira was based on a left-right match-up. Hopefully, the hamstring issue is not serious, and with a week's break, it should settle down."

RR have lost four of their last five. Parag has a hamstring concern with the playoffs approaching. Is this a blip or is RR's form at exactly the wrong time?

Written with authoritative precision for r/CricketBriefing*.* Nissanka's 62 off 33 and Rahul's 75 off 40 built a 110-run opening stand that made 226 look like a training target: DC move to 8 points while RR's four losses in five games is a worrying pattern heading into the playoff race.

Full IPL 2026 match report covering RR vs DC Match 43 at Jaipur, including Parag's 90 off 50, Ferreira's 47 off 14, Nissanka's powerplay blitz and DC's seven-wicket win. Searching for RR vs DC scorecard, KL Rahul IPL 2026 form, Rajasthan Royals losing streak 2026 or Delhi Capitals points table climb, this is your complete breakdown. RR remain on 12 points but their form slump and Parag's hamstring raise serious questions about their readiness for the knockout stages of IPL 2026.

Jason Holder was everywhere. Two wickets with the ball, three catches, involved in five of RCB's ten dismissals. RCB were 59 for 2 at the powerplay in a decent position. Then they lost six wickets for 37 runs between overs 7 and 11 and never recovered, bowled out for 155. Gill hit 43 off 18 in the GT powerplay before Kohli caught him at short cover. GT wobbled to 111 for 5 in the middle overs but Tewatia and Holder steadied the ship. Rashid finished it with a six. GT win by four wickets with 25 balls to spare. RCB drop to third on 12 points. GT climb to fifth on 10.

Match Pulse: RCB lost six wickets for 37 runs between overs 7 and 11, turning a decent powerplay position into a below-par total that GT chased comfortably.

Phase Diagnostic

Overs	RCB runs/wkts	GT runs/wkts	What it meant
1-6	59/2	69/2	GT hit 10 more in powerplay, both lost two wickets
7-11	38/6	42/3	RCB's catastrophic collapse, GT steadied after losing Gill and Buttler
12-16	58/2	47/1	RCB lower order fought, Tewatia-Holder closed chase out
17-20	—	—	GT won in 15.5 overs

RCB's dot ball rate was 48% against GT's 35%. RCB's collapse from 59 for 2 to 96 for 6 across five overs was the entire match. Outside of that phase both teams batted reasonably.

Impact Match-Up

Jason Holder vs RCB's middle order: 2 wickets with the ball, 3 catches in the field, involved in five dismissals. Got Patidar and then Shepherd with the ball, caught Padikkal off Rashid, caught David off Rashid, caught Pandya off Arshad. Rashid's 2/19 at 4.75 ECO and Arshad's 3/22 at 6.60 complemented Holder's fielding brilliance perfectly.

Gill's powerplay assault was decisive for GT. He hit Hazlewood for three fours and two sixes in a single over, his 43 off 18 the most he has scored in an IPL powerplay. Padikkal's pull brought 12 runs, control 79%, and his 40 off 24 was RCB's best innings but it came with too little support. Bhuvi was GT's best bowler in the chase: 3/28 at 7.00, getting Sudharsan, Buttler and Washington but by then the target was already comfortably within reach.

The Over That Broke It & The Over That Closed It

Overs 8-11: Holder got Patidar in over 8, Jitesh in over 9, David dragged Rashid to Holder at midwicket in over 10, Krunal popped Arshad to Holder in over 11. RCB went from 59 for 2 to 96 for 6 in four overs, their innings direction gone completely. Padikkal was the last recognised batter still standing and Rashid bowled her on for 40 in over 14.

Overs 13-16: GT were 111 for 5 needing 45 off 42 when Tewatia came in as Impact Player. He hit four fours in his 27 off 17. Holder added 12 off 10. Rashid finished it with a six over extra cover off Suyash in the final over, GT winning with 25 balls to spare. The target never looked dangerous after Gill's powerplay.

Player Ratings

#	Name	Team	Role	Label	Descriptor
1	Jason Holder	GT	Allrounder	Match-winner	5 dismissals, everywhere all night
2	Shubman Gill	GT	Batter	Powerplay Weapon	43 off 18, set the chase up early
3	Arshad Khan	GT	Bowler	Enforcer	3/22, 6.60 ECO, sharp and accurate
4	Rashid Khan	GT	Bowler	Strangler	2/19, 4.75 ECO, killed RCB's middle overs
5	Devdutt Padikkal	RCB	Batter	Lone Fighter	40 off 24, nobody stayed with him
6	Bhuvneshwar Kumar	RCB	Bowler	Bright Spot	3/28, fought hard in the chase

Trivia

1. Holder's five dismissals (2 wickets, 3 catches) is the joint-most involvement by any fielder in a single IPL innings this season (source: provided dataset, Ranjit).
2. Gill's 43 off 18 is the most he has scored in an IPL powerplay (source: ESPNcricinfo match blog).
3. RCB's collapse of 6 wickets for 37 runs between overs 7 and 11 is their worst batting phase of IPL 2026 (source: provided dataset, Ranjit).

Simulation Verdict: RCB's 48% dot ball rate and six-wicket middle-over collapse left a total 40-50 runs below par; once Gill and Buttler put on 69 in the powerplay the chase was never seriously tested.

Hot Take: Hazlewood went for 56 off 4 overs at 14.00 ECO tonight. He bowled brilliantly in Delhi two days ago and got taken apart tonight in Ahmedabad. The same bowler, completely different results on different surfaces. RCB's bowling reliance on conditions rather than plans is their biggest vulnerability heading into the playoffs.

RCB drop to third after losing to GT. Was this a one-off bad day or is their middle-order fragility a genuine playoff concern?

Written with authoritative precision for r/CricketBriefing*.* Jason Holder was involved in five of RCB's ten dismissals, Gill hit 43 off 18 in the powerplay, and GT chased 156 with 25 balls to spare: RCB's six-wicket middle-over collapse is the most concerning sign for the defending champions this IPL season.

Full IPL 2026 match report covering GT vs RCB Match 42 at Ahmedabad, including Jason Holder's five-dismissal performance, Gill's 43 off 18, Arshad Khan's 3/22 and GT's four-wicket win. Searching for GT vs RCB scorecard, Jason Holder IPL 2026 performance, RCB middle-order collapse 2026 or Gujarat Titans points table, this is your complete breakdown. GT move to 10 points and fifth place while RCB remain second on the IPL 2026 points table with 12 points from 9 games, staying ahead of SRH and RR on NRR despite this defeat.

Ryan Rickelton made 123 not out off 55 balls, the highest score ever by an MI batter in IPL history. MI posted 243, their highest ever first-innings total. SRH chased it in 18.4 overs with six wickets to spare. Head and Abhishek put on 129 for the first wicket, 92 of those coming in the powerplay. Ghazanfar took two quick wickets to give MI a brief window. Klaasen shut it. His 65 off 30 and Arora's 30 off 10 finished it. SRH move to 12 points, five wins in a row. MI stay eighth on 4 points with six losses from eight.

Match Pulse: Head and Abhishek hit 92 in the powerplay without losing a wicket, the highest powerplay score of any SRH chase this season, and the required rate never looked threatening from that point.

Phase Diagnostic

Overs	MI runs/wkts	SRH runs/wkts	What it meant
1-6	78/0	92/0	SRH hit 14 more in powerplay, chase always ahead
7-10	49/2	42/3	Ghazanfar took two quick wickets, brief MI hope
11-16	75/1	79/0	Klaasen-Reddy 80-run stand sealed it
17-20	41/2	36/1	Both teams finished hard, SRH crossed the line

SRH hit 18 sixes to MI's 14. SRH scored 188 runs in boundaries to MI's 168. Not a single SRH bowler kept their economy under 7. Not a single MI bowler kept theirs under 10. Both teams attacked throughout on a flat Wankhede surface.

Impact Match-Up

Head and Abhishek vs MI's new-ball attack: 129 off 52 balls, 93 of those in the powerplay. Head's flick produced 18 runs, control 73%, eight sixes off 30 balls total. Bumrah went for 54 off 4 at 13.50 ECO. Ashwani went for 41 off 2 at 20.50. When Ghazanfar removed Abhishek and Kishan in consecutive balls to make it 129 for 3 in over 9, MI had a brief chance. Then Klaasen came in.

Rickelton's pull shot produced 42 runs, control 78%, and his 93-run opening stand with Jacks off 43 balls set the foundation. His partnerships kept building: 55 with Dhir, 56 with Pandya. He was at the crease for all 20 overs, batting through to finish unbeaten. It still was not enough.

The Over That Broke It & The Over That Closed It

Over 7: Ashwani Kumar came on and Abhishek-Head hit 23 off it including two sixes and a four. **SRH went from 92 for 0 to 115 for 0 after seven overs, the required rate below 10 for the first time in the chase and it stayed there.**Ghazanfar's two-wicket burst in over 9 was brilliant but came too late to matter.

Over 16: Ghazanfar's final over went for 19 runs including two sixes from Klaasen. SRH went from needing 57 off 24 to 38 off 18, Klaasen reverse-sweeping Bumrah and punching Cummins over mid-off with equal disdain. Arora hit three sixes off 10 balls to finish it with eight balls to spare.

Player Ratings

#	Name	Team	Role	Label	Descriptor
1	Heinrich Klaasen	SRH	Batter	Chase Closer	65* off 30, won it when it mattered
2	Travis Head	SRH	Batter	Powerplay Weapon	76 off 30, eight sixes, brutal
3	Ryan Rickelton	MI	Keeper-Batter	Record Knock	123* off 55, highest MI score ever
4	Salil Arora	SRH	Batter	Finisher	30 off 10, sealed it cleanly
5	Will Jacks	MI	Batter	Strong Start	46 off 22, set the platform
6	AM Ghazanfar	MI	Bowler	Brief Hope	2/51, only one who fought back

Trivia

1. Rickelton's 123 not out is the highest score ever by an MI batter in IPL history*.*
2. SRH's 249 for 4 is the highest successful chase in IPL history at Wankhede Stadium.
3. None of MI's bowlers finished with an economy below 10, the first time this has happened to MI in a completed IPL innings this season*.*

Simulation Verdict: SRH's 92-run powerplay without a wicket reduced the required rate below 10 before MI had taken a single wicket; Klaasen's 80-run stand with Reddy off 40 balls after the three-wicket cluster removed any remaining doubt.

Hot Take: Bumrah went for 54 off 4 overs at 13.50 ECO tonight against a batting lineup he should trouble. This is the second time in recent matches he has been taken apart at Wankhede. MI's home ground is becoming their biggest problem.

SRH have won five in a row. They are 12 points, joint third. MI have lost six of eight at home. Is Wankhede actually MI's biggest problem this season?

Written with authoritative precision for r/CricketBriefing*.* Ryan Rickelton made the highest score by any MI batter in IPL history and it still was not enough: SRH chased 244 in 18.4 overs to register the highest successful chase at Wankhede and move to five wins in a row.

Full IPL 2026 match report covering MI vs SRH Match 41 at Wankhede, including Rickelton's 123 not out, Head's 76 off 30, Klaasen's match-winning 65 not out and SRH's six-wicket win. Searching for MI vs SRH scorecard, Ryan Rickelton IPL 2026 record, SRH winning streak 2026 or Mumbai Indians bowling problems, this is your complete breakdown. SRH are now joint third alongside RCB and RR on 12 points with five consecutive wins heading into the business end of IPL 2026.

PBKS posted 222 on the back of Stoinis's 62 off 22 balls. RR chased it down in 19.2 overs with six wickets to spare. Sooryavanshi and Jaiswal set the foundation with 84 in the powerplay. Chahal fought back with 3/36 to leave RR at 151 for 4 needing 72 off 38 balls. Then Ferreira and Dubey added 77 off 32 together and made it look easy. PBKS suffer their first defeat. RR move to 12 points, level with RCB and one behind PBKS.

Match Pulse: Chahal took three wickets to leave RR at 151 for 4 needing 72 off 38, then Ferreira and Dubey added 77 off 32 to win it with four balls to spare.

Phase Diagnostic

Overs	PBKS runs/wkts	RR runs/wkts	What it meant
1-6	65/1	84/1	RR hit 19 more in powerplay, chase always ahead
7-10	42/1	25/1	Both teams consolidated, RR slightly ahead
11-15	53/2	42/2	Chahal's three wickets briefly gave PBKS hope
16-20	62/0	77/0	Stoinis exploded, Ferreira-Dubey matched it

RR hit 14 sixes to PBKS's 12. RR scored 168 runs in boundaries to PBKS's 144. Both teams had nearly identical dot ball rates of 28% and 25%, this was an all-out batting contest from ball one.

Impact Match-Up

Ferreira and Dubey vs PBKS's death bowling: 77 unbeaten off 32 balls for the fifth wicket, the partnership that settled the chase. Ferreira's 52 off 26 included six fours and three sixes, his pull shot bringing 18 runs. Dubey's 31 off 12 as Impact Player was surgical, hitting Jansen for a six into the second tier at long-on and consistently finding the gaps in the final four overs. Arshdeep went for 68 off 4 at 17.00 ECO. Ferguson gave 57 off 4 at 14.25. PBKS's pace attack had no answers.

Stoinis was the standout for PBKS: 62 off 22, six sixes, four fours, 82% control, his pull bringing 18 runs. His 41-run final partnership with Shedge off 12 balls pushed PBKS from 181 to 222 and gave them a total that should have been enough on most nights.

The Over That Broke It & The Over That Closed It

Over 15: Arshdeep returned and Ferreira took three fours off him. RR went from 151 for 4 needing 72 off 38, required rate above 12, to 165 for 4 with momentum firmly back in their corner. From that over the chase never wavered again.

Overs 18-19: Ferreira hit Arshdeep for four and six in over 18, Dubey followed with four and six off Ferguson in over 19. RR went from needing 40 off 18 to needing 7 off 7, and Ferreira finished it off with a six in over 20. PBKS's unbeaten run ended not with a tight finish but a canter.

Player Ratings

#	Name	Team	Role	Label	Descriptor
1	Donovan Ferreira	RR	Batter	Match-winner	52* off 26, clinical at the death
2	Shubham Dubey	RR	Batter	Impact Finisher	31* off 12, won it in the final overs
3	Marcus Stoinis	PBKS	Batter	Explosive	62* off 22, kept PBKS in the game
4	Yuzvendra Chahal	PBKS	Bowler	Brief Hope	3/36, only one who fought back
5	Vaibhav Sooryavanshi	RR	Batter	Powerplay Weapon	43 off 16, 84-run powerplay set the tone
6	Prabhsimran Singh	PBKS	Batter	Anchor	59 off 44, held innings together

Trivia

1. RR's 84-run powerplay is their highest of IPL 2026 and came in the same venue where PBKS hit 116 without loss three days earlier (source: provided dataset, Ranjit).
2. Ferreira and Dubey's 77-run unbeaten fifth-wicket stand off 32 balls is RR's highest partnership in a successful IPL 2026 chase (source: provided dataset, Ranjit).
3. This is PBKS's first defeat of IPL 2026, ending a run of six straight wins after one washout (source: provided dataset, Ranjit).

Simulation Verdict: RR's 84-run powerplay kept the required rate manageable through Chahal's three-wicket spell; once Ferreira and Dubey took on the pace attack in the final five overs, no target was ever going to stop them.

Hot Take: Arshdeep went for 68 off 4 overs, Ferguson 57 off 4. PBKS's pace attack has been exposed at death in this match and their previous one too. Chahal is their best bowler right now and he cannot bowl the death overs. That is a problem heading into the playoff phase.

PBKS lost their first game. RR chased 223 with a pair nobody saw coming in Ferreira and Dubey. Is this RR's moment to build a winning run or just a one-off on a flat Mullanpur pitch?

Written with authoritative precision for r/CricketBriefing*.* Ferreira and Dubey added 77 off 32 balls from 151 for 4 to end PBKS's unbeaten run: RR move to 12 points and are now firmly in the title conversation alongside PBKS and RCB.

Full IPL 2026 match report covering PBKS vs RR Match 40 at New Chandigarh, including Donovan Ferreira's 52 not out, Stoinis's 62 off 22, Chahal's 3/36 and RR's six-wicket win. Searching for PBKS vs RR scorecard, Donovan Ferreira IPL 2026 form, Punjab Kings first defeat 2026 or Rajasthan Royals points table, this is your complete breakdown. RR join RCB on 12 points as the IPL 2026 title race enters its most competitive phase yet.

PBKS are unbeaten in six completed matches. RR have lost three of their last five and face a SRH double-header later in the season. Tonight is not just about playoff position; for Rajasthan, a loss here makes their remaining schedule genuinely brutal.

Match Intel: Punjab Kings vs Rajasthan Royals | Maharaja Yadavindra Singh Stadium, New Chandigarh | Tue, 28 Apr 2026 | 07:30 PM Local | 02:00 PM GMT | Format: T20 - Match 40

Standings

Team	M	W	L	PTS	NRR
Punjab Kings (1st)	7	6	0	13	+1.333
Rajasthan Royals (4th)	8	5	3	10	+0.602

NRR Oracle

• PBKS Almost There: Win tonight and they reach 15 pts from 8 played. One more point from 6 remaining seals top-two.
• RR's Double Danger: Lose tonight and stay on 10 pts. Then face SRH twice. That sequence is close to elimination territory.
• RR's NRR Warning: They lead GT by 1.077 NRR at 10 pts each. A heavy loss tonight could shrink that buffer dangerously.

The Oracle says: If RR lose by 30+ runs tonight, GT could overtake them on NRR before the SRH matches even arrive.

Weather and Toss

Morning rain clearing, cloud cover persisting into evening, 28-31°C, dew expected from over 14-15 onwards. PBKS have bowled first in nine of their last ten matches. Dew reinforces that instinct. Toss winner almost certainly fields.

Pitch and Ground

Square	Straight	Avg 1st Inn	Avg 2nd Inn	Bat first wins	Chase wins
~68 m	~72 m	178	164	5 of 10	5 of 10

• Black soil surface with grass cover; genuine carry and bounce from ball one, pacers consistently find movement in the first four overs.
• New ball swings under cloud cover; tonight's overcast start means Arshdeep Singh and Jofra Archer both get ideal early conditions.
• Surface flattens significantly from over eight; batters who survive the powerplay score freely through the middle overs on a fast outfield.
• Dew from over 14 reduces spin grip and slightly assists the chasing side in the death, though both teams are powerful enough that this fixture's death overs average over 9.00 RPO in both innings.

The Pace War: Arshdeep Singh vs Vaibhav Sooryavanshi

Sooryavanshi has 454 runs at 227.00 SR, the highest strike rate of any established batter in this match. He destroys powerplays. Arshdeep has 10 wickets at 10.14 economy but his value is new-ball swing under clouds, precisely the condition tonight. If Arshdeep removes Sooryavanshi inside the first two overs, RR's powerplay total drops by 30-40 runs instantly. Jaiswal then has to rebuild rather than accelerate. In H2H phase data at Mullanpur, the 1st innings powerplay averages 7.67 RPO; if Sooryavanshi goes early, RR post 150-160 instead of 185-plus.

Predicted Playing XIs

Punjab Kings: Prabhsimran Singh (wk), Priyansh Arya, Shreyas Iyer (c), Nehal Wadhera, Shashank Singh, Marcus Stoinis, Marco Jansen, Harpreet Brar, Yuzvendra Chahal, Arshdeep Singh, Lockie Ferguson

Rajasthan Royals: Vaibhav Sooryavanshi, Yashasvi Jaiswal, Riyan Parag (c), Shimron Hetmyer, Dhruv Jurel (wk), Ravindra Jadeja, Dasun Shanaka, Jofra Archer, Tushar Deshpande, Ravi Bishnoi, Nandre Burger

All names verified against official squad lists.

Injury and Availability

No injury concerns reported for either squad.

Form and H2H

Team	Form (Oldest → Newest)	Reading
Punjab Kings	NR · W · W · W · W	Four straight wins, chased 265 against DC two days ago.
Rajasthan Royals	W · L · L · W · L	Lost to SRH last match after posting 228, chased down in 18.3 overs.

RR lead H2H 6-4 in last ten meetings. At Mullanpur specifically, RR have won both previous encounters at this ground.

Phase by Phase: Where Matches Are Won

PBKS vs RR, last 2 at Mullanpur:

Phase	1st Inn RPO	2nd Inn RPO
Powerplay (1-6)	7.67	6.83
Middle (7-10)	5.75	7.25
Middle (11-15)	9.00	8.60
Death (16-20)	12.20	7.60

The 1st innings death phase at 12.20 RPO is the headline number. This fixture at this ground produces extraordinary death-over hitting when batting first. The 2nd innings death collapses to 7.60 despite dew; batting first and posting 200-plus remains the structural advantage.

Venue Scoring Patterns: Last 10 at New Chandigarh

• Results split exactly 5-5 between defending and chasing; no structural advantage for either side.
• Average 1st innings: 178. Average 2nd innings: 164. A 14-run first-innings advantage.
• PBKS have posted 254 and 223 in their last two home matches here; their death-over batting at this ground is exceptional.
• RR's only previous match at this venue ended in a 50-run win defending 205.

Win Probability

PBKS are unbeaten, at home, with a bowling attack built for these conditions and a batting lineup that has chased 265 two days ago. RR's bowling attack (Archer, Burger, Bishnoi) is strong enough to restrict PBKS on any given night, and their top order, if Sooryavanshi fires, can post 190-plus. The match is genuinely competitive but PBKS 65-35 on current form, home advantage, and toss likely going their way.

Hot Take

RR's best chance is Sooryavanshi and Jaiswal posting 60-plus in the powerplay and reaching 200-plus. PBKS chase 200 with ease; they have done it twice this season already. RR's realistic win condition is posting 215-plus and Archer taking Prabhsimran and Arya in his first two overs. Both things simultaneously. Hard but not impossible.

Trivia Nuggets

PBKS have chased targets of 223 and 265 in their last two matches at New Chandigarh; both won with overs to spare.

Vaibhav Sooryavanshi's 227 SR is the highest among established batters in this fixture by a distance.

RR have won both previous H2H encounters at this specific ground; tonight would be a third.

Community Challenge

PBKS are unbeaten in six completed matches. RR have beaten them here twice before. Which version of Rajasthan shows up tonight: the one that chased 202 off RCB, or the one that got chased down for 228 by SRH?

Written with authoritative precision for r/CricketBriefing*. PBKS's death-over batting at this ground averaged 12.20 RPO in H2H; RR's bowling attack is being asked to contain something historically difficult to contain.*

This IPL 2026 match preview covers tactical analysis, NRR Oracle qualification scenarios, and phase efficiency data for Punjab Kings vs Rajasthan Royals at Maharaja Yadavindra Singh Stadium, New Chandigarh.

At this venue in H2H meetings, the death overs (16-20) batting first have averaged 12.20 RPO, making first-innings target-setting and powerplay survival the two decisive variables in tonight's fixture.

Punjab Kings enter Match 40 of IPL 2026 as the only unbeaten side in the competition, while Rajasthan Royals face a result that could determine whether their playoff campaign remains in their own hands.

48 hours after 265 played 264 on the same ground, a completely different pitch served up swing, bounce and carnage. Bhuvi took 3/5 off three overs. Hazlewood took 4/12 off 3.3. DC were 8 for 6 inside four overs, bowled out for 75. RCB chased it in 6.3 overs with nine wickets to spare. Padikkal hit 34 off 13, Kohli finished it with back-to-back sixes and became the first player to 9000 IPL runs along the way. RCB move to 12 points, one behind PBKS at the top.

Match Pulse: Bhuvi and Hazlewood shared seven wickets in the first six overs as DC crumbled to 13 for 6, the lowest powerplay score in IPL history.

Phase Diagnostic

Overs	DC runs/wkts	RCB runs/wkts	What it meant
1-6	13/6	65/1	DC powerplay lowest ever in IPL, RCB's was five times more
7-16	58/3	12/0	DC lower order fought, RCB already done
17+	4/1	—	Hazlewood cleaned up the tail, RCB won in 6.3

DC's dot ball rate was 61% against RCB's 33%. DC scored just 38 runs in boundaries for the entire innings. RCB scored 62 in 6.3 overs. DC had only one six in the match, RCB hit seven.

Impact Match-Up

Bhuvi and Hazlewood vs DC's entire top six: seven wickets between them for 17 runs across six overs. Bhuvi got debutant Parakh yorked for a two-ball duck, then Stubbs and Axar edging behind. Hazlewood removed Rahul with a steep short ball top-edging to Jitesh, Rizvi first ball edging behind for a golden duck, then Rana fending a snorter from around the wicket to slip. DC's top six combined for 8 runs off 20 balls. Only Porel's 30 off 33 as Impact Player and Miller's 19 off 18 gave DC any respectability.

The Over That Broke It & The Over That Closed It

Overs 1-4: Bhuvi over 1, Hazlewood over 2, Bhuvi over 3, Hazlewood over 4. Four overs, six wickets, 9 runs. DC went from 0 for 0 to 8 for 6 in 23 balls, the contest was functionally over before most people had sat down. Patidar kept two slips throughout, backing his bowlers to keep attacking. It worked beyond anyone's expectations.

Over 7 of RCB's chase: Kohli hit Natarajan for back-to-back sixes to end the match. RCB chased 76 in 6.3 overs, winning with 81 balls to spare, the second-most balls remaining in a successful IPL chase ever. Padikkal finished unbeaten on 34 off 13 at 92% control. The crowd at least got to see Kohli bat.

Player Ratings

#	Name	Team	Role	Label	Descriptor
1	Josh Hazlewood	RCB	Bowler	Destroyer	4/12, four top-order batters
2	Bhuvneshwar Kumar	RCB	Bowler	Precision	3/5, 1.66 ECO, immaculate
3	Devdutt Padikkal	RCB	Batter	Finisher	34 off 13, 92% control
4	Abishek Porel	DC	Batter	Lone Fighter	30 off 33, only one who competed
5	Virat Kohli	RCB	Batter	Milestone Maker	9000 IPL runs, closed it with sixes
6	David Miller	DC	Batter	Brief Resistance	19 off 18, batting at No.8

Trivia

1. DC's powerplay score of 13 for 6 is the lowest six-over total in IPL history*.*
2. RCB won with 81 balls remaining, the second-most balls to spare in a successful IPL chase behind MI's win over KKR at Wankhede in 2008*.*
3. Kohli became the first player to reach 9000 IPL runs during the chase.

Simulation Verdict: DC's 8 for 6 in 23 balls left no realistic path to any total; Bhuvi's 1.66 ECO and Hazlewood's 3.42 ECO across six combined overs made this the most one-sided powerplay bowling performance of IPL 2026.

Hot Take: Bhuvi took 3/5 off three overs. His economy rate of 1.66 is the kind of number you see in club cricket against schoolboys, not in an IPL game at a venue where 265 was chased two days ago. The same ground, a completely different pitch, and RCB read it perfectly from ball one.

DC have lost three in a row. Bhuvi and Hazlewood just made their top six look completely helpless. Is this DC's season falling apart or just one very bad day on a difficult pitch?

Written with authoritative precision for r/CricketBriefing*.* Bhuvneshwar Kumar and Josh Hazlewood reduced Delhi to 8 for 6 inside four overs on the same ground where 529 runs were scored 48 hours earlier: RCB are one point behind PBKS and playing the most complete cricket of any team in IPL 2026.

Full IPL 2026 match report covering DC vs RCB Match 39 at Delhi, including Hazlewood's 4/12, Bhuvi's 3/5, DC's record-low powerplay of 13 for 6 and RCB's nine-wicket win in 6.3 overs. Searching for DC vs RCB scorecard, Hazlewood IPL 2026 bowling figures, RCB points table 2026 or Delhi Capitals collapse analysis, this is your complete breakdown. RCB move to 12 points from eight games and are firmly in title contention alongside PBKS heading into the second half of IPL 2026.

KL Rahul made 152 not out off 67 balls. The first Indian to score 150-plus in IPL history. DC posted 264, their highest ever total. PBKS chased it down in 18.5 overs with six wickets to spare. Nine dropped catches across the match. 529 runs scored. DC's highest total was not enough because PBKS hit 116 in the powerplay without losing a wicket and Shreyas Iyer was dropped twice in the same over by Karun Nair and punished DC immediately. PBKS move to 13 points from seven games, unbeaten, and the gap to second place keeps growing.

Match Pulse: Prabhsimran and Arya hit 116 in the powerplay without losing a wicket, the second-highest powerplay score in IPL history, turning 265 from impossible to inevitable inside six overs.

Phase Diagnostic

Overs	DC runs/wkts	PBKS runs/wkts	What happened
1-6	68/1	116/0	PBKS hit 48 more runs with one extra wicket in hand
7-12	74/0	57/3	DC middle phase dominant, spinners clawed back
13-15	51/1	30/1	Both teams scoring freely, PBKS just behind pace
16-20	71/0	62/0	Both teams exploded, PBKS crossed the line with seven balls left

PBKS hit 20 sixes to DC's 13. Both teams scored 200-plus runs in boundaries. DC's dot ball rate was just 17%, the lowest in this match, yet they still lost. PBKS's dot ball rate of 23% was the highest in this match, yet they still won by six wickets. This was not a bowling contest.

Impact Match-Up

Rahul and Rana vs PBKS's entire bowling attack: 220 together off 96 balls for the second wicket, DC's highest ever partnership*.* Rahul's on drive produced 24 runs, control 82%, and he reached his century off 47 balls before going from 100 to 150 in just 19 more balls. Rana's pull produced 18 runs, control 84%, and his 12th over off Bartlett went for 28 runs alone including 6,4,4,4,4,6 in consecutive balls.

Kuldeep was DC's best bowler in the chase: 2/46, 11.50 ECO, got both openers and Connolly to leave PBKS at 145 for 3 in the tenth over. Axar was economical too with 1/44. But Shreyas was dropped twice by Karun Nair in over 16 off Kuldeep and hit 4, 6, 6 off the next three legal balls. That sequence ended the contest.

The Over That Broke It & The Over That Closed It

Over 4 of PBKS chase: Auqib Nabi's over went for 27 runs including three sixes and a no-ball. PBKS were 83 for 0 after four overs on their way to 116 without loss at the powerplay break, the required rate effectively below 10 before DC had taken a single wicket. Three drops in the PBKS powerplay, including Prabhsimran on 15 and 71, allowed both openers to bat through and set a foundation that made 265 look like a batting practice target.

Over 16: Nair dropped Shreyas on 29 at long-off off Kuldeep. Two balls later Nair dropped him again at long-on. **Shreyas hit the next three legal deliveries for 4, 6, 6 to take 23 off the over and bring the target down to 39 off 18.**Game over from that point. Shreyas finished unbeaten on 71 off 36. PBKS crossed the line in over 19 off Natarajan.

Player Ratings

#	Name	Team	Role	Label	Descriptor
1	KL Rahul	DC	Keeper-Batter	Historic Knock	152* off 67, first Indian 150 in IPL
2	Prabhsimran Singh	PBKS	Keeper-Batter	Powerplay Weapon	76 off 26, 292 strike rate
3	Shreyas Iyer	PBKS	Batter	Chase Master	71* off 36, dropped twice, punished DC
4	Nitish Rana	DC	Batter	Destructive Support	91 off 44, 220-run stand
5	Kuldeep Yadav	DC	Bowler	Best of Bad Lot	2/46, only one who stuck to plans
6	Priyansh Arya	PBKS	Batter	Launch Pad	43 off 17, powerplay architect

Trivia

1. PBKS's 265 is the highest successful chase in IPL history, surpassing the previous record*.*
2. Rahul's 152 not out is the highest score by an Indian in IPL history, making him the third overall behind Chris Gayle's 175* and Brendon McCullum's 158*.
3. The Rahul-Rana partnership of 220 off 96 balls is DC's highest ever partnership in IPL history.

Simulation Verdict: PBKS's 116-run powerplay without a wicket reduced the required rate below 10 before DC had taken a single wicket; Shreyas being dropped twice in over 16 and responding with 4, 6, 6 was the moment the chase moved from probable to certain.

Hot Take: Nine dropped catches across the match. Both teams. DC dropped Rahul twice and Rana once. PBKS dropped Prabhsimran twice, Arya once, Connolly once and Shreyas twice. In a game where 529 runs were scored, the fielding was a collective embarrassment from both dressing rooms. DC's drops cost them a target they could have defended. PBKS's drops gave DC the total they needed to make it a record chase.

PBKS are unbeaten in seven, 13 points clear at the top, and just chased down 265. Is anyone actually capable of beating them this IPL season?

Written with authoritative precision for r/CricketBriefing*.* KL Rahul made 152 not out and DC posted their highest ever IPL total of 264, and it still was not enough: PBKS pulled off the highest successful chase in IPL history to stay unbeaten and extend their lead at the top of the table.

Full IPL 2026 match report covering DC vs PBKS Match 35 at Delhi, including KL Rahul's historic 152 not out, the Prabhsimran-Arya 116-run powerplay, Shreyas Iyer's match-winning 71 not out and PBKS's six-wicket win. Searching for DC vs PBKS scorecard, KL Rahul IPL 2026 record, highest IPL chase ever, Punjab Kings unbeaten run 2026 or Delhi Capitals highest total IPL history, this is your complete breakdown. PBKS move to 13 points from seven games as the most dominant team of IPL 2026 so far, with the highest successful chase in the tournament's history now to their name.

Washington Sundar dropped Kohli off the very first ball he faced. Kohli made 81 off 44. Padikkal followed with 55 off 27. Their 115-run second-wicket stand off 59 balls chased down GT's 205 with seven balls to spare. Sai Sudharsan's 100 off 58 was brilliant but ended in a losing cause, as it has done for GT in all seven meetings between these two sides. The chasing team has won every single one. RCB climb to joint top with PBKS on 10 points. GT slip to fourth consecutive defeat.

Match Pulse: Washington Sundar dropped Kohli on zero off the first ball he faced; Kohli punished GT for that miss with 81 off 44 and the game never came back to them.

Phase Diagnostic

Overs	GT runs/wkts	RCB runs/wkts	What it meant
1-6	57/0	58/1	Virtually identical powerplays, GT with an extra wicket in hand
7-12	64/1	76/0	Kohli-Padikkal partnership took complete control
13-15	29/2	40/3	GT tightened at the death, RCB wobbled briefly
16-20	55/0	32/1	GT finished hard, RCB closed it out through Krunal

RCB hit 14 sixes to GT's 10. RCB scored 152 runs in boundaries to GT's 128. GT's dot ball rate was 24%, exceptionally low, but RCB matched it with only 32% themselves showing both teams attacking throughout.

Impact Match-Up

Kohli and Padikkal vs GT's entire bowling attack: 115 together off 59 balls, the partnership that sealed the chase. Kohli's flick produced 26 runs, control 78%, and his back-to-back sixes off Rashid in over 10 changed the momentum completely. Padikkal's first ball was a six off Rabada at 153.6kph, over square leg. He reached his fifty off just 20 balls. Rashid eventually bowled Padikkal with a googly but by then RCB needed 65 off 8 overs with wickets in hand.

Sudharsan's cut shot brought 23 runs, control 80%, and his 128-run opening stand with Gill off 76 balls gave GT a foundation that should have been enough. But GT scored only 35 in the last four overs after being 170 for 2 after 16. Bhuvi, Hazlewood and Suyash nailed their yorkers to choke the total. Krunal's final over went for 18 but by then the damage was limited. Rashid's 2/49 off 4 at 12.25 ECO tells you how well RCB handled their best bowler.

The Over That Broke It & The Over That Closed It

Overs 9-10: Kohli hit Prasidh for 4, 6, 1, 1, 6 across over 9 to take 19 runs. Then Rashid dropped one short and Kohli pulled him for six, followed by a cut for four. RCB went from 83 for 1 after eight overs to 118 for 1 after ten, a 35-run burst in two overs that made 205 look completely chaseable. GT had no answer for Kohli when he was in this mood and the required rate dropped below 9 for the first time in the chase.

Overs 17-19: RCB were 175 for 5 needing 31 off 18 balls after losing four wickets in a cluster. Krunal hit Suthar for two fours and a six in over 18. 19 runs off that over, game down to 7 off 12, and Krunal finished it with a pull through midwicket in over 19. What looked like a wobble at 5 down was never truly dangerous with Krunal and Tim David still to come.

Player Ratings

#	Name	Team	Role	Label	Descriptor
1	Virat Kohli	RCB	Batter	Chase Master	81 off 44, dropped on 0, ruthless
2	Devdutt Padikkal	RCB	Batter	Blitz Artist	55 off 27, 200+ strike rate
3	Sai Sudharsan	GT	Batter	Brilliant, Losing Cause	100 off 58, team let him down
4	Krunal Pandya	RCB	Allrounder	Closer	23 off 12 when it mattered most
5	Bhuvneshwar Kumar	RCB	Bowler	Disciplined	1/31, kept GT to 205 not 230
6	Jason Holder	GT	Allrounder	Impact	23 off 10, GT's best death batter

Trivia

1. All seven matches between RCB and GT have been won by the chasing team, four by RCB and three by GT*.*
2. This is RCB's fifth successful chase of 200-plus in IPL history, making them joint fifth on that all-time list.
3. RCB have won four of five home games at Chinnaswamy this season, their final home game here being this one.

Simulation Verdict: GT's drop of Kohli on zero off ball one gifted RCB their most dangerous batter for free; his 115-run stand with Padikkal off 59 balls reduced a 206 target to a formality before the 13th over.

Hot Take: GT scored 170 for 2 after 16 overs and finished on 205. Those last four overs produced only 35 runs. Bhuvi, Hazlewood and Suyash completely shut GT down at the death. If GT had found even 220, this would have been a completely different chase. Their inability to accelerate in the death overs is becoming a pattern.

RCB and PBKS are joint top on 10 points. Kohli was dropped on zero and made 81. GT have now lost four straight.

Is this RCB's title to lose or can PBKS, RR and SRH still overtake them in the second half?

Written with authoritative precision for r/CricketBriefing*.* Washington Sundar dropped Kohli on the very first ball he faced and GT paid for it with 81 runs, a 115-run partnership and a five-wicket defeat: RCB go joint top of IPL 2026 with PBKS and are starting to look like the team to beat.

Full IPL 2026 match report covering RCB vs GT Match 34 at Chinnaswamy, including Virat Kohli's 81 off 44, Devdutt Padikkal's 55 off 27, Sai Sudharsan's century in a losing cause and RCB's five-wicket win. Searching for RCB vs GT scorecard, Virat Kohli IPL 2026 form, Royal Challengers Bengaluru points table 2026 or Gujarat Titans losing streak analysis, this is your complete breakdown. RCB climb to joint top of IPL 2026 on 10 points alongside PBKS, making this the most competitive title race of the season so far.