Caps 217 and 218: One Name, Two India Test Careers — and Cricket Data's Weakest Link

Wisden's Cricket Quiz asks a small question: what name do India's men's Test caps 217 and 218 share?

The more useful place to stop is not at the question but at its foundation. Two different men. Two different careers. Two different scorecards. And binding them into a single line, one integer. 217. Then 218.

The third thing, which never gets printed on a quiz page: the answer. The piece carries the question and withholds the reply. That omission is not a slip; it is the signal. When the material has no answer, the reporter's job is not to invent one. It is to say which register holds the answer, and where that register's edges are soft.

I have kept a debut ledger since the mid-1990s. It began with county data work in London — one line per debut, a sequence number against each line, a date against each number. This question sent me back to it. My first thought was not what the answer is. It was how the question can be asked at all.

The number has one job: order of arrival

An India Test cap number is not a ranking. It is not a measure of quality, nor a certificate of standing. It is a serial number. India played their first Test at Lord's in June 2026, and from that day the record-keeper has handed each new debutant the next integer in the sequence. On the day a player first wears the Test cap, he receives a number no one has held before.

Within that definition, the entire information payload sits in one place, and it belongs to record-keeping rather than to sport. Caps 217 and 218 are adjacent. In sequential debut numbering, adjacency means the two debuts almost certainly came in the same Test, or in consecutive Tests. That inference runs at high confidence because the system's architecture forces it. It also narrows the search sharply: this stops being a question about ninety years of Indian Test history and becomes a question about a window of one or two matches.

The number's second function is to supply a denominator. A cap of 217 means India had already given Test caps to 216 men. The figure is not a story in itself, but it is the base rate against which any story has to be told. When I assess a career, I first ask how large the population was. The 217th cap means 216 had come before him, and not all of them came back. A count without its denominator is decoration.

The quiz's own architecture follows the same logic. It spans Test, ODI, T20, women's internationals and the English County Championship inside a single question. Namesake identity is format-agnostic, so the quiz does not care. For the reader that is fun. For the data it is a hazard, and I will come to that. The piece also cross-links five other quizzes — the Sharmas in international cricket, the Smiths who played Tests. It is a traffic product, not a research document.

The article's one operative rule is not sporting but classificatory: a namesake counts only if the name matches exactly. Four pairs are therefore explicitly excluded — Mehidy Hasan and Mahedi Hasan, Claire Taylor and Clare Taylor, Abdul Razzaq and Abdur Razzak, Mohammad Sami and Mohammed Shami. That rule is the most analytically transferable thing in the whole piece.

The real subject is identity resolution

The quiz's subject is namesakes. The article's real subject is identity resolution — how a record system keeps two men apart when they carry one name. And it performs that work silently, without announcing that it is doing it.

Rank the four exclusions by risk and the picture clears.

Mohammad Sami and Mohammed Shami are both right-arm pace bowlers, from different countries, and the highest-traffic confusion pair of the 2010s. Same role, different flag. The scorecard shows the country, so this pair can be handled.

Abdul Razzaq and Abdur Razzak are worse, because here the name is near-identical and the function is entirely different. Razzaq is a right-arm pace all-rounder for Pakistan; Razzak is a left-arm spinner for Bangladesh. A change of bowling type is not a detail — pool these two into one row and both the economy-rate baseline and the matchup baseline are corrupted. Joining a left-arm spinner's record against a batsman to a right-arm seamer's record is not a data error; it is an analysis error wearing a data error's clothes.

Mehidy Hasan and Mahedi Hasan are the worst case, because all three filters fail at once: same country, same role as spin-bowling all-rounders, and near-identical eras. When team, role and time all overlap, only spelling survives. Two vowel marks, and two careers rest on them.

Claire Taylor and Clare Taylor is the most delicate pair in the set. Both are former England women's internationals. The team filter fails; the gender filter fails. Only exact spelling and date of birth separate them. Any database keyed on name, team and gender alone will always read them as one person.

Then the pairs the article accepts, because those carry lessons too.

Ollie Robinson (b. 2026) is a right-arm seamer for Sussex and England who has played Test cricket. Ollie Robinson (b. 2026) is a wicketkeeper-batter in the English domestic game. One country, one decade, one name. The only field separating them is role — and role is precisely the column most scorecards do not carry as a structured field.

Daryl Mitchell (b. 2026) captained Worcestershire in the County Championship from 2026 to 2026. Daryl Mitchell (b. 2026) is New Zealand's middle-order batter from 2026 onward. Mitchell Santner's joke rests on this pair, and it lands for a reason. The joke only works because both men were active inside the same professional ecosystem at the same time. Namesakes separated by decades raise no laugh.

Zaheer Abbas is a different case entirely, because here the identifier was changed by the player, not the database. His full name was Syed Zaheer Abbas Kirmani, and he chose to use his middle names — the alias under which he is recorded was created by the man himself. His first and last names collide with Syed Kirmani, the contemporary Indian wicketkeeper. Historical records need alias fields; a single name string will not do.

This is where I had to correct my own habit. In football I never merged two players on name alone, because shirt number and position were the primary keys. In cricket the name is the primary key, and that is the bug. Cricket's own units are bowling type, format, debut date, date of birth, batting position. Until those are stored as structured fields, the name is not a reliable key.

Where the damage shows: IPL auction lists and franchise shortlists are keyed on names, and in a name-keyed list one letter can sell one bowler at another bowler's price. Fantasy rosters are built the same way. And on a live feed where markets price in seconds, one name error becomes one price error. Data velocity has risen; identity verification has not risen with it.

Back to 217 and 218. The inference has already narrowed the window — adjacent numbers, so one Test or consecutive Tests, so the early 2000s. The source withholds the answer. I will not print it, because I have no verification, and dressing a guess as reporting would be the exact error this piece is about. The answer sits in the BCCI cap register. Opening it and matching a date and a debut venue is a verification step, not an inference.

The quiz's editorial patterning offers a weak signal — separate quizzes on common surnames like Sharma and Smith suggest the intended answer is an ordinary Indian surname rather than an obscure one. Confidence is low. It cannot be used as evidence.

The biggest error is treating this as a memory test

Most readers will file this as a memory game. It is a data-model test. The question is answerable not because two men share a name, but because someone recorded both of them in sequence. The question's strength belongs to the register, not the quiz.

The second error is assuming the record is solid. A Test cap number looks like the most stable figure in cricket, and in practice it comes from a register maintained by hand. The four pairs this article excludes are a public list of that register's soft edges. Someone chose them from experience of recurring, real-world confusion, not from a hypothetical list.

The third error is treating namesakes as a funny coincidence. It is not a coincidence; it is a production defect. The fields needed to keep apart two men who share a country, a role and a decade are still not mandatory in most systems.

For me the finding here is not the hidden answer but the visible misfit: a quiz can ask what name caps 217 and 218 share, in the same moment that cricket's data infrastructure cannot reliably say how to keep them apart.

What gets verified next

The next step is straightforward: open the BCCI cap register, fix 217 and 218 with a date and a debut venue, and check whether they came from the same match. On the day that verification lands, the quiz will have done its real work — not on memory, but on record integrity.

The next time a quiz, a scorecard, an auction list or a live feed asks you to trust a name, ask one question back: where is the role field, where is the format field, where is the date of birth. If the map is clean, the story is probably hiding something.