501 Runs and 33 Sixes in Ranchi: How Shai Hope's 45-Ball Century Flipped the Chase Equation

At Ranchi's JSCA International Stadium, when the third ball of the 19th over left Axar Patel's hand and sailed over wide long-on into the stands, two numbers lit up the scoreboard at once — 250 and 100. One for West Indies' target, one for Shai Hope's personal century. A century off 45 balls, a six-wicket win with nine balls to spare, and the five-match series level at 1-1. After the game, everyone was counting sixes — 33 of them, 501 runs across two innings. But as I began laying the over-by-over scores into my notebook, a different picture sharpened. You can file Ranchi away as a night of sixes, but that file is incomplete. This was a quiet lesson in required run rate. The man who won the match did not attack for the whole innings — he played the maths. The context matters. This was the second T20I of a five-match series; India had won the first, so West Indies carried the pressure of levelling. Ranchi's surface is traditionally batting-friendly — the ball comes onto the bat, the boundaries are short, and evening dew strips the spinners of their grip. Put those three variables together and you get 501 runs. India batted first and made 249. Do the arithmetic: 501 runs in total, West Indies made 252/4, so India stopped at 249. That is not a small number — in international T20, 249 almost always wins. On that Ranchi evening it did not. Two things worked against it: a dew-soaked ball and a small ground. A target of 250 means 12.50 an over from ball one. Chasing that in international T20 means a boundary in almost every over — otherwise the equation drifts. That is where India's bowlers ran into trouble. At 12.50 an over there is no room for error; one indulgent over has to be recovered across two. Shai Hope's profile matters here too. For years he was known as an ODI anchor — slow, measured, an innings built at a 70-80 strike rate. His historical T20 strike rate sits around 130. A batsman with patience written into his DNA scored a century off 45 balls. That is the match's biggest data surprise. The question is whether this is a sudden transformation or a temporary adaptation forced by the equation. I did not have ball-by-ball tracking data for this match. There is no Hawk-Eye feed at Ranchi, and no API pushed data to my table. So I went back to the old method — rebuilding the innings from the scorecard. I keep a ritual for every model: name the data, clean the data, then trust the data. The evidence my eyes gathered over years of watching also went to one side — what my eye test was seeing did not square with my pivot table, so I made it sit in the corner. The arithmetic runs like this: 250 off 120 balls is 12.50 an over. At the end of 18 overs West Indies were 240/4 — 13.33 an over. They were 0.83 an over ahead of the required rate. The last two overs needed only 10 runs, 5.00 an over. That is the real story. The hardest part of a 250 chase is not the death overs — it is the first 15. A side that stays above 12.50 through 15 overs turns the last five into near-formality. West Indies did exactly that. They did not grope for wickets; they took boundaries, and the boundary count is what made the finish easy. Thirty-three sixes means 198 runs from sixes alone — about 39.5% of the 501 total. Nearly four runs in every ten came from a six. That single number tells you how batting-friendly the surface was and how thoroughly the bowlers' plans were cancelled. In bowling analysis this is an uncomfortable truth: when the pitch is not fair to the bowlers, there is no clean yardstick to measure them by. Look at the closing overs. Axar Patel came on for the 19th, Hope unbeaten on 90. Ten needed, ten to the century — two equations at the same distance. First ball, six over deep midwicket — Hope 96, four needed. Second ball, pushed to extra cover, no run — a dot ball in a situation where a dot ball means pressure. Third ball, six over wide long-on — 102, and the match was done. That dot ball deserves a pause. Under chase pressure, a dot ball in the 19th over is usually big news. Here it was not, because Hope's boundary rate was high enough. That is the first rule of data analysis: the value of a dot ball depends on how many sixes sit beside it. When the six rate is high, a dot ball is luxury; when it is low, a dot ball is sin. In Hope's innings the dot ball was luxury. In my table there is an index I call the boundary dependency index — runs from boundaries as a share of the total. At 39.5% it is very high, though on the small grounds of the subcontinent it is normal. The question is whether that number travels outside Ranchi. Here I am cautious. Football analysis taught me that a metric surviving one tournament does not mean it survives everywhere. PPDA survived Euro 2026; Tokyo made it prove it could travel. Ranchi's 12.50 run rate is the same — a product of this pitch, this dew, these short boundaries. If the same two sides played on a bigger ground and a dry, turning pitch, 33 sixes would never arrive. Now to the part where the story flips. After the game all the talk was about Hope's 45-ball century. It was a superb innings. But if the data is honest, West Indies won this match not in the 19th over but much earlier. They won it between the 7th and 15th overs, when India could not take a wicket and the boundaries kept accumulating over by over. Needing only 10 from the last two overs means the result was effectively settled. India lost not in the final over of bowling but in the middle overs. And they lost on a piece of arithmetic that did not add up — defending 250 demands roughly a wicket an over. India did not get them. On a six-hitting ground a wicket is the only brake; without it, the run rate slowly strangles you. Another point worth holding: this second-highest successful chase in international T20 is a product of a flat pitch. Whenever we see such a record, we should ask whether the surface was fair to the bowlers. Ranchi's 501 runs is a match result, but it is also a failure of bowling analysis. On a surface like that, measuring bowlers is hard, because the conditions are against them. One match, one innings — declaring Hope a new aggressor on that basis is a classic overfitting error. My experience says an innings needs at least ten to twelve innings of data before it becomes a trend. If Hope's transformation is real, the next few series will prove it; one night of sixes is not the proof. For the matches ahead, three things hold my attention. India's middle-overs bowling plan — if they cannot break wicket-to-wicket spells, the same equation returns. West Indies' batting order — as Hope moves from anchor to aggressor, how does the top order arrange itself around him? And the pitch — if the rest of the series is played on different surfaces, Ranchi's 501 becomes an outlier, beautiful for research, useless for prediction. I learned one thing from the football market — a fee is just a number with a rumour attached. A cricket score is the same. 501 runs is a number with a story attached. The job is to separate the number from the story. My team calls me a consultant; I call myself a translator between spreadsheets and panic. On the Ranchi night the job was not easy, because the story was talking loudly. But the maths, calm and unhurried, kept telling the truth — Shai Hope won this match, yes; but West Indies had already won the middle overs. The coming games will show whether Ranchi was an accident or the start of a new trend.