I Opened Cricket's Ledger: Three Results the Scorecard Never Settled

Hook

On 14 July 2026, at Lord's, the scoreboard read England 241, New Zealand 241. The Super Over ended 15 apiece. Then one line of fine print — the boundary countback. The word 'champion' settled next to England. I was in Delhi, not watching as a fan but keeping a ledger. In my notebook I wrote one sentence: a settlement was reached; the truth was not.

That sentence is the most expensive lesson of my working life. A settlement and a truth are not the same thing. Someone hands down a ruling, but the debt is never cleared — and in cricket this happens every week, every series, every rain-shortened night, every selection meeting. We file the ruling. We never file the debt.

I am 69. Since 2026 I have written results down by hand — first in notebooks, then spreadsheets, now a database. I began on a football desk and built a career in cricket. As an ISTJ, I keep one rule: an entry without a source does not enter the ledger. Today I am opening three unpaid entries.

Context: how the ledger is actually written

A cricket ledger has four columns — result, margin, net run rate, and revised target. The last is the least discussed and the most productive of results. The method Frank Duckworth and Tony Lewis introduced in 2026 was a resource table: it priced the asset of wickets and overs in hand. Steven Stern revalued it in 2026. The method is not a prophecy; it is an arithmetic settlement. But audiences read it as prophecy, and then build an emotional politics on top of it.

When I joined The Daily Star's sports desk in 2026, I was taught that the first sentence of a report should contain a number. A senior editor used to say, 'You can pick a team with love, but you cannot write a report by picking a team.' In 2026, standing as the BCB spokesman during the Ashraful disciplinary affair, I learned that if you get one sentence wrong, a whole country treats it as fact. The arithmetic has to be balanced before the sentence is written.

Bangladesh-India series are the best illustration. On 26 December 2026 in Dhaka, Bangladesh beat India in an ODI for the first time, by 15 runs. On 17 March 2026 in Port of Spain, they beat India by five wickets at the World Cup. In June 2026 at home, they won the series 2-1. Those three entries are firmly recorded. Between them, however, information has been lost — and that is the account I am balancing today.

Core: three unpaid entries in the ledger

Entry one — the rain clause.

The first great rain settlement in international cricket was the semi-final at Edgbaston on 17 June 2026. Australia and South Africa finished level, and Australia advanced to the final on net run rate. The ledger read: tie; Australia through. But was the match a tie? The scores were level, yet nobody that night could say who had won it. The ledger said the process had decided. That is the first lesson of the rain clause: when we do not know the outcome, we pass the process off as the outcome.

What happened in Dhaka in June 2026 was another version of the same clause — created not by water but by an absence of information. On 18 June 2026, in the first ODI, Bangladesh won by 79 runs, with debutant Mustafizur Rahman taking 5 for 50. Three days later, in the second ODI, he took 6 for 43 as Bangladesh won by six wickets; the series ended 2-1. India won the third match by 77 runs to salvage pride.

So what is the unpaid entry? India's batting line-up had no prior ODI data on Mustafizur. No ball-by-ball sample, no sprint data, no rotation data on the slower cutter. In India's team meeting before the series his name was a blank cell. And in cricket the blank cell is the most expensive asset there is. An absence of data is not a neutral state; it is a pricing error. I call it the no-data premium.

When I opened the 2026 ISL rumour ledger I found a debt still unpaid: the player Kerala Blasters were building headlines around had only 1,412 minutes of football in the previous 18 months. That is a football story and I will not drag it across into cricket — the sampling rules differ, the physics of the ball differ. But the method is identical: look at the birth certificate of the data, not the claim.

Entry two — the bowler's debt.

Mustafizur took 11 wickets in that June 2026 series, in his first two matches. The ledger recorded: Bangladesh won 2-1. What it did not record was the bowling workload debt. He was 19, had barely any domestic or A-team load on record, and was being summoned on a national calendar that rang the bell continuously. That debt was serviced over the following two years — injury, rest, broken rhythm.

Cricket's ledger has no column for bowling workload. It has runs, wickets, economy. It does not have 'how many overs has this bowler sent down in the last six weeks.' So when we record a series win we write 2-1 and never balance the body behind it.

Part of the blindness is that we have learned to measure a batsman's workload and never a fast bowler's — because a fast bowler's workload is not an insider topic, it is an outsider topic, which is to say an uncomfortable one. In football, Croatia ran 14.3 kilometres and the xG correction still rewrote the story, because effort and outcome are not the same contract. Cricket makes the opposite error: the bowler did not run, he bowled, and nobody prices the bowling.

Entry three — the age curve.

A selection meeting is cricket's silent court. The least recorded evidence in it is the age curve. A batsman slowly loses strike rate after 30; a fast bowler enters injury risk after 32. These are ordinary rules, but for an established player they are suspended.

At the 2026 World Cup, Shakib Al Hasan scored 606 runs and took 11 wickets. That pairing is rare. The ledger holds that entry. It does not hold what must also be said: his workload across formats was close to uncontrolled, and the consequence arrived in another form.

Many assume the age-curve question only concerns a player's rise. It does not; it returns at the end. When do you drop the chosen veteran — at 32, 34, or 36? No public criterion sits behind that decision and no document exists. That is the widest blank in cricket's ledger: experience is always documented as an asset; its cost never is.

Entry four — the class of evidence.

At the 2026 World Cup, Bangladesh won three matches in a row — South Africa by 21 runs at The Oval on 2 June, West Indies by seven wickets at Taunton on 17 June (Shakib 124, Liton Das 94), Afghanistan by 62 runs at Southampton on 24 June. In 2026 they reached the quarter-final and knocked England out on 9 March at Adelaide with a 15-run win.

Here is my most contested calculation. These results are not equal evidence. A win chasing 130 in 20 rain-truncated overs and a win by 15 runs in a full 50-over match sit in the same 'win' column, but they come from different samples. In the first, the resource ceiling is artificial; in the second, it is full. Cricket's ledger does not record that difference.

Contrarian: correction is not conspiracy

Now I must stand against my own arithmetic.

First, I am not saying the rain rule discriminates against any team. It runs on the same grid for everyone, and there is still no alternative to Duckworth-Lewis-Stern. What I am saying is that storing its output under the label 'full-match win' is misleading.

Second, debt and conspiracy are not the same. Reading the ledger, some will conclude that the rules robbed a side. My arithmetic says the reverse: in a match one side won, the body of the losing side often paid more — and that bill arrived in the next series. I call it debt transfer, not conspiracy.

Third, cricket data cannot be read on the model of another sport. In football I used xG to rewrite the 2026 Croatia-England story, because goals are rare events and shot quality must be measured. Cricket has runs in abundance and data on every ball, so 'one number proves everything' has no room. Strike rate alone says nothing without batting position; economy alone says nothing without phase. Hence my own signature rule: turning a single metric into the whole truth is just stuffing the ledger again.

Fourth, my memory is not evidence. Every date in this piece was cross-checked against the archive, and wherever doubt remains I have either flagged the date or left the entry open. Six decades of experience is an advantage, but experience is never a substitute for a document.

Takeaway: what I will watch next series

The ledger stays open. Over the next three months I will watch one thing. After a rain-shortened win, what does that side's pace workload look like in the following healthy, full-length match? If a pattern emerges, it proves the correction happens not only in the rules but in the body. And if a side takes the no-data premium on a new fast bowler across two successive series, the question stops being one of selection and becomes one of structure: who ultimately pays — the selector, the coach, or the 19-year-old who only knows how to bowl?