Pakistan 110 All Out: 24.3 Overs Unused, and the Column the Scorecard Left Blank

I opened the scorecard and looked first at the number nobody prints. 25.3 overs. A fifty-over match, and Pakistan's innings ended twenty-four overs and three balls before its allocation. 110 all out. Three hundred balls were available; 153 were used. One hundred and forty-seven deliveries — roughly forty-nine per cent of the innings — went unused.\n\nGaddafi Stadium, Lahore. The host side. Lost the toss, sent in. Match five of a tri-nation series. A left-arm seamer bowls eight overs and three balls, concedes thirty-four and takes five. The scorecard records all of that. It does not record how many balls Babar Azam faced — and for five years every argument about Pakistan's white-ball batting has rested on exactly that column.\n\nI logged every ball before I allowed myself an opinion. This is written in that order.\n\nMethod before verdict\n\nThe information available on this match is single-sourced and is not tied to a published card. In the record I have, the source field beside every data point is blank. Three figures — 110 runs, 25.3 overs, 5/34 — are internally consistent, so there is no reason to assume fabrication. But the evidentiary base is medium-low, and I am putting that in the first three hundred words so the reader knows what ground he is standing on.\n\nSecond, the format. The source does not name it. But Dilshan Madushanka's spell is logged at 8.3 overs. A bowler is capped at four overs in a T20 and five in The Hundred. An 8.3-over spell exists only in an ODI or a Test. Tri-nation series, single innings, a total of 110 — this is an ODI. That inference rests on the rules, not on a hunch.\n\nThird, what is absent. No pitch report. No weather. No second-innings card. No result. Which means I cannot tell you Sri Lanka won, because I do not have their innings. And I cannot tell you the pitch was poor, because the curator's sheet never reached me.\n\nThe partnership arithmetic: 15.3 balls per wicket\n\nOne hundred and fifty-three balls, ten wickets. A wicket every 15.3 balls. In plain cricket language, no pair averaged even three overs together. In an ODI that means the innings never produced the one thing that makes a total: a stand long enough to let the batting be shrunk and then expanded. A fifty-over innings is built on three or four partnerships, at least one of them a hundred balls long. Here the longest did not approach it.\n\nThe other face of the same arithmetic: both openers failed to reach double digits. The first wicket therefore fell inside twenty runs, which put Babar Azam at No. 3 into the stabilising job from the first over. When an opening pair does not give you fifty in the first ten, the No. 3 cannot do two jobs at once — he can neither protect wickets nor generate rate.\n\nNot 110. 4.31 is the real number.\n\n110 is not a magic figure. It is a ratio. 110 over 25.5 overs is 4.31 an over. Contemporary ODI par at a Pakistani venue sits somewhere between 5.5 and 6.0. This innings ran roughly 1.2 to 1.7 an over below its own era. Carried across fifty overs — which this innings never could be — the same rate reaches about 215, itself a sub-par score.\n\nThe real damage is not 110. It is 110 with the innings truncated. A side dismissed inside 26 overs never gave its middle order the only conditions under which big totals are made: survive, then accelerate in the last fifteen. Here is a warning about my own arithmetic — 215 is a projection, not a measurement. I am labelling it as such. The 4.31 was real.\n\nBabar's 29: the top score is the harshest statistic\n\nThe highest score in the innings was 29, by Babar Azam — 26.4 per cent of the total. In newsroom language that is called resistance. Within a total of 110 it is something sharper.\n\nWhen the leading scorer makes 29, blame is distributed — which is exactly the difficulty. Nobody's 70 was left behind, and nobody's four mattered less than somebody's fifteen. In a shared failure every batter owns an equal share, whatever the column says. The source's framing that Babar tried to play cautiously, got a start and failed to convert is accurate, and it should be left at that. It should not be inflated into a vindication of his method, because 29 in an innings of 110 is not the same object as 29 anywhere else.\n\nThe column that is empty\n\nI went hunting for a pattern and came back with its absence. Babar's balls faced are not in my record. That is not a technicality; it is the largest hole in this story. The entire public argument about Babar in white-ball cricket is a strike-rate argument, and both sides bring their numbers. Here the number does not exist.\n\nSo I will write it plainly: insufficient information, no assessment possible. A claim that he anchored the innings is an opinion without data. A claim that he throttled the tempo is nothing at all. We know 29, we know 26.4 per cent, and that is the whole of it.\n\nHasan Nawaz's 54.8: a decision error, not a technique error\n\nHasan Nawaz made 17 off 31, a strike rate of 54.8. A modern ODI No. 6 or 7 operates between 85 and 100. That looks deep red. But a strike rate read without context is an accusation, not a number.\n\nOccupying the crease in a collapse has value. At 20 for 2 or 30 for 3, batting 31 balls was not the error. The error was the moment patience broke and the big shot went up and was caught. And here I have to doubt my own reading: was that impatience, or was it his natural game trapped at half throttle? His T20-league reputation is high-intent. If that identification holds, 54.8 is a deviation, and the cause is circumstance. I cannot verify it.\n\nSo I limit the conclusion. The shot was defensible in isolation, because by the 25th over the required rate was already climbing. The real failure was earlier, when nobody rotated strike at 20 for 2. One batter getting out is normal. An entire innings without strike rotation is a condition.\n\nShaheen's 115.4 is a diagnostic, not an achievement\n\nShaheen Afridi made 15 off 13. The source presents this as him helping Pakistan reach a hundred. The arithmetic disagrees. A frontline fast bowler batting at nine or ten and holding the second-fastest strike rate in the innings is not a story about courage. It is a report. It says the top seven were comprehensively outplayed. Fifteen off thirteen is what a No. 9 does when the innings is already dead, not when a batter is building.\n\nCalling tail-end runs resistance is an old habit. It reads the card and not the innings. If your No. 9 is your second most fluent scorer, the card is telling you where your batting went.\n\nMadushanka's 5/34: the most significant data point in the match\n\nEight overs, three balls. Thirty-four runs. Five wickets. Economy 4.00. Bowling strike rate 10.2 balls per wicket.\n\nThat combination is what makes the spell the most important figure here. Wickets can be taken and still cost you — five-fors at seven an over are not cheap. Not here. Five wickets at four an over means he was never milked and never played out. He was broken five times.\n\nThere is another layer. The innings lasted 25.3 overs; he bowled 8.3 of them — a third of the innings. Whether that was one spell or two I cannot establish from what I have, and 8.3 overs often implies a return spell. The mechanism is plausible: left-arm seam, relatively hard ball, against a right-hand-dominant top order. It is also documented as a recurring matchup vulnerability. But the dismissal modes are not recorded, so I will not describe how they fell. The number is certain. The mechanism is not.\n\nContrarian: the toss did not make this innings\n\nHere I have to fight my own favourite explanation. The reflex is: Pakistan lost the toss, were inserted, the ball moved in the morning, and there it is. It is a comfortable story, it assembles in five minutes in a press box, and part of it is true. Being inserted in seam-friendly conditions is a genuine disadvantage.\n\nLook at the magnitude. A toss disadvantage can cost you two or three wickets and twenty or thirty runs. It cannot cost you ten wickets and 110. Attributing a collapse this size to a coin is the same error I normally catch in the other direction: over-crediting luck so that a technical failure does not have to be discussed.\n\nThe second comfortable story is the slow pitch. On a genuinely difficult surface, sides usually survive longer and score slower. They do not get bowled out in the 26th over. A batter can score at 4.31 on a slow pitch and still bat until the 45th. This one did not bat.\n\nThird, the host dimension. Pakistan were the home side at Gaddafi Stadium. Visiting teams are the ones who struggle with unfamiliar surfaces. Collapsing at home weakens every pitch-based mitigation.\n\nAnd fourth, the discipline. One innings inside 26 overs says the top order was unprepared for the conditions that day. It does not establish that Pakistan's ODI side is declining. Distinguishing a one-off from a trend needs three to five surrounding innings. I do not have them. The answer is: insufficient sample.\n\nWhat is missing is also a finding\n\nThe host board prepares the surface at Gaddafi Stadium. When a host watches its own team bowled out for 110, a legitimate question arises about curator instructions and venue philosophy. That is a question, not a conclusion, because there is no pitch report. I do not publish questions as findings.\n\nNor is there any integrity signal. I state that positively rather than leave it blank. A low total is not by itself an anti-corruption flag; the units look for abnormal betting patterns and specific-event manipulation. Nor is there any DRS controversy, weather or DLS. The innings ended by dismissal, not interruption. On the information available, this is a clean cricketing outcome.\n\nOne small note. The card carries a name rendered as Saif Beg, very likely a transliteration of another squad member. No player-level conclusion should be drawn from that entry before verification. In data work, small things become large errors later.\n\nStructure and market\n\nMatch five of a tri-nation series. Three teams, six league games, a final — this was a mid-tournament fixture with table consequences, not a formality. A collapse of this size in that setting costs more than one defeat; it loads the rest of the tournament, especially at home.\n\nOn batting depth, the only evidence available is that the innings reached the tail by the 22nd or 23rd over. That is not a depth question, it is a top-order question. Opening stability is the highest-leverage structural issue the innings raises, and the causal chain from there — openers fail, No. 3 stabilises from ball one, intent compresses — is plausible but undemonstrated.\n\nOn Sri Lanka, one spell at least suggests a bowling unit with a plan and the discipline to execute it, the kind of profile that travels better than a batting-dependent side. One spell, not a series.\n\nCommercially, this is an international tri-series, not a franchise league, so auction arithmetic, retention and transfer fees are not engaged. What can be said is that the tri-nation format itself is commercially marginal, squeezed between the IPL window and FTP bilateral commitments, and exists largely as preparation. The value of this match was sporting and reputational, not commercial. A sub-120 total at a recently redeveloped flagship venue damages the product being sold to broadcasters more than an away defeat would.\n\nAnd the discipline I repeat: a strong ODI spell does not itself translate into T20 auction value, because the formats reward different skills. Madushanka's 5/34 raises his visibility. It does not establish his price.\n\nTakeaway: the next three to five cards\n\nI refuse to turn this innings into a thesis, and the refusal is method, not modesty. What I have is one innings, 153 balls, ten wickets, one spell. What I need is the next three to five cards, with the balls-faced column filled and the dismissal modes recorded.\n\nUntil then, three things are worth watching. The opening pair next match — a second failure inside twenty runs turns an accident into a selection question. Babar's balls faced — if it is missing again, the problem is record-keeping, not batting, and record-keeping poverty is a real story nobody prints. And the next surface at Gaddafi Stadium.\n\nThe log remembers what the highlight reel edits out. The reel has 110, five wickets and a broken innings. It does not have the 24.3 overs nobody batted, or the empty column where balls faced belonged. I will wait — for the next scorecard, and for that column to be filled.