The First Column of the Dhaka Desk File: Where BPL Home Advantage Actually Hides

Seven in the evening in Dhaka. The fan turns slowly above the desk, and one column sits still on the screen. For the current Bangladesh Premier League T20 season, the home-team win rate across the 24 matches played at the Sher-e-Bangla National Cricket Stadium reads 38 per cent on my sheet. In the next column, the same index for foreign franchise leagues sits between 54 and 58. Placed side by side, the two numbers started an argument. Mirpur means a fortress — that phrase echoes from the commentary box to the thumbnails, the fan forums, even the board's press notes. My sheet says the opposite. I opened the Dhaka desk file, and the first column was already arguing with me. I first assumed an entry error, that I had mixed up a venue or dropped a fixture. Three cross-checks later, the column had not moved. So I decided the quarrel was not with me; it was between the numbers themselves.

The file I am working with is not a board document; it is my own desk's ball-by-ball log. Since I built the Dhaka data desk in 2026, I have kept one rule: no match report leaves without a dot-ball percentage and a powerplay run rate. In cricket that is the equivalent of xG or pressing data in football, at least for me. This BPL season, 46 matches have been logged across three venues — Mirpur's Sher-e-Bangla, the Zahur Ahmed Chowdhury Stadium in Chattogram, and the Sylhet International Cricket Stadium. For every match I filled fourteen columns: powerplay run rate, dot-ball percentage, separate spin and pace economy, the field-first share, the second-innings run-rate delta, the fielding side's review success, the scheduling slot (day or night), the rest days in between, the travel distance, and an estimated dew level.

One extra condition I added later: I do not measure dew with a gauge, I measure it through the ball's grip and how often the fielders near the boundary wipe their hands. This is not a precise method; it is a proxy. But I have worked with it for five years, because nobody installs a dew meter in a stadium. What is not measured must be trusted through indirect evidence. That indirect evidence sits at the centre of this story.

First I split by venue. In Chattogram, across 12 matches, the home win was 50 per cent; in Sylhet, 40 per cent across 10; in Mirpur, 38 per cent across 24. The venue we call Bangladesh's most 'home' ground, Mirpur, is where the home side fares worst. Sylhet and Chattogram, where the crowd is often neutral or semi-neutral, see the home team do comparatively better. That inverted relationship stopped me first.

Then I cut by match time. In daylight matches the home win is 52 per cent; in night matches it is 34. That is the first clue. Roughly seventy per cent of the BPL fixture list sits in the night window, because of broadcast ratings and prime time. And night means dew. Dew means the ball loses its grip, the spinners lose their bite, and batting becomes easier in the second innings.

The second-innings run-rate delta is the most honest column I keep. Across the season, the first innings averaged 7.9 runs per over, the second 9.2 — about 1.3 runs more per over. That is no small gap; over seven overs it is nine runs, enough to flip many matches.

Then I picked up the toss column. In 31 of 46 matches — 68 per cent — the winning captain chose to field. The reason is no longer hidden: nobody wants to bat first, wet the ball in the dew, and then suffer in the chase. Winning the toss and choosing to chase is now almost an institutional decision.

Fielding-first sides win 63 per cent of the time; batting-first sides 37. Such a clear pattern is rare in T20, where toss bias usually stays close to fifty-fifty. Here it lands near two-thirds.

But I stopped at this point, because the first insight was forming. The column labelled 'home advantage' in the BPL is not measuring any quality of home at all — it is measuring dew and scheduling, things we have given the wrong name. The Mirpur fortress story is collapsing for exactly the reason it was built: night matches, a wet ball, and toss-driven chasing.

At the venue level, the spin-pace split makes the picture sharper. At Mirpur, spinners' economy is 6.9, pace 9.2 — a gap of nearly two and a half runs. Yet in the second innings that gap almost vanishes; spin economy jumps to 8.4. Dew is spin's worst enemy, and however spin-friendly the Mirpur pitch is, the night dew washes that advantage away on paper and on grass.

The powerplay numbers tell the opposite story. Home teams score 7.2 in the powerplay, visitors 7.8. In the first six overs the home batters bat slowly, holding back on attack. One easy explanation is that they are batting first against the new ball, when the pitch is still damp and the ball moves more.

Dot-ball percentage supports this reading. Home teams sit at 43 per cent, visitors at 39. In T20, four percentage points mean roughly five extra dot balls an innings, costing five to eight runs.

Here my bolder hypothesis formed. Mirpur's home side struggles because it bats first more often, eats more dot balls, and bowls in the dew. The advantage does not accrue to the home team; it accrues to the team that wins the toss.

In other words, home advantage is really toss advantage. And toss advantage is really scheduling advantage. And the schedule is set by the board's file, the broadcast window, and prime-time ratings.

Now comes the question dearest to a data monk like me: can we separate venue from time? In Sylhet, the night home win is 31 per cent, the day 53. In Chattogram, night 38, day 55. In Mirpur, night 33, day 51. Three venues, one direction — the schedule is the true venue-neutral variable.

Using the dew proxy makes it clearer still. In night matches where my dew index read 'high', the second-innings run rate was 9.8; where it read 'low', 8.3. Not all nights are equal. A cool, dry night in early December and a humid night in late January are two different worlds.

This is where the cruelty of the schedule leaks out. A few early-season matches were played at midday; later the whole fixture list shifted to the evening. So the home-advantage column visible on the table is an average — an average of two different conditions that describes neither.

Another column — rest days — quietly tells a large truth. Sides playing back-to-back matches lose 0.6 off their powerplay run rate on the second day, and their dot-ball percentage rises by about four points. In the BPL's compressed schedule, this happens regularly.

Travel distance is part of the same story. Teams travelling from Dhaka to Sylhet or Chattogram with only one rest day have consistently produced weaker powerplays in the next match — on average 0.4 off the run rate. That is not huge, but in T20 such small margins decide results.

Now to the section nobody discusses — women's cricket. I opened the scheduling file for the women's matches running alongside the BPL season. Nearly every one sat in a weak morning slot, at the same venue, with minimal promotion. Between the sponsor deliverables and the 'women's empowerment' bullet points, the matches disappear at the edge of time.

The data for these matches is almost incomplete, because scoreboard coverage itself is irregular. A league that parks its women's game in the morning also loses them from its data columns — that is not an accident, it is a decision. The board's schedule file is a document of values, and in that document women are still waiting.

I return to the home-advantage story. Dew is one explanation, but there is a danger here — dew and night arrive almost together, so one borrows the other's name. Unless we separate them, we tell stories, not analysis.

This is exactly where 2026 handed me a rare gift. In the Covid season the stadiums were silent — no crowd, no applause at the boundary, no roar of encouragement. If home advantage were truly the power of the crowd, it should have melted away that season.

In my log, the home win rate in that silent season fell from 40 per cent to only 38 — essentially unchanged. When the 2026 stadiums went silent, the home-advantage columns began to confess — the crowd was not the driver. The drivers were the pitch, the dew and the schedule.

This is my second, more uncomfortable insight. The crowd's roar is not the cause of home advantage; the administrative decisions on scheduling and pitch preparation are. In the empty-stadium natural experiment, whatever survived was real; whatever evaporated was illusion.

Now I stand against myself. I am writing from the Dhaka desk with 46 matches — a small sample. Drawing 38 per cent from 24 Mirpur matches means a wide confidence interval. Five matches swinging the other way could change the picture.

The second objection runs deeper. The word 'home' is almost meaningless in this league. In franchise cricket, players live in Dhaka year-round, train in the same nets, at the same venues. Who is 'home' and who is 'away' is not geographic — it is administrative, a matter of labels.

The third objection: dew itself is an effect, not a cause. Dew comes from the combined effect of time, humidity and temperature, all set by the season's calendar. So behind dew, too, another layer of administration hides.

I have learned to trust the row that refuses to fit the story. Each of these three objections tugs at one leg of my argument. Yet the story does not fully collapse, because the direction points the same way across three venues, two innings, and the silent-crowd experiment.

I gave my junior analyst one task — try to break my conclusion. He found that of the 24 Mirpur matches, in 9 the home side actually chased, and won 5. So when the home team wins the toss and chooses to chase, its win rate rises to 55 per cent — close to the league average.

This hardens my conclusion rather than weakening it. The home side does well exactly when it can take the toss advantage. Without the toss, the home team gets no special power from the venue. The advantage belongs to the toss, not the fortress.

I had another idea — that BPL pitches at Mirpur might be deliberately made spin-friendly to help home spinners. The numbers do not support it. Mirpur's first-innings spin economy is 6.9, but that applies equally to both sides' spinners. There is no evidence of an advantage for specific home spinners.

The dashboard was never the answer; it was a map I had to redraw. On this map, Mirpur is no fortress; it is a story of a cool, humid night, where the ball slips from the hand and the toss-winning side takes its advantage.

A practical lesson has accumulated from this whole investigation. In cricket analysis we often treat a venue's name as a cause. But a venue does nothing by itself. The pitch curator does, the board's scheduling committee does, the broadcaster's prime-time demand does. The game happens on the field, but the advantage is built in an office file.

And right here the audience question arrives. How the toss was taken before the match, how much water the pitch got, when the roller ran — none of this is announced to the crowd. They see only 38 per cent and think the team is bad. Yet the explanation sits silently in front of them, simply never spoken.

Transparency means something only when the information behind a decision reaches the audience. So far the BPL's dew, pitch preparation and scheduling logic remain a dark room for the viewer. The numbers are visible; the reasons are not.

For the next round I am keeping three warning signals. First, before reading any home-win statistic, I will ask whether the match was day or night, and who won the toss. Second, if a side plays on back-to-back nights, I will expect its powerplay run rate to drop. Third, if the women's match slots change, the data there will change too — and I will log it separately.

Finally, I leave one question hanging, one that the next season will answer. If the board moves half the fixtures from evening to midday, will the home-advantage column climb back to 50 per cent? I am assuming it will. And that day it will prove that the 'fortress' we spent years building was a scheduling accident we mistakenly called emotion.