The Silent Database of Mirpur: Where Bangladesh's Home Test Advantage Disappeared

West gallery, Sylhet International Cricket Stadium. Third day, second session. A dusty March afternoon. Notebook on my lap, thermos on the next seat, camera bag at my feet. The scoreboard was showing nothing worth a timestamp. But the sound that was missing from the ground is what went into my notebook — no trumpet, no drum, just the creak of folding chairs and the shuffle of people leaving.

In an empty stadium, the game speaks in echoes, not roars. The cricket-echo that Mirpur, Chattogram and Sylhet have produced since 2026 is not comforting news for someone who travels to watch matches. It is a question. Because on the days Bangladesh used to break opponents at home, not just beat them, the gap between then and now is no longer visible on the scoreboard. It is visible in my spreadsheet, and in the silence of the stands.

My first database was not about cricket. In 2026, I filmed 12 matches of Rajshahi Collegiate School's under-18 football team on a borrowed camcorder and logged 47 set-piece sequences. Striker Arif Hossain (No. 9) scored 5 of his 12 goals from near-post corners. A 2,000-word breakdown went up on a local blog, got 3,000 views, and the coach started using my sheet in training. From that day, one habit stuck: decision after the frame, frame after the timestamp.

That habit took me to Russia in 2026, to Hannes Halldorsson's 63rd-minute penalty save. I watched the match five times to see how Iceland's 4-4-2 squeezed Argentina into 0.8 expected goals. In 2026 I applied the same method to empty stadiums: across 50 behind-closed-doors Bundesliga matches, home wins fell from 43 percent to 33 percent, and home teams scored 0.3 fewer goals per game. Two Bangladeshi coaches used that piece.

In cricket I asked the same question: is Bangladesh's home advantage an object or a habit? And if it is an object, which corner hides it — the pitch, the toss, the spinner's over-the-wicket line, or the noise in the stands?

My notebook holds 16 home Tests between February 2026 and October 2026: three wins, twelve defeats, one draw. In the same window, Bangladesh have won two away Tests — both in 2026, both in Rawalpindi. The gap between home and away wins is now roughly zero.

Read the table again. February 2026, Mirpur: an innings-and-106-run win over Zimbabwe. March 2026, Mirpur: a 546-run win over Afghanistan, Bangladesh's biggest Test victory. November 2026, Sylhet: a 150-run win over New Zealand, Taijul Islam taking 10 wickets in the match. Across the rest: West Indies won both Tests in February 2026; Pakistan won both in November 2026; Sri Lanka won in Dhaka by 10 wickets in May 2026 with the Chattogram Test drawn; India won both in December 2026; New Zealand won at Mirpur by 4 wickets in December 2026; Sri Lanka won by 328 runs in Sylhet and 192 in Chattogram in March 2026; South Africa won by 7 wickets at Mirpur and by an innings and 273 runs in Chattogram in October 2026.

Two of the three home wins came against opponents where the paper gap is wide. The third, against New Zealand at Sylhet, came on a surface where one spinner took ten wickets and carried the match on his back. The home wins are not the output of a system; they are either a gift from a weak opponent or one man's day.

Read the list of defeats and something else stands out. I cannot recall a single one of those twelve that rolled into the final session. 328 runs in Sylhet, 192 in Chattogram, an innings and 273 in Chattogram — those are not matches, they are timestamps. Beside each of them in my notebook is the same note: first innings, first hour.

I keep a simple method for that first hour: wickets in the first 15 overs and the run rate attached to them. In post-2026 home Tests, Bangladesh's first-innings collapses in that window draw the same picture — two or more wickets, run rate under three, then a small partnership that drags the total to 125-150. That kind of score cannot save Bangladesh at home, especially when they concede a first-innings lead.

Open the Rawalpindi file. August 25, 2026, first Test. Pakistan declared on 448 for 6, Shan Masood 151. What followed I watched from a room in Rajshahi at 2:40 in the morning — Bangladesh made 565, Mushfiqur Rahim 191. Pakistan's second innings lasted 146. Bangladesh won by 10 wickets. On September 3, 2026, in the second Test, Litton Das made 138 and Bangladesh won by 6 wickets to take the series 2-0.

I want to say this plainly: those two Tests do not announce a new aggressive philosophy. They are a story about a structural opening. A side that declared on 448 for 6 was bowled out for 146 on the fourth day. That is a fault line inside the opponent. Bangladesh inserted a lever into that fault line, coldly and patiently. Mushfiqur's 191 was not a highlight-reel cameo; it was a lesson in batting time.

So why does that patience vanish at home? My answer: at home Bangladesh believes it is the favourite, and believing that costs it the follow-through.

This is where my objection to the data invasion of dressing rooms begins. In recent years, most analysts around Bangladesh's set-up have argued for flat decks — modern batters express themselves, matches last five days, innings get long. On paper the logic is clean. In practice it optimises the wrong variable. Bangladesh's problem is not the character of the pitch; it is losing wickets in the first hour regardless of the pitch. A flat deck hides that problem. It does not solve it. If data must enter the dressing room, it should measure footwork at the point of defence and the success rate of the late sweep, not the millimetres of grass.

One thing I have tracked for years, and hardly anyone writes about. Mirpur's square was relaid at some point. My notebook has no date for that work. It has the scores from the Tests that followed, and one observation: ball speed dropped, bounce dropped, and the fifth-day spin is no longer as vicious as it was. Sylhet speaks differently — seam for two days, spin for two, with a strange quiet session in the middle. Chattogram is different again. Three squares, three characters, one team composition.

The toss. I log what Bangladesh does after winning it. In post-2026 home Tests, Bangladesh have mostly chosen to bat, and with no hesitation — yet the fear in the first hour has remained. Put the toss decision and the first-hour score in adjacent columns and the pattern is blunt: after choosing to bat, Bangladesh have repeatedly lost three wickets inside 40 runs.

Light and the fifth day. At Mirpur, light drops after four o'clock, the ball skids, and it becomes the spinner's hour. A large share of Bangladesh's home defeats have grown in that session — not only the final one, but the last half hour of the third session too. I log that window separately: 4:20 to 5:30. In those seventy minutes, Bangladesh's run rate falls and they lose, on average, a wicket a match. That is not an accident. It is a habit.

The spinner's load tells the same story. Taijul Islam is Bangladesh's primary weapon at home, and at home he can bowl long spells because conditions help him. But one pattern keeps returning in my notebook: Taijul's home success correlates weakly with team wins, because on days he does not take three or four, the batting cannot cover the shortfall. Two of the three home wins had a spinner at the centre. In the rest, the spinners applied pressure and the scoreboard did not answer.

Back to empty stadiums. In 2026, from 50 Bundesliga matches, home wins fell from 43 to 33 percent and home teams scored 0.3 fewer goals. What is the cricket translation? I am not claiming it as fact, but the hypothesis is interesting: a large part of home advantage is psychological, and its fuel comes from the crowd. In post-2026 home Tests, Bangladesh's crowds were thin, patchy, rarely continuous. A side raised to pin an opponent down with crowd pressure found that weapon blunted. A bowler does not get the roar back when he bounces someone at midnight.

I stop here. Writing in Bengali, English words keep slipping in. My notebooks are, in truth, a mess of two languages — data on the right, timestamps on the left, half-finished sentences in the middle. There is no time to write full sentences from the stands. And those unfinished sentences later turn out to be the truest ones.

Let me state the contrarian angle cleanly. Over the past two years I have heard two big explanations for Bangladesh's home Test failures. The first is a lack of intent — low strike rates, a slow top order, an outdated approach. The second is bad pitches — curators produce self-destructive sporting surfaces and the match becomes a lottery.

Both are comfortable. Both are largely wrong. On intent, look at how slowly those 565 runs in Rawalpindi were built. That was patience, not intent. On pitches, Bangladesh have lost at home on flat decks and won away on seaming ones in the same period. The link between surface character and outcome is far weaker than it feels.

The real variable is duller and more specific: at home, when opposing spinners bowl into the off-stump line, Bangladesh's top order freezes its feet. There is no pitch-based explanation for that paralysis. It is a technique problem, and technique does not show up in a database — it shows up when you watch hours of footage.

After years of watching matches, one thing I have learned: the margin between a run and a defence lives in frames nobody watches twice. The frame where the batter decides whether the foot goes forward or back. Those wrong decisions get logged as return catches or lbw, but the frame says something else: hesitation.

As a travelling writer I hold one advantage a studio analyst does not. Travelling with a team means learning the rhythm of buses, meals and set pieces — who stays silent in a team meeting, who goes to the nets alone at dawn, who talks most on the bus after a loss. After Bangladesh's home Test defeats, what I notice most is not a score. It is the morning net session the next day. After a win, the top order finishes in ninety minutes; after a loss, four hours is not enough. The problem is that the four hours of effort return to the same mistake in the next series. Effort and correction are different things.

Now the underdog angle, which matters after Rawalpindi. After the 2026 win, the old rhythm returned — congratulations, then scouts' phone calls, then franchise contracts. Nahid Rana's pace suddenly drew every eye, clips of his quickest balls spread everywhere, and within months the workload question followed him. That is the economics of an upset: the win is yours, but the market takes the most valuable part of it, and it arrives far faster than the trophy does.

This is where the tension between data and dressing room is most visible. When analysis enters a dressing room, its best use is workload mapping, injury profiling, opposition bowling patterns — things that actually touch the rhythm of a match. Too often it becomes its own dialect of pre-match decisions: match-ups, working percentages, left-right combinations. At one point during Bangladesh's home slump, I felt the team trusted the opposition's spreadsheet more than its own.

Take one specific innings I keep re-watching. Sylhet, March 2026, first day, Bangladesh's first innings, from the seventh over to the fifteenth. A spinner bowling flat into the off-stump line, a crowded field with slip and short leg. The batter's feet stay still for roughly three frames, then decide to play through cover. No reverse sweep, no long sweep. Because the memory of succeeding at home tells him patience will bring runs. Away from home that memory does not exist, so he is forced to take risk.

That is the real pattern. Bangladesh's home Test failure is not a crisis of courage, it is a crisis of comfort — forced away, they play well; at home, they slow down in search of safety. I built the database one corner at a time, and the pattern finally blinked.

A caveat, as part of doing this honestly. Much of this piece rests on my own notebooks and ground observation, some on match records. Some Tests in this window were played with limited crowds, others almost empty. So I keep the psychological reading of home advantage as a thesis, not proof. Verification needs several things: actual attendance series per Test, session-by-session run rates, and first-15-over wicket data — a running log, not a single scorecard.

Another gap is my own fault. Long stretches of simply building the database have forced me to publish late more than once. Working independently, I never sit in the opposition's room, so the line between inference and fact blurs. In this piece I have marked where I am unsure, even which cells of my own sheet are incomplete. What I am sure of is the silence at the ground, the mistakes of the first hour, and those seventy minutes of the final session.

So what do I watch in the next home series? Three signals. One, the toss decision and its logic — batting or fielding. Two, the first-hour score: if Bangladesh lose fewer than two wickets in 15 overs I will not be satisfied; I will watch the last half hour of the third session. Three, not the strike rate but the length of innings — how many batters face more than 80 balls. That last point will not please analysts, because it is not sexy.

The question ahead: if Bangladesh's home Test failure is in fact a recurring technique pattern, who is responsible for measuring its evolution next series — the coach, the analyst, or the person sitting in the stands logging timestamps? If Mirpur fills again and the first hour draws the same picture, we will have to admit it: the problem was never in the crowd. It was in the batter's feet.