India's Test Caps 217 and 218: One Quiz, Four Excluded Pairs, and the Unaudited Drawer of Cricket Data

It was a Wednesday afternoon at the Delhi desk and there was a Wisden Cricket Quiz link sitting in the inbox. The question is short: what name do India's men's Test caps 217 and 218 share? I read it twice. On the third reading what stopped me was not the question. It was the small list printed under it, four pairs the quiz had already thrown out — Mehidy Hasan versus Mahedi Hasan, Claire Taylor versus Clare Taylor, Abdul Razzaq versus Abdur Razzak, and Mohammad Sami versus Mohammed Shami.

The quiz did not publish the answer. Neither did I, and that is not evasion. Where the source does not carry an answer, sending in a guess is a fault on my ledger, not the reader's.

It is worth being clear about what this quiz is, because its real subject is not cricket. Its subject is cricket's record register. The Wisden piece is an engagement product — not a report, not an analysis, and I have to add, not written in a form I would file. It pulls five different layers into one short page: Test, ODI, T20, women's internationals and the English County Championship. One short article carries five cross-links to other quizzes — the Sharmas in international cricket, the Smiths who played Test cricket. That tells you a great deal about the publisher's strategy and almost nothing about the sport.

The operative rule sits in one sentence: a namesake counts only if both the first name and the surname are identical, letter for letter. That rule is what excludes the four pairs. Three worked examples are supplied — the two Ollie Robinsons, the two Daryl Mitchells, and Zaheer Abbas against Syed Kirmani.

The source contains thirteen information points. Not one of them is a scoreline, a transfer fee, a ranking, a fitness update or a board decision. I run a five-dimension worksheet, and four of those dimensions came back empty. I am recording the empty cells rather than dressing them.

In a cricket database a name is not decoration, it is a key. The day two names collapse into one, every downstream number attached to that player — average, economy, matchup baseline, auction value — can belong to either man. That is not a philosophical point. It is the technical crack the whole quiz stands on, even though the quiz never called it a technical crack.

The cleanest demonstration is Abdul Razzaq against Abdur Razzak. Pakistan's Abdul Razzaq was a right-arm pace-bowling all-rounder. Bangladesh's Abdur Razzak was a left-arm spinner. Near-identical name, opposite bowling type. Merge those two rows and your economy-rate baseline corrupts in both directions — a spinner's economy leaks into a seamer's record, and a seamer's new-ball spells leak into a spinner's matchup graph. This is exactly why bowling type has to be a structured field and not a sentence in prose.

Claire Taylor and Clare Taylor are the most dangerous pair in the set, and the reason is technical. Both played international cricket for England's women. The team filter does nothing — both England. The gender filter does nothing — both women. What remains is exact spelling and date of birth. One letter, Claire against Clare, and two careers become one. When I see cases like this I remember the morning in 2026 when I was building a dead-ball expected-goals model for the Russia World Cup. The first task there was the same: settle identity before you touch a number. I logged 29 penalties across that tournament, and in Moscow on 15 July France beat Croatia 4-2 with three of France's four goals originating from dead-ball situations. The model worked because every event attached cleanly to one identity. Merge a name and it is not the model that dies, it is the model's credibility.

Mohammad Sami and Mohammed Shami are the highest-traffic confusion of the 2010s. Both right-arm pace, one Pakistan, one India. The team filter saves you here, but only if you already know which is which. In a scouting workflow that lacks that knowledge, the pair quietly welds two careers together.

Zaheer Abbas belongs to a different category, and to my mind it is the most interesting one. The former Pakistan captain's full name is Syed Zaheer Abbas Kirmani. He preferred to use his middle names — a rare documented case of a player changing the identifier under which he is recorded. No database did that; the player did. And in roughly the same era India's wicketkeeper was Syed Kirmani, whose first and last names sit inside Zaheer Abbas's full name. Historical records have to run on alias fields, not a single name string. That is not my opinion; it is the operational consequence of one example.

The two Ollie Robinsons are the cleanest worked example in the quiz. One, born 2026, right-arm pace, Sussex and England, has played Test cricket. The other, born 2026, wicketkeeper-batter, English domestic cricket. Here I have to add a caveat the quiz does not: the claim that only one has played Test cricket has a shelf life. Before I republished it I would check it against England's current cap register. Date of birth is the cheapest and most reliable tiebreaker available, and it should be the first field in any serious identity register.

The two Daryl Mitchells explain when a namesake joke lands. One, born 2026, Worcestershire captain, County Championship. The other, born 2026, New Zealand middle-order batter. Mitchell Santner's joke worked because the two were contemporaries inside the same professional ecosystem. A namesake pair separated by decades generates no comedy — it just becomes two separate records. Contemporaneity is the condition for the joke, and it is also the condition for the data error.

Now back to the question the quiz asked and did not settle. India's men's Test caps are sequential — every new Test debutant takes the next number. That is a BCCI and record-keeper convention, not a law of the game. From that sequentiality one solid inference follows: caps 217 and 218 almost certainly debuted in the same Test, or in consecutive Tests. That is the only reliable constraint the source offers, and it narrows the answer space sharply. Any specific name I wrote beyond this would be unverified, and I will not write it.

One professional note belongs here, because it is my actual concern. What the quiz turned into entertainment is in fact an audit nobody has run. Cricket holds an enormous store of names at every level — five players with the same surname on a domestic circuit, three identical names on an international list. IPL auction lists and franchise shortlists are keyed on player names. Near-identical names create real mis-selection risk in the auction room and in scouting workflows. That is my inference, not the quiz's claim, and I will label it as inference when I publish it. Inference has limits too, and this one stays inside them.

I also have to record that this argument does not live only at the top. Look at Ranji knockout coverage counts — the matches still being covered after the stands emptied. Down there a domestic batter whose name collides with an international's never gets a record of his own. The baseline I rebuilt after the crowds left has held ever since, and the first condition of that baseline is that every innings is booked to one correct human being.

Now the part where I argue with my own profession. The existence of this quiz does not mean namesake confusion is common among cricket's audience. A quiz is an engagement product, not a survey. I refuse to convert a puzzle into a prevalence estimate. Reading causation into correlation is the error I have watched most often in three decades of this work.

Second, and this is the more uncomfortable one. Analytics beat intuition in the 2010s, and after that win it became very easy to assume the argument was over. It is not. Name-merge errors are still alive — in large databases, in franchise scouting systems, in fantasy rosters. The commentary box is the last unaudited room in this sport, and the record-keeper's desk is the second. I will keep auditing both on their own terms.

Third, and this one is against myself. Depth cannot be manufactured from this source, and performing depth is worse than admitting its absence. Four of my worksheet's dimensions came back null — match analysis null, team landscape null, league and commercial ecosystem null, governance null. Calling an empty cell empty is itself a finding. An analyst who extracts a thesis from every quiz is not extracting anything.

I keep two ledgers: what the model said, and what happened. The gap between them is the lesson. On this quiz there is very little to say from the model's side, and what happened is that a publisher raised, inside thirteen information points, a technical problem cricket's data infrastructure has not fully solved.

On the night of 21 May 2026 at the Rajiv Gandhi International Stadium in Hyderabad, Mumbai Indians defended 129/8 and beat Rising Pune Supergiant by one run. The market had Mumbai as underdogs at the innings break; my death-overs economy benchmark did not. That benchmark was priced in three phases, and it worked because every bowler's record attached cleanly to one man. One run decided the final, and I had already written down why it might. If two identical names had merged in a scorecard that night, that one run would never have shown up in my model.

My next question goes to the BCCI cap register, and to whoever compiles the next quiz. The question is not what caps 217 and 218 are called. The question is how many names in your register carry an alias field, and who holds final authority when two records are merged. The next time two identical names appear on a scorecard, remember — the number printed beside them may belong to neither man.