Eleven Boundaries at Mirpur: The Powerplay xG Story the Scoreboard Hides

Eleven Boundaries at Mirpur: The Powerplay xG Story the Scoreboard Hides

Last Friday night's match at the Sher-e-Bangla Stadium in Mirpur finished in the 19th over. The target was 168. The winning side got home with just eleven boundaries and five wickets down. From the commentary box the verdict was a "cool-headed chase." The scoreboard agrees—a run rate of 8.8, little dot-ball pressure. But after coding all 243 deliveries myself, a different picture appeared on my table. Behind those eleven boundaries sat 37 "silent strikes"—balls struck from the middle of the bat that travelled straight to a fielder. A scoreboard counts boundaries; it does not count shot quality. That gap is now the most valuable and most neglected piece of information in Bangladesh's domestic cricket.

In 2026, at 24, I joined Golpo Sports as a junior data analyst from my flat in Rajshahi. Back then I treated data as scripture. I hand-coded 1,248 shots from the 2026-17 Dhaka domestic football league. Abahani Limited Dhaka scored 34 goals from 27.6 xG; Sheikh Jamal Dhanmondi scored 29 from 31.2. The finishing gap between the two was the real story, not the table position. After that series I stopped writing "deserved" and started writing "xG differential." At the 2026 Russia World Cup, Germany's 26 shots against Mexico produced only 1.3 xG; Mexico's 12 produced 1.1. Germany's PPDA was 6.9, conceding 18 transition chances. I shipped the model before the final whistle—Germany would not escape Group F. Germany finished bottom. PPDA showed me Germany.

I have carried that lesson into cricket, though not blindly. Football xG and cricket shot quality are not the same object; in cricket every delivery is a separate event, and in Bangladesh ball-tracking does not exist at every venue. Mirpur, Sylhet, Chattogram—the camera angles differ, the standard of scoring differs. So before building a model I sat with scorers, video operators and local coaches. What counts as a "press," which ball created "line-and-length pressure"—I fixed those definitions with them, otherwise the model would have stayed my private imagination. An ESTJ builds the pipeline first and the poetry second. In Bangladesh's reality, data collection means people first, algorithms later.

Now the actual table. In the current BPL phase I split every powerplay shot across six overs into three tiers: controlled (middle of the bat, along the ground), semi-controlled (in the air, toward a fielder) and free swing. The two sides playing the most controlled shots in the powerplay have fewer boundaries than the top two on the table—yet their run rate across those six overs is nearly identical. The explanation is simple: a boundary is an outcome, a controlled shot is a process. The side ahead in process stays close to a big score; the side chasing only boundaries collapses to 120 while trying for 170. Powerplay xG carries two separate variables, the fielding restriction and pitch bounce—and this is where Bangladesh's pitches punish the league.

The middle overs, seven to fifteen, are the real battlefield of the BPL. The batters who walk in here—experienced men like Mushfiqur Rahim or Mahmudullah—are not there merely to score; their job is to open gaps between deliveries. For every spinner I pulled two numbers: boundaries per over and forced dots. The result is striking—the spinner who bowls more dot balls does not always take more wickets; the one who concedes slightly more but drags the opposition's strike quality down is the one controlling the match's flow. Our selection still gets stuck on wicket counts. If a spinner concedes 34 in four overs but cuts strike quality by 30 percent, he was the most valuable bowler on the ground—even with a zero beside his name.

In the death overs I built a cricket version of PPDA—"pressed dots per over," meaning how many deliveries in the last five overs a bowling side can pin a batter down to line and length. PPDA showed me Germany because the number measures pressure, not outcome. Cricket works the same way—45 runs in overs 16 to 20 is not bad if twelve of those balls forced the batter onto the wrong foot. The two sides creating the most pressed dots in the last five overs this phase are not top of the death-over economy table—yet their win rate is the highest. Matches are won by applying pressure, not merely by blocking runs.

There is an invisible layer of the regular season that never shows on the table: fitness and scheduling. Mirpur to Sylhet, Sylhet to Chattogram—travel and back-to-back matches drain fielding intensity in the final five overs. In my coded data, by the third of three consecutive matches a side's intensity in the last fifteen minutes drops by roughly five percent. In 2026, in empty stadiums, I saw exactly this decay—across 306 matches, distance covered in the final fifteen minutes fell 5.2 percent. Empty stadiums taught me that home advantage is a variable, not a law. Back in the BPL I ask the same question: is Mirpur's "home advantage" the crowd, or a squad's familiarity with its own pitch? My data says travelling sides behave differently in Sylhet than in Mirpur—the cause is not the crowd, it is the pace of the wicket.

There is another layer nobody measures: umpiring. In the BPL the consistency of lbw and wide calls shifts from venue to venue; a single wrong call in the powerplay can reshape an entire innings structure, so I track it separately, because it feeds straight into the xG chain.

On the auction table I place the same mirror. The link between a player's price and the xG he adds is not always a straight line. In recent BPL seasons a large share of the most expensive batters start slowly in the powerplay—because their reputation was built at the finish, not at the top. Yet franchises pay for the top of the batting order. That is not a market error, it is market blindness. In Bangladesh, I taught a league to see its own xG. Some think I am judging players; I am handing teams a mirror of themselves.

Now the admission: correlation is not causation. Powerplay xG and match wins are related, but it is not a one-way street—wickets change how batters carry risk, and the model does not capture that. Blaming the pitch is easy but wrong. For several seasons I have watched everyone cry about Mirpur's slow wickets, while the sides that built separate field placements for their spinners on those same wickets are the ones winning. The real dark spot is the middle-overs batting order—where the shortage is not talent but planning. The word "talent" is how we paper over that gap. And my model is not a verdict, it is a mirror; without what coaches and players see from the field, a number is half a truth.

For the next round I would tell selectors to watch one number: the percentage of controlled powerplay shots, and pressed dots in the final five overs. Wickets and boundaries will arrive on their own. The real question is this—will we decide by reading the scoreboard, or will we have the courage to watch what actually happened out there?