The Rawalpindi Match Ended in 98 Overs, Yet Both Teams Were Fined — The Twenty-Two Minutes the Scoreboard Never Records

The queue outside the Rawalpindi Cricket Stadium was getting longer just as the floodlights came on inside. Sunday, 18 October. At the tea stall near the gate, a man said, "There'll be runs today." He was right. By the end of the evening the scoreboard held 573 runs, 19 wickets and a 37-run win. But the sheet that reached my hand in the press box had no runs on it. It had minutes.

The match finished in 98 overs. In a 100-over fixture, both innings were done with two overs still on the clock. On paper, that should mean the game ran ahead of schedule. And yet in that very match, Pakistan and Sri Lanka were both fined for a slow over-rate.

That single sentence is the centre of everything here. Because it exposes cricket's oldest confusion: we count balls, runs and wickets, but we do not count the one thing that actually owns the match — the clock.

The scoreboard does not lie, but it tells an incomplete truth. The over-rate sheet is the only written record of what it leaves out.

A match fast on paper, slow on the clock

Kusal Mendis won the toss and chose to field — the standard chase-under-lights logic at a Pakistani venue. It was not a wrong decision. It simply did not pay off.

Pakistan batted first and were bowled out for 305 in 49.5 overs, one ball unused. Salman Ali Agha made 107 off 90 balls and took the Player of the Match award. Babar scored 45, debutant Saad Baig 39, Mohammad Nawaz 37. Four batters passed 37, yet the side folded before the final over — the first signal that the runs came in clusters rather than in a spread.

Sri Lanka replied with 268 all out in 48.1 overs. Along the way sat a 119-run fifth-wicket stand between Pavan Rathnayake (79) and Janith Liyanage (60). That partnership was the real hinge of the match. What followed was a lower-order collapse: the remaining roughly 49 runs cost five wickets.

The bowling picture is cleaner still. Shaheen Shah Afridi took 3/55; Naseem Shah, Haris Rauf and Faheem Ashraf took two each. Four specialist seamers sharing nine wickets tells you Pakistan had read the Rawalpindi surface correctly — pace over spin.

Then came the sheet. The match officials' panel under referee Jeff Crowe found both sides guilty of a slow over-rate. The officiating composition — home umpires Asif Yaqoob and Faisal Afridi, neutral on-field umpire Wayne Knights (New Zealand), neutral TV umpire Sharfuddoula Ibne Shahid (Bangladesh), neutral Elite Panel referee Jeff Crowe (New Zealand) — matches the current one-home, one-neutral bilateral model and is a positive reliability signal for the report.

One thing to notice: the third team in the tri-series is never named. For a competition whose entire premise is three participants, that is a material omission. It will return later.

The 37-run margin says less than it seems

The most dangerous reading of this match is that Pakistan won by 37, therefore Pakistan were 37 runs better. That is the classic margin-versus-process error.

Sri Lanka were in the contest at the point of that 119-run stand. Even after five wickets had gone in the chase, they were still inside the fight. The last five wickets fell for under 50 runs. The match was won by Pakistan's pace attack in the final fifteen overs, not by the 305 total.

Rawalpindi has historically been a batter's surface — short boundaries, the ball travelling. 573 runs across 98 overs supports that inference. On such a deck, 305 is never a safe total. But Pakistan had four specialist quicks, and that selection was the strategic choice that decided the game.

Years of watching cricket on these surfaces teach you something specific: the ball does not bounce extravagantly, it simply arrives in the middle of the bat. The only way to stop a side there is a patient mix of yorkers and slower balls. Pakistan did exactly that.

A caution is still required. This is one match. Nothing here should be read as a series or career trend. Salman Ali Agha's 107 off 90 — a strike rate near 118.9 — sits clearly above the roughly 95–105 benchmark for a modern ODI middle-order accumulator. That is a tempo-setting innings, not a passive one. But his boundary share, his home-away splits, his twelve-month trend: none of it is stated. The analysis should stop there and go no further.

The real story is the clock, not the ball

The term "over-rate" is a misnomer. It is a time-rate. And on that measure both sides are culpable, because the fault belongs less to a team than to the match itself.

Nineteen wickets fell. Every wicket means a new batter walking out, taking guard, fields being reset, sometimes a celebration, sometimes a review. There was a debut innings — Saad Baig's 39 — which brings its own extra minutes. There was a 119-run partnership, which brings conversation, drinks, planning.

Every one of those seconds adds to the clock. None of them adds to the ball count. The innings ended at 49.5 and 48.1 overs. Fewer overs were used. More minutes were spent.

That is the weakness of the over-rate method. It measures time but does not separate the causes of time. A match with 19 wickets will always take longer. Both teams being penalised in the same fixture does not mean both delayed equally; it means the metric is measuring the match, not the team.

This is where data analysis most often fails. Heatmaps have become the new reading of tea leaves — they hide a player's real role inside the system, just as the over-rate hides the reasons a match ran long. Both compress a complicated reality into a single number, and the number is easy enough to read that nobody looks inside it.

The economics of a fine

Under the standard ICC framework, players are docked a set percentage of their match fee per over short, with the captain paying double. The report does not specify the percentage or the amount, and guessing would be worse than saying so.

One detail is worth pausing on. Saad Baig made his international debut in this match — 39 runs, first cap. In the same week, another sheet arrived in his hand: a fine notice. A young player's international career opened with two documents: a scorecard and a penalty slip.

In percentage terms everyone is docked equally. In meaning, they are not. For a player to whom every rupee or pound of a match fee matters, the weight is different. And a debutant fined for an administrative concept he did not cause carries a personal memory for life.

Does the fine change behaviour? In four decades around this game, the evidence that over-rate penalties work is thin. A problem that cannot be solved by punishment only produces more bookkeeping, not less time.

Where the number disappears

What will we remember from this match? Salman's 107 off 90. The 119-run stand. Shaheen's 3/55. The 37-run margin.

What will we not remember? The twenty-odd minutes both sides lost. The minutes they were fined for.

Collective memory holds the score, not the clock. The fine notice is the only official record of the time that went missing.

Modern cricket's economy runs on broadcast windows. An ODI is packaged into roughly three and a half hours. Step outside that frame and what is lost is not cricket — it is advertising. The over-rate penalty guards the frame, not the quality of the play.

That is not a complaint, it is a description. But it has a consequence. When teams know their time is being measured, they speed up — and what speeds up is not the bowling, but the field settings, the walk back to the mark, the tactical conversation. What the clock squeezes out is thinking time.

And notice this: both teams were penalised in the same match. Two teams guilty in one fixture usually means no single team was guilty. Nineteen wickets, a debut, a 119-run stand, and — unmentioned but likely — a review or two. None of those belong to one side.

What Rawalpindi actually taught us

First, the missing third team is not an editing slip; it is an analytical blind spot. The difficulty of a tri-series depends on the quality of all three sides. If the third team is a top-five nation, this 37-run win carries different weight. If it is a lower-ranked side, the tournament is effectively a bilateral series with a calendar-filler attached. The report gives us no way to decide.

Second, a dating caution. The piece says "Sunday, 18 October" but omits the year. 18 October falls on a Sunday in 2026 (and in 2026); in 2026 it fell on a Saturday. The date needs verification before being used as a fixed reference. Small thing — but in administrative reporting, small things become large.

Third, a myth to clear. A slow over-rate does not always mean deliberate time-wasting. In this match the wickets fell so steadily that there was little room to waste anything. The opposite happened: the game ended so quickly that two of the allotted overs went unused.

A match that used fewer overs than scheduled, in which both teams were found guilty of slowness — that is the central contradiction of the over-rate method.

Fourth, honesty about the result. Pakistan's win looked comfortable and was not. Sri Lanka were alive at 119 for the fifth wicket. What followed was a collapse of five wickets for under 50. Calling that Pakistan's strength hides the truth of the match: it was Sri Lankan batting failure, which made Pakistani pace look larger than it was. Those are two different things.

The clock, the anthem and the last ball

Walking out of the press box, the stadium was almost empty. Outside the gate a few rickshaws waited, phone torches were on, and a man was telling his son, "What Salman played today was worth watching." He was right. Nobody nearby was saying how long the match had taken.

That is the most interesting contradiction in this game. Before play we listen to two national anthems and remember them for years. We read the scorecard and remember it for months. The clock? Nobody remembers the clock — and yet the clock is the only witness to how long the match actually took.

An anthem outlives the score because it belongs to the people, not the scoreboard. An over-rate calculation outlives nothing, because it belongs to administration, not to the game.

Still, there is a lesson here, particularly for someone who watches South Asian cricket from Britain. We see the game through emotion — every match a festival, every innings a story. This match showed that the emotion has a price, counted in minutes. Nobody counts that price. It is only counted when the fines are issued.

The league table is a map, but the tunnel is where the territory cries. On the table, Pakistan have two points and Sri Lanka none. In the tunnel there is money docked from two sets of match fees, a debutant's first fine, and an incomplete tournament whose third participant remains unnamed.

What to watch next. Whether the over-rate stays controlled through the rest of the tri-series is a genuine indicator. If both teams are fined again, the problem is the method. If only one team keeps appearing on the sheet, the question turns toward them.

The last ball is not a full stop; it is a paragraph break. The Rawalpindi match ended in 98 overs, but its accounting has not closed — because the time nobody wrote down is now speaking loudest.

Next time the floodlights come on, watch the clock rather than the scoreboard. That is where the real match is being played.