Fakhar's 127 didn't beat Sri Lanka — Sri Lanka's last nine overs did

Two runs were needed. Pakistan were seven down in Karachi, three wickets in hand, and neither of the two men at the crease had been part of the stand that got them there. Minhas and Faheem had gone in successive deliveries, at precisely the moment the win was two runs away. Then Shaheen Afridi walked out and put the ball over the boundary.

I have been reading scorecards for forty-six years, and one habit never left me: when a report calls a partnership "match-securing", I go and look at the tail of the card. This report described the 94-run stand between Minhas and Nawaz as having secured the game. The tail says something else — two wickets at two runs required, and a fast bowler's six needed to finish it. The stand did not secure the match. It turned a difficult equation into an easy one and left the last part in the middle.

The tail of a scorecard is always longer than the headline.

A tri-series whose third team is never named

This is a match from a triangular ODI series in Pakistan. Three teams are involved: Pakistan, Sri Lanka and England. England is not named once in the original match report. That is not a small slip. In a three-team tournament, the points table, the net run rate and the road to the final all run through the third side. The reader is left to reverse-engineer the format from stray data points. In cricket journalism, this is the equivalent of printing a company's balance sheet without naming the company.

The tournament context is left half-built too. Four days earlier, this same Pakistan batting line-up had been bowled out for 110. Four days later, the same line-up chased 326. The report records the contradiction; it does not turn it into a question. What changed? Did the pitch ease, did the attack change, did the order get reshuffled? None of it is answered. A large, startling contradiction is placed in the copy as decoration rather than as an argument.

Sri Lanka made 325 for 8 in fifty overs. At 41 overs they were 255 for 2. That means 70 runs and six wickets in the last nine overs. That is the single largest fact of the match, and the report disposes of it in one line.

The last nine overs: six wickets in fifty-four balls

The arithmetic is plain. From 255 for 2 after 41 overs to 325 for 8 after 50 — nine overs, fifty-four balls, seventy runs, six wickets. A wicket every nine balls, at 7.77 an over. This is the number that explains why a target of 326 was really a target of 350-plus that Sri Lanka cut down themselves. Had those nine overs run normally, Pakistan would have faced a mountain, and a chase that began at 14 for 2 would never have come back.

Kamindu Mendis made 131 — his best ODI score, and by the report's own account more than double his previous best. It came seven years after his ODI debut. Pavan Rathnayake added 77 and now has 427 runs in the series. Together they carried the score to 255, and then both men's work was washed away in the final nine overs. The report calls Kamindu's innings "in vain". The word choice alone tells you which side of the field the camera is on. Kamindu's innings did not go in vain. It was rendered vain, by the six wickets that fell after him.

There is a technical fault worth recording, because the original report slips on it. It states that "Pavan and Kamindu pushed Sri Lanka to 255 for 2 at 41 overs". But elsewhere the same report shows Pavan dismissed for 77 and Kamindu removed by Shaheen in the closing stages. Neither was at the crease at 41 overs. The fact was compressed for narrative smoothness. These small stitches are how you tell a report from a story.

Of Fakhar's 127, 121 came after a life

Now the part the headline rests on. Fakhar Zaman made 127, reached his hundred in 84 balls, and was named the architect of Pakistan's win. The scorecard shrinks that story.

Fakhar was dropped three times — at 6, at 69 and at 106. At 106, Maheesh Theekshana put him down twice. Do the arithmetic: after the first reprieve at 6, he added 121 more. Ninety-five per cent of his innings came after the moment he could first have been dismissed. On a normal day in the field, that innings ends at 6 and the headline carries someone else's name.

This is not to say the knock was counterfeit. A hundred in 84 balls is fast at any level. But to assess an innings while setting aside the reprieves is the same error as reporting a company's profit without flagging a one-off sale. The report logs all three drops — the honesty is present — but never processes them at the level of causation. Fact and frame run alongside each other and the tension between them is left unresolved. The reader has to assemble it alone: the man who "denied Sri Lanka" was denied three times by Sri Lanka.

What the 94-run stand did, and what it did not

Pakistan's chase began at 14 for 2. Babar Azam fell for nought — the same Babar the report had said was expected to produce something special. Then Minhas (21) and Nawaz (24) came together and added 94. Between them they are 45 years old, and neither would walk into Pakistan's first-choice XI. That stand is the real architecture of the match.

What was its function? A target of 326 is 6.52 an over. At 14 for 2 it had climbed past 7.2, with the rest of the order being the same men who had folded for 110 four days earlier. The stand absorbed that pressure, preserved wickets, and brought the last fifteen overs back into the ordinary range of six to seven an over. That is a large contribution. But "securing" a match means something else — it does not mean leaving three wickets in hand and losing two more with two runs required.

The report's own numbers show that 46 were needed from 30 balls, and that a 15-run over followed. Then Minhas and Faheem went within two runs of the target. That is the exact point where the partnership's work ended and the match opened again. Any report should think twice before calling such a stand "decisive" rather than "path-clearing". The distinction looks small; the reader's entire understanding rests on it.

Saad Baig: hours before his twentieth birthday

There was an innings in this match that found no room in the headline: Saad Baig's 74. Hours before turning twenty, his first international fifty, in a match where his team was 14 for 2.

In the age of social media, birthday numbers are easy content — a graphic gets made, a caption gets written, and by the next day everyone has moved on. My interest is not in the caption but in the shape of the innings. Those 74 runs came while wickets fell at the other end and the required rate sat above 6.5. That is the kind of contribution that decides selection over the next five years, and it does not make the headline that day.

The future of the sport is always settled somewhere the cameras are not. Saad Baig's 74, Minhas bowling and batting under pressure at 21, Nawaz holding it together at 24 — that is the layer that gives a tri-series meaning beyond the week. Fakhar's 127 is today's news. Saad Baig's 74 is tomorrow's selection.

Shaheen at both ends

Only one player appears at both the beginning and the end of this match: Shaheen Afridi. He removed Kamindu Mendis. He removed Dasun Shanaka. Those are the two points from which Sri Lanka's scoring rate began to break. Then, at the finish, he hit the winning six.

That is a rare profile. In ODI cricket a fast bowler is usually a guest in one part of the match: the new ball, ten overs, and the dressing room. Shaheen appeared here in two separate roles — bowler first, batsman later — and was decisive in both. If a single name must carry the credit, it is Shaheen's rather than Fakhar's, because his contribution is spread across both ends of the game.

And here another weakness of the report surfaces. Shaheen is said to have "brought Pakistan back" and to have "stopped Sri Lanka from scoring at an even higher rate" — but no economy rate, no overs bowled, no spell figures. Haris Rauf's two late wickets are mentioned with tactical detail and no numbers. Minhas's left-arm spin is described as "expensive" without saying how expensive.

Batting gets a downpour of figures — 127, 74, 61 off 31, 131, 77, partnerships of 87 and 146, a fifty in 52 balls, a hundred in 84, 427 runs at 106.75. Bowling gets events, not data. The asymmetry is telling. When one side of a report is given full numbers and the other only adjectives, the reader cannot form an independent judgement; he is handed the writer's.

An average built on four innings

One more number the report uses without warning: Rathnayake's 427 runs in the series at 106.75. The arithmetic says that is 427 divided by 106.75, exactly four dismissals. An average built on four innings measures nothing statistically. It reports a mood, not form.

In the same paragraph, Rathnayake is credited with "a healthy strike rate" — without the figure. Where the copy counts fifty off 52 balls elsewhere, here an adjective is judged sufficient. That is selective approximation. The reader is entitled to know whether 106.75 is impressive or an artefact of four innings, and that entitlement only exists if "four dismissals" is printed alongside.

Similarly, Kamindu's Test average is called "Bradmanesque", with "five hundred runs in his first eight Tests" offered as substitute evidence, and the actual average withheld. A metaphor cannot stand where a number belongs. When a report offers a comparison instead of a figure, it is asking for trust rather than supplying proof.

What the headline rewarded, what the scorecard rewarded

A different question arises here, and it is the most important part of this piece. This match report does not read like a correspondent's work. There is not a single direct quotation — not the captain, not the coach, not the player of the match, not the boy whose birthday was the next day. Three catches went down, a 326 chase happened, two wickets fell with two runs needed, and nobody said anything? That silence is not an accident. It tells you the material came from a wire feed or an official website copy where nobody was spoken to.

Such copy always contains two sentences that are not reporting but stage-setting. They are visible here: "the target was considered well within reach, even for the Pakistan batting lineup" and "the chase was expected to call for a Babar Azam special". Considered by whom? Expected by whom? No source. These sentences are not reporting anything; they are building an expectation in the reader's mind so that Babar's nought can land as irony later. As craft it is clever. As journalism it is the author's manoeuvre rather than a recorded fact, and it should be flagged as such.

The largest defect is structural. The report gives away the result, the partnership and the finishing six in its opening paragraphs, then narrates the same ending again ten paragraphs later. That double ending is chosen not to build tension but to build a hero. Result first, story after — that is the magazine feature's method, not the wire's. The cost is that by the eleventh paragraph the reader has already spent the taste of the win.

And Sri Lanka? Sri Lanka is not the subject of this coverage; it is the obstacle. A side that made 325 is turned into the object of a verb — "denies Sri Lanka". Kamindu's 131 is described as having gone in vain, when that same innings is what kept the match alive to the fiftieth over. The camera swings towards one dressing room from first ball to last. It is a match report, but its gaze is one-directional.

I add this warning out of habit. In 2026, when the match-fixing story broke, I stepped away from the microphone for eleven weeks and listened back to thirty-eight hours of old commentary. What I learned then was this: the important question about any report is not what it says, but what nobody was willing to put their name to. Here there are more than four dozen data points and not one named source. The scores, partnerships and ball counts may well be right — the arithmetic suggests they are — but there is no route inside the report to verify them.

Three things to watch next

Sri Lanka's problem is not batting. It is the plan for the last nine overs. The journey from 255 for 2 to 325 for 8 is not the product of one bowler's skill; it is the product of batting-order strategy — who comes in at which over, who plays for himself and who is allowed to play. England's attack will apply pressure to exactly that nine-over window, and then we will learn whether Karachi was an accident or a habit.

Pakistan's question is different. Fourteen for 2 and a nought from Babar say the top order is still in the air. The 94-run stand covered it; it did not hide it. Against a side with England's depth, chasing 300-plus, a start of 14 for 2 does not reach 326. Fakhar's 127 was a fine innings, but it stood on three lives; against a good fielding side the same innings ends at 6.

And the third question belongs to Saad Baig. Seventy-four under pressure at 14 for 2, at twenty, hours before a birthday — that is the kind of signal selectors forget after one series because their eye is already on the next auction. Give him a run and Pakistan's middle order can change in two years. Do not, and those 74 runs become a birthday graphic and nothing more.

The crowd in Karachi stayed late and then went home. The crowd left, but the match kept speaking — in six wickets across the last nine overs, in two wickets with two runs needed, and in those three dropped catches that never made a headline. The scorecard is still lying there. Whoever wants to read it, can.