The Dot-Ball Ledger: A 2026 World Cup Audit and the 2026 T20 World Cup Sample Threshold

On 7 November 2026, in Mumbai, Afghanistan made 291. Australia slid to 49 for 4, then 91 for 7. From that rubble, Glenn Maxwell made 201 not out from 128 balls — 21 fours, 10 sixes. The television cameras kept showing the cramps in his back. My laptop kept showing a column I had opened and named dot-ball pressure.

For the first 40 matches of the tournament I had written a rule into the ledger: more dots in the middle overs means fewer wins. That night the rule did not break. It bent. Maxwell's first 45 balls were patience; his last 83 were storm. Collapse those two phases into one number and the data lies. And when data lies, the fault is not the data's; the fault belongs to the reader who saw the scorecard and never saw the ball.

Context: format, method, and where my ledger began

The 2026 ODI World Cup ran from 5 October to 19 November across ten Indian cities. Ten teams, a round-robin league, nine matches each — 45 league games, two semi-finals, one final. The format is merciless. In a football World Cup a mis-timed draw can hide a lot in the group stage; here nothing hides. Nine matches pull your real shape out of you.

India won all ten league games, something no team had done before in a World Cup. Australia lost their first two, then won nine in a row, reached the final, and on 19 November in Ahmedabad beat the hosts by six wickets for a sixth title. Bangladesh finished eighth, with two wins (Afghanistan and Sri Lanka) and seven defeats.

Every audit I run begins with the two questions I have written into every memo since 2026: who recorded this data, and when? In ball-by-ball files, labels like 'dot ball', 'pressure ball' or 'field concession' are applied differently by different providers. Until you know which provider counts a dropped catch as pressure and which does not, placing two tables side by side is placing two different sports side by side.

The roots of the method are in football. In 2026, at 54, working at a transfer desk in Manchester, I built an xG-PPDA matrix for Premier League midfielders. It put Ross Barkley's 0.12 xG per 90 and 8.7 pressures per 90 into the flagged column, and I wrote a memo against a 15 million pound bid. The desk ignored it; Barkley made only two starts in his first half-season. Since then I have held one habit: I do not write an 'obvious' talent claim without at least 900 minutes of evidence. In cricket I translate that into a minimum of 300 balls faced by a batter, 600 balls bowled by a bowler, and at least five different opponents.

At the 2026 World Cup in Russia, the same method put me on a broadcast data desk. In the final, N'Golo Kante was substituted on 55 minutes; I showed it was France's defensive block, not individual dominance, controlling the match. The post-match data reconstruction drew 200,000 reads and silenced a press-box critic who had said women do not understand tactics. The 2026 audit did not argue; it simply left the critic no row to stand on.

In 2026, working on the Bundesliga restart in empty stadiums, I found the home-win percentage fall from 43.3 to 33.3 in the first five rounds. That was 45 matches. I wrote about it, and I wrote that the sample was small. Clubs wanted crowd-effect models; I refused to overclaim. The empty stadiums taught me one lesson: bring more sample or bring silence. Behind-closed-doors Tests and T20 leagues deserve the same discipline.

That is the condition under which this audit is written.

The core analysis: the middle overs are where tournaments are written

I split an ODI innings into three parts — the powerplay (1–10), the middle overs (11–40) and the death (41–50). In the first ten overs only two fielders are outside the circle, so finding boundaries is easier. In the last ten the batter must take risk, so wickets fall faster. But overs 11 to 40 — those thirty overs, with five fielders out and spinners operating — are where the real arithmetic of a match is produced.

After re-running the ball-by-ball files from all 45 league matches of the 2026 World Cup, one pattern came out simple and uncomfortable: teams whose dot-ball percentage in overs 11–40 sat below 42 won roughly 70 percent of their matches; teams above 50 percent won under 30 percent. A dot ball does not concede runs, but it builds pressure for the next ball — the fielders press up, the batter chooses a worse shot, the wicket falls.

That is why I built the dot-ball pressure column. Here a 'dot' is not merely an empty ball; it is a ball that forced the batter to hunt for a boundary off the next one. Count only dots and you know half the story.

India's 10-0 league record was not produced by batting fireworks alone. Virat Kohli made 765 runs in the tournament, a record for a single World Cup. But in my ledger the bigger fact is that a large share of those 765 runs came in ones and twos; he did not gamble on fours and sixes, he rotated strike. In the middle overs, with fielders out, regular one-and-two rotation is what keeps the dot-ball percentage down. Kohli's strike rates in his unbeaten innings were not spectacular to the eye, but his dot-ball percentage was among the best in the tournament.

With the ball, Mohammed Shami took 24 wickets, the most in the tournament. Shami's real contribution, though, was not in the wicket count but in pressure. At his length, a batter driving risked an edge and a batter defending produced a dot. To measure a bowler's true value I keep a second number beside the wickets: the opponent's run rate on the ball after his delivery. That number is cricket's version of football's PPDA — a measure of how much discomfort is being created.

Now back to Maxwell. Sliding to 49 for 4 meant no recognised batter at six; Maxwell walked in and played his first 45 balls almost in silence. He understood that if a wicket fell the team lost, and that dots keep a team alive. That innings was really two innings: one of patience, one of assault. An analyst who sees only the final 201 and writes 'power hitting wins' has skipped the first two-thirds of the match.

Bangladesh's audit is harder because the problem is plain. The six-wicket win over Afghanistan in Dharamsala on 7 October and the three-wicket win over Sri Lanka in Delhi on 6 November showed a middle-overs ledger that was civil. In the other seven matches, the run rate after the powerplay fell so far that the last ten overs demanded an impossible equation. Mahmudullah's 111 against South Africa in Mumbai on 24 October came in a losing cause, and its tempo was slower than the match required.

One thing must be said clearly, because it is repeatedly got wrong in Bangladesh discourse: a batter's strike rate is a compound number, and Bangladesh's problem is not strike rate; it is ball-by-ball compression. A batter who makes 18 off 20 has a strike rate of 90; but if 11 of those 20 balls were dots, that is a bigger loss than the strike rate suggests, because he released the opposing bowler from pressure.

To catch that gap I use a simple index: the ratio of dot-ball percentage to boundary percentage in an innings. In the 2026 World Cup the top four teams held a middle-overs ratio between 2.1 and 2.4; Bangladesh sat above 3.3. That single number explains why, chasing 300, Bangladesh always look like they need 350.

The 2026 T20 World Cup did not break this formula; it sharpened it. On 29 June in Barbados, India made 176 for 7 and South Africa finished on 169 for 8 — India won by seven runs. Heinrich Klaasen made 52 off 27 and still lost. Why? Because of the mix of dots and wickets in the last three overs, where Jasprit Bumrah's 2 for 18 in four overs and the day's best pressure balls turned the match. Bumrah was player of the tournament with 15 wickets, but his real weapon was economy, not aggression.

Afghanistan's rise belongs to the same ledger. They reached the semi-final of the 2026 T20 World Cup, and it was possible because their bowling unit could bank dots in the middle overs. Rashid Khan's wicket count catches the eye, but the structure was built on holding the same pressure from start to finish. A team becomes durable only when its dot-ball percentage on its worst day is not far worse than on its best day.

The contrarian angle: correlation is not causation

The easiest wrong conclusion from this audit is: play fewer dots, win more, so buy power hitters. I fear that conclusion, because it repeats the 2026 memo in which a matrix flagged a player and the desk believed data meant decision.

The truth is that dot-ball percentage and winning are correlated, not causal. A team batting well naturally plays fewer dots; a team facing good bowling naturally plays more. In both cases the dot is an outcome, not a cause. If you bring in an aggressive batter purely to reduce dots, without improving strike rotation in the middle overs with fielders out, you will not reduce dots — you will increase wickets.

The second danger sits inside the strike-rate debate itself. Pitch, opposition, match state — compare strike rates without those three and the comparison is meaningless. The Ahmedabad final pitch in 2026 was slow; Travis Head's 137 is history now, but declaring India's middle order a failure on the same surface is a denial of that surface.

The third point comes from 54 years at a desk: transparency in injury information never really arrives. Just before a tournament or an auction, whatever surfaces about a fast bowler's workload or a senior batter's fitness is usually curated. Boards and franchises decide which injury is shown and which becomes a 'personal reason'. So one column of your table will always be incomplete — until medical data is fully protected and selection is fully independent.

The fourth danger is my own habit: sample-size purism. 'Bring more sample or bring silence' is a good discipline, but it can become an excuse for long silence. So now I publish an interim uncertainty note in every major series, separating provisional signal from final verdict.

And there is a question I keep asking myself: what did cricket learn from the empty stadiums of 2026? In the Bundesliga, home advantage fell because part of the pressure comes from the crowd. In cricket we talk loudly about 'spin-friendly pitches' and 'home conditions', yet the behind-closed-doors Tests of 2026–21 showed the big difference was being made by bowlers' routines and crowd pressure, not by the character of the pitch. Bring more sample or bring silence — that line is even truer in cricket, because in cricket one toss can change a pitch's fate.

Takeaway: the ledger to watch for 2026 and 2027

The ICC Men's T20 World Cup 2026 will be held in India and Sri Lanka from 7 February to 8 March 2026 — 20 teams, 55 matches. The 2027 ODI World Cup will be in South Africa, Zimbabwe and Namibia with 14 teams. Both formats are expanding, which means more sample, which means more of my own agony — because every glimpse from a small series will now be tested on a bigger stage.

At sixty-three I still trust the ledger more than the highlight reel. So my next target is specific: Bangladesh's dot-ball percentage in the middle overs (overs 7–15 in T20 format) across their first six matches. If it drops below 38 percent without the wicket rate rising, structural progress can be claimed. If dots fall but wickets rise, only the shell has changed, not the structure.

I leave one question, because I have never met a narrative that survived a clean, audited CSV file: in a twenty-team tournament a smaller side will produce a surprise — but will it be the surprise of one match, or the surprise of one system? To know that I need at least ten matches, five different opponents and one clean ball-by-ball file. Until then, no verdict.