A 352 Chase and an Unfinished Ledger: Shai Hope's 162* and the Arithmetic of a Dead Rubber in New Chandigarh

It was 2:20 in the morning. In my room in Khulna, the old spiral ledger lay open beside a laptop with a cracked screen. The match in New Chandigarh was still unfinished in my book — I was rewriting what the television scoreboard had said, ball by ball. India 351 for 7, seven point zero two runs per over across fifty overs. West Indies 352 in 48 point 2 overs, five wickets in hand, ten balls to spare. More than seven hundred runs across two innings. And yet the headline carried a word I never write at the top of a ledger — "consolation."

I began with a hand-coded ledger, and the numbers learned to confess. Today's confession is not that West Indies beat India. The confession is that a side which made 351 lost before its fifty overs were done, and that the man who made 162 not out off 143 balls finished with a strike rate below his team's required rate.

This piece starts from the seventh page of my ledger, because that is where the arithmetic of the two innings first fails to add up.

Context: A Match Already Decided

The state of the series has to come first, because almost every number in this match takes its meaning from there. India won the first two ODIs by eight wickets each. So the series stood 2-0 before the third match began, and it finished 2-1 to India. This was a dead rubber — which, in working terms, means the result carries low news value but high process value, if you know how to read process.

The venue: Maharaja Yadavindra Singh International Cricket Stadium, New Chandigarh, a relatively new Punjab host. More than seven hundred runs across two innings says one thing clearly — the pitch was flat and true, with little help for seam or spin. Kuldeep Yadav taking only one wicket is the clearest witness to that.

The toss: India won it, chose to bat, and made 351 for 7. On paper that is the conventional winning template — bat first, post a big total, then squeeze with the ball. India lost. So there is no toss-luck or Duckworth-Lewis excuse here. This is a clean case of a batting side failing to defend, which is rare in the two-new-ball ODI structure.

That structure matters. In the first fifteen overs two new balls search for swing, the middle overs squeeze the rate with spin, and the last ten overs break every calculation. In a match where both innings passed 350, the first two phases were effectively neutralised — meaning nobody won middle-overs control. The side that made 351 lost seven wickets, which tells me they bought runs with wickets through the middle.

Now, my own method. In 2026, at sixty, I left a thirty-one-year sub-editor's desk at a Khulna daily and began charting the Bangladesh Premier League by hand — twelve teams, sixty-six matches, four thousand one hundred and eighty passes logged into a spiral notebook and a cracked-screen laptop. I coded PPDA and shot quality by rewatching streams at two in the morning. When new-media outlets needed numbers, I emailed the ledger free to three websites and two clubs and asked for nothing back. Within a year, four of them were quoting "the Khulna numbers" without knowing whose they were.

That habit is why I stopped writing "deserved to win" and started writing "won the shot battle 2.1 to 0.7." Every claim now carries a figure I can open to.

One caveat belongs at the top of today's piece, because proceeding without it would be dishonest. Nearly every information point I hold on this match reads "Source: None," the publication is unnamed, and the only date is "Saturday." In other words, the material is an abbreviated wire-style report, not a full scorecard. So I treat every figure below as pending verification, and where the arithmetic does not close, I say so.

Core Analysis: 162*, and the Numbers Beside It

Shai Hope's 162 not out off 143 balls is a volume-anchor innings, not a tempo innings. That sentence is the centre of this piece, and it is the most useful information I have.

Let me do the arithmetic. 162 off 143 is a strike rate of 113 point 29. The elite benchmark for a traditional ODI anchor is 85 to 100; for a modern aggressive top order it is 100 to 110 plus. So Hope's tempo was good, not extraordinary. West Indies needed 352 in fifty overs — seven point zero four runs per over. Hope's own scoring rate was roughly six point eight per over, just below the required rate.

So where did 352 come from? Jangoo made 67 at roughly a 120 strike rate, and Keacy Paul made 44 at roughly 126. Without their acceleration, Hope's anchor would have been an unfinished half-story. The chase was controlled — not a last-ball thriller, finished with ten balls and five wickets in hand. That tells me nobody was ever gasping under the rate, because Hope stood there for the whole innings.

Carrying the bat is the real technical data point here. Staying unbeaten through a full innings means sustained concentration, fitness, and a game plan built on batting deep in a chase. That does not happen by accident. It is the profile of an ODI top-order anchor, and in this match it worked perfectly.

Look at the boundary composition: seventeen fours and three sixes, so 86 runs came in boundaries — about 53 percent of his total. For anchors the figure usually sits between 45 and 60 percent. So this was not a boundary-or-nothing innings; it was an innings of strike rotation and gaps. Holding that much patience in a dead rubber is not easy, and here I give Hope his due.

But here is my second objection. The headline is Hope, yet the highest-difficulty tempo in this match belonged to KL Rahul. 129 not out off 87 balls, a strike rate of 148 point 28. The benchmark for death-overs surge is 150 plus; Rahul came within touching distance. Of his 129, 76 came in boundaries — ten fours and six sixes, about 59 percent. India's 351 was built mainly on that innings, alongside Rohit Sharma's 92 (reported at roughly a 108 strike rate) and Ruturaj Gaikwad's 57.

So the two innings had different characters. India's 351 came from aggressive middle and death-overs batting; West Indies' 352 came from anchoring plus support. Same score, entirely different architecture. That difference is exactly why the scoreboard number tells you nothing about how the two teams worked.

Now the bowling. For West Indies, Jayden Seales took 3 for 62 — the only genuine strike-bowling performance of the match. Gudakesh Motie took one, Keacy Paul two. For India, one wicket each — Siraj, "Gurnoor Bar/Brar," Kuldeep Yadav, Naman Dhir.

And here the ledger stops me. Four Indian bowlers took wickets, yet West Indies lost five. Six West Indies wickets are named, yet India lost seven. That means at least one dismissal in each innings sits outside the arithmetic — probably a run-out, or a bowler the report omitted. In an abbreviated wire report that is normal, but in a ledger it is a gap, and I write gaps down.

One more thing worth noting. No Indian bowler took more than one wicket. At home, even in a dead rubber, India's traditional spin-dominance story is absent here. Two explanations are possible: either the pitch did not turn, or India's first-choice attack was not on the field. Either way, drawing conclusions from this match's bowling figures is dangerous.

The same caution applies to Seales' 3 for 62. The report gives no over count, so economy cannot be calculated; three wickets on a flat pitch means he bowled well, but reading it as "a new star is born" goes beyond what this information supports.

I keep one separate note on the middle overs. In a match where the required rate sits above seven, an anchor running at six point eight leaves a deficit to be pulled up at the other end. Jangoo and Paul pulled it, and that is precisely why West Indies finished with ten balls to spare. The real hero of this chase is a partnership structure, not an individual.

Contrarian: Correlation, Not Causation

At sixty-nine I have accepted one thing: I trust slow numbers more than loud ones. And the slow number here says West Indies' win is evidence of discontinuity, not of consistency.

The series finished 2-1, and both wins were by eight wickets, both India's. In two of the three matches India were thoroughly dominant. In the third, India rotated — they gave fringe bowlers a run. Rotation in a dead rubber is entirely normal, and it is the most probable reason a side that made 351 lost.

Here I want to avoid one error: "Hope made 162, so West Indies' batting has turned a corner." That conclusion confuses correlation with causation. A 352 chase in one match is an event; it is not a trend until the same side does it twice in the next series.

A second error: inflating Hope's strike rate. 113 point 29 sits below the required rate. So this innings was match-winning but not tempo-controlling. Part of the credit goes to Jangoo and Paul. Meanwhile, Rahul's 129 not out at 148 point 28 slipped past almost unnoticed, and to me that is a structural imbalance in the coverage.

Third, the home-pitch question. 351 and 352 — this is a surface on which every bowling figure looks inflated. Reading Kuldeep's single wicket as "poor form" is as wrong as reading Seales' 3 for 62 as "a star is born." When bowlers win on a flat pitch it is skill, and when they lose it is the pitch's fault — I have never accepted that accounting.

Fourth, the final-ten-overs question. Both sides scored heavily at the death, but India appear to have lost a large share of their seven wickets there, since they posted 351 while losing seven. Losing wickets in the death overs is normal when chasing rate, because scoring demands risk. Before concluding that "India's death bowling is weak," the rotation has to be factored in.

I add a professional caution that I always keep. Nearly every information point in this report reads "Source: None," the publisher is unnamed, the date is only "Saturday," and the arithmetic fails in both innings. Until this is verified against ESPNcricinfo or ICC scorecards, it is a working estimate for me, not settled truth.

And this too: one match's numbers speak only for one match. In 2026 I built a fatigue curve for Croatia — three consecutive extra-time knockout ties against Denmark, Russia and England, past 360 minutes. From distance-covered and sprint counts I predicted France would take the midfield after the sixtieth minute. France won 4-2, scoring in the 59th, 65th and 81st. I had the window right and the sequence wrong, and I printed the correction myself before anyone asked. That lesson applies here: I can name the window, not the sequence.

Takeaway: What I Will Watch Next Series

Hope's innings has entered my ledger with a specific yardstick. If his strike-rate-adjusted output holds at forty plus through the next series, it is anchor value; if it does not, it was a single night's flash. For India, my lens will be on their rotation policy — how different the XI looks in live matches versus dead rubbers. And for West Indies, the most urgent question is not about Hope, but about who stands at the other end.

The sixtieth-minute line is not a statistic; it is where matches change their minds. In this match that line sat around the forty-third and forty-fourth overs, where Jangoo and Paul lifted the tempo. Next time I will mark that exact over separately.

I am a data monk; I sweep the same columns until they become prayer. Having left a desk at sixty to start a hand-coded ledger is why I can read this match today as process rather than result.

What I missed: whether the match was day or night, and whether there was dew, is information I do not have. If dew was present, part of the 352 chase belongs to that advantage. And if India genuinely did not field their first-choice attack, then my sentence about "India's bowling depth under question" is only half true. I leave both open, and will try to fill both gaps in the next report.