Test Caps 217 and 218: Cricket's Namesake Ledger and a Question Left Unanswered

There is a spreadsheet on my laptop called IND_Test_Caps. Five columns: cap number, player, debut date, opponent, venue. India's men's Test caps now run past three hundred, so the sheet has more than three hundred rows. Rows 217 and 218 sit directly on top of each other.

This week Wisden published a quiz asking which name India's men's Test caps 217 and 218 share. I opened the sheet assuming the answer would fall out in four seconds. It did not fall out in four minutes. The reason is structural: my sheet has no column called shared name. I have the date, the ground, the opponent — I have nowhere to record that two players' names are identical.

That absence is the actual subject of the quiz. Cricket's data infrastructure stores a player as a string, while a player is an identity made of separate fields — date of birth, role, bowling type, format. The day you notice the gap, namesake trivia stops being a joke and becomes a maintenance problem.

What a cap number is, and why adjacency matters

A Test cap number is not a performance metric. It is a registration convention — the BCCI's record-keeping habit of assigning every new Test player a serial number in order of debut. The count from cap 1 to today moves on who walked out first, not on averages, strike rates or wins.

One structural inference sits inside that convention, and it is the firmest thing this quiz offers: caps 217 and 218 being consecutive almost certainly means the two players debuted in the same Test, or in back-to-back Tests. Sequential numbering behaves that way. That is a high-confidence inference, not a fact — and I will label it an inference, because the source I would need to confirm debut dates is not on my desk.

One disclosure before going further. Wisden's quiz is an engagement product, not reporting. Its material contains thirteen information points, and not one of them is a performance number, a match result, a transfer or a governance decision. And most importantly: the answer is not supplied. The question is asked and the solution withheld. So I will not invent it. The ledger does not care what I hoped it would say.

What is genuinely analysable here is not the quiz's answer but the quiz's rule.

The rule: exact match, and its four exclusions

The quiz's operative condition is that a namesake must be an exact match. That condition explicitly excludes four pairs: Mehidy Hasan against Mahedi Hasan, Claire Taylor against Clare Taylor, Abdul Razzaq against Abdur Razzak, and Mohammad Sami against Mohammed Shami.

This is not a sporting rule. It is a data-classification rule, and it is the most reusable element in the entire piece. The four exclusions span four different geographies — Bangladesh, English women's cricket, Pakistan-Bangladesh, Pakistan-India. That spread is unlikely to be accidental. The compiler most probably drew these four from real, recurring misidentifications rather than hypothetical ones. Inference, logged at medium confidence.

Now the actual difficulty, pair by pair.

Abdul Razzaq and Abdur Razzak — near-identical name, entirely different function. Razzaq is Pakistan's right-arm fast-medium allrounder from 2026; Razzak is Bangladesh's left-arm spinner from 2026. Pool the two in one row and a model corrupts both its economy baseline and its matchup logic. The higher the name similarity, the more essential the bowling-type field becomes, because that field is the only thing separating them.

Claire Taylor and Clare Taylor — the most consequential pair in the set, because both played international cricket for England's women. Team filters will not help. Gender filters will not help. Format filters will not help. Only exact spelling and date of birth remain. When spelling is the last line of defence, there is no line of defence.

Mohammad Sami and Mohammed Shami — the most frequently mis-merged pair of the 2010s. Both right-arm pace; one Pakistan from 2026, one India from 2026. The risk here is workflow, not statistics — IPL auction lists and franchise shortlists are keyed on names, and names are the weakest key available. That is an inference drawn from the quiz, not a claim the quiz makes.

Mehidy Hasan (Miraz) and Mahedi Hasan — both Bangladesh spin-bowling allrounders, from 2026 and 2026. Same team, same role, near-identical name. This pair demonstrates that team-based filtering is not a solution either.

The quiz's cross-format, cross-gender spread is a genuine hazard rather than a quirk. Test, ODI, T20, women's internationals and the County Championship all sit at the same level inside one short article. Anyone merging these names into a single record would be merging formats, eras and genders at once — precisely what analytics discipline forbids.

The pair the exact-match rule cannot catch at all

Here is the example this piece exists for.

Zaheer Abbas, born 2026, former Pakistan captain. His full name is Syed Zaheer Abbas Kirmani, and per the source he chose to use his middle names. In the same era, India's wicketkeeper Syed Kirmani, born 2026. One player's full name overlaps wholesale with another player's name.

That case sits outside the exact-match rule — which is the rule's limit. The rule screens out four pairs separated by a single letter, and fails to catch the pair where one name is fully contained inside another. That is a coverage gap, and coverage gaps are the most expensive defects a database carries.

Zaheer Abbas's case teaches a second lesson: the alias was not created by a database. The player created it. Historical records therefore need an alias field and a provenance note for that alias, not a single name string.

The two Ollie Robinsons are the modern version. One, born 2026, a Sussex and England right-arm seamer in Test cricket from 2026. The other, born 2026, a Durham/Kent wicketkeeper-batter in English domestic cricket from 2026. The source states that only one of them has played Test cricket. That sentence demands a date. It was true the day it was written; whether it still holds I will not assert without verification. Every number carries a date, a ground and the person who counted it — here the date is missing.

The two Daryl Mitchells worked as comedy, and the reason is data. One, born 2026, Worcestershire captain in the County Championship from 2026 to 2026. The other, born 2026, New Zealand middle-order batter from 2026. Mitchell Santner's joke landed because the two men were contemporaries inside the same professional ecosystem — a pair separated by decades carries no comic force. Contemporaneity is the joke's precondition.

The contrarian turn: the rule is aimed at the wrong target

I began this piece assuming the exact-match rule was the fix. The back-test returned the opposite.

The rule excludes four near-misses but does not catch the oldest form of the confusion — Syed Zaheer Abbas Kirmani and Syed Kirmani. It applies where names are almost identical, and it skips the case where one name lives inside another. Coverage, again.

Second, an admission the source forces: the caps 217 and 218 question is not resolved by this material, and that is the material's form, not its failure. Consecutive cap numbers narrow the answer space to one Test or two. Narrowing is not answering. Anyone declaring the answer obvious is dressing an inference as a fact.

Third, the publisher's side. Five separate quiz links appear inside one short article. That is a traffic strategy, not a journalism strategy. Calling it a fault would be wrong — quizzes exist because they get read. Calling it research would also be wrong. Demand accuracy from engagement content; do not demand depth from it.

What comes next

Before the next auction cycle opens, and the next time an all-time list is printed, one thing should be demanded: a public player-identity register carrying date of birth, role, bowling type, format and alias together. A name is not a key. A name is only the first filter.

As for caps 217 and 218, that question stays open. Those two rows are still stacked in my sheet, the name column empty, the date recorded. Sometimes the honest result is exactly this: no answer arrived, so I wrote it down anyway.