33 Sixes, 501 Runs and Hope's 45-Ball Century: West Indies Level the Series in Ranchi

Ranchi's JSCA Stadium. The 19th over of the second T20I. The scoreboard says West Indies need just 10 runs from the last two overs. Axar Patel has the ball. I took my eyes off the scorecard. In that one second, sound was truer than numbers—the flat crack of ball on the middle of the bat, then the unbroken roar of the stands. Shai Hope hit the first ball for six over deep midwicket. He pushed the second to extra cover and took no run. The third he launched over wide long-on—and with that six came a 45-ball century, a six-wicket win with nine balls to spare, and a 1-1 level series in a five-match contest. The match produced 33 sixes and 501 runs.

Those three balls deserve to be remembered separately, because together they are the summary of an entire chase. First ball—courage. Second ball—restraint. Third ball—decision. The full character of a T20 run chase is arranged inside three deliveries, and that is the real story of this match.

Context: 250, 240/4 and one night's arithmetic

The target was 250. At the end of 18 overs West Indies were 240/4. The maths was simple—10 runs needed off 12 balls. At that exact moment, Hope himself was 10 runs short of a century. The two sums met at the same point, and from there the match tilted toward a personal story. A 45-ball hundred, and the ball that brought the hundred was also the last six of the match. The century and the win did not become two separate moments; they merged in the same over.

This was the second T20I of a five-match series, and the result means the series stands level at 1-1. That the story would swing this fast was not something anyone wrote down after the first game.

501 runs and 33 sixes are a statement in themselves. There was no mercy for bowlers on this night. But the question sits right there: chasing 250, West Indies reached the last two overs needing only 10—was this merely a night of six-hitting, or was there a plan underneath?

My work begins outside the boundary, from the tunnel. The Rangpur Riders final began in the tunnel, long before the first ball. That habit never leaves me. So after 18 overs I did not stop at the score; I watched who stood where, which bowler released the ball early while counting his own over, which fielder kept shifting his position.

West Indies never chased 250 in this match. They broke it into pieces—twelve to fifteen an over, a leap here and there, but the required rate never climbed above six. 240 in 18 overs means more than thirteen an over on average. That did not arrive suddenly; it arrived ball by ball from the very first over.

Croatia taught me that a run is not a straight line; it is a heartbeat. At the 2026 World Cup, from the base camp in Sochi to Luzhniki in Moscow, I learned to measure that heartbeat—when a side slows, when it pushes, when someone risks his own wicket to steal an extra ball. Ranchi worked the same way.

And this is where the record settles in: a chase of 250 is the second-highest successful run chase in international T20 cricket. The number may sound dry, but it means that what West Indies did on this night sits beneath only one innings in history.

Core analysis: the decisions behind 33 sixes

33 sixes means roughly one six every five or six balls. That many sixes usually arrive in one of two ways—either the bowling plan has collapsed, or the batters have already decided and are waiting for the ball. In Ranchi both happened, but the proportion matters.

India's biggest bowling problem was length consistency. If the six-hitting balls could be replayed, most would be either full or short—both on the batter's side of the ledger. In T20 cricket a bowler is saved by the length that forces the batter to delay his decision. India's bowlers could barely find it in Ranchi.

Second—the pace of the surface and the dew. In the second innings, with a wet feel in the hand, a spinner struggles to keep his grip, and a poor grip means either shortening the length or pitching it up. Both invite sixes. When a spinner bowled the 19th over, that problem was at its sharpest.

Third—the match-up arithmetic. Ten needed from 12. The natural plan is yorkers and slower balls, because the batter must take the risk. But Hope was not forced to take it—he chose to. That is the real distinction of his innings. When the required rate is already in your favour, attacking is not the easy option; the easy option is to play safe and finish the game. Hope finished it by attacking, because he knew the century and the win could come from the same ball.

A 45-ball century means a strike rate above 200. To score a hundred at that pace, a batter usually takes risks from the start of his innings. But Hope's innings had a different rhythm—he began in step with the team's need, then gradually raised the tempo. As West Indies captain, his most important job was to carry the side, and he did it without losing his wicket. A six-wicket win with nine balls remaining tells you the West Indies camp retained its belief to the end.

From twenty years of watching cricket from the ground, I can say this without hesitation: the real hero of a chase like this is not the last over, but the four or five before it. What West Indies did between the 12th and 15th overs—sustained boundaries, battering the fielding side, taking regular runs off the spinners—is what delivered the last two overs into the comfort of 10 runs.

And here my old objection returns. A data model shows a probability number during a match, and that number never hears the sound inside the dressing room. At 18 overs some model may have said the game was nearly over. But the feeling on the ground is something else. In the 2026 BPL final, Chris Gayle scored 146 not out off 69 balls, including 18 sixes, and that day the scoreboard showed a similar kind of number. The number was true that day, but it could not describe the character of the match.

Contrarian angle: why the flat-pitch story is wrong

The easiest explanation from outside is this—flat pitch, short boundary, T20 match, and what had to happen happened. That explanation is comfortable, but incomplete.

First, 33 sixes and 501 runs are not purely a gift of the pitch. Both bowling units drifted away from their own plans that night. If one side makes 250 and the other makes 240 in 18 overs, blaming only the surface is unfair.

Second, some will say this was Hope's individual brilliance. But chasing 250 and winning is a collective act. The final sixes came off Hope's bat, yes—but the platform beneath them was not built by one man.

Third, the biggest misconception is that there is nothing to learn here. The opposite is true. Reliance on a spinner in the death overs, compromise with a wet ball, and the timing of bowling changes—these three questions will travel beyond Ranchi. Because in league cricket almost every side now puts six-hitting power first and bowling plans second.

In this part of journalism I often think about agents—how they build teams in football now finds a reflection in cricket's player-market chatter. But results on the field do not always obey that market. Ranchi's result was a result of decisions on the field, not of the market.

Takeaway: where to look in the third match

The series is 1-1. In the next match my eyes will be on two things—whether India changes its death-overs bowling combination, and whether West Indies can hold the same rhythm in the second innings.

An empty stadium still has a pulse; you just have to press your ear to the broadcast. I learned that in the spectator-less bubble cricket of 2026. But even inside the roar of a full house, one question remains—if a side can chase 250, can that same side defend 250?