Caps 217 and 218 Share a Name: Identity Is Cricket Data's Weakest Link

Two rows, one name. Mohammad Sami on the left, Mohammed Shami on the right, and a single vowel between them. I first saw that pair on a tagging sheet in the winter of 2026, where an intern had merged both bowlers into one column. The result was a career average in which two countries, two decades and two entirely different bowling plans had dissolved into each other. Nobody was shown the sheet. The error surfaced four months later, when a scout asked why this bowler's death-over economy was so different across two domestic sides.

Based on my years of watching matches and, more usefully, of cleaning the spreadsheets behind them, the weakest link in cricket's numbers is not the bowling average or the strike rate. It is the player's name — the key that holds up every table, every fantasy roster, every scouting shortlist and every auction list.

The Wisden Cricket Quiz recently posed a question: what name do India's men's Test caps 217 and 218 share? The question is short, it is playful, and the answer is nowhere in the source. When I transferred the material to cards, thirteen information points came out — and not one of them was a match result, a transfer fee, a selection decision or a performance number. Manufacturing analysis where evidence does not exist is the oldest mistake in this profession. So this piece will hold only what the source can carry: the problem of identity, and the integrity of record-keeping.

The quiz's operative rule is a definition, not a sporting one. Namesakes count only when the names match exactly. That is why the compiler explicitly excluded four pairs — Mehidy Hasan versus Mahedi Hasan, Claire Taylor versus Clare Taylor, Abdul Razzaq versus Abdur Razzak, and Mohammad Sami versus Mohammed Shami. The rule keeps the quiz clean, and by accident it also states the most useful design condition in cricket data. The quiz's real subject is not namesakes but identity resolution — and it silently demonstrates why role and bowling type must be stored as structured fields.

The cleanest example is Abdul Razzaq against Abdur Razzak. The first was Pakistan's right-arm pace all-rounder, the second Bangladesh's left-arm spinner. Nearly identical name, functionally opposite job. Any model that pools them corrupts both the economy-rate baseline and the left-right matchup prior. In my experience this kind of contamination never makes noise; it walks quietly into a report, and then a price is set on the strength of that report.

The Claire Taylor and Clare Taylor pair is the most dangerous in the whole set, because both are former England women's internationals. A team filter will not save you. A gender filter will not save you. A format filter will not save you. What remains is exact spelling and date of birth. When a data cleaner assumes that name plus country is sufficient identity, this is the pair that breaks the assumption.

Zaheer Abbas sits at the other end of the problem — here the identity was changed not by a database but by the player. His full name was Syed Zaheer Abbas Kirmani, and he chose to use his middle names. Standing beside him is Syed Kirmani, India's wicketkeeper, with whom both the first and last name would collide. This is not a comic coincidence; it is documented history. Historical records require an alias field, because several players chose the name under which they are recorded.

English domestic cricket has two Ollie Robinsons. One is a right-arm fast bowler born in 2026, who has played Tests for England out of Sussex. The other is a wicketkeeper-batter born in 2026, who has moved between Durham and Kent. The source states that one of the pair has played Test cricket; whether that claim still holds literally today is something I cannot verify, so I will not write it as a claim. That is the discipline — sample size first, confidence band second, conclusion last.

The Mitchell Santner joke about New Zealand's Daryl Mitchell (born 2026) and Worcestershire's captain Daryl Mitchell (born 2026) landed because the two were active in the same professional ecosystem within roughly the same window. A namesake pair separated by decades carries no comic force at all. This looks trivial and is extremely useful: the namesake problem is created not by the name but by the timing overlap.

Now the part of the question that is genuinely analysable — the Test cap sequence. India's men's Test cap numbers are issued in order to each debutant. Caps 217 and 218 mean two players who walked into Test cricket at almost the same moment, or within one match of each other. That inference comes not from a source but from the architecture of sequential numbering, and it narrows the answer space sharply. The source withholds the answer. So will I — because an answer offered without verification is precisely the error this entire piece is tracing.

It is worth pausing here, because the reader's natural question is why anyone should be this serious about something this small. The answer is that the quiz's most valuable content is not the three examples it included but the four pairs it excluded. The four exclusions are effectively a list of the four most common identity collisions in cricket's public data. The compiler picked them from experience, not from imagination. My own file of things the data said first and the pundits said later has namesakes sitting at the top of it.

The second thing that follows from the quiz's existence is that namesake confusion arrives often enough among cricket's core audience to sustain an entire engagement product. That is a weak signal, and I will treat it as a signal rather than proof. If it is right, though, the question is not how many namesakes cricket contains. The question is why a permanent unique identifier is still not mandatory in our databases.

One more thing needs saying plainly: a name match is not an identity match. Two different people sharing a name is a correlation, not a sameness. Cricket analysis makes this error in other costumes all the time — treating two players with similar numbers as the same player. Name collisions are simply more visible, and therefore more embarrassing. The real damage happens when someone preparing for an auction looks at a shortlist and does not read the letter between the two rows. Every market has a blind spot; mine is that I still check it twice.

Five explainers went out that summer. Four came back filed. The fifth was this lesson — that a gap in clarity is closed with a field, not with sentences.

What comes next is a matter for record-keepers rather than forecasters. On the day every Indian debutant is logged with a permanent ID, an alias field and a date-of-birth primary key, the question of caps 217 and 218 will stop being a question — because the answer will not need to be found, it will already be stored. Until then, the next time a quiz hands you two identical names, ask for the date of birth first, then the bowling type. And if both answers come back the same, tell me — I keep a page in the file open for exactly that.