The Chattogram Table Was Lying: 32 BPL Matches and an xScore Audit

February 14, 2026. Twenty-two yards from the mid-wicket boundary at Chattogram's Zahur Ahmed Chowdhury Stadium, I wrote two numbers side by side in my notebook: 163 and 171. The scoreboard said the hosts had won by posting 163. My ball-by-ball log said that on that pitch, in that humidity, after that toss, the two sides' expected totals were 171—and the tilt favoured the visitors. Chattogram have won four of their five home games in the first leg; in exactly those four wins their xScore margin was negative. I am not hunting a conspiracy. I want to know how quietly a league table can lie. Context first, because numbers born in a place mean little if you do not know the soil. I built xG Chattogram because the league table was lying in plain sight—the method that began in 2026, hand-logging 14 shots from Chattogram Abahani's 2-1 win, now lives as a ball-by-ball log. The 64-match spreadsheet of the 2026 World Cup taught me that a tournament must be framed by repeatable metrics, not match reports. Furloughed in 2026, scraping 306 matches, I learned that crowd presence is a controllable variable: with empty stands, home win rate fell from 45.2% to 40.1%. This time I applied both lessons to the 2026 BPL first leg. Sample: 32 matches between January 1 and February 20, 2026, across four venues—Dhaka, Chattogram, Sylhet, Khulna. For each match I logged pitch age, dew timing, toss outcome, travel gap, bowler workload and actual attendance. Expected runs rest on three inputs: shot quality, match state, pitch decay. Two colleagues verified entries independently, because the ethics of counting is simple—a number nobody can check is not a number, it is a claim. The core finding sits in the powerplay and the death overs. At home, Chattogram's powerplay xScore is 47.2 against a league average of 51.8, so they start behind. Yet their powerplay wicket loss is 0.9 per match against a league 0.7. Bowling tells the opposite story: their new-ball pair sits at 21.3 on the dot-ball pressure index (dot balls bowled per wicket taken), better than the league's 24.6. They build pressure with the ball and cannot buy it back with the bat. At the death it turns brutal: Chattogram's death-over economy is 11.4 against a league 9.8. Across 32 matches, set-piece phases—powerplay and death—supplied 58.4% of their runs, against 52.1% league-wide. They crawl through the middle, gamble late, and that gamble is exactly what decides small chases. Thirteen years of watching from the boundary rope tell me this pattern is no accident. Against spin in the middle overs, singles and sweeps are read so carefully that sides routinely let their scoring rate sag between overs 7 and 14, then treat the last three overs as rescue work rather than a plan. I have watched batters hesitate over a second run in the tenth over; that hesitation is invoiced later. Set-piece dependence is a trap. Only 47% of Chattogram's runs came from powerplay and death, but that kind of scoring does not travel, because opponents change plans in the second leg: boundary cover with the new ball, cutters at the death. Fielding is leaking value too—six catches dropped in the first leg against a league average of 5.2. Here I distrust heatmaps. A heatmap shows where the ball landed, not why a fielder stood there. A fielder's real role emerges from his starting position relative to the bowler's plan, not from a coloured blot. The bowling story differs. Taskin Ahmed's new-ball spell, Mustafizur Rahman's slower cutters, Mehidy Hasan Miraz's middle-overs control—those three layers put Chattogram's attack close to the league's best. Their problem is not talent but usage. The two frontline seamers have bowled 96.4 overs in 21 days; that workload bend shows up in economy in the second leg, and we usually discover it only when someone breaks down. Umpiring and reviews get their own ledger, because the transparency gap is countable. The first leg produced 29 reviews, 11 successful, with 9 falling to umpire's call. Not one of those nine was explained on the big screen. Fans buy tickets for the cricket, but the reasoning behind a decision is part of the package. A board that shows the review graphic while withholding the language of the decision treats spectators as a crowd, not an audience. Attendance is the most uncomfortable figure. By my count the first leg averaged 5,400; in the same window in 2026 it was roughly 11,200. When the stadiums emptied, the numbers did not go quiet; they changed their accent. An empty seat is not just lost revenue—it redefines home advantage, because the pressure moves from the batter's ears to the inside of his head. Sponsorship takes a direct hit too: advertising value per thousand spectators fell about 38% against the full-house sample. Now the counter-argument, aimed at myself. Thirty-two matches is a small sample; at that size the gap between a 43.8% home win rate and 2026's 40.1% is fragile, with a confidence interval near nine percentage points. Home advantage is not fixed—pitch preparation, dew timing and toss luck all bleed into results by venue. And an xScore model measures shot quality, not decision quality; for batters like Litton Das or Towhid Hridoy, a deliberate risk can register as an error when it was the correct play for the match state. The Data Monk does not worship numbers; he interrogates them until they confess context. Still, one claim I will make: the table's portrait of Chattogram as a strong home side rests on luck, not method. Three watch-lists for the second leg. One, middle-overs strike rate: if the run rate between overs 7 and 14 does not rise from 6.8 toward 7.6, set-piece dependence grows. Two, whether death economy drops from 11.4 below 10, because those two overs are the table's real editor. Three, whether crowds return—because a win in an empty stadium and a win in a full one are the same two points, and not the same thing.