Rawalpindi's 302: 113 from the lower order and 19 in the last two overs

First ball of the match at Rawalpindi Cricket Stadium. Fakhar Zaman had exactly one delivery to survive. The ball came in, hit the stumps, and Fakhar walked back on zero. Fourteen overs and two balls later the board read 59-3. Reaching 302-9 from that start, on a ground where three hundred is routine, means Pakistan's innings does not tell one story. It tells four, and the centre of all of them sits at positions seven to eleven.

I opened the ledger before I trusted the legend. What the ledger showed does not match the standard telling of this innings. You can call it a fighting total and move on, but the arithmetic says the foundation was not at the top.

The format is ODI, fifty overs, two new balls. The tournament is a tri-nation series, though the third participant is not named in the material available to me. No toss, no pitch report, no dew note, no day-night confirmation. So what follows is an analysis of one first innings only: no target, no chase, no result.

I know Rawalpindi's character from years of watching: short boundaries, quick outfield, a surface that favours batsmen. Three hundred there does not squeeze the opposition, it relaxes them. Given that, blaming the pitch for 59-3 is lazy. The new-ball movement and the top order's shot selection explain it better. That is my inference, not established fact, and without a pitch report nothing here can be called certain.

The two-new-ball regulation makes the first phase easier to read. The ball stays relatively fresh through the first twenty-five overs, seam and movement remain available, so a run rate of 4.12 is no accident. After two of the top three fell, the work Salman (16 off 19) and Saad (35 off 54) did will never show on the scorecard: they took the shine off, they used up the new ball's advantage.

Split by phase, the innings falls into four blocks. New ball: 59 runs for 3 in 14.2 overs, rate 4.12. First rebuild, 14.3 to 27.3: 74 for 2, rate 5.65. Second rebuild and acceleration, 27.4 to 48: 150 for 2 in 20.3 overs, rate 7.32, with Hasan's 79 and Arafat's 59 as the engine. Death: 19 runs for 2 in the last two overs.

The partnership ledger makes the picture sharper. Second wicket 31, third 28, fourth 23, fifth 51, sixth 78, seventh 72. The sum is 283, exactly the 283-7 on the board at 48 overs. That internal consistency is a good credibility signal for the source material. The book balances.

Here is the core. Positions seven to eleven, Arafat 59, Faheem 39, Shaheen 10 not out, Haris 4 not out, Naseem 1, made 113 of 302, or 37.4 percent. The top three, Fakhar 0, Saim 8, Babar 34, made 42, or 13.9 percent. The innings was built from the lower middle order, not the top, and Babar's 34 was not even the team's highest score, it was seventh.

That shape carries a tactical value and a tactical risk. When the lower order drags an innings, a middle-over wicket does not cause a collapse. The reverse is equally true: two failures in the top three push the entire burden onto number seven. On a Rawalpindi shirtfront that holds. On a difficult surface it will not.

The last two overs need separate treatment. At 48 overs Pakistan were 283-7 with two in hand. They added 19, and Faheem, 39 off 25, fell in the 49th. On this ground, 320-plus was a realistic expectation from that position. The shortfall is ten to twenty runs, and it can grow into something larger at the end of the match.

This is where I part with the standard reading. "Fighting 302" is editorial language, not analysis. On this ground 302 is par or slightly below, not a score that puts pressure on a chase. The innings had already accelerated to 7.32 after 27.4 overs; eighty-plus should have come from the last ten. Faheem's dismissal and the shot selection in the final overs explain why it did not.

One thing gets forgotten in a tri-nation series: net run rate. In a three-team tournament, equal points can be settled on run rate. Then a fifteen-to-twenty-run shortfall is not just an innings statistic, it is a table statistic. This is inference, because the third team and the detailed playing conditions are outside the material I have.

One small pattern caught my eye, and I will not overplay it: the 31-run stand broke just after crossing fifty, the 51-run stand just after crossing a hundred. Two events prove no trend. It goes in the ledger, and I will watch the next match.

A large gap remains. Who won the toss, whether dew is settling, how England's chase is shaping, none of it is known. If dew is present, 302 loses much of its value, because batting becomes easier in the second innings. Without that information the true worth of the score cannot be fixed, which is precisely why there is no verdict here.

In the next match my eyes will be in two places. First, how long Pakistan's top order survives the powerplay, because leaning on the lower order repeatedly is not a durable strategy. Second, the run rate after the fortieth over. If the tape says Pakistan are stopping below ninety in the last ten, then 302 was not a fighting score. It was a warning.