Jitesh's 85* Powers RCB Past LSG to Seal Top-Two Finish in Lucknow


Published 2026-11-06 · By Pranav Kulkarni (Mobile Gaming & UPI Fintech Editor · Jaipur Desk)

At 7:42 PM IST, with Ekana's floodlights still sorting themselves out, Mitchell Marsh miscued Bhuvneshwar into the deep and LSG's 218/5 suddenly looked 15 runs light. Nobody in the dugout bought that excuse either.
RCB needed 219 and a top-two finish. Virat Kohli walked out like he'd already read the script — 54 off 38, all placement, no panic. Then Jitesh Sharma happened. 85 not out off 37, four sixes over extra cover, and the Lucknow crowd went from loud to library in nine balls. The chase ended at 219/4 in 18.4 overs. Simple. Brutal.
The Impact Player gamble — LSG swapping in an extra seamer instead of a finisher — backfired the moment RCB's middle order stopped respecting length. You could see it in Rishabh Pant's body language by the 16th over. Shoulders dropped, gloves off, done.
Why the Middle-Overs Choke Keeps Happening
LSG's batting is a paradox. Marsh and Pooran give them 190-plus floors, but between overs 7 and 15 the run rate dips to 7.2. On a sticky red-soil track that grips after 9 PM, that's fatal. RCB bowled into the pitch, hit the hard length, and let the dew factor after 8:30 PM IST do the rest. The skiddy hard length from Yash Dayal cramped Pooran for room — two dots, a wicket, game over. Boundary-percentage for LSG dropped from 22% to 9% after the 18th over.
Second-Screen Reality Check From a Gurugram Couch
I watched this on a 5G phone in Gurugram while bench-testing three second-screen apps. The toss spike at 8:00 PM IST is real — JioCinema held at 1.3s delay, Hotstar drifted to 2.4s, and one fantasy app crashed twice during the powerplay. The same refresh window, for what it's worth, is when goa casino live tables online lobbies see their nightly traffic spike across tier-2 cities. Coincidence? Maybe. The latency, though, cost me two live-bet windows before I switched to a backup hotspot.
- Ekana's black-soil strip gripped after 18 overs; LSG boundary-percentage fell from 22% to 9%.
- RCB's chase boundary-percentage: 28%, highest of the week.
- Ranji grind showing: Jitesh's off-side play looked like a red-ball session, not a T20 cameo.
- UPI payments on match-night: success rate dipped to 94.2% between 9:15 and 9:45 PM IST.
- Hotstar's 2.4s delay meant spoilers on Twitter landed before the ball reached the keeper.
What This Means for the Table
RCB finish top two and carry the form into the playoffs. LSG go home asking the same question they've asked since 2024: who bats at five? The answer isn't on this roster, and no Impact Player swap is going to find it. Pant's 34 off 28 summed up their season — pretty, late, and not enough.
— Pranav Kulkarni, Mobile Gaming & UPI Fintech Editor, Jaipur Desk (filed from a Gurugram couch, 11:40 PM IST)
Related coverage
- Mithali Raj’s Ranji Lesson: Why the New Ball Did the Talking at Chinnaswamy
- IPL Records vs. Latency: Tracking Fast Centuries and Goa Casino Live Tables Online

Updated 2026-11-06 · Instant Rupee Deposits & 60s Withdrawals · 24/7 Support.
Access Official TravelCafe Portal →
IPL Auction & Fantasy Strategy Editor · Kolkata Desk
Yash Banerjee has tracked IPL auctions, T20 toss trends, and fantasy combinations since 2016. From Kolkata, he oversees TravelCafe's live match previews and goa casino live tables online guides.
Reader Discussion & Match Reactions (7)4.8★ Community (7 Comments)
Verified Indian cricket reader perspectives & tactical debate on travelcafeinc.com
The 85* off just 37 balls is insane. Jitesh’s strike rate of 229.7 crushed LSG’s bowling plan completely.
RCB’s win highlights the chaos in the draft. Pooran getting cramped by Yash Dayal shows how fragile their middle order really is under pressure.
Where is the state association feedback? Focusing only on IPL stars ignores the grassroots pipeline that fuels these matches across India's districts.
JioCinema’s 1.3s delay is a disaster for second-screen apps. The latency spike at 8 PM is ruining the live engagement metrics for advertisers.
Swapping a finisher for a seamer was a tactical nightmare. Pant’s body language confirmed the team was dead before the final over even started.
We need more Ranji tracking here. Focusing only on Ekana’s floodlights ignores the domestic circuit struggles that keep Indian cricket alive at the grassroots level.
@Saurabh_NRR That strike rate explains the pressure. The 7.2 run rate dip between overs 7 and 15 was their fatal weakness on that sticky pitch.


