The 113 Hidden Inside 302 for 9: The Story Pakistan's Scoreboard Did Not Tell

Tuesday, Rawalpindi Cricket Stadium. The first ball of the innings. Fakhar Zaman trapped on the pad, the scoreboard reads zero. I was watching a phone stream from a plastic chair behind a tea stall in Chattogram, and at the next table a voice note was playing in the 'Pakistan Cricket Adda' group. One man was saying, 'Babar has to bat through today.' Another was saying, 'See off the new-ball spell and it is 320.' That hope went hollow before the first over was done.

The beat began in a WhatsApp group before the stadium lights ever came on. The quietest man in the group, the one who normally only posts scores, sent a voice note too: 'No top order today.' News from the 22 yards often arrives in those notes first. But notes come, then the match comes, and the match frequently proves the notes wrong. On this day it did not.

What I do not know is also part of this piece. Who won the toss, what the pitch report said, whether dew fell, whether it was a day-night fixture, who the third team is — none of that is in my hands. Kazan taught me that a roar can travel farther than any passport, and for that reason I will not write early about the Rawalpindi evening's noise, because I have no evidence of it. What follows is arithmetic inside one innings, not a verdict on a match.

Context: two new balls, fifty overs, and a tri-nation series

One-day cricket now runs on two new balls. The first fifteen overs swing, the middle overs bring spin and slower cutters, the last ten bring the return of the quicks. Pakistan's innings travelled through that shape but slipped away from the classic mould in one place. Their biggest sprint came between overs 28 and 48, not in the final ten.

From twenty years of watching cricket at the ground, I would say Rawalpindi Cricket Stadium has its own character. Short boundaries, a quick outfield, a surface that favours batsmen — here 300 is closer to a losing score than to a winning one. That is my inference, not something in the document, so it should be used with care.

The skeleton of the innings runs like this. In the new-ball phase, 59 for 3 in 14.2 overs, a run rate of 4.12, far below the modern ODI norm of 5.5 to 6.0. Then 74 runs for two wickets between overs 14.3 and 27.3, a rate of 5.65. Then 150 runs for two wickets from over 27.4 to over 48, a rate of 7.32. In the last two overs, 19 runs for two wickets.

The partnerships match that picture: 31 for the second wicket, 28 for the third, 23 for the fourth, 51 for the fifth, 78 for the sixth, 72 for the seventh. Those six stands add up to 283, which is exactly Pakistan's 283 for 7 at 48 overs. The arithmetic is internally honest, and that is a good credibility signal for the source.

Core analysis: the bottom built the score, not the top

Here is the real story. Of Pakistan's 302, batsmen at positions seven to eleven contributed 113 runs, or 37.4 per cent of the total. Arafat's 59, Faheem's 39, Shaheen's 10 not out, Haris's 4 not out, Naseem's 1. By contrast, the top three — Fakhar's 0, Saim's 8, Babar's 34 — made 42 runs together, 13.9 per cent of the total.

The foundation of this Pakistan innings was the lower order, not the top order. Thirty-seven per cent of the runs coming from seven to eleven means the upper half of the batting order once again did not do its job.

The 78-run sixth-wicket stand and the 72-run seventh-wicket stand are what actually pulled the innings up. Hasan's 79 and Arafat's 59 were not firefighting cameos; they were a patient rebuild, with Saad's 35 off 54 and Salman's 16 off 19 buying time. The 5.65 rate between overs 14.3 and 27.3 was not about speed, it was about laying a floor.

The trouble started after that. From around 133 for 5 in the 28th over, Pakistan scored 150 runs at 7.32 until the 48th. That spell was the real achievement. But having reached 283 for 7 at 48 overs, they added only 19 in the last two, and Faheem fell in the 49th over for 39 off 25. On a ground like Rawalpindi, 320-plus was realistically available from that position; the shortfall is 10 to 20 runs.

There is a smaller pattern worth noticing too. The 31-run second-wicket stand broke immediately after crossing fifty; the 51-run fifth-wicket stand broke immediately after crossing a hundred. Two data points prove nothing, but this side does show a recurring habit of losing focus right after touching a milestone. It is a small signal for the coaching staff, not hard proof.

The contrarian angle: 'fighting total' is journalism, not analysis

Instant reaction will call 302 for 9 a fighting total. I would say that at Rawalpindi, 302 is not a fighting total. It is par, or a shade under par. Defending that on a small ground requires two or three wickets with the new ball at once; otherwise the chasing side simply walks to the last ten overs.

The second contrarian point is about narrative. It is easy to turn this innings into a story about character. But the men who dragged the team out of trouble are mostly men whose places are not secure — this is not a story about character, it is a story about selection structure. Batsmen who score under pressure get trusted precisely when the top order fails. When the top order returns next match, those same men drop back to seven or eight and get four or five overs. That cycle is the actual problem.

The third point is the arithmetic of a tri-nation series. In a multi-team tournament, net run rate is a live variable. Finishing 15 to 20 runs short carries a small cost that can return large at the end of the group stage. Nobody will remember that 283 for 7 at 48 overs was a good position; everyone will look at the final run rate.

A scoreline tells you the ending, but the away end tells you the story. Here the away end is not England's dressing room — it is Pakistan's own, where under the line reading 302 for 9 there should have been another line: 'Seven to eleven: 113.'

Takeaway: the next signal will not be on the scoreboard

Once England's chase begins, the real question will sit in Pakistan's team meeting, not on the pitch. Will this innings be read as a total worth defending, or as a total that had to be rescued? If it is the second, hard questions about the top-order structure follow immediately. If it is the first, the same mistake repeats, and the Arafats and Hasans of the squad bat again in the last five overs. When the feed goes quiet, I listen for the pulse underneath the silence — on this day it said 302 was not enough.