Ranji Trophy: Prithvi Shaw's 53* and Maharashtra's 10-wicket win — one innings, not a trend

I opened Maharashtra's scorecard in the Eden Gardens pavilion and paused for a moment when I saw the chase: 114 in 19.4 overs. In first-class cricket, 114 is not a mountain — but the surface was worn, and Prithvi Shaw made it clear with 53 not out off 50 balls that he wanted to reach the target by attacking, not by grinding. Three fours, four sixes — 36 of his 53 runs came in boundaries. For a batter whose previous four scores read 21, 0, 17, 12, this innings was a relief. The question is whether it is also proof.

The Ranji Trophy, the BCCI's domestic first-class competition, is where the Elite Group C table is decided. Bengal were bowled out for 143 in the first innings, and Maharashtra took a 75-run lead. Bengal recovered from 87/6 in the second innings to reach 186 through a 64-run seventh-wicket stand between Abhishek Porel (65) and Shahbaz Gupta (59), but the target of 114 was always within Maharashtra's reach, and Shaw finished it in 19.4 overs. With seven points including a bonus point, Maharashtra moved to the top of Group C with 19 points, while Bengal slipped to second with 18. The one-point gap shows how fragile the top spot is — the equation could change in the next round.

Now look at the innings ball by ball, because the scorecard does not tell you what the field placement does. Shaw scored at a strike rate of 106 off 50 balls — unusually aggressive for a top-order batter in first-class cricket. He hit four sixes, meaning 24 runs came from sixes alone. After the match, he said he had spoken to the coach and the target was 70-80, and that "attacking is the best form of defence". This innings was the execution of that plan. But note: he finished unbeaten on 53 while the target was 114 — the innings was decisive for the team, but personally it fell short of his own 70-80 target. That does not mean the innings was weak; it means the gap between intent and outcome remains — the intent is fast, but the question of consistency persists.

Technically, scoring at a strike rate of 106 on a wearing surface is risky. Shaw's previous four scores — 21, 0, 17, 12 — show his form is moving in waves. He himself admitted that his dismissals were not due to a "fundamental technical flaw" but to "his own shots". That is a self-diagnosis, not third-party technical verification. 53 off 50 balls in one innings does not prove the technical problem is solved — it only proves that on that day his shot selection was right. In first-class cricket, a single innings is too small a sample; one good innings is not enough to erase four poor ones. It reminds me of the 3 a.m. live-blog shift in 2026, when decisions had to be made within 40 seconds of a goal — in cricket, the decision comes from the scorecard, not the headline.

The real story of Maharashtra's win goes beyond Shaw. In the first innings, Sanghvi scored 60 and took two wickets — an all-round contribution. In bowling, left-arm spinner Walunj took four wickets, and seamer Dadhe also took four. Four-wicket hauls from two different types of bowler show that Maharashtra's attack is varied — a durable asset in first-class cricket. During the chase, young Dhas made 61* alongside Shaw; Shaw later called him a "tremendous young talent". But it is also true that Maharashtra's batting leaned heavily on three contributions — Shaw, Dhas and Sanghvi. The depth question remains: if both Shaw and Dhas had fallen cheaply, would a chase of 114 have been so easy?

Bengal's real concern is their top order. The collapse to 87/6 in the second innings is not just about this match — it is a pattern. Porel (65) and Gupta (59) saved face with a 64-run seventh-wicket stand, but the top order lost wickets cheaply. In first-class cricket, if the top order repeatedly gives starts like 87/6, no bowling attack is good enough to win matches consistently. Bengal have 18 points, but if their top order keeps stumbling, their position in the table could slip further in the next round.

Now the angle that is off the scorecard but matters: Prithvi Shaw's innings is part of a bigger story — a former India Test opener who moved from Mumbai to Maharashtra last season. That domestic transfer was for playing opportunity, and it has commercial undertones: more game time affects selection and franchise value. But one domestic fifty is not a guarantee of international return. The report itself cautions that this 53* "cannot erase recent disappointments or guarantee a return". The media tendency to frame a former superstar's single innings as a "comeback" is strong; caution is needed here. I will not say Shaw's return is impossible — rather, that the evidence is one innings, not four.

Those who say Shaw "is back" should remember his previous four scores were 21, 0, 17, 12. A 50-ball innings does not break that sequence, it only pauses it. The real question is not whether Shaw made 53*, but what he does in the next two or three innings. If he strings together two fifties, the story can change; if he falls for 20-30 again, this innings will remain just a good day's memory.

For Maharashtra, the win came with a bonus point and took them to the top of the table — but a one-point gap shows how unstable the top spot is. For Bengal, the loss exposes the weakness of their top order. And for Shaw, this innings is a signal, not proof. As I write in my notebook: the scorecard waits, but it speaks only after the count. The next round's scorecard will tell whether this 53* was a beginning or an outlier.