Babar Azam's Form: 118 Runs, Four Starts, and a Question the Data Cannot Answer

Three numbers were on the table. One: 118. Two: four. Three: zero. Babar Azam has 118 runs from four innings in the ongoing tri-series, and not one half-century among them. Pakistan are unbeaten in the tournament and moving towards the final. Ahead of Tuesday's fixture, the batting coach stated plainly that there is no concern about Babar's form.

The third number — zero — travels fastest. But the second is just as real and drew far less attention. A start in all four innings. Four out of four. Not once did he fall cheaply to the new ball. That is the line that separates a good player from a struggling one, and the coach leaned on it hardest in his defence.

I left a print desk for the numbers and the numbers led me here. The central problem with this story is that the three figures that would settle the question — strike rate, dismissal modes and opposition quality — are precisely the three the report does not carry. What follows is an audit, not a verdict.

Context: what the series is, and what we are not told

Start with the frame. This is a multi-nation tri-series, not a bilateral, and not an ICC event. A mid-tournament press briefing on one batter's form tells you the management is taking the fixture seriously. The value of regular-season coverage is exactly this: picking up the threads before the final turns them into headlines.

Now the absences, because they shape everything.

The format is not stated. ODI or T20I, the report does not say. "Half-century", "four knocks" and "getting established at the crease" sit equally comfortably in either. That means Babar's 118 cannot be weighed against a single benchmark. An elite top-order ODI average sits around 45-plus; the T20I equivalent around 35-plus. Merging them would be the exact error this framework exists to prevent.

Opposition, venue, pitch and date are missing. The only scheduling marker is "Tuesday's contest". That matters. On flat subcontinental surfaces 118 runs in four innings reads worse; on a seaming or drop-in pitch, four starts read considerably better. I do not know which case applies, so I keep both open.

Methodology box Source: ICC published report (team briefing plus coach quotes). Sample: four innings, one player. Hard data available: 118 runs, zero fifties, a start in every innings, best score under 50. What the model cannot see: strike rate, balls faced, dismissal modes, pace/spin splits, home or away.

Before trusting a model I rebuild it from the raw match feed. Here there is no raw feed. So the analysis that follows measures the gap between three hard numbers and one set of assertions.

The evidence chain: what 118 runs prove and what they don't

The first calculation is the simplest. 118 runs across four innings. If all four ended in dismissal — and the report does not say whether any were not out — the average is 29.50. That is the number that raises a selector's eyebrow, because a top-order batter claims far more. But the caution is immediate: an average over four innings is not a statistic, it is an accident. One large score and the same average clears fifty. Four innings to an average is four days of weather to a climate.

The second calculation is more interesting. Zero fifties in four innings. A top-three batter's conversion rate is usually taken as roughly one fifty in three innings. At that rate, the probability of four straight sub-fifty scores in any four-innings block is (2/3)^4 = 16/81, about 19.75 percent. One in five. If you take a more realistic one-in-four conversion, the probability rises to 31.6 percent.

That is the most important number in this entire debate: an elite batter has somewhere between a one-in-five and a one-in-three chance of a zero-fifty four-innings block purely by variance. Which means zero fifties is not, on its own, evidence of technical decline. And it also means it is not proof of the absence of decline. Probability and evidence are different things, and this debate keeps swapping them.

The third calculation is one the report never supplies. 118 runs off how many balls? At 85-90 balls this is a batter scoring quickly and getting out to a poor shot. At 150-160 balls it is the opposite profile — occupying the crease and slowing the team. Those two pictures are not interchangeable. Without balls faced, any claim about strike rate is an estimate, not a measurement.

The fourth, and the most diagnostic, is entirely missing: dismissal mode. Four different modes — caught at cover, bowled to a slog sweep, run out, caught at point — points to a batter in form making poor choices. Three of four to the same mode, say against one spinner or against the new ball, points to a technical fault that no number of starts can offset. The report allows neither reading.

The fifth is a team-level fact that gets overlooked. Pakistan are unbeaten while their premier batter has no fifty. The direct reading is that runs are coming from elsewhere. Good for the batting ecosystem. But for the coach's argument it cuts the other way: team results in a side not dependent on Babar are weak evidence about Babar's form.

The level-of-analysis error

The coach's reasoning is simple and emotionally effective: the team is unbeaten, Babar is getting set every innings, therefore form is not an issue. There is a structural flaw worth naming. A team result is a sum — bowling, fielding, other batters' runs, opposition errors. Individual conversion is a separate variable. Team unbeaten-ness tells you nothing about an individual's conversion.

Using a team's unbeaten run as evidence about an individual's form is swapping the answer to one question for the answer to another.

I go back three years, to when I was modelling death-over economy in the IPL and a television analyst dismissed the work on air as spreadsheet cricket. I published the methodology footnote the next morning and kept the column. Since that day every claim I make carries its sample size. That rule is what forces me to say here that the coach's claim rests on a sample — four innings — smaller than the claim itself.

The century counterfactual that changes the question

The coach's sharpest line was this: had one of those four innings become a century, this conversation would not be happening. As rhetoric it works. As logic there is a sleight of hand. The question being asked is not about centuries. It is about fifties. For a top-order batter, one fifty in four innings is not a controversial bar. A century is a far higher bar, and using it to dismiss criticism is like telling a student that complaints about 60 percent are invalid because they did not get 95.

The coach answered a stricter question than the one asked. It is an effective technique — pull the debate to a higher standard where failure is guaranteed, then present the failure as vindication — and a common one in press briefings.

The unfalsifiable claim

The weakest sentence in the whole briefing is: those who understand the game can see how well he is striking the ball. There is no number attached. No sweet-spot map, no intent-stroke percentage, no boundary-contact rate. A claim that cannot be disproved is not evidence, it is a posture.

When expected-goals-style imports arrived in cricket, one thing became clear: before trusting the model you rebuild it from raw data. Here the raw data does not exist. So I can neither accept nor reject "striking the ball well". I can only note that it carries no weight in the argument.

What "former captain" actually means

The report calls Babar a former captain. That is analysis, not biography. A former captain is judged on a different baseline — every innings is read alongside leadership, a question about his form becomes a team-management story by default, and the reaction to identical numbers is amplified relative to a team-mate. That is invisible in any scorecard, and it is why a four-innings sample becomes a national debate.

Two doors stay open

If Babar's four dismissals cluster against one bowling type, that is a technical issue and under-rating it would be a mistake. If they are spread across modes and styles, with a healthy strike rate, it is variance. One scenario demands a decision and the other demands patience, and the source gives us no way to tell them apart. When the narrative outruns the data, I slow the article down. This is where it slows.

Contrarian: the obvious conclusion is correct, and the bigger question is elsewhere

Let me state the boring consensus plainly, because it happens to be right. A four-innings dry run happens to every great batter, and reading it as a trend is over-reading the data. The coach is defensible by default. Four starts really is a positive leading indicator, and he is a victim of a media habit that counts hundreds and ignores starts.

But the real knot is not statistical. It is about accountability.

"Zero concern" and "a big score is imminent" are not just encouragement. They are predictions on the record. And the cost-benefit is asymmetric. If Babar scores heavily in the final, the coach gets little credit — people will say it was always going to happen, he is Babar Azam. If Babar falls cheaply in the final and the pattern repeats into the next assignment, the story stops being about Babar's form and becomes about the coach's quote.

What the management has done is fix its public position and pay for it with selection flexibility. If Babar has to be dropped or reordered, that is a direct rebuke of the briefing. I saw this several times on the print desk: a management defends a player in public and later the defence becomes the story rather than the player.

The second knot is statistical. The loudest number — zero fifties — is being asked to carry more weight than its size supports, while the most useful number — a start in four out of four — appears in no graphic.

The spreadsheet did not settle the argument; it gave us a better question — is this variance, or something the rest of the team is currently covering?

That question matters most in a knockout. Pakistan have been reaching competitive totals without a Babar fifty. In a final the bowling gets sharper, the run-rate pressure rises, and a 25 off 35 at the top has to be absorbed by the middle order. Group games absorb it. Finals often do not.

Takeaway: three things to watch in the final

I will not be watching the total. I will be watching the first twenty balls — does he leave the new ball, is the front foot moving, is he forcing the bowler to change his line. Second, if he is dismissed, how. That single field decides whether this is technique or time. Third, where the team bats him; the batting position is the selection signal about internal confidence.

The question I am left with does not come from the data. If Babar is out for nought in the final and Pakistan win, was the coach right or wrong? The result says win, the process says loss. In this sport we routinely let the result pardon the process. The argument over four innings and 118 runs is really pointing at that, and no scorecard will ever record the answer.