What Name Do India's Test Caps 217 and 218 Share? The Question Matters More Than the Answer

Wisden's quiz asks a small question: what name do India's men's Test caps 217 and 218 share? The quiz does not supply the answer. That absence is the most honest part of the exercise. When I read a quiz like this from my desk in Kuala Lumpur, I open the scorecard first and the name list second. In cricket, a name is not only an identity; it is a database key. When two players share one, a single scorecard line splits into two careers.

The spreadsheet held 115 balls, and the derby still refused to balance. In July 2026 I watched Harmanpreet Kaur's 171 not out against Australia on a stream that buffered every third over. My classmates were arguing about the road to Russia 2026; I was logging bowler, length, field and shot for every delivery. The sheet had a “name” column too. Later an editor asked how I knew which player was which. The answer came from the sequence of balls, not from the name list. In cricket data, the weakest link is often the one we treat as strongest: the name.

Wisden's quiz turns that weakness into entertainment. It offers two Ollie Robinsons, two Daryl Mitchells, the Zaheer Abbas and Syed Kirmani pair, and four near-name pairs that are explicitly excluded. The rule is exact matching. Mehidy Hasan and Mahedi Hasan do not count as one. Claire Taylor and Clare Taylor do not count as one. Abdul Razzaq and Abdur Razzak do not count as one. Mohammad Sami and Mohammed Shami do not count as one. This is not a playing rule; it is a data-classification rule. It is also the most transferable thing in the quiz.

India's Test caps are sequential. Every new Test player gets the next number. Caps 217 and 218 therefore mean two players who entered the Indian Test side at roughly the same time. It is highly likely they debuted in the same Test, or in consecutive Tests. That inference comes from the architecture of cap numbering, not from a scoreline. The quiz withholds the answer, so I will not invent one. I will say only this: the shared-name question is really a shared-identity question, and identity has been a record-keeping problem for as long as cricket has kept a scorebook.

I spent six days in Southampton watching the same release point become a sentence. June 2026, the World Test Championship final. India 217 and 170, New Zealand 249 and 140 for 2. Inside the press tent, “India choke again” was filed within the hour. I spent two rain breaks frame-capturing Kyle Jamieson's 5 for 31 and measuring a release point roughly 30 centimetres above anything India had. My piece ran on mechanics, not verdict. But another sheet was open on my laptop: names, dates of birth, roles, bowling types. Because when you build data upward from a scorecard, the “name” column is the first to deceive you.

The quiz contains 13 information points. There is no match result, no transfer, no performance data. That matters. Extracting “India's batting depth” or “a fast-bowling legacy” from this source would be manufacturing depth. What the source does provide is a small register of identity confusion. Four pairs in that register are the real enemies of cricket databases.

Abdul Razzaq and Abdur Razzak are the cleanest case. One is a Pakistan right-arm pace-bowling all-rounder; the other is a Bangladesh left-arm spinner. The names are nearly identical; the functions are not. If a model pools them, both economy-rate and matchup baselines are corrupted. This is not hypothetical. IPL auction lists, fantasy rosters and scouting shortlists are keyed on names. One bad merge can change a player's role.

Claire Taylor and Clare Taylor are more difficult. Both are former England women's internationals. A team filter will not fix the confusion; a gender filter will not fix it either. Only exact spelling and date of birth will. For me this is the most consequential pair in the quiz, because women's cricket records already contend with thinner coverage and thinner data. A shared name there can swallow one career into another. That is not a harmless quiz error; it takes a record away from the less discussed player.

Mohammad Sami and Mohammed Shami are the highest-traffic confusion of the 2010s. Both right-arm pace, both with near-identical names, both from different countries. In a commentary box, haste does the rest. On social media, the error is daily. The quiz excludes them, and that is its intellectual honesty.

Mehidy Hasan and Mahedi Hasan are two Bangladesh spin-bowling all-rounders. One vowel separates the spellings; a career separates the players. The pair shows that a full name can still be an insufficient identifier. Search “Hasan” and both appear. Search “Mehidy” and one disappears. That is the crisis of the name-as-key.

Zaheer Abbas is a different kind of case. His full name is Syed Zaheer Abbas Kirmani. He chose to use his middle names. The player changed the identifier, not the database. Syed Kirmani was the contemporary Indian wicketkeeper whose first and last names overlap with Zaheer Abbas's recorded name. The question is not only who is who; it is under which name each is recorded. Historical records need alias fields. A single name string will not do.

Ollie Robinson is the modern example. The pace bowler born in 2026 has played Test cricket for England. The wicketkeeper-batter born in 2026 is the second Ollie Robinson in English domestic cricket. The quiz says only one of them has played Test cricket. Whether that claim still holds today is a separate verification question. The point stands: search “Ollie Robinson” and you get two profiles, one pace bowler and one wicketkeeper. Without role, the name is incomplete.

Daryl Mitchell's case includes Mitchell Santner's joke. The Daryl Mitchell born in 2026 captained Worcestershire and played County Championship cricket. The Daryl Mitchell born in 2026 bats in New Zealand's middle order. Santner's quip works because the two were active contemporaries in the same professional ecosystem. A pair separated by decades would carry no comic force.

The quiz's real subject is identity resolution, not namesakes. Cricket data should store name, date of birth, role, bowling type, format and team as separate fields. If all of that is crammed into one string, the quiz remains fun and the analytics become useless. In every match sheet I keep, the date-of-birth and role columns are filled before the numbers. That is not a habit; it is a necessity.

India's Test caps 217 and 218 return us to the same point. The source does not answer the question. That does not make the question worthless. It means the answer must come from the board's record, not from the quiz. Sequential cap numbers give one solid constraint: the two players belong to the same cohort, possibly the same debut Test. To learn the shared name, we need that debut list. And if the list is only names and matches, we are back to the problem the quiz started with.

There is a professional trap here. In trying to extract “depth” from a quiz, writers often produce claims the source does not support. “The shared name of caps 217 and 218 reveals Indian cricket's democratic tradition” sounds good and has no basis in the quiz. I will not write it. The source has 13 information points and no performance data. My claim will be limited: this quiz is a cultural signal of identity error, not a performance analysis.

The outside misreading is that name collisions are a fun detail. They are a data-infrastructure failure. When the commentary box makes a joke of two similar names, the data desk knows how many records one bad join can damage. This is the commentary-box lag. The technical argument was settled at the data desk years ago; the holdout is the old habit of treating names as sufficient.

Wisden's quiz is itself an engagement product. Five separate quiz cross-links in one short article—on the Sharmas, the Smiths and others—suggest a traffic-and-conversation strategy. That is an observation about the publisher, not the sport. I will disclose it rather than pretend the quiz is a research document.

In the auction world, the practical risk is real. Franchise shortlists and auction lists are keyed on names. If Sami/Shami, Razzaq/Razzak or Mehidy/Mahedi sit in one spreadsheet without dates of birth and roles, a scouting team can pick the wrong profile. That is inference, not a claim in the quiz. It rests on a simple fact: a name is a key, and a duplicate key does not open the lock; it jams it.

The lesson I take is that cricket must stop treating a name as a sufficient identity. Every public record should show date of birth, role and format separately. A board cap list with only names and matches is incomplete. A database without an alias field will always struggle with cases like Zaheer Abbas and Syed Kirmani.

I am not claiming that nobody knows the answer to caps 217 and 218. I am saying the source that asked the question did not supply it. In journalism, that distinction matters. To answer it, we need the official Indian Test cap list, the scorecards of that period and the players' dates of birth. Matching surnames alone would repeat the very error the quiz avoids.

The most useful part of the quiz is its four exclusions. They show that the compiler knows where real confusion lives: two Bangladeshi Hasans, two England Taylors, a Pakistan-Bangladesh Razzaq/Razzak pair, and a Pakistan-India Sami/Shami pair. These look like recurring real-world errors, not hypothetical ones. That is my inference, not a confirmed fact.

I should also record what the quiz cannot tell us. It offers no ICC ranking, no WTC points, no squad depth, no home-away profile. Writing about those absences would be filling space. I will not.

If you play the quiz, do one thing before answering: ask on what basis you are treating two names as one. Spelling? Date of birth? Team? Format? Bowling type? The day those questions become part of the scorecard, quizzes like this will no longer be necessary. Until then, the shared name of caps 217 and 218 is a harmless question with a serious record-keeping problem underneath.

My next piece will return to that problem: how many names in India's Test cap list can split into two players without a date of birth. That number will tell us more about the strength of the record than the quiz does. And if the number is zero, the quiz's answer will become clear too.