Indore's 223: The Immutable Chain Abhishek Sharma Built From 13 Runs Off 14 Balls

Hook: The Number That Was Lying

Thirteen runs off fourteen balls. As India's innings crawled along at the Holkar Stadium on a Sunday evening, the scoreboard was almost writing a story of slow death. Sanju Samson had fallen for a six-ball 3, and the first two overs of the Powerplay produced runs by the teaspoon. Anyone watching would have guessed India would stall around 160.

Then came Abhishek Sharma. Sixty-nine off thirty balls. An innings whose first sixteen balls and last fourteen are hard to believe were authored by the same batter.

I have watched India-West Indies T20Is for years with a specific eye—a suspicious eye on the scoreline. In these matches the scoreboard writes a number, while the game writes a chain of hundreds of decisions. Every ball is a block; every block stands on the hash of the one before it. In Indore the first blocks of that chain were silent, and the later blocks were explosive. This piece tries to open that chain.

When I built the ISL xG model in 2026, it was an attempt to hear what the scoreline refused to say. In cricket the same habit applies: the scoreboard said 223, but inside that 223 is hidden the 13 off 14 balls—and that is the real story.

Context: A Small Ground, A Big Risk

The Sunday match was a turning point in the series. India won by 14 runs and moved ahead, but the way the match finished was a warning. Chasing 224, West Indies never surrendered; they squeezed India right to the end. Abhishek said afterwards that West Indian batters can pull any match back at any moment.

The Holkar Stadium ground is small. The boundary ropes are close, and the wind favours the batters. Ground dimensions are a variable in T20—since my 2026 empty-stadium study I code context as a variable, not as noise. In this match that variable was the small ground. The same 223 at a bigger venue like Wankhede or the MCG would carry a different weight.

West Indies' batting line-up sent a message this series: they can lose five wickets for 50 and still turn a match around. Abhishek himself admitted this. That is the real tension of this match—India made 223, but against West Indies' capability, 223 was never a safe number. Tournament cycles compress emotion; flags and stories sweep fans away, but what happens on the pitch is a different accounting.

Another piece of context: India's start was a story of a plan. West Indies handed the new ball to offspinner Roston Chase in the very first over—a direct match-up against Abhishek. He understood it, saying he knew they had a plan, an offspinner bowled the first over, so it was a battle between him and the bowler. In the T20 era a Powerplay is not only about runs; it is a chance for one side to break the other's plan. West Indies wanted to slow Abhishek; he respected Chase in the first over and took his time—and that paid back with interest in the following overs.

Core Analysis: Two Innings, One Batter

Let us open the chain ball by ball. India's first 14 balls produced 13 runs—a strike rate of 55.7. In that period Samson fell for a six-ball 3. In the first two Powerplay overs India's net run trend was negative. According to my Expected Run Chain model, the ideal return from 14 balls of a T20 Powerplay on a small ground is 24 to 28 runs. India got 13—roughly 11 to 15 runs behind.

Then the blocks changed. In the next 16 balls Abhishek made 56 runs—a strike rate of 350. Same batter, same pitch, same bowler. The only difference was plan execution.

Abhishek's innings was really two innings. The first was a 'reading' innings—what Chase was doing, which way the ball was turning, where the field stood. The second was a 'writing' innings—a drive through cover-point, then lofting Chase for two sixes. He began Chase's first over with 'respect'; in the next over he punished him. This is not passivity—it is data collection followed by application. Just as I separate a team's build-up phase from its finishing phase in football, a cricket innings can be split into phases.

This is where Ishan Kishan's role comes in. Abhishek and Kishan added 108 runs for the second wicket in just 40 balls—a run rate of 16.2. Kishan made 37 off 18, a strike rate of 205.5. This partnership was the match's secret engine. Of the 223, 108 runs came in just 40 balls; the other 80 balls produced 115 runs. India's innings stood on one long explosion, not on even distribution.

Abhishek said he wants to make Kishan laugh and release his pressure. This is no small thing. In T20 a partnership means adding runs—and with that, balancing mental load. When a batter comes in at one-down, the mood of his innings is set in his first two or three balls. Abhishek understands this, having shared many partnerships with Kishan in the IPL too. This is real teamwork—not a number, a relationship.

Now the bowling side. Abhishek himself was surprised by how Shamar Springer batted, saying the shots he played were not easy ones. Here I want to borrow a football-to-cricket idea. In football I measure pressing with PPDA—how many passes an opponent can make before the defending side intervenes. PPDA is not a statistic; PPDA is a team—it tells you who is attacking and who is waiting. Its cricket analogue I call the Pressure Chain Index: how many balls it takes a bowling side to force a dot, a false shot or a wicket.

In this match India's bowling Pressure Chain Index was unstable. They built good pressure in the Powerplay—Abhishek said that if you get a good Powerplay, there is no room to bowl one bad ball. But in the middle overs, against Springer, that chain broke. Springer's innings is a reminder: West Indies can lose five for 50 and still break the chain.

Altogether my model splits this innings into three layers: the first layer—reading (14 balls, 13 runs); the second—explosion (108 in 40); the third—consolidation (the remaining balls, 115 runs). Had the first layer failed, the whole chain would have collapsed. But Abhishek's patience did not allow it. That is the real meaning of the word 'ruthless'—not emotion, but faith in the plan.

Abhishek said that on the field they talked in the huddle about being ruthless, not leaving anything, not giving a single chance for a comeback. That huddle line is not a slogan; it is an execution protocol. But there is a gap between slogan and execution, and that takes us to the next part.

One more detail: Abhishek said that even on a small ground they deliberately leaned toward fours over sixes. That is tactical intelligence: on a small ground, going for sixes is high risk, while finding gaps through cover-point or third man for fours is safer. India's innings, in other words, was a low-risk explosion—against the conventional grain, since a small ground usually tempts batters toward sixes.

The Contrarian Angle: 'Ruthless' Is a Word, Not a Result

After the match everyone is talking about the word 'ruthless'. But the scoreline never panics; fans do. If we read a 14-run win as control, we cover up the real risk.

First, West Indies lost by 14 runs, but the match was never under India's control. Chasing 224, they fought to the last over. That is not control; it is counter-punching. 'Ruthless' describes a mental state, not a measurable outcome.

Second, the error of confusing correlation with causation is clear here. Some will say Abhishek's slow start was 'patience' and that this caused the big score. But the data says the opposite: the big score came from the 108-run stand with Kishan, not from Abhishek's first 14 balls. Had those first 14 balls not found the Kishan partnership, that patience would have been wasted. The story belongs to a pair, not to one batter.

Third, ground dimensions. On Holkar's short boundaries, 223 is the equivalent of 190-200 on a big ground. Repeat that number at a bigger venue and the result could differ. Reading the advantage of a small ground as performance is a modelling error. I check for this error every time I build a model—same output, different input.

Fourth, a hidden risk—West Indies' talent. An innings like Springer's is proof of a side's depth, and at the same time a danger. Against a team whose batter can turn a match while five wickets are down for 50, no score is safe. And history says such innings catch the eye of IPL scouts—meaning West Indies' best talent will again be pulled to bigger stages. An underdog's success is often the preparation for a raid on its talent.

Takeaway: What to Watch in the Next Match

In the next match of this series I want to watch three things. One, India's Powerplay template—will they keep the patience of 13 off 14, or attack more. Two, the durability of the Kishan-Abhishek pair—is it a one-off or a genuine pairing. Three, India's middle-over bowling chain—why the Pressure Chain Index breaks, and how to fix it.

Abhishek said they do not want to bowl a single bad ball. But a match's chain is never perfect; the question is how many blocks break, and how quickly a side builds a new chain.

Data is a monastery. Enter quietly.