The 112 Threshold: A Dot-Ball Ledger of the 2026 T20 World Cup in New York

On the first page of my notebook the number is still written in red ink — 232 runs off 234 balls.

June 9, 2026. Nassau County International Cricket Stadium, New York. India bowled out for 119 in 19 overs. Pakistan finished on 113 for 7 from 20. India won by six runs. Two of the most explosive batting line-ups in the world produced 232 runs from 234 legal deliveries, a rate of 5.95 an over — in the same tournament where India alone made 205 in St Lucia.

I watched that match from a room in Chattogram at two in the morning on the ICC feed. The first thing I counted afterwards was not run rate. It was dot balls. The press-box explanation I kept hearing — 'the pitch was bad' — did not satisfy me. The right question was narrower: at which over, and off whose bat, did the score stop moving?

This is the ledger of that question.

Context: what I am measuring, and where the data comes from

The 2026 ICC Men's T20 World Cup ran from June 1 to June 29 across the United States and the West Indies. Twenty teams, four groups. The most discussed venue was the temporary Nassau County stadium in New York, built on drop-in turf. Eight group matches were played there. From the Super Eight onward, the tournament moved to the Caribbean.

I applied the method I use in football. In 2026, charting 22 Bangladesh Premier League matches by hand in Chattogram, I set one rule for myself: open the columns before the adjectives. That work became the first xG ledger for Chattogram football. Football's shot-quality model does not transfer directly to cricket, but the principle does — venue, wicket loss, game state and opposition quality have to be separated, or the numbers lie.

My 2026 Empty Stadium Index taught me something I reused here: environment is a variable, not a mood. So the New York drop-in pitch sits in its own box in my sheet, not in the background of a story.

I built an eight-column ledger for the eight matches:

1. Venue and date
2. First-innings score and overs
3. Second-innings score and overs
4. Margin (runs or balls remaining)
5. Dot-ball share (percentage of deliveries producing no run)
6. Strike rate between overs 7 and 15
7. Wides and no-balls in the death overs
8. Catches dropped and review incidents

Honesty first. Columns 1 to 4 are complete for all eight matches. Columns 5 and 6 are complete for four of the eight. Columns 7 and 8 are still open. I will not draw conclusions from a partial column. Partial columns make the story bigger and the cricket smaller.

I keep clean columns so the messy truth has somewhere to land.

Eight matches, one threshold

Here are the scores in order.

June 3 — Sri Lanka 77 all out; South Africa 80/4. June 5 — Ireland 96 all out; India 97/2. June 7 — Canada 137/7; Ireland 125/7. June 8 — Netherlands 103/9; South Africa 106/6. June 9 — India 119 all out; Pakistan 113/7. June 10 — South Africa 113/6; Bangladesh 109/7. June 11 — Canada 106/7; Pakistan 107/3. June 12 — United States 110/8; India 111/3.

Now the arithmetic. The eight first innings total 861, an average of 107.6. The eight second innings total 848, an average of 106.0. Across all 16 innings the average is 106.8. Batting first or batting second made almost no difference — a gap of 1.6 runs.

That is the spine of this piece: in New York the pitch did not get easier in the second innings, and neither did the batters.

Thirteen of the 16 innings finished below 120. Only three sides passed it: Canada 137, Ireland 125, India 119.

Pair each first-innings score with the result and the picture sharpens.

77 — lost 96 — lost 103 — lost 106 — lost 110 — lost 113 — won 119 — won 137 — won

Five times a side batted first and made 110 or fewer. All five lost. Three times a side batted first and made 113 or more. All three won. Eight matches, no exceptions.

The New York defence threshold was 112.

I am not claiming a universal law. Eight matches is a small sample, and no single venue's property should be turned into a general rule. But the split is clean enough to be a more precise explanation than 'the pitch was bad'. A score of 106 fell short by only a few runs; the result jumped from zero per cent to one hundred per cent. That jump is the finding.

There is an easy objection: scores near 107 produce matches decided by a few runs, and small margins punish small errors. That is a weak objection. Canada defended 137/7 against 125/7 — a margin of 12 runs, also tight — with composure. The difference was the height of the score, not the size of the pressure.

Without dot balls, 112 makes no sense

Here my incomplete columns earn their place. I completed over-by-over charting for four of the eight matches. In two of those four, the chasing side's dot-ball share exceeded 40 per cent. Roughly every second delivery produced nothing.

The mathematics becomes unavoidable. Forty per cent dots in 120 balls means 48 wasted deliveries. From the remaining 72, if only 30 singles come, the boundary count has to supply at least 82 — seven or eight fours plus two or three sixes. The sides stuck on 77, 96 and 103 did not lack power. They lacked the ability to push a dot ball into a single.

In football I learned this from the Japan versus Belgium pressing map: pressure is not a feeling, it is a number. On a 22-yard strip, pressure is a ball not rotated. Commentators reach for the word momentum; the hardest evidence of momentum is a run of consecutive dot balls. India's squeeze on Pakistan on June 9 was not inspiration. It was a set of deliveries, a set of lines, and the discipline to leave the ball alone.

One thing needs stating plainly, because it has been written wrongly too often: a bad pitch damages both sides equally, so the pitch cannot explain the result — the difference in ability does. On the same strip, in the same week, four days apart, Canada made 137/7 and Sri Lanka collapsed to 77.

The same disease reached the final

June 29, Barbados. India 176/7. South Africa 169/8. India won by seven runs. Jasprit Bumrah was named Player of the Tournament with 15 wickets at an economy of 4.17 (source: ICC). Arshdeep Singh took 17 wickets.

But the match turned somewhere else. South Africa needed 30 from 30 balls with six wickets in hand. An ordinary target, an ordinary passage of play. They lost by seven runs.

In my ledger that is not a pitch story. It is a story about 30 balls and about batting order. The link to New York is a single shape: the collapse pattern repeated itself.

The contrarian angle: the pitch story swallowed the others

The toss got the most words. The ledger says chasing sides won five of eight in New York and defending sides won three. The second innings averaged 1.6 runs fewer than the first. Put together, 'it is easier batting second' does not survive.

So why did chasing sides win more often? Because with a defence threshold of 112, a target of 107 to 110 is reachable. The wins came from small targets, not from an easier pitch. One explanation credits the batters; the other credits the environment.

The second contrarian point travels further. On June 7 in Providence, Guyana, Afghanistan restricted New Zealand to 159/6 and bowled them out for 75. On a Caribbean surface, where the ball is supposed to come onto the bat, the same collapse. On June 22 in Kingstown, Afghanistan defended 148/6 against Australia. None of this involves the New York pitch. The shape is identical: an ordinary target, then a breakdown in batting discipline during the decisive overs.

The tournament's real illness was not venue-specific. The pitch only magnified it.

This is where I write a warning to myself, because I am at risk of the same trap. A good framework stretched everywhere stops being credible. The 112 line belongs to New York. On June 16 in Kingstown, Bangladesh batted first against Nepal, were bowled out for 106, and still won by 21 runs. Change the venue and the threshold moves. Anyone dragging 112 everywhere will be wrong.

The rejected alternatives belong in the record too. I first suspected dropped catches and review errors decided those eight matches; with column 8 incomplete I could not prove it, so I set the claim aside. I then suspected the associate sides' success came from inexperience; the data does not support that either, since Canada and the United States both batted to the venue's terms.

Bangladesh: a shortfall of six runs

Bangladesh's campaign reads differently under this ledger. They won three of four group matches — against Sri Lanka by two wickets, the Netherlands by 25 runs, Nepal by 21 runs — and lost only to South Africa, by four runs, in New York.

On June 10 they bowled first. Holding South Africa to 113/6 meant keeping them one run above the venue threshold. The bowling unit did its job. The batting stopped at 109. Six runs short.

Six runs sounds trivial. The threshold table says it is not. Batting below 112 at that venue means depending on the opposition's mistakes. Bangladesh lost by four runs, which means the opposition made none.

In the Super Eight the picture clears: a 28-run loss to Australia, a 50-run loss to India, an eight-run loss (DLS) to Afghanistan, where Bangladesh were bowled out for 105 chasing 115. Rain intervened, so that match needs separate reading. Still, three consecutive collapses in scoring rate show that the group-stage wins had covered the batting problem rather than solved it.

One press-box convention deserves scrutiny. Bangladesh's batting debate starts with the word intent. Intent is an attitude and cannot be measured. Strike rate between overs 7 and 15 can. My partial charting shows Bangladesh's run rate in that phase lagged the tournament average, while their wicket-loss rate stayed low. The problem was a shortage of aggression, not an excess of it. And the cure for too little aggression is not more recklessness — it is handing the job to somebody else.

Takeaway: the index needed before 2026

The 2026 Men's T20 World Cup will be played in India and Sri Lanka in February and March. Neither country uses New York's drop-in pitches, and scores will be far higher. The 112 line will not survive there. The method will.

I propose an index, working name Defence Threshold Index. The calculation is simple: for a given venue in a given season, match each first-innings score against the result, and find the score below which no total was ever defended. That number is the venue's threshold. Toss decisions should follow it, instead of sentences about pitches drying out.

My working assumption is that the threshold in India and Sri Lanka will sit near 170 or 180. Assumption — because I want the gap between estimating and measuring kept visible. When the columns fill, the number will move, and movement is normal.

A ledger never replaces the match; it remembers what the match forgot. The New York pitch, the drop-in turf, the temporary stadium — those debates will fade once the tournament ends. What stays in the ledger is five first innings below 112, and five defeats. The question for the next cycle: will teams carry an extra venue-specific death bowler, or an extra batter who can rotate the strike through the middle overs? The New York ledger points at the second. The sides that stalled below 112 never had a last-two-overs problem. They had an overs-seven-to-fifteen problem.