The Anchor Is a Dead Machine — and the Scorecard Is Its Alibi

Hook

I opened the Delhi notebook and stopped believing the brochure that night — sitting in the West Stand of the Arun Jaitley Stadium, watching roughly sixteen thousand people rise to applaud a batsman who had spent forty-seven balls to make fifty-two runs. The team needed one hundred and eighty. The runs he made while holding on for more than fifty balls matched the arithmetic of defeat almost perfectly. Yet the scoreboard showed only "52" beside his name; "47" was written nowhere. That night the line went into the notebook: In T20, the currency is not runs but balls — and batting average is that currency's biggest counterfeit note. Four years later the line still feels both the cheapest and the most expensive thing I own — cheap because anyone can say it; expensive because nobody says it without the air of a stadium in their lungs.

I was at the ground that night, not in front of a television. The feed would not have taught me how sharply the demand for balls rose in the last ten overs, or how a fielding coach sitting below the scoreboard kept shifting his field placement each time the left-arm spinner returned. The camera shows you the batsman; the stadium shows you where the ball is not going. That night the ball kept not going through cover. That was the real news.

Context

T20 cricket's first decade stood on a particular morality. The idea was simple: when wickets fall, teams lose, so one batsman must be preserved, however slowly he plays. From that belief the "anchor" was born — a role in which a batsman lifts the burden of strike rate off his own shoulders and takes the team's fear of defeat into his own body. Broadcasters, scorecards, fantasy leagues, panel shows — everyone jointly declared the role sacred. Protecting your average became equivalent to virtue, and getting out quickly became equivalent to irresponsibility.

The problem is that this morality was written in an era when six runs an over was enough. That has changed. Power-hitting training in franchise leagues, shorter boundaries, flatter bats, two new balls in the powerplay — together these have made six an over a losing formula even for a mid-table side. Team totals in the IPL have soared. On April 15, 2026, at the M. Chinnaswamy Stadium, Sunrisers Hyderabad made 287/3 — the highest team total in IPL history. Against that backdrop, a batsman scoring at six an over is not holding the innings together; he is pushing the team backwards, and only the language of statistics fails to catch it.

I am writing this because T20 is now played every week, and every week I see an innings that gets called "responsible" in classical vocabulary while numerically it is a promise of defeat. I want to do the autopsy on this machine. The machine is dead. The only question is who is still standing beside it, checking for a pulse.

Core Analysis

Start with one calculation. Twenty overs means one hundred and twenty balls. Say a batsman survives the whole innings — roughly thirty-five to forty percent of the balls pass through his bat. If he plays at a strike rate of 130, he makes sixty-five to seventy-seven runs. If the other six or seven batsmen play the remaining balls at 140-150, the team reaches somewhere around 180 to 190. That is now a middling score, not a winning score. Which means the biggest myth of the anchor is that he saves the team — in truth he quietly sets the ceiling on the team's overall tempo.

Second calculation, the balls. A strike rate of 130 means thirteen runs per ten balls, roughly one dot or single every two balls. In the middle overs, when spinners bowl and the field is spread, those dots accumulate. The scorecard does not show them, because a scorecard does not count dot balls — a scorecard counts runs. Yet matches are won and lost on dot balls, not runs. If an anchor makes thirty off thirty, his average is two to two point five; but his team lost four extra boundary opportunities in those thirty balls. The average is his; the loss is the team's.

Third calculation, the phases. Modern T20 splits an innings into three parts — powerplay (1-6), middle (7-15), death (16-20). The single biggest predictor of team success is the strike rate in the nine middle overs. A side that plays below 140 there reaches the death overs and makes twenty-seven to thirty, because slogging there costs wickets. On November 10, 2026, at Adelaide Oval, England beat India by chasing 170/0 in sixteen overs — that was not just batting talent, it was a precise art of phase division. On the other side, on June 29, 2026, at Kensington Oval in Barbados, India made 176/7, where Virat Kohli scored 76 off 59 balls — a strike rate of roughly 129. India won because Jasprit Bumrah conceded just 18 runs in four overs for two wickets and squeezed South Africa at the death. That match proves the slow anchor survives only when you have a Bumrah in hand — that is, when someone else writes the cheque for your weakness.

Fourth calculation, the economics. In franchise cricket a batsman's value is set by his brand, the memorability of his innings and his average. But a team's victory is priced by its use of balls. In the crack between these two valuations sits the anchor. He is easy to write stories about — because a story's hero must survive to the end, and a surviving man is easy to put on television. The batsman who hits two sixes in two balls and gets out is the villain of the story; the batsman who makes thirty off thirty and stays not out is the hero. Yet the second man's strike rate is forty percent worse than the first's. Because the media sells survival as a moral quality, it makes strike rate look obscene.

Fifth calculation, the spectator. Sitting in stadiums, I have noticed that when an anchor is at the crease, the nature of the noise in the stands changes. The powerplay has a roar; in the middle overs that roar thins into a low murmur, and then people begin talking to the person beside them. In Delhi I have tried crude decibel readings on a phone app across several matches — not scientific, but the tendency is obvious. There is a sociology not of empty seats but of silent seats, and the hush of the middle overs writes down exactly how many balls a team is wasting. That silence is not rudeness, it is arithmetic — the crowd knows something is wrong, only what is wrong is not written on the scoreboard.

Sixth calculation, the bowling machine. DRS, Hawk-Eye, Snicko-Ultra — these machines now measure every ball's trajectory, bounce and swing. I have worked on machine autopsies; I know when a machine dies. In June 2026, after Germany lost, I wrote that the machine died in Moscow and the autopsy turned out to be all too human. In T20 the machine is dying differently — the technology supplies every data point, but nobody uses that data to make decisions. Expected-runs models for every ball have entered the ground, yet selectors and coaches still pick teams by looking at averages. The machine does not die; the person responsible for acting on it does — that is the most human autopsy of all.

Seventh calculation, opportunity cost. In an anchor's slot you could place a power-hitter at number two. His strike rate might be 150, but his average twenty. The question: which wins more matches? In recent franchise samples, strike-rate-heavy top orders win more matches, because a big score is easier to defend. But there is a trap here, and I will address it in the next section.

Contrarian Angle

I could be wrong, and my chance of being wrong is greatest precisely here: the pitch. Not every T20 wicket is flat. On spin-friendly Chennai pitches, on the slow low surfaces of Lucknow, or on a cracked, burnt raw pitch, a strike rate of 130 is a good score. In some 2026 matches we saw 150 defended comfortably, because the ball was not coming on and the bat was not connecting. There the anchor is necessary, because he absorbs pace, gives the spinner time, and saves overs.

My second doubt: the anchor's role is not defensive, it can be offensive. Early in an innings, when the pitch is damp, taking two or three overs is the intelligent move, because risk is high and reward is low. In fact, what I am against is not the anchor-role; I am against the anchor-doctrine — the doctrine that says surviving is always nobler than scoring fast. A twenty-ball anchor is fine; a forty-seven-ball anchor is often team suicide.

My third doubt: the injury-prone side. If your batting line-up is fragile, if you do not trust your sixth or seventh batsman, then an anchor is really insurance. He stops the domino collapse. In the 2026 World Cup final, India's 76-run innings matters exactly here — India's batting was uneven, the lower order fragile, so Kohli's slowness was calculated insurance, and it worked, because Bumrah and Pandya settled the remaining account. But if India had made ten fewer runs that day, we would not be calling Kohli's innings "responsible" — we would call it "slow." Success is the judge of strike rate, and the anchor's real existence lives inside that unfairness.

And my fourth doubt, against myself: I argue against the anchor from the stands, but the stands themselves love the anchor. The spectator wants to watch a man survive, because survival gives hope. The crowd lives in the story of a hundred from zero; in the story of two sixes and out, the crowd only laughs. My sociology says people do not want statistics, they want narrative. The anchor is a narrative, and that is his greatest protection.

Takeaway

I want to make a timestamped claim, because a claim without a timestamp is only a feeling — and a hot take is just a feeling that got tired of waiting. My claim: over the next five years, any franchise or side whose middle-overs strike rate drops below 150 will not win a trophy — unless they own a four-over Bumrah. I also claim that batting average will slowly leave fantasy cricket, just as the rules changed, so will the judgment change.

The question for the spectator: when you rise in the stands to applaud a man, are you saluting his runs, or his balls? And when you stopped applauding and started talking to the person beside you — was that silence the first draft of your defeat?