Caps 217 and 218: The One Name That Exposes Indian Cricket's Record-Keeping Problem

At 1:05 a.m., in the same one-room Chennai setup, three tabs were open on the screen — the list of Indian Test caps, the Wisden cricket quiz, and my own "wrong file" worksheet, where I keep the names of every player I have mis-tagged, with the date I got them wrong. The question was simple: India's men's Test caps 217 and 218 share a name. What is it? For the first two minutes it read like a harmless pub-quiz line. By the third minute it read like an X-ray of cricket's data infrastructure.

Because we identify players by name — and in cricket, a name has never been a unique identifier. What is unique is the cap number. Yet every database entry, every auction shortlist, every fantasy roster, every commentary panel is keyed on the name. That is why this question is bigger than the scorecard.

This edition of the Wisden Cricket Quiz is an engagement product, not reporting. There is no match, no scoreline, no toss, no DLS, no DRS controversy. The source yields thirteen information points, and not one of them is a match result, a transfer or a governance decision. I gave this thirty-six hours rather than the full forty-eight, and the take only got sharper. What is genuinely real inside the quiz is not cricket — it is record-keeping integrity.

The operative rule is exact-match only. Four pairs are explicitly excluded: Mehidy Hasan against Mahedi Hasan, Claire Taylor against Clare Taylor, Abdul Razzaq against Abdur Razzak, and Mohammad Sami against Mohammed Shami. The quiz spans Test, ODI, T20, women's internationals and the English County Championship. That cross-format, cross-gender scope is the analytical hazard: any downstream consumer who merges these identities is folding formats, eras and genders into a single record.

The only team-specific artefact in the entire source is the Indian men's Test cap numbering itself — a BCCI and record-keeper convention that assigns each debutant a sequential number. Which is what makes the 217/218 question tractable at all, and why I will call what follows an inference and not an answer.

Start with the pair everybody skips: Abdul Razzaq and Abdur Razzak. Near-identical names, completely different bowlers — right-arm pace all-rounder from Pakistan, left-arm spinner from Bangladesh. Pool those two identities and both the economy-rate baseline and the matchup baseline corrupt at once, silently. That is the argument for storing role and bowling type as structured fields rather than as text inside a name string. It is not a cricket lesson; it is a lesson for any system that treats a name as a primary key.

The most consequential pair is Claire Taylor and Clare Taylor, because both are England women's internationals. Team filter fails, gender filter fails, format filter fails. All that survives is exact spelling and date of birth. That is the worst-case scenario for any data infrastructure — the scenario where every convenient disambiguation rule breaks simultaneously. My confidence on the career-window detail is only medium, because the source does not give clean dates, and I do not publish a date I cannot check.

The most instructive case is Zaheer Abbas. His full name was Syed Zaheer Abbas Kirmani, and he preferred to use his middle names — meaning the player himself changed the identifier under which he is recorded. That is not a database-created alias; it is a player-created alias. It is exactly why historical records need an alias field rather than a single name string. Syed Kirmani, the contemporary Indian wicketkeeper, sits inside Abbas's full name. In a search bar, those two collapse into one person.

And if you think this is an old-men's argument about spelling, look at the Ollie Robinsons. One, born 2026, is a right-arm pace bowler for Sussex and England who has played Test cricket. The other, born 2026, is a wicketkeeper-batter in the English domestic game. Same country, same domestic structure, same name, entirely different role. My confidence is high on role and format, medium on the claim that only one has played Tests today — that is a line I verify before I print it.

The Daryl Mitchell anecdote is the best proof that this is a human problem, not just a software one. Mitchell Santner's joke was aimed at two Daryl Mitchells — the Worcestershire captain born 2026 and his own New Zealand teammate born 2026. The joke lands because both men were active contemporaries in the same professional ecosystem; separate them by two decades and the comedy evaporates. Namesake confusion is sharpest where two players are simultaneously live.

Back to the cap numbers, the quiz's actual engine. Sequential debut numbering means caps 217 and 218 almost certainly debuted in the same Test or in consecutive Tests — a high-confidence structural inference that narrows the candidate list hard. My working file places the window in the early 2000s. But here is the honesty clause: Wisden posed the question and withheld the answer, and I refuse to declare it "solved". The moment I open the official BCCI cap registry with dates of birth and debut dates, this inference either hardens or dies. Until then it is a reasoned guess, and I will label it one.

There is a commercial edge too, and it matters in a transfer-window cycle. IPL auction lists, franchise shortlists, scouting workflows are all keyed on names. Sami/Shami and Razzaq/Razzak are real mis-selection risks in an auction room. That is inference, not a claim — but it is the kind of inference you pay for with a wrong bid.

Now the part where I turn on my own argument. The easiest reply is that I am over-engineering a pub quiz, and you are not wrong. I concede specifics: there is no performance data here, no average, no strike rate, no venue factor. I concede that Wisden's real objective is engagement — five separate quiz cross-links inside one short piece say plainly that this is a traffic strategy, not a research strategy. And the third concession stings most: if the answer turns out to be a very common Indian surname, my whole structural argument is decoration. If that happens, the inference is junk and I will file it as junk.

As I wrote after the 2026 no-ball piece — somewhere in the replay, the comfort blanket started to fray. There, the comfort was believing one delivery explained a whole match. Here, the comfort is believing one name explains one person. Same error in both places: we settle the verdict before we look at the detail.

So what next? My forecast is that within two or three years an alias registry will be as mandatory for serious cricket data products as a date of birth. And the day the BCCI makes its cap registry public, searchable and birth-date-tagged, this quiz becomes a one-minute exercise nobody remembers. The question is how many players we will have filed wrongly by then.