I Opened the Rajshahi Ledger Again: The Quiet Powerplay Deficit and the Unbalanced Death-Over Account

When the third ball of the 14th over slid past the stumps into the wicketkeeper's gloves, the Mirpur gallery roared with every dot ball. But I was looking at the scorecard, and the ledger was telling me something far quieter and far crueller than that roar. Ninety-eight for three after fourteen overs — the number itself admits nothing. But when I broke it down over by over and ball by ball, an imbalance surfaced that the gallery never sees: this side had made 47 for one in the powerplay, a strike rate of 141; then between overs seven and fourteen the strike rate fell to 104, and the dot-ball rate climbed to 43 percent. I opened the Rajshahi ledger again, and the season confessed a quieter pattern — this collapse is not a shortage of talent, it is a problem of scheduling and of role. I have watched this game for 31 years, and for the past six I have written a data column from Rajshahi. In 2026, at 38, I built an xG model for the Bangladesh Premier League match Abahani Limited Dhaka versus Sheikh Jamal Dhanmondi. The first version underpredicted set-piece goals by 18 percent. I spent six weeks reweighting shot location, defensive pressure and goalkeeper positioning. The corrected model hit 74 percent directional accuracy over 12 matches. I published the error log alongside the model, refusing to hide the miss. That habit persists: when I apply this model to cricket, I compute expected runs, a ball-pressure index and field-set fragility, and I write the sample size and error bars next to every claim. I remember in 2026, while at The Daily Star, I interviewed Soumya Sarkar, and the piece was later picked up by Prothom Alo — that was my first verifiable byline. From that day a habit formed: seeing the glimpse of talent and the accounting of the system as two separate things. In 2026 I left The Daily Star to cover the national team home and away, and through that I learned that a player's form is one object while the system around him is another. I watched this match from a Mirpur seat where the whole powerplay ring is visible, with a data screen beside me, noting two things every over: the line of the delivery and the batsman's first step. Now to the structure of the main account. In cricket xG does not translate directly, because the game is made of discrete balls, not continuous flow. So I built an index — expected runs per ball (xR/B). It takes four inputs: shot type and angle, the pressure of fielders' positions, the phase of the match, and the batsman's historical strike rate in that phase. Over a 12-match back-test the index predicted end-of-over actual runs within 8 runs in 71 percent of cases. The model is not perfect, and I admit that. But it clarifies one thing the camera never catches: where a side is actually losing runs. My account says that in this match the powerplay's six overs carried an xR/B of 1.41, with an actual 47 runs. Between overs seven and fourteen the xR/B was 1.18, but the actual runs came to only 51 — a rate of 6.4 across eight overs. Here is the first imbalance: the model said at least 66 runs should have come in these overs, a shortfall of roughly 15 runs. The second imbalance is even more visible — across these eight overs there were 34 dot balls, close to 70 percent of the 48 deliveries. If a side takes no run from 70 percent of deliveries, it must score at an abnormal strike rate from the remaining 30 percent. In this match, they did not. Breaking it ball by ball, a quiet pattern emerged. Twenty-six of those dot balls came from spinners bowling a length of about 4.8 metres, with seven fielders inside the ring. The side was pinned by length, and the batsmen could not take singles because the ring was packed. This is no coincidence — the opposing captain understood that this batting line-up's weakness is not the big hit but rotation. So he brought the field in immediately after the powerplay and gave two spinners the ball together in the middle overs. In my ledger this is a familiar thread: in Bangladesh's domestic cricket, sides fear taking singles in the middle overs because they depend on the big shot. I recalled an old habit in Rajshahi. In domestic seasons I often see a young batsman make 40-45 in the powerplay, then, once the field spreads, get out attempting the same shot. This pattern returns again and again in the season's ledger. In this match exactly that happened — a 21-year-old made 38 off 31 in the powerplay, then managed only 6 off the next 11 before being dismissed. His body is not yet fully developed, yet he has been pushed into senior rhythms. I have written many times that this haste is an accounting error — sides trust the young but do not verify their physical and mental readiness. Now to a thread I have pulled for years. In 2026, at 39, I applied my calibrated model to the Russia World Cup. Using PPDA and set-piece xG, I gave Croatia an 11.4 percent chance to reach the final, while the market implied 4.7 percent. I noted Croatia's PPDA of 9.8 and their unusually high xG from dead balls. Croatia reached the final. I also flagged Germany's low xG despite high possession. My model beat closing odds on seven of eight quarterfinalists. — Root: Croatia. But I am careful here, because this thread does not apply directly to cricket. Croatia's lesson is this: peripheral geography and systems outside expectation sometimes explain core outcomes. In cricket the translation is peripheral domestic scouting — a player from a small town whose data nobody reads can sometimes invert the system. In one case in this match I saw exactly that: an opposing bowler, average in the domestic league, came on in the middle overs and took two for eighteen. He has no big name, but his length and ring management were flawless. When the stadiums emptied, I stopped trusting the crowd and started measuring silence. When the gallery fell silent, I saw that this side's real problem was not the powerplay but the death-over account. In the last six overs they made 58 runs, roughly 32 percent of the total. The number is not bad. But when I applied the cricket version of set-piece xG — the ratio of expected to actual boundaries in the final two overs — I saw they fulfilled only 70 percent of expectation. The reason is simple: in the final two overs they played six dot balls, and four of those were at yorker length, which they could not read. Here is my second observation, hidden deep in the ledger. I looked at data from 24 matches across the last three seasons and found a pattern: this batting unit holds a strike rate of 108 in the middle overs (7-14), while other sides hold 125 in those same overs. That is a shortfall of about 12-14 runs per match, in the middle overs alone. Across a season that is nearly 280 runs, enough to change the outcome of many matches. This is not one player's problem, it is a problem of squad construction — the side has no defined role for rotating the strike in the middle overs. I opened the Rajshahi ledger again, and the season confessed a quieter pattern — in domestic cricket, selectors do not produce middle-over specialists. They pick big-name batsmen who play the powerplay, then hope someone will manage the middle. That hope is an accounting gap, and on the international stage the gap shows. The market sees goals; I trace the process that made them feel inevitable. The market sees only sixes and fours; I trace the process that makes runs feel inevitable. In this match my screen carried a number absent from any scorecard: the ball-pressure index. For every delivery I scored the batsman's balance, backlift and swing time. It emerged that of the 34 dot balls this side played, 22 showed a late backlift — they could not read the length. That is a sign of fatigue, not of skill. Now a hard question I ask myself every time I open the ledger. Is this fatigue the fault of scheduling, or of role? I calculated this side's match spacing over the last 14 months. It turned out 38 percent of their matches came at intervals of less than seven days, three of them post-travel. That is a systemic problem. I have said many times that cricket administration builds schedules to television's demand, not to the player's bodily rhythm. So middle-over fatigue is an inevitable result. Here lies my biggest disagreement, and I want to open it slowly. The prevailing view says this side lost through a lack of talent. My account says the opposite: the talent is sufficient, but the system cannot place talent in the right role. Correlation ≠ causation — correlation is not cause. When the gallery sees a batsman out and says 'no form', perhaps he is simply batting in the wrong place, the wrong over, the wrong role. A transfer is not a headline; it is a system looking for a new home. In this side's case I saw they had lost a specific role — a batsman rotating strike between overs seven and fourteen — and had not replaced it. Instead they bought another power-hitter, good in the powerplay but leaving the same middle-over gap. That is a mis-buy: the side did not buy what it needed, it bought what was easy to find. I know I have a weakness here — I keep pulling the Croatia thread, and it can be forced. So I want to stay careful: in this match the Croatia thread applies only when we speak of peripheral scouting and systems outside expectation. Croatia's lesson is process, not event. Esports taught me that meta is just football with faster feedback loops. In cricket this means every format has a meta, and sides that cannot keep pace with it fall behind. The current T20 meta is attack in the middle overs, because the fielding ring is not mandatory in the powerplay. This side still plays the old meta — attack in the powerplay, conserve in the middle. I learned that sports culture worships heroes, but the ledger only worships repeatable processes. In this match the hero was one man who made 55 off 40, but his strike rate was 137, not enough in this situation. The ledger says 155 was needed. The hero's number and the ledger's number do not meet, and here the paths of the media and the analyst diverge. I now try to read the forward signal. For this side, two things must be watched next. First, selection must make clear who takes the middle-over role. Second, no strategy works without reducing the scheduling load. I make a prediction that is falsifiable: if this side cannot lift its middle-over strike rate above 125 in the next three matches, their win probability will sit below 40 percent. I write this number now and will not hide it in hindsight. I recalled a junior analyst in Rajshahi who works with me. She told me, 'Sir, your model does not measure fatigue.' She is right. I am trying to add a variable — sleep and travel. It is still experimental, and I admit that. Veteran omniscience is a trap of mine, so I listen to juniors and publish my errors. The whole thread of this writing settles on a simple question. If this side's problem is not talent but system, why do we change talent instead of the system? Selectors change players, coaches change, but nobody changes the schedule or the role structure. Because changing the system is invisible, and changing players is visible. The media wants visible change, because that becomes the headline. I want to be clear, because there is room for confusion. I am not saying talent plays no part. I am saying that in this specific match the talent deficit was the second cause; the first was the mismatch of role and schedule. The distinction matters, because the first cause can be fixed by tactics, the second only by structure. I looked at the ledger again. 98 for three, fourteen overs, and a hidden shortfall of 15 runs. The gallery will never see those 15 runs, because they hide inside a space — the difference between a dot ball and a single. But at season's end, when the points table is read, those 15 runs return, in a match's margin, in a net run rate's margin. Croatia. I use this word because it reminds me that things outside expectation also live inside the account, if you look at the right column. Croatia was peripheral in 2026, but its PPDA and set-piece xG were in the core column. This side is not peripheral either, but its problem hides in a peripheral column — middle-over rotation. My final observation concerns scheduling. I looked at a decade of tournament data and found a pattern: sides that play more than three matches in the first two weeks of a tournament see their middle-over strike rate fall by an average of 9 percent in the closing stage. The number looks small, but in T20, 9 percent means about 11 runs per match, and across a tournament that is the difference between reaching a final and not. Now, a caution. I am using a model borrowed from football xG, and it does not apply directly to cricket. I found 71 percent accuracy over 12 matches, but 12 matches is a small sample, and patterns deceive in small samples. So I am not saying this analysis is final. I am saying it is a thread, a direction, that needs more data to verify. When I left Mirpur it was late. The gallery was empty, nobody there. Only the pitch curator and his lights. I stood a while and thought about what this pitch would do tomorrow. In domestic cricket I have seen such pitches slow in the second innings and turn more for spinners. If that happens, the middle overs will again decide tomorrow's match, and this side's role problem will be tested again. I know this writing offers no simple solution. Because cricket has no simple solution. But one thing I can say with certainty: if we look for this side's problem in the wrong column, we will change the wrong player, and the pattern will return, in exactly the same place, the same over. The season's ledger is not yet closed. And I am waiting for the next match, where a number will tell me whether my thread was right, or whether I magnified a peripheral pattern. That waiting is the real part of my work — not the hero's story, but the ledger's patience.