Nineteen Matches, Zero Tests: The India–Pakistan Ledger That Reopens Every Tournament

A file arrived. Every label was intact — title, source, format, player, team, date — and every value was blank. No scorecard, no venue, no name. Only a tag: cricket_asia.

There are two ways to fill a file like that. The first is the default on every content desk: build something that sounds credible. Asia Cup heat, cross-border tension, young blood waiting. The template was ready; only the names were missing.

The second way is this: when the file is empty, don't invent the story — go and count.

So I counted. Since January 2026, when bilateral series between the two countries stopped, India and Pakistan have played 19 completed matches. Ten ODIs. Nine T20s. Zero Tests. India won 15, Pakistan won 4.

That number is the spine of this piece. It is also the reason the empty file never needed filling.

For a few years now, cricket coverage has repeated one sentence: the rivalry is dead. The evidence is always the same — there are no bilateral series. That is true. Between December 2026 and January 2026 Pakistan toured India for three ODIs and two T20s. Nothing bilateral since. The two teams meet only in ICC events and the Asia Cup.

But that sentence carries a hidden assumption: that the rivalry lives inside bilateral series. I read it differently. The rivalry lives inside the scheduling, not the cricket. And when you open nineteen scorecards one by one, you find that on the field this is the most one-sided fixture of the past decade — a fact that never makes it onto a talk show, because it lowers the price of the emotion.

Tournament economics makes this clearer. The 2026 Asia Cup was played on a hybrid model — Pakistan named hosts, no India matches in Pakistan. The 2026 Asia Cup was also played in the UAE while Pakistan held hosting rights. A fixture once driven by home grounds and home crowds is now driven entirely by neutral venues and a tournament calendar. A home ground is half the fuel of a rivalry; that fuel is gone, and promotional content took its place.

Remember March 2026. The World T20 game between India and Pakistan was shifted from Dharamsala to Kolkata. Venue, security, ticketing, broadcast — all rewritten for one match. Almost no other fixture in cricket moves administrators like that. But note what moved: not the match, the market around the match.

That is why an India-Pakistan game becomes the most expensive broadcast property in any tournament it sits in, group stage or final. At the 2026 World Cup, tickets for this fixture were among the most expensive of the tournament, and the ground was still full. This is where the trouble starts: when the product is that expensive, telling the truth about it also becomes expensive.

So the question is not whether bilateral cricket stopped. The question is what those nineteen matches actually were.

Here is the ledger, hand-tallied from scorecards:

2026 · Asia Cup (ODI) · Mirpur · India

2026 · World Cup (ODI) · Adelaide · India (76 runs)

2026 · Asia Cup (T20) · Mirpur · India (5 wickets, last ball)

2026 · World T20 · Kolkata · India (6 wickets)

2026 · Champions Trophy group · Edgbaston · India (124 runs)

2026 · Champions Trophy final · The Oval · Pakistan (180 runs)

2026 · Asia Cup group · Dubai · Pakistan (8 wickets)

2026 · Asia Cup Super Four · Dubai · India (9 wickets)

2026 · World Cup · Manchester · India (89 runs)

2026 · World T20 · Dubai · Pakistan (10 wickets)

2026 · Asia Cup group · Dubai · India (5 wickets)

2026 · Asia Cup Super Four · Dubai · Pakistan (5 wickets)

2026 · World T20 · Melbourne · India (4 wickets)

2026 · Asia Cup Super Four · Colombo · India (228 runs)

2026 · World Cup · Ahmedabad · India (7 wickets)

2026 · World T20 · New York · India (6 runs)

2026 · Asia Cup group · Dubai · India

2026 · Asia Cup Super Four · Dubai · India

2026 · Asia Cup final · Dubai · India (5 runs)

Twelve-plus years. Nineteen matches. One and a half a year. Three of those came inside a single tournament — the September 2026 Asia Cup. Several years produced nothing: zero in 2026, two across 2026 to 2026. This is not a rivalry calendar. It is a side event attached to somebody else's main event.

Now the part that genuinely surprised me: zero Tests. The last Test was played in Bengaluru in December 2026, and it was drawn. Eighteen years since, not one.

The Test is the format that built this rivalry. Sehwag's 309 at Multan in 2026, five days in Rawalpindi and Karachi, the 2026 Bengaluru Test — the heaviest memories of this fixture come from Tests, not T20s. And that exact format vanished from it in the twenty-first century. That is not only a scheduling necessity; it is a choice, because a five-day Test is worth less to a broadcaster than the emotion of one evening's three hours. The rivalry that borrowed its seriousness from Test cricket cut Test cricket first.

Now the inverted arithmetic of density. Between 2026 and 2026 — four years — the two teams met more than twenty-five times: three Test series, several ODI series, two ODIs in Abu Dhabi, and the 2026 World T20 final. Then nineteen times in the next twelve years. The supply of matches more than halved; the supply of story attached to each one did not. Every modern meeting carries a double load of old memory. And when demand for narrative exceeds supply of cricket, the narrative starts repeating itself.

You can feel it. In the twelve months before the 2026 Asia Cup, my feed carried more India-Pakistan analysis than India-Pakistan matches. That is an observation, not a statistic, and I will not dress it up as one. But there is a measure: more content has been produced about these nineteen matches than was produced about the twenty-eight of 2026-2026. Less cricket, more noise.

And here is the part that bothers me most: 15-4.

18 June 2026, The Oval. Fakhar Zaman's 114, Pakistan's 338/4, and India bowled out for 158 in 30.3 overs — a 180-run defeat. That night I was in Kolkata, in my second year of an international communication degree. I wrote nine hundred words arguing it was not a failure of nerve but a failure of template: three wickets down inside nine overs with 33 on the board, and a middle order with no plan past the fifteenth over.

That post reached 3.8 lakh people, was shared 9,100 times, and drew 1,400 comments, half of them furious. The post outgrew me. This column is me catching up to it.

Because what I wrote that night was one page of this ledger. Open the whole thing and the 2026 final is one of exactly four Pakistan wins against India — the largest, yes. The other three: the 2026 Asia Cup group game, the 2026 World T20 in Dubai, and the 2026 Asia Cup Super Four. That night I thought I had watched an upset. The count says it was an exception.

Let me count the close ones. Matches that reached the final over or finished inside ten runs: Mirpur 2026 (last ball, India winning despite Mohammad Amir's 3/18), the 2026 Asia Cup group game in Dubai, the 2026 Asia Cup Super Four, Melbourne 2026, and New York 2026. Five. Five out of nineteen — twenty-six per cent.

The other fourteen include margins of 124 runs, 180 runs, 89 runs, 228 runs. In the 2026 Asia Cup Super Four, Kuldeep Yadav took 5/25 and the match ended 228 runs apart. That is not a rivalry. That is a recurring appointment with one predictable participant.

And when the most famous recent edition of this fixture is a defence of 119 — New York 2026, where India made 119 and Pakistan finished on 113/7 — you should understand that the stake is on the name, not the cricket. Eight years earlier in Kolkata, Pakistan made 118/5 and India chased 119, Virat Kohli unbeaten on 55. Two World Cups, eight years apart, almost the same scoreline, and the same one name deciding it both times. That tells you less about a team than about how much of this fixture's drama rests on one pair of shoulders.

Here I had to stop for a moment. Because the 2026 Asia Cup contains another entry that is not in my ledger: the group game in Kandy that washed out without a single ball bowled. Zero deliveries. And it still generated days of coverage — previews, previews of the preview, the washout report, and then the argument about whether India should get the points. That is the entry that proves cricket is no longer a necessary condition for this fixture.

Ahmedabad, 14 October 2026. World Cup. 1.32 lakh seats in the largest cricket stadium on earth. Pakistan bowled out for 191, Rohit Sharma's 86, India home by seven wickets. I watched it twice — live, then with the scorecard. On the second viewing the clearest thing was that the contest was settled inside ten overs and the remaining forty were ceremony. Two hundred thousand people came to watch the ceremony. That is the whole story.

Nineteen scorecards later, the rewatch started arguing with me. Its case: what fills this ledger is not the ground but the schedule. Behind every match sits a calendar, a broadcast slot, a visa process, an administrative decision. Cricket arrives last. And if cricket arrives last, its result matters least — which is exactly what 15-4 looks like.

Dubai 2026 is both the best example and the biggest exception. Rizwan 79 not out, Babar Azam 68 not out, a ten-wicket win, and Pakistan's first World Cup victory over India at the twelfth attempt after eleven straight defeats. Eleven losses, then a win. Nothing proves better that this rivalry is built on repetition rather than results.

Now the part where I have to give myself a chance to be wrong. Before counting, I wrote down a falsifier — the one everyone should write: if forty per cent of these nineteen had gone to the final over, I would concede that scarcity raised the intensity and that the demand for bilateral cricket is just habit. The number came back at twenty-six per cent. I did not clear my own bar, so the argument stands.

But there is a weak link, and it is visible. The 2026-2026 era was not wall-to-wall thrillers either. In a five-match series, the third and fourth ODIs were often dead rubbers nobody remembers. If eight of those twenty-eight were memorable, that is roughly twenty-eight per cent — almost exactly what we have now. Which means fewer matches did not raise the rate of drama; it raised the price of each match. Raising a price is a market decision, not a cricket improvement.

The second counter-argument I cannot dismiss: my ledger cannot measure what happened in the stands. The Rizwan-Babar stand reads as ten wickets on a scorecard, but in two countries it read as something else. Melbourne 2026 reads as four wickets, but Kohli's 82 not out is the innings people will show their children. The spreadsheet does not capture that. And if the spreadsheet does not capture it, my whole argument is measuring something that does not matter.

The sharpest self-criticism is this: I am doing what I accused the empty file of doing. That file turned feeling into data. I am turning feeling into a tally. The difference is that my tally has a source and that file had nothing. But having a source is not the same as being right — I know that too.

On the third objection I do have an answer. If the contest is one-sided on the field and enormous in the stands, then what we call a cricket rivalry is not cricket. It is a cultural and political ritual dressed in cricket whites every couple of years. If that is true, measuring it in cricket terms is a category error — and selling it in cricket terms is a worse one.

So here is the forward math. Before the 2027 World Cup, India and Pakistan will meet at most five more times, and every one of those will be inside an ICC or Asia Cup event. There will be no bilateral series — not in 2026, not in 2027. That is my claim, and it is checkable.

And if three of those five go to the final over, I will withdraw my own argument. Because then it will be proven that scarcity did raise the intensity, and my ledger was only bookkeeping, not a verdict.

The tournament argued with itself. I just kept the minutes. And the minutes record that the weight of nineteen matches is not the weight of nineteen matches — it is the weight of the twenty-eight that no longer happen, and of memories we reload onto every new series.

That was the lesson of the empty file. Its format field was blank, and not by coincidence. When we never look at this fixture through format, the format field stays blank. Nobody asks whether it is a Test, because the answer is always no.

The question is not whether nineteen is too few. The question is why we discharge so much frustration through nineteen that we never discharged through twenty-eight — and the answer may be that in the twenty-eight era we never needed to count, because we were watching cricket, and now we are watching content about cricket.