Adelaide's 66/0 and 145/6: Which Bangladesh Module Broke First

Hook

The first page of my Adelaide notebook has one line written in pencil — “6 overs: 66/0.” On November 2, 2026, at the T20 World Cup, India made 184/6 and Bangladesh's powerplay module touched its own ceiling. Litton Das scored 60 off 27 balls. I still remember every square cut from that innings in the stands; my notebook doesn't hold the innings, though. It holds what came after it.

Because the match went into the record books for an entirely different reason — rain, a Duckworth-Lewis-Stern revised target of 151 in 16 overs, and a five-run defeat at the end. Rain here is weather data, not explanation. What I read off the scorecard: the powerplay was Bangladesh's best module of that tournament, which makes it the exception; the rule was the quiet evaporation between overs seven and fifteen. Taking the exception for the rule is exactly what sent the next few seasons of squad-building down the wrong road.

Context

Adelaide Oval's geometry is this match's silent character. Long straight boundaries, short square ones — which means the true seam of ore for a boundary-dependent batter is that square arc. Once rain arrived in the second innings, the arithmetic tightened further: 151 in 16 overs is 9.44 an over. When Duckworth-Lewis-Stern cuts overs, the value of wickets in hand falls and the value of boundary probability rises. A batting model built on “keep wickets in hand, explode in the last five” becomes structurally irrelevant the moment the overs compress.

The opposition's bowling architecture was the mirror image. Seam and swing with the new ball, a spin pair through the middle, and the long side of the ground policed in two layers. The plan was not complicated — push Bangladesh toward the short square boundary, where deep fielders and a point/third-man trap were waiting.

One more piece of context cannot be moved aside. This was a tournament-pressure match played inside a group — net run rate, scores from other venues, the knockout door. I rewatched France — Root: 2026 World Cup Final — mapping France, and the lesson holds: pressure does not change geometry, pressure changes the tempo of decisions. France surrendered 66% possession that day and still held Croatia to three shots on target, because the territory they gave up was low-value territory. In cricket, that “possession” is powerplay runs — spectacular to watch, cheap in a compressed-overs equation.

Core

Across the first six overs, Bangladesh's scoring map was almost one-dimensional. The bulk of Litton's 60 came through the square arc — the pull, the square cut, the slash over backward point. Given Adelaide's short square boundaries, the plan was correct. But the seed of the collapse sat inside it: the assault never built a strike-rotation structure underneath it — boundaries were arriving, strikes were not turning over. So the day boundaries stopped, the machine for grinding out runs was not ready either.

Spin came on in the seventh over. Long straight boundary, two layers deep, a boundary rider on the leg side. Against that combination, Bangladesh's middle-overs module slowly shut down. Dots accumulated, the ball went round the field, and the strike-rotation index began to fall. In a phase where even six or seven an over would be enough — because the risk of a big shot is low — Bangladesh got stuck between line, length and the long boundary.

That middle-overs choke was no accident; it was the standing condition of Bangladesh through that tournament. After the powerplay, the scoring rate dropped in virtually every match. Keep that design in mind and Adelaide's powerplay reads as an anomaly — and building a last-five-overs plan on top of an anomaly is building a fort on sand.

Turn the arithmetic over once more. A revised target of 151 in 16 means roughly nine and a half an over. Sustaining that requires persistent boundary probability — a batter who can clear the rope even with the field pushed back. Bangladesh's middle order that day visibly lacked that boundary-first profile. As the required rate climbed, batters were forced into big shots they had not been selected for, in roles they had not been practising — because for years they had been cast differently.

India's death-overs design is readable too. They kept the ball away from the arc with yorkers, slower cutters and wide lines. The more pressure in the situation, the less risk a bowler takes — and with a batter already leaning toward the slower ball, the risk migrates into the hands of the deep fielder.

Bangladesh's bowling module belongs to the story as well. India's route to 184/6 was built by breaking timing in the middle and finishing hard at the end. Bangladesh's bowlers created pressure in the powerplay but never controlled the arithmetic at the back end. Football has a phrase for it — transition defence, the discipline of getting back into shape as the attack turns into defence. Cricket's equivalent is owning the over that follows the departing bowler. Small leaks there are where control of the match drains away.

The empty stadium revealed Bayern — Root: 2026 Empty Stadiums — Bayern. With no crowd, Bayern's pressing triggers could not hide behind the noise, so the structure became visible. Adelaide produced the inverse: crowd noise and a rain break together concealed Bangladesh's structural weakness, which is why the weakness never got properly logged afterwards.

I keep a noise log in my notebooks. Two entries from that night: two mistimed cuts early in the middle phase, and the dressing-room return schedule during the rain break. Neither maps cleanly onto the model. I flag them as unmapped and leave them there rather than forcing them into a grid.

Contrarian

The lazy line is that rain took the match away. Rain does not hand a team a batting structure or take one away; rain only removes time. Bangladesh did not lose to Duckworth-Lewis arithmetic in a compressed innings — Bangladesh lost to the same middle-overs module that had been broken for the entire tournament. The powerplay hid it that night; the rain only made it visible.

Nor is the defeat a story about one batter's shot selection. It is a story about squad construction. Without a boundary-first number five in the XI, a module can be planned perfectly and still not match the profile needed to execute it. I follow transfer rumors like formations: shape first, noise later — and reading construction rumours works the same way, the geography of roles first, the beauty of names afterwards.

Saudi Arabia — Root: 2026 Qatar World Cup — Saudi Arabia. Hervé Renard's 4-4-2 high line caught Argentina offside ten times, because Argentina's 4-3-3 running timing was half a beat late, every time. Bangladesh's middle-overs batting repeats that same offence: half a beat late in the decision to leave, half a beat late in the decision to take on the shot. It is a timing error in football and a timing error in cricket.

Takeaway

For the next match I am writing down two things to watch. One, strike rotation between overs seven and twelve: at least two strike changes per over through the boundary arc. Two, whether a boundary-first profile walks in at number five — that selection decision is the falsifiable one. My confidence is 60%, and I will update as soon as the next powerplay ends.