Babar Azam: 118 Runs, Four Starts, Zero Fifties — the Coach's Defence and the Three Numbers the Release Leaves Out

A media release carried fifteen information points.

I counted them. Three numbers, four quotations, the rest interpretation. The three numbers: four innings, 118 runs, zero fifties. The three absentees: strike rate, mode of dismissal, venue, opposition — and the format itself.

I do this count because it has become my most useful habit over the last few years: reading a release first by what it leaves out. In the report on Babar Azam, the missing number is the answer to the question. 118 runs in four innings tells you runs are being made. It does not tell you how he was getting out. And in a four-innings sample, mode of dismissal is the only piece of information that can separate form from coincidence.

The headline says: no concern. The number says: four starts, zero fifties. Put the two side by side and the first sentence becomes the conclusion of the second, not its alternative.

Context: what the release is about, and what it is not

A tri-series is underway, Pakistan are unbeaten in it, they are looking towards the final, and Tuesday's contest remains. The only live ball in the release is this: the team's batting coach faced the press on Babar's form and dismissed the question.

I was not at any match of this series. That must be stated, because my entire method rests on writing what I have seen and not writing what I have not. This article rests on two things — that release, and my 214 digitised notebooks, which carry my own logged notes on Babar's nets sessions and past matches. Ground, pitch behaviour, breeze and dew, the toss — not one of those facts appears in the release. Analysis conducted without them is inference, not reporting.

So the arithmetic here runs on two tracks. The format is not stated, and a four-innings sample is small in either limited-overs format — but the benchmarks differ. An analyst who merges them has already lost his own scale.

The numbers that are there, and the ones that should have been

Four innings, 118 runs. If he was dismissed in all four — and the release does not record any not-outs — the average works out to 29.50. For a top-order batter, the accepted white-ball marks sit above 45 with a strike rate above 90 in ODIs, around 35 and 135 in T20Is. 29.50 is below the mark on either track. But a four-innings average is not a batter's average; it is a batter's weather.

The real number is the half-century. Zero from four. Conversion for a top-three batter runs at roughly one substantial score every three innings. Here the rate is zero — and that is the only hard fact in this entire report. Everything else is commentary on it.

Now the three things not supplied. First, strike rate; without it, there is no way to establish whether the 118 runs were made slowly through the middle overs or quickly. Second, mode of dismissal — the single most diagnostic field, and the biggest omission. Third, the quality of the opposition attack, because 30 runs against a spinner on a turning surface and 30 against a quick on a flat one are not the same innings.

All three are missing. And all three are precisely the fields that would have settled the argument. That is not accident. A report whose conclusion is fixed before its reasoning gets attached will not carry the numbers that could challenge the conclusion.

A ceiling locked in by arithmetic

One thing the release does not state, the mathematics does. Zero fifties in four innings means, directly, that Babar's highest score in this tournament is under fifty. He did not pass 49 in any innings. That is not opinion; it is arithmetic. And it is the sentence that cracks the frame of the defence, because the coach's argument rests on "the starts are happening" — and the top end of a start is exactly where these innings are ending.

There is a second side to it, less discussed. Starting every innings is itself information. The first ball, the swing of the new ball, the pressure of the first two or three overs — that is the zone where top-order batters fall most often, and on the subcontinent that phase becomes decisive before spin even arrives. Babar cleared that phase four times out of four. That is genuinely good news and it cannot be dismissed.

The difficulty is that the good news stops there. The next phase — rotating strike through the middle, working the spinner to the feet, unlocking the middle overs — has no data attached to it in the release. And that is the exact phase in which fifties are made.

Treating two team wins as a guarantee about one batter

At the centre of the coach's case is the team's unbeaten record. That argument seems to me wrong at the level of analysis, and it is not a small slip.

A team being unbeaten and an individual batter converting are two separate variables. A side can win while its premier batter is in the dark, provided the other batters are scoring or the bowling is carrying the match. That appears to be exactly what is happening here. Pakistan are unbeaten and Babar has no fifty. The most direct inference is that the runs are coming from elsewhere.

That is good for the team and bad for the defence. The very fact being used to protect the batter is telling us that there is no evidence from that batter's innings to protect him with. A team scorecard cannot be a witness to individual conversion.

It should be added that the release carries not one figure for any other Pakistan batter. Who made the runs, who won the match, which position contributed — nothing. Which means even "the runs are coming from elsewhere" is an inference, not a stated fact. A strong inference, but an inference.

An answer to a question nobody asked

In one line the coach said that had one of those four innings been converted into a century, this discussion would not exist.

It sounds solid. Look closely and it answers a question nobody put. Nobody said Babar is not scoring hundreds. What was asked was simpler: why not one fifty in four innings. A century in four games is a high bar even for a top-three batter in a tri-series. The old move in argument is to make the question harder, answer the harder question, and imply the original question was absurd.

The same release carries another line, and it is the weakest link in an otherwise partly defensible case: those who understand the game can see how well he is striking the ball.

That sentence cannot be verified. No ball-striking data accompanies it, no field map, no over-by-over detail. "Those who understand the game" is not a category; it is a status the speaker confers on his listeners, and through which he rules dissent out of order.

I will put it plainly: if Babar is genuinely striking the ball well, proving it is not hard. Strike rate can be quoted to two digits. Boundary percentage can be quoted. The zones in which the shots were played can be named. None of it arrived. And where the evidence does not arrive, the sentence gets louder.

My notebook holds half of that argument

In October 2026 in Ahmedabad I watched two of Babar's nets sessions, and what I wrote that day has come back into this argument in a strange way. For the first ten or twelve minutes he played straight-batted, on straight balls, without risk. The aggression came later, and when it came it was built on that quiet phase. What the coach is calling "getting established" is in my notes too. He did not invent it.

So one part of the coach's case is data-supported. That must be conceded. Four starts are not four zeros. They are four proofs of clearing the first hurdle. A batter dismissed four times for two has a technical crisis, and a deep one. A batter dismissed four times in the twenties and thirties has a problem in the upper middle of the innings, not at the base.

But my notebook says nothing beyond that. And here my second rule applies, the one I built on the Rajkot beat in 2026, filing nets notebooks for forty-one consecutive days: anything seen at training requires two sources — the player's own words, or a coach's confirmation. Never an agent's.

On this standard there is one source. The coach. And an interested one. Not a single sentence from the player himself appears in the release. When the sole witness is a party to the case, a report is obliged to say that the witness is one.

It took me ninety nets sessions before I trusted the app, and here the situation is inverted — a claim that no device, no data desk, no tracking app is following up. When trust starts speaking in place of data, my habit is to start counting. Three numbers, four quotations, the rest interpretation.

A former captain is measured on a different scale

One thing here is institutional rather than technical. Babar is a former captain. Every score a former captain makes is read through the lens of internal politics. When he scores, it becomes a sentence about leadership; when he does not, the sentence doubles in length. A batter without that status does not get this much coverage on identical numbers.

The direct effect is that the pressure generated in this tournament is larger than his numbers. The fact that the coach is sitting in a press conference explaining that four innings mean nothing is itself a signal. Coaches are not asked about form that is not being questioned outside.

And the absence of format is not merely an editorial lapse. It is a condition of the analysis. Four innings in T20I and four innings in ODI are not the same object, because 118 runs in T20I is a different story entirely — there, 118 runs across four innings is not an average of 29.50, it is a strike-rate conversation. A report that will not name its own format is telling the reader to pick his own scale. The reader will pick one, and it will not be the report's.

Both outside readings are wrong

Now the part that irritates me most, because it is the easiest road.

One camp says: no fifty in four innings, so there is a crisis. The other says: no concern, the big score is coming. Both make the same error. Both draw a firm conclusion from a four-innings sample, when four innings cannot support a firm conclusion in either direction.

My habit is to weigh any form claim on a ten-to-fifteen-innings window. Since last March I have kept a ledger — every pre-match technical claim, dated and signed, reviewed each March. That ledger has taught me two things: to be slower about big claims, and to record the times the app was right and my eye was wrong.

Tempo is what remains once the noise has been subtracted. There is a great deal of noise around this — in the subcontinent a star batter's form is always a larger subject than the numbers, because cricket here is not only a sport but a conversation. Treating a four-innings sample as a trend is an old local problem. The tempo exists in one place only: what the mode of dismissal looks like over the next two innings.

One further institutional point, and this one is my own trade's weakness. This report came from the ICC's own editorial channel, and its headline adopts the coach's conclusion. A reader who stops at the headline has received an interpretation, not a fact. The fact was four innings, zero fifties. The headline became no concern. On two thousand screens that is a report; in the transparent moment of a press conference, it is in effect a PR document.

The three things the next week will decide

The claim I would enter in that ledger is not about the runs. It is about the type of delivery.

Watch how he is dismissed in the next two innings. If the dismissals are clustering in one zone — the new ball, or spin, or playing around the front pad — then four starts and no fifty is a technical deficiency, and its remedy is in the nets, not at a press conference. If the modes are scattered and the runs are coming at pace, this is variance and it will correct itself across the next four games.

Pitch behaviour is worth the same attention. Flat subcontinental surfaces compress the gap between good and ordinary batting. If this series is being played on such pitches, 118 runs looks thin, because the conversion rate there should be high. If the surfaces are seamer-friendly, the same 118 runs reads better. I do not know which case applies, and when I do not know, I do not write.

The sharpest question is a selection one. Two or three more innings without a substantial score, and this team management will not be facing a form question — it will be facing a selection question. The "zero doubt" line the coach has put on the record is a prediction, not a tribute. A prediction on record becomes the management's judgement if it lands and the management's liability if it does not. The scale is one-sided: little gain for being right, a large cost for being wrong.

Takeaway

Babar's 118 runs are the fact nobody will remember in a week. What will be remembered is the first movement of his bat in the next two innings, and what follows it — a fifty or a dismissal on twenty-two — will tell us whether this series broke his form or merely gave him a small sample.

The notebook went to a screen; the rhythm stayed on paper. The three numbers missing from the release — strike rate, mode of dismissal, opposition — will show up next week not in a news report but in a batter's footwork. The final is on Tuesday, but the real examination of this form begins after it, and it will not need to be imitated. It will only need to be counted.