Overs 7–15 at the Asia Cup: The Quiet Ledger of Bangladesh's Dot Balls

Six Dot Balls in the Thirteenth Over

The thirteenth over of a chase. The required rate had already crossed eight an over. Five deliveries, no runs — not dangerous balls, just off-stump lines pulled back in length, with the gap between cover and mid-off left open on purpose. On the sixth, the bat swung and the ball did not meet it. The sound that went around the stadium was not excitement. It was thirty thousand people collectively recognising that the game was slipping away without anyone being able to say from where.

Commentary had already reached for the word twice. Choke. Pressure. I did not start there. I started with a blank spreadsheet and a suspicion about the numbers, because six dot balls look identical and each of them has a different birth.

What the log gave me was the real discomfort. In the phase where the required rate was climbing, boundary attempts were climbing too. It was strike rotation that had collapsed. The broadcast story said the batters had frozen. My ledger said they had changed direction.

Why I start from a blank spreadsheet

Summer 2026, Barishal. I was seventeen, a statistics student, and I hand-logged 1,024 shots from all 64 World Cup matches, three hours per match, splitting distance, angle and assist type into separate columns. That model said France scored 14 goals from 10.4 xG while Brazil scored 8 from 12.1. Winning is an outcome; creating chances is a process. Two different numbers.

Two years later, German football returned to empty stadiums. I tracked PPDA and distance covered for every match. Bayern Munich's PPDA moved from 7.1 to 8.3, distance covered fell 4.2 kilometres per match, home advantage dropped 12 percent. Some of pressure, it turns out, is acoustics.

In Qatar in 2026 I tracked Sofyan Amrabat as a remote data scout. Against Spain in the round of sixteen: 12.7 kilometres, three tackles, one interception, zero times dribbled past. Morocco's tournament PPDA was 12.3. That five-page report reached three agents and one club analyst and led directly to my first job as a Transfer Market Administrator. Sofyan Amrabat — Root: 2026 Qatar World Cup, Morocco — is not a glamour story to me; he is a denominator.

I carried the football habit into cricket for one reason. Cricket measures effort and measures results, but rarely measures responsibility. Amrabat's distance was never an aesthetic contest. It answered a question: how many passes were allowed per defensive action, meaning where pressure was actually created. The cricket question becomes: how many singles per six balls, meaning whether rotation is alive.

For this piece I hand-logged 1,180 legal deliveries across six Asia Cup matches — over, ball number, bowler type, line and length, shot attempt, contact, runs, and a six-way outcome code. The limitations are plain: a single observer, television camera angles, no proprietary ball-tracking, and six matches, not twenty. These numbers are signals, not verdicts.

Overs 7 to 15: the empty room in the plan

The first six overs are now routine. The last four are a data mine where finishers are priced ball by ball. The gap sits in the ten overs between, where tempo is built and pressure accumulates.

In my log, the singles rate was roughly 58 percent in the powerplay, 52 percent in overs 16 to 20, and 31 percent in overs 7 to 15. In the middle ten overs, two out of every three balls ended with rotation switched off. And this is exactly where shot attempts rose — about 14 percent more than in the powerplay. The bat swung more and the running stopped.

Read those two numbers together and the picture clears. A dot ball is not simply one wasted delivery; it forces the batter to attempt more than the situation allows on the next one. After two consecutive dots, boundaries roughly doubled in my sample — but false shots went up about two and a half times, and wickets fell nearly three times as often. Pressure is not born in the dot ball. It is born in the answer to it.

A dot ball is never neutral

Three bowler types dominate this phase: the left-arm orthodox spinner operating on a length that protects the gloves, the leg-spinner mixing googlies and flippers to kill the slog sweep, and the seamer relying on cutters and slower balls that never arrive in the middle of the bat.

Roughly 64 percent of my middle-phase dots came from those three types, and more than 70 percent of those came off slow surfaces where the ball does not turn, only stalls. The batter is late through cover, or on top of the ball through mid-on. A dot follows.

Here is the complication. Bangladesh's middle-order batters usually arrive in two categories: those who bat top order domestically, and those who bat six or seven for the national side. Facing the same phase, the first has fielders up; the second has sweepers back. Same over, two different sports, and only one of them is trained for it.

Role-adjusted output: thirty is not thirty

A number three's 30 from 28 and a number five's 30 from 28 are not the same product. The first gets the smoother pitch, the field inside the circle in patches, the freedom to set tempo. The second is asked to finish other people's overs and to leave the boundary alone until it is safe. In my log, false-shot rate for batters starting at five inside their first twenty balls ran near 41 percent; for batters starting at eight, 23 percent.

That is where my suspicion sits. We grade the middle overs on raw run rate and never split the roles. The player doing the harder job looks worse on paper; the player doing the easier job looks better. Two batters sit at similar net returns while living on different planets of difficulty.

Measuring the running, not the responsibility

Cricket's viral equivalent of distance covered is how far a batter ran between the wickets. The number looks clean and hides a real problem: pointless running counts the same as necessary running. If the signal is misread twice in the same ball, distance rises and runs do not.

I used a simpler denominator — turn-producing runs as a share of total running between the wickets. When that share fell below 40 percent in the middle phase, the final four overs almost always came in three to four runs per over below the innings baseline. The running had not disappeared. The running in the right place had.

But stopping there would be wrong

These numbers are honest and autobiographical at the same time. What I coded as a false shot from a mid-left television camera is not what a tracking system codes. Bad timing, one-handed attempts and being beaten by a slower ball all went into the same bucket. Some exaggeration is unavoidable.

Then there is the environment. In the United Arab Emirates in September and October, dew so dominates the second innings that slow-pitch data from overs 7 to 15 often becomes meaningless — the bowler cannot grip the ball, so my false shot is really the ball's. Correlation is not causation. Dew and dot balls appeared together; dew did not cause them.

And there is the alternative explanation nobody should discard. If the top two bat 20 from 30, the number six believes he must hit. Carry-over pressure in my log pushed boundary attempts up about 30 percent and dot balls up 7 percent once the top order consumed four overs cheaply. The fault may sit at number seven in the middle phase, but the decision was made in the first six overs. Sri Lanka's spin pairing — Wanindu Hasaranga and Maheesh Theekshana — bowled overs 7 to 15 at roughly five an over while the death bowlers went above eleven. Their blueprint keeps spin for the middle and saves pace for the end.

I keep one warning. Dropping "passes allowed per defensive action" straight into cricket will mislead you. In football, lower PPDA means more pressure. In cricket, low rotation means the innings is failing. A ball is a resource; a pass is only a tool. I borrow cross-sport denominators to sharpen a question, never to prove an answer. Before I trust a press release, I count the passes allowed per defensive action — and then I still call it a hypothesis.

How this ledger reaches the transfer market

After an Asia Cup, a quieter process begins. The player who absorbed pressure in the middle overs and kept rotation alive draws franchise attention, and the offer usually arrives as a replacement or bench-squad commitment, where responsibility is not named but "experience" is. A transfer is a number with a birthday, a contract, and a hidden clause, and the clauses stay thin because the numbers are small. A young player who spent two months being hammered in overs 7 to 15 and learning to respond is then handed the job of developing for somebody else. The villain is not a club. The villain is the design — smaller sides are permanently tasked with supplying half-finished goods, and the shipping label always comes from a bigger stage.

Barishal taught me that a model is only as honest as its missing rows. What happened in the innings I could not log is unknown to my spreadsheet, and keeping the conclusion humble about that blind spot is the actual work. I do not chase narratives; I reconcile them against the match log.

What to watch in the next round

I will not watch the scoreboard. I will watch singles per six balls in overs 7 to 15, and I will separate the dots caused by the pitch from the dots caused by the field from the dots caused by the decision. If rotation climbs back above 40 percent after the twelfth over, the middle-overs design is changing. If it does not, the question becomes who is building this side, and on what contract length.

The data did not shout; it waited until the noise left the stadium. My suspicion is that the truth of the next round is hiding between two dot balls, exactly where nobody applauds.