Test Caps 217 and 218: The Namesake Problem That Has No Scorecard Column

A question from the Wisden Cricket Quiz has been making the rounds: what name do India's men's Test caps 217 and 218 share? The question is charming, and the quiz did not supply the answer. But what stopped me was not the question. It was that the question can be asked at all. In India, every Test debutant is handed a sequential number — from 2026 to today, without a break. That number is printed on no scorecard, appears in no broadcast graphic, and remains the only register that records who came after whom. Across five Ranji matches at the Kotla in the 2026-18 season I hand-coded 1,842 deliveries — batter, bowler, line, length, shot type, false shot. Nobody had asked for that sheet. The cap number is the same sheet, only older than I am.

The arithmetic of cap numbering is simple, which is why it is useful. Every new Test player takes the next number. Sachin Tendulkar is cap 187 — a figure still quoted everywhere, because it became the yardstick for measuring generations. The two men who debuted at Lord's in 2026, Sourav Ganguly and Rahul Dravid, carry adjacent cap numbers. That is not coincidence; it is the rule, and the rule is the only thing here worth trusting.

One conclusion follows cleanly: caps 217 and 218 debuted either in the same Test or in consecutive Tests. Sequential numbering leaves no room in between. So the answer space is narrowed not by age, state or role, but by a date. And that date sits in the early 2000s, because it took roughly a decade to travel from 187 to 217. The debut cluster of that period is dense — Deep Dasgupta, Virender Sehwag, Sanjay Bangar, Iqbal Siddiqui, Tinu Yohannan, Ajay Ratra, Parthiv Patel, Sairaj Bahutule, Rahul Sanghvi, Hemang Badani. Several of those pairs come from a single match, and that pair is the answer.

One honest note belongs here: the quiz withheld the answer, and I will not announce one without BCCI's cap register. Anyone who supplies a confident answer without that register is selling an estimate. What I have is the constraint that sequential counting produces by itself. That is little, but it is not false.

The real story is not the cap number but the four pairs Wisden deliberately excluded from its quiz. The rule is that namesakes must match exactly — spelling, team, format, everything. The four exclusions are not exceptions to that rule; they are its proof.

First: Mehidy Hasan (Miraz) and Mahedi Hasan. Both Bangladesh spin-bowling all-rounders. The gap is a single vowel. In any table where the name is the key, they collapse into one row and two careers become one line.

Second, and the most dangerous: Claire Taylor and Clare Taylor. Both England women's internationals. Team filter fails here, gender filter fails, country filter fails. What survives is spelling and date of birth. When no other pillar of identity remains, a database has to promote date of birth to primary key — that is not a convenience, it is a necessity.

Third: Abdul Razzaq and Abdur Razzak. One a Pakistan right-arm pace all-rounder, the other a Bangladesh left-arm spinner. Near-identical name, opposite function. Merge them in a model and both the economy baseline and the matchup split are corrupted — because a left-arm spinner's matchup is built against left-hand batters, and a right-arm seamer's is not.

Fourth: Mohammad Sami and Mohammed Shami. Both right-arm quicks, Pakistan and India. The most frequently conflated pair of the 2010s. Here the role does not differ — only the team does. Which means no natural signal flags the error.

From those four, one thing is clear. Cricket's data system treats the name as an identity, when the name is not an identity at all. A name is a string, and strings repeat. Identity is the thing that does not repeat.

Three further examples sit in the quiz, and each shows a different species of failure.

Ollie Robinson — there are two. One born 2026, a Sussex right-arm seamer who has played Tests for England. The other born 2026, a wicketkeeper-batter in the English domestic game. The failure mode here is that both are active at once, in the same country, inside the same first-class structure. The quiz asserts only one has played Test cricket, and I have no way to verify that claim as of today. I file it under pending verification, not under fact.

Daryl Mitchell — there are two, and this pair is the funniest because the joke was made by an international cricketer. One Daryl Mitchell, born 2026, Worcestershire captain and County Championship top-order batter. The other, born 2026, a New Zealand middle-order batter across Tests, ODIs and T20Is. Mitchell Santner's joke rests on exactly this — and a joke only lands if both men were contemporaries in the same professional ecosystem. Namesakes separated by decades make nobody laugh.

Zaheer Abbas and Syed Kirmani. This pair is unlike the rest, because the error was not the database's — the player changed his own identifier. Zaheer Abbas's full name was Syed Zaheer Abbas Kirmani, and he chose to use his middle names. In the same era, India's wicketkeeper was Syed Kirmani. Two players, two countries, one shared name fragment — and one of them decided to hide it. That is precisely why historical records need a mandatory alias field rather than a single name string. A player may change his name; the register must be able to absorb the change.

Now the part that irritates me most. This is a quiz. There is no innings, no scoreline, no average, no strike rate, no economy rate. Across thirteen information points there is not one performance figure. Which means not a single sentence about any player's technique can be written from this material. Whoever writes one is writing from his own head, not from the quiz.

And that is the actual find: the namesake problem does not detonate in trivia. It detonates wherever the name functions as a key. IPL auction lists, franchise scouting shortlists, fantasy rosters, endorsement attribution — in all of them the player's name is the primary identifier. One wrong click between Sami and Shami means a franchise spending money on the wrong scouting report. That is inference, not the quiz's claim, and I will label it as inference.

One more thing sits close to my own desk. Whenever a number surprises me, I first hunt for the context variable I forgot — crowd, dew, toss, travel. The namesake is that same forgotten variable, except it sits in the spreadsheet rather than on the pitch. A number is only as honest as the person who typed it.

So what is the answer? The answer is that I do not know, and saying so is the most useful part of this piece. What is known: both caps come from one match or adjacent matches, the decade is the early 2000s, and the name is shared. What is not known: which name. Closing that gap is what record-keeping actually means.

And that is where the forward argument begins. We keep debating whether Test cricket survives in India. My reading is that the audience has survived — the grounds fill. What has not survived is the domestic game's evidentiary base. Ranji scorecards are not digitised, coverage begins at the knockout stage, and no public dataset exists on which a selection argument can be built. The cap 217 and 218 puzzle is a small sample of that same deficit — the register exists, and there is no way to reach it.

The next time a quiz asks you about namesakes, demand one thing before you answer: the date of birth. Because on the day every Indian cricketer carries a unique ID, this question stops being interesting. And on that same day, perhaps, a selection argument can be verified for the first time.