88 in Six Overs and a 31-Run Over: At the Hong Kong Sixes, India's Defeat Is a Story About Format, Not Form

Mission Road Ground, Mong Kok. Here the six does not land in a stand. There is a makeshift board at the back of the ground, the ball clears it and goes out toward the road, and a boy runs to fetch it. In forty-one years I have stood on many grounds like this — where the boundary is a strip of white paint, where there is no moat between the spectator's chair and the pitch, where the run-up is two patches of grass. On a ground like that, the arithmetic of runs is never textbook.

India made 88 in six overs. Pakistan chased it down with four wickets in hand. Anyone reading the scorecard will call that a heavy defeat. I keep going back to the first over, which cost 31 — five sixes in a row. In a six-over game, one over is 16.7 per cent of your entire bowling resource. Thirty-one runs is thirty-five per cent of the target. In one over. That is not a failure of form. That is a failure of arithmetic, and the arithmetic is set by the format, not by the players.

The format has to be stated plainly before anything else, because almost everything being written about this match is format-mixing. The Hong Kong Sixes is a six-a-side, six-over invitational. Six batters per side, five wickets ends the innings. There is no lower order, no buffer, no number eight to hold things together. An innings is thirty-six balls. If two of those overs go wrong, half your innings has gone wrong.

Mission Road is a community-scale ground, not a full international venue. The boundaries are short. Of the eleven sixes struck across both innings, at least half are an artefact of the venue rather than evidence of mastery. Every number in this match — 88 in six overs, 40 off 11 balls, 35 off 8 — is structurally non-comparable to T20I benchmarks. I learned that in July 2026 at Lord's, filing a Women's World Cup final as a live blog rather than a match report; after that I stopped trusting a number until I knew which game had produced it.

Pakistan needed 89. First over 31, second over 28. Fifty-nine runs, sixty-six per cent of the target, inside twelve legal deliveries. Both overs were bowled by India's two most experienced seamers, Krunal Pandya and Natarajan.

In a six-over format, experience is not an asset. It is a bet. You pick the senior bowler because he will absorb pressure. But in six overs there is no time to absorb anything. A bowler gets three or four balls to find his length, and if the first two are not on the spot, the batter is already ahead of the game. Krunal's over was not lost to skill; it was lost to distance, and at Mong Kok the distance is short.

The single most important fact of this match is that Pakistan scored two-thirds of the target in twelve balls. After that there was no uncertainty left in the contest. Pakistan lost two wickets — Afridi and Nafay — and Niazi finished it with a six off his first ball. The scorecard says four wickets. The truth is the match was settled in the first over.

Do the balls-faced arithmetic: Afridi 8, Nafay 12, Samad 3, Niazi 1. Roughly twenty-four legal deliveries, before wides and no-balls. In a six-over innings that is a finish around the fourth over. Pakistan very likely won with about two overs to spare. That figure is derived, not stated, and my confidence is medium rather than certain — but it changes the reading, because a side that finishes in the fourth over did not control the chase. It detonated it.

India's collapse was structural. Tewatia and Krunal both fell first ball — two experienced batters gone for nought. Natarajan was left unbeaten at the end, which means a specialist bowler never got to bat. Two first-ball ducks in a six-batter team means half the innings' scaffolding fell inside the first over. In T20 you say: save wickets, save overs. Here there is nothing to save. Six become four, and those four must score at twenty-plus an over.

That is not a talent problem. It is a selection problem, and it is a small version of an argument I have made for years: India's celebrated bench strength is a selection question, not a talent question. In a six-a-side team you need three players who can both bowl and bat. India picked specialist bowlers who were not batting options, and the consequence was an innings with nobody left to bat at the end. Natarajan unbeaten is not a statistic. It is a message.

Pakistan's win is not clean either. Four wickets, 89 chased, done by the fourth over — it reads like control. But they lost two wickets, and one of them was Afridi, the man who had just hit five sixes, dismissed trying to finish the game faster. Pakistan won this match; it did not manage it. Chasing 89 in six overs needs no plan, only one good over. They got it immediately. Had Krunal's over cost twelve, Pakistan would have needed 70 from the last two, and then we would have learned something about what they actually have.

The tournament's own language — "bounce back", "kept hopes alive" — tells you Pakistan had almost certainly lost their opening Group C fixture. This match mattered because there was no route left after it. That information is not in the scorecard. It is in the dressing-room air.

Three misreadings are circulating. The first: India were bowled out for 88 in six overs, therefore Indian batting has a problem. Convenient, and wrong. Eighty-eight in six overs is 14.7 an over; it is not a bad score. The problem is that 22 an over was achievable on the same ground on the same day. When two-thirds of a target goes in twelve balls, the argument should be about one over of bowling, and about whether a six-over side should prioritise experience or flexibility.

The second: Afridi's opening over is the birth of a new talent. Possibly. But five sixes in this format are not proof of technique. Short boundary, six bowling options, one bowler who cannot find his rhythm — any competent batter can hit five sixes through that combination. I am not saying the player is not good. I am saying this match proves nothing about him. Selecting a T20I side from this format is like picking a marathon team from a 100-metre race.

The third, and the cleverest: this was another chapter of India versus Pakistan. It was not. It was a group match in an invitational tournament on a community ground, where both sides are there for the tournament's profile and the players' extra payday. There is nothing wrong with the rivalry framing — the market needs it. But if you read it as a rivalry, you never reach the question that actually matters: what is six-a-side cricket, in itself, and who is it for?

The beat was there long before anyone thought to listen for it. The real significance of the Hong Kong Sixes is not India against Pakistan. It is a window for cricketers who have no door — associate players, domestic names who never get a cap, men for whom six overs is not a footnote but a career. When I watch this tournament I see the players who will be back at work on Monday. Most of what happens here is repetition, and that is the story.

For the next group fixture I will not watch the scoreboard. I will watch how many of India's six names change. If it is the same six, the management has filed this defeat as a format accident. If an all-rounder comes in, something was learned. And if Pakistan treat this as a controlled win and wait for another over like that one, they will wait a long time; those overs do not arrive on schedule.

Six overs. Thirty-six balls. One bad over and the match is gone. In a game where the cause of a defeat can be counted this precisely, returning to the old argument about who is stronger is a waste of everyone's morning.

My notebook has one question in it today, and it is not about either team: if one over is thirty-five per cent of a target in this format, can any coach genuinely plan a bowling sequence — or will we all keep saying, every time, that it was somebody's day?

It was nobody's day. It was the over's.