Block Fifteen: What a Hand-Coded Ledger Reveals About Where a T20 Match Changes Its Mind

On 29 June 2026, at Kensington Oval in Barbados, the floodlights came on and the scoreboard read India 176/7. South Africa's chase rolled on; at the end of fifteen overs they were 147/4, needing thirty runs from thirty balls. The set batter, Heinrich Klaasen, was unbeaten on 52 from 27. From the commentary box came the familiar phrase — 'now the death overs.' In the spiral notebook in my hand, a different column was glowing. I had written: this match was not decided in the last five overs. It was decided before them.

India won by seven runs; the International Cricket Council (ICC) later named Virat Kohli's 76 from 59 balls as Player of the Match. The result is correct. My ledger said the broadcast aimed its camera at the moment of decision far too late.

I began with a hand-coded ledger, and the numbers learned to confess. In 2026 I left a thirty-one-year desk at a Khulna daily and started charting the Bangladesh Premier League by hand — 66 matches, coded alone. Nobody knew. After every major tournament I still write over by over in a spiral notebook and re-watch old streams at two in the morning to check the entries. When new-media outlets asked for numbers, I emailed the ledger free of charge; nobody knew whose 'Khulna numbers' they were.

The 2026 ICC Men's T20 World Cup produced 55 matches. I broke every match into over-blocks. Each block holds the venue, the date, the bowler, the batting pair, the field setting, runs, wickets, dot balls, and a pressure index I calculate myself. Every block carries the state of the block before it, exactly as each block in a blockchain carries the previous block's hash. I cannot rewrite the past; if I find an error, I leave the old block intact and append a correction block. That is the discipline of the method — evidence, not verdict.

The first thing the ledger caught was the timing implied by the phrase 'death overs.' In T20 cricket, fielding restrictions end after the sixth over; no new rule begins at the sixteenth. Yet commentary, writing and debate turn the sixteenth into a 'gate of death.' In my count, 22 of the 55 matches at the 2026 World Cup were won by the side batting second. In 15 of those 22, the chasing side's win probability crossed fifty per cent before the fifteenth over. By the time viewers thought the game was 'starting,' the match had already changed its mind.

The clearest signal in my ledger is a line of required run rate — roughly 10.5. If, at the end of the twelfth over, the chasing side's required rate sits below 10.5, they go on to win about four matches in seven. If that rate climbs above 10.5, the win rate falls to roughly one in three. I call this line the cricket version of the sixtieth-minute mark; the sixtieth-minute line is not a statistic, it is where matches change their minds.

The second signal concerns the type of wicket. More wickets fall in the last five overs — everyone knows this, because batters take risks. But my ledger has a separate column: the 'decisive wicket,' the one whose fall drops win probability by more than twenty percentage points at a stroke. In 14 of the 22 successful chases, that decisive wicket fell between the thirteenth and sixteenth overs, not in the final two. The departure of the batter who had set himself is usually the real hinge. In Barbados that batter was Klaasen; the way the required-rate line steepened either side of his exit was already visible in my twelfth-over column.

The third finding concerns the distribution of pace bowling. In my hand-coded count, sides that saved their best death bowler for the last two overs succeeded in more than 70 per cent of cases in that tournament. For India, that bowler was Jasprit Bumrah, who took 15 wickets at the tournament and conceded only 4.17 runs per over. The number is handsome; in my ledger what mattered was which overs he bowled, not how few runs he gave. Three of the last four overs were left in his hands — that decision was the blueprint of India's title.

The fourth finding concerns the rhythm of the field setting. Between the twelfth and sixteenth overs I tracked who was bowling and which batter stood before him. In successful chases, 68 per cent of the time the bowler used after the twelfth over was someone who had bowled at most one over earlier in the innings. Sides were saving not two overs but three or four. That saving is what produces the final scene.

Here I have to stop, because correlation is not causation. The fifteenth over is no magic line; it is a narrative convention. What my ledger shows is that the real shift comes from two things meeting — the required rate crossing 10.5, and the fall of the set batter. When both happen together, the match tips; the over number alone does nothing. Analysis that only says 'the death bowling was good' hides the actual cause.

The second caution concerns format. Franchise cricket has introduced the 'impact player,' effectively giving a side an extra batter. Just as the five-substitute rule in football hands big clubs an edge in the final twenty minutes, the impact player does the same in cricket — it rewrites the arithmetic of the closing overs. A number from one league cannot simply be pasted onto another; in my ledger I keep league blocks and international blocks separate.

The third point is one nobody wants to write. Distance covered, ground covered, 'high-intensity sprints' — these measures get passed off as proof of effort. From years of watching, I can say much of that running meant nothing; pointless running also produces pretty numbers. So in my ledger I do not record distance alone; I record the field setting the run was made against and how tired the bowler was beforehand. And on injured players I am always careful: the media only receives what a club or board chooses to disclose, so beside the words 'fit' or 'absent' I always place a date, so that anyone can check it later.

At sixty-nine I trust slow numbers more than loud ones. In this regular season my next watch is not the sixteenth over but the twelfth — where the required rate stood at its close, and which batter was still unbeaten. Silence has a grammar, and empty stadiums taught me to parse it; every over has a grammar too, readable only by those who write it down patiently. I am a data monk; I sweep the same columns until they become prayer. The question is not for tonight but for next season: will you remember the result of the match, or the over in which the result was written?

— What I missed: Before the 2026 World Cup final I built a fatigue curve for Croatia and predicted France would take the midfield after the sixtieth minute. France won 4-2; I had the window right and the sequence wrong. The correction block for that error stays in the ledger to this day. I never erased it.