IPL 2026 Week 3: The Week the Fortresses Fell

There is a rhythm to an IPL season. Week one is the settling-in. Week two is the first honest look at who's turned up. Week three is when the home sides are supposed to consolidate. The big grounds are known, the surfaces are read, the captains have three matches of data to play off. Week three usually belongs to the hosts.

This one did not.

Nine matches across seven days. Fifty-four hundred runs. Six last-over finishes. Two home teams losing at venues they had owned for the first half of the season. And a team that nobody was talking about in April showing up with 254 on the board. If you had told me at the start of the week that Mumbai would lose at Wankhede and Bengaluru would lose at Chinnaswamy in the same seven days, I would have asked who got injured. Nobody did. They just got outplayed.

The arrival of Punjab Kings

Here's the line I want you to sit with. Chasing 196 at Wankhede against the best pace trio in the competition — Bumrah, Boult, Hardik — Quinton de Kock scored 112 with eight fours and seven sixes. Punjab won in 16.3 overs. Twenty-one balls to spare. At Wankhede. Against Mumbai.

In the dressing room that I played in for twenty years, we used to say Wankhede rewarded courage. Small square boundaries, pace on the ball, dew when it's a night match. You either hit through the line or you died on the line. There was no middle. Quinton de Kock hit through it. Prabhsimran Singh hit through it at the other end — 80 with eleven fours. Even Naman Dhir got fifty. Punjab didn't win a close chase. They hammered a perfectly good target into the outfield and walked off.

Three days later in Mullanpur, they did it again. First batting this time. Priyansh Arya 93 with nine sixes. Cooper Connolly 87 with seven. Punjab posted 254 for 7. LSG tried and got to 200. Fifty-four-run margin that felt bigger. That's 450 runs in two innings across two matches, and in both of those matches Punjab were cleaning up the boundary rope as if the outfield had shrunk overnight.

The Punjab we remember from the last two seasons was the team that kept falling short. Set 180, chase 175, walk off with the spirit-of-the-game handshake. That team is gone. Whatever Ricky Ponting and the support staff have done this off-season, they've produced a Punjab side that hits every ball hard and hits the sixth ball hardest. Two wins. Both chased or defended against tougher opposition than what's coming next.

Home advantage in April 2026 is not what it was in April 2025. The travelling sides have finished reading the pitches. The middle of the season is where that starts to matter.

— Neha Saxena

Mumbai's first home scar

Before this match, Mumbai's home record at Wankhede this season read like a seminar on batting-friendly conditions. Post 180, win. Post 200, win big. The attack was operating in two phases — new ball inswing from Boult, death-overs yorkers from Bumrah, Hardik in the middle overs. It worked in April. It did not work on April 16.

The thing about defending 195 at Wankhede on a still night is you need three bowlers to bowl well. You got two. Bumrah was tidy, two for fewer than forty. Boult was honest. But Hardik's middle overs leaked, and the sixth-and-seventh over partnership between de Kock and Prabhsimran put Punjab ahead of the rate before the middle overs even started. Once a chase at Wankhede gets ahead early, the asking rate works for the batting side rather than against it. It's the flattest deck in April, it has the shortest straight boundaries, and the humid air does not swing the ball past the seventh over.

MI's bowling coach will be watching overs seven through twelve on loop for the next four days. Not because anyone bowled badly. Because the match was already gone, and nobody on the field was quite ready to admit it.

RCB at Chinnaswamy — the first crack

Royal Challengers Bengaluru had the season's cleanest home-fortress story through week two. Four wins from four at Chinnaswamy. Kohli scoring properly. Hazlewood and Bhuvneshwar operating with the confidence of a bowling attack that hadn't been hit for twenty in any recent over. Then Delhi Capitals happened.

RCB posted 175 batting first. On a Chinnaswamy deck in April, that's the honest number — slightly below par but defendable if the bowling clicks. Philip Salt, Tristan Stubbs, and KL Rahul decided otherwise. Sixty-three, sixty, fifty-seven. Three batters past fifty means you are not winning a 175 defence. DC chased it down in 19.5 overs. One ball remaining. The closest any chase at Chinnaswamy has come to going wrong this season — and it still went right for the travelling side.

This wasn't tactical brilliance from DC. It was competent top-order batting against a bowling attack that had run out of fresh ideas by the third over of the middle phase. Bhuvneshwar went for twenty-six in his four. Three wickets but sixes in them. The problem wasn't the plan. The problem was that the plan was the same one RCB had used in every Chinnaswamy win, and the DC top three had studied it.

Nothing is broken at RCB. One loss at home, still the best home record in the competition on a points basis. But the myth of Chinnaswamy as a fortress in April 2026 has its first chip. Axar Patel's two-wicket, forty-five-run spell was the difference. Not because the wickets were brilliant. Because nobody else on the DC side was particularly worried about losing.

Sunrisers at home — back-to-back defences

SRH had the cleanest home week of any side. Two matches, two wins. The 216 vs Rajasthan early in the week was the kind of total that ends a contest before the chase begins. Ishan Kishan 91 — he's quietly become one of this team's most reliable middle-order scorers. Donovan Ferreira 69 off not-many. Sakib Hussain four for twenty-four with the ball. Seventy-plus-run margin.

Then Friday night at Rajiv Gandhi — another 194 posted, and a ten-run defence against CSK that required exactly the kind of death-overs bowling SRH were supposed to be missing without Cummins. Eshan Malinga three for twenty-nine. Anshul Kamboj on the CSK side was good in reply — three for twenty-two — but CSK's top order couldn't catch the required rate and finished 184 for 8. Five runs short at the halfway point of the chase, ten runs short at the end.

The Hyderabad pitch is the highest-scoring venue this season. The pattern in week three: whoever posts 195-plus there wins. Both times it was SRH doing the posting.

Chennai's week — chamber and correction

CSK beat KKR at Chepauk on April 14, in the way CSK beat most teams at Chepauk. Spin, spin, more spin. Noor Ahmad three for twenty-one in four overs. Sanju Samson got 48 for KKR in a losing cause — you don't win at Chepauk when your top scorer manages 48. Spinners took six of the ten wickets. Standard CSK home formula, standard CSK home result.

Four days later in Hyderabad, the same CSK side found out what every travelling team at Hyderabad finds out. When the pitch plays true and the square boundaries are short and the dew doesn't arrive, the bowling attack that works at Chepauk becomes a different animal. Jamie Overton bowled three for thirty-seven — good numbers, expensive runs. Kamboj was excellent. The batting couldn't keep up. CSK fell short by ten.

Two matches, one win. An honest week. The pattern that's emerging about CSK this season: they're everything they need to be at home, they're a middle-of-the-table travelling side everywhere else. That's the truth about most IPL sides, but this year it's a little starker for the yellow jerseys.

Gujarat's Ahmedabad — still unbroken

GT hosted KKR at Narendra Modi Stadium on April 17. Standard GT-at-home scenario. Chased 181 in 19.4 overs. Shubman Gill got 86 — third half-century of his week if you count the unfinished fifty he was on when the match ended. Cameron Green got 79. Two balls left. A Gujarat Titans game where the margins were tight but the result was never in real doubt.

There are three home fortresses left standing in the IPL 2026 season right now. Ahmedabad. Chennai. Hyderabad. RCB's Chinnaswamy joined the cracked column this week. Mumbai's Wankhede joined it. Punjab's Mullanpur and Delhi's Kotla haven't been tested enough to say. Eden Gardens — which was where Kolkata completed a tight win over Rajasthan on Saturday by four wickets, Varun Chakaravarthy three for fourteen — sits in an uncertain middle.

Home advantage in April 2026 is not what it was in April 2025. The travelling sides have finished reading the pitches. The middle of the season is where that starts to matter.

Close finishes, big totals

Nine matches. Three decided with two balls or fewer remaining — RCB-DC, GT-KKR, KKR-RR. One decided by ten runs — SRH-CSK. One decided by 54 runs — PBKS-LSG. One decided by 58 runs — SRH-RR. One decided by 32 runs — CSK-KKR. One by seven wickets with twenty-one balls to go — PBKS-MI. One by five wickets with twenty-nine balls to go — RCB-LSG.

Five of the nine finished with at least one team past 190. Two finished with a team past 250. Bowling economy as a group: north of 8.5 an over. This was a bat-friendly week at most venues, and the exceptions — Chepauk, where spin still ruled — are becoming the venues where result certainty is highest.

Individual performances — who's running hot

Hundred this week: Quinton de Kock. 112 against MI at Wankhede. One of the most complete chase hundreds of the season so far — seventeen fours and sixes combined, scored at a strike rate the pitch was not designed to accommodate.

Ninety-three and not out equivalent: Priyansh Arya at Mullanpur. Nine sixes in a single innings is a sentence I haven't typed in recent memory for a Punjab batter.

Bowler of the week: Sakib Hussain for SRH — four for twenty-four — and Rasikh Salam Dar for LSG — four for twenty-four in a losing cause. Two identical scorecards, two very different contexts. Rasikh's effort was MoM in defeat, which tells you everything about how limited LSG's batting was that night.

Most improved: Anshul Kamboj at CSK. Two matches this week, two three-wicket hauls. Ten wickets in the season now leads CSK's bowling card and he's barely a year into senior-level exposure.

CM AI pre-toss scorecard

The engine called four of the first five matches correctly this week — SRH over RR, CSK over KKR, RCB over LSG, GT over KKR. The one we got wrong was Mumbai over Punjab. That one was ours to own, and the season tracker at cricketmind.ai/accuracy holds it permanently on the record. The weekend's four matches — RCB-DC, SRH-CSK, KKR-RR, PBKS-LSG — are still being scored into the tracker as the Lambda catches up with the Sportmonks feed, so week three's final accuracy number will land by Monday. The baseline coming out of week two was 54 percent. If we hold the four we called going into Saturday, we go into week four ahead of where we were.

What to watch in week four

Punjab's next three matches tell the story of whether this run is real or whether it's two good nights from two unusually good batsman performances. The form says real. The sample size says wait.

RCB play at Chinnaswamy twice in week four. After losing the first home match of the season, the response is the whole story. Do the bowlers double down on what worked before and risk getting read again, or do they try something new and risk being caught between two plans? I've watched both of those outcomes in championship seasons. The correct answer is always the harder one.

Mumbai travel. Three away matches in a row. After losing at home, travel is either restorative or accelerating. This squad on paper is deep enough to restore itself. On the field, we'll see.

Chennai also travel — two away in week four. The formula that works at Chepauk does not work at Jaipur or Lucknow. CSK will have to prove they can win a T20 that isn't played on a spin-friendly deck.

Nine matches, eight venues, four teams with genuine title credentials and six who still need to prove it. The fortresses are falling. The middle is opening up. That makes everything that comes next more interesting.

Neha Saxena Data Visualization Editor CricketMind AI