Empty Chairs in Mirpur, a Spreadsheet in Rawalpindi: Why Home Advantage Is a Variable

September 2026, Rawalpindi Cricket Stadium. Fourth day of the second Test. Bangladesh needed 185, six wickets in hand, and Litton Das had already made 138. From my study in Sydney I was logging ball by ball; on the second monitor sat the home-advantage coefficient sheet I had built myself. The sheet said Pakistan's home edge at this venue was 0.41 — roughly 60 percent of the expected home benefit had evaporated.

The scoreboard agreed. In the first Test, Pakistan declared at 448/6 and still lost by 10 wickets. In the second they made 274 and 172, and lost by 6 wickets. Two matches, two defeats, no wins — on their own soil, in front of their own crowd.

Something became clear that night. The roar of the stadium, the familiar dressing room, the home food — all real, none of it a moral asset. These are input variables. They can be weighted, and they can be zeroed out.

Context

The sheet is not new. In 2026 the A-League returned to empty stadiums in Australia. I tracked 24 matches and found home teams' xG had fallen from 1.45 to 1.12, while away teams' PPDA improved from 12.1 to 9.8. Within 72 hours I updated the model and installed a no-crowd coefficient. After we adjusted Western Sydney Wanderers' set-piece routines, their set-piece xG per match rose from 0.18 to 0.31.

That experience taught me a line I now repeat before every cricket series: empty seats taught me that home advantage is a variable, not a myth.

In cricket that variable has four parts. The crowd index — attendance, tickets sold, average decibel level. The pitch baseline — the venue's average score across its last ten innings, spin share, day-night behaviour. Travel load — days in transit between matches, time-zone shift, rest hours. The toss coefficient — how often winning the toss and bowling first has actually paid off here.

In Asian conditions the pitch is the heaviest of the four. Mirpur's fourth- and fifth-day surface, Chattogram's sea-influenced humidity, Rawalpindi's dry flat deck, Galle's green tinge — each carries its own signature. That is why I never write home advantage as a single number; I write it as a range — 0.35 to 0.55, with a sample-size caveat and a sensitivity analysis attached.

Keeping the method simple matters. I write the weights down before the series begins and I do not change them afterwards to fit the story. To me that is fraud, and the beauty of a spreadsheet is that it catches the fraud. I do not trust the eye test until the data signs the same sheet.

Core analysis

Put the two Rawalpindi Tests side by side and the picture sharpens.

| | First Test (21–25 August 2026) | Second Test (30 August–3 September 2026) | |---|---|---| | Pakistan, 1st innings | 448/6 dec | 274 | | Bangladesh, 1st innings | 565 | 262 | | Pakistan, 2nd innings | 146 | 172 | | Bangladesh, 2nd innings | 30/0 | 185/4 | | Result | Bangladesh won by 10 wickets | Bangladesh won by 6 wickets |

The 448/6 declaration in the first Test is the real trap. A score that large means a batting-friendly pitch, limited seam movement, and a game of patience for fast bowlers. In the second innings, on the same surface, Pakistan folded for 146. That gap cannot be explained with the word pressure alone; it is ball condition, a reverse-swing window, and the line and length of Bangladesh's seamers. Bangladesh replied with 565, Mushfiqur Rahim making 191.

The second Test flipped the equation. Pakistan 274 and 172, Bangladesh 262 and 185/4. A small target, but a large pressure — because on the Rawalpindi deck spin slowly bares its teeth in the fourth innings, and Bangladesh's batting order read that subtle shift correctly. Litton Das's 138 came exactly when the ball was old and the pitch was changing character.

This is the central conclusion: Pakistan's home advantage did not disappear; Pakistan mis-arranged its own home conditions. By preparing a batting-friendly surface they disarmed their own fast bowling, their single biggest weapon, and handed the opposition the luxury of settling in on a flat deck.

The comparative framework earns its keep here. I run the same template across ODIs, T20 franchise leagues and Tests, but I change the weights. In T20 leagues squad rotation is higher, travel is lighter, pitches are relatively neutral — so the home-advantage weight is usually lower. In Tests it is the reverse: five days, pitch deterioration, the long-tail effect of the toss — the weight is heaviest. ODIs sit in the middle, though add dew in a day-nighter and the toss coefficient suddenly grows heavy.

Comparing Mirpur and Rawalpindi teaches something. At Mirpur, home advantage comes mainly from spin share — home spinners already know the grip, the bounce, the speed variation off the surface. At Rawalpindi it comes from the reverse-swing window for fast bowling. On the day a curator prepares the wrong kind of pitch, the home team cannot find its own weapon. That is exactly what happened to Pakistan.

One more borrowing is worth noting, because I took this framework from football too. At the 2026 World Cup semi-final in Russia, England's xG after 90 minutes against Croatia was 1.2 to Croatia's 0.8; the match finished the other way, and Luka Modrić covered 14.2 km. I began with the live thread and ended with a broadcast truth — the number tells the truth of the first 90 minutes, but the match ends in the 120th. In cricket, that extra time is called the fourth innings.

Contrarian angle

Declaring a law off two matches would be foolish, and I will not do it. Between correlation and causation there is an empty space, and before stepping into it three alternative explanations should be hung on the wall.

Pitch curation is one. A flat deck erases the home pace attack's main edge. Squad transition is another. Pakistan's Test squad lacked experience and consistency at the time, while Bangladesh's seam attack had added raw pace in Nahid Rana, who made his Test debut in Sylhet in March 2026. The third is the most neglected — schedule geometry. With both Tests at the same venue, the travel variable was almost zero.

That last point deserves its own paragraph. When we say home advantage we usually mean crowd and familiar conditions. But zero travel load silently removes a major structural benefit for the host — the visiting side gets two adaptation windows, twice the chance to build a relationship with conditions. In this series we did not watch home advantage collapse; we watched several of its inputs go inactive at once. The difference sounds small. For the model it is enormous.

And one caution for myself. Because Pakistan lost on a flat pitch, I cannot claim that a flat pitch always endangers the home side. In 2026, on similar decks, host teams batted big and saved matches. Run the sensitivity analysis and changing only the pitch variable moves the coefficient by 0.08 to 0.12 points — not enough to flip a decision. The pitch is a factor. It is not the only factor.

Takeaway

Two lines will stay on my monitor next series. One, how well Bangladesh converts Mirpur's spin share into a coefficient at home, especially once the ball goes old in the second innings. Two, whether Pakistan changes its pitch-curation approach in its next home series, or returns to the same flat template.

The spreadsheet remembers what the stadium forgets. The match ends, but the model keeps playing — and the first ball of the next innings is a fresh data point for me.