Caps 217 and 218: The Namesake Question Is Really an Identity Problem

India's men's Test cap register holds 217 and 218 as adjacent entries — one immediately after the other. Wisden Cricket Quiz's 'The Cricketing Namesakes Quiz' asks the question directly off those two numbers: what name do India's men's Test caps 217 and 218 share? The quiz does not print the answer. My interest is not in the answer but in the construction of the question. A cap number is not a name; it is a serial, and a serial only holds up when the register contains no duplicates. The whole quiz bets on that single property — that each cap number is a separate human being, and that every human being carries a name somebody else also carries. Asking for a name from two consecutive serials is really asking a question about record architecture, not about cricket.

Context: what the quiz is, and what rule governs it

This is not a piece about a match, a series or a selection dispute. It is an engagement product, and its construction shows Wisden running it as a standing category — a single short article links to quizzes on the Sharmas of international cricket, on Test-playing Smiths, and now this namesake quiz. That is publisher behaviour, not cricket analysis. The shared surname has become a franchise theme.

The quiz's operative engineering rule fits in one sentence: the name must match exactly. Change the spelling, and the pair is out. The article names four excluded pairs — Mehidy Hasan against Mahedi Hasan, Claire Taylor against Clare Taylor, Abdul Razzaq against Abdur Razzak, Mohammad Sami against Mohammed Shami. That is not a sporting rule. It is a data-classification rule, and it is the most analytically transferable element in the entire piece.

The quiz's scope is deliberately wide — Test, ODI, T20, women's internationals, and England's County Championship. The namesake theme is format-agnostic, which makes the breadth convenient for a quiz. For data, the breadth is a genuine hazard. Any consumer who merges these pairs puts formats, eras and genders into a single record — the exact error cricket analytics forbids. I started with 214 names and a last-place finish, and in the first weeks of that sheet I merged two different people into one row because their names were spelled alike. A valuation sheet is a promise the league table tests, and the promise rests on identity, not on the name string.

Core: the four excluded pairs, and why they are excluded

Abdul Razzaq and Abdur Razzak are the most instructive pair on the list, because the difference is not in the name but in the bowling arm. Razzaq was Pakistan's right-arm pace all-rounder; Razzak is Bangladesh's left-arm spinner. Pool them into one identity and the model loses its economy baseline and its left-arm/right-arm matchup split at the same time. There is no valid way to average a spinner's economy rate with a seamer's. Here the name similarity is an illusion and the role difference is a fact.

Mohammad Sami and Mohammed Shami are the highest-traffic confusion pair of the 2010s — both right-arm pace, one Pakistan, one India. Country provides a filter, so the pair is separable. It remains dangerous because the career windows overlap across the 2010s and the format profiles run parallel. This is the pair that misfires most often in headlines and commentary, which is precisely why it should sit at the top of the list.

Claire Taylor and Clare Taylor are the heaviest pair in the set, because no team or gender filter can separate them. Both played for England women. Same team, same gender, same country. What remains is spelling and date of birth. A record system storing only name, team and format leaves this pair permanently unresolvable. If one pair justifies making date of birth a mandatory field, it is this one.

Mehidy Hasan and Mahedi Hasan are the most dangerous, because team, role and era all collapse together. Both are Bangladesh spin-bowling all-rounders with overlapping careers in the same decade. Nothing structural separates them except spelling. The quiz removed them by rule; in the wild, these two names can land in the same column and quietly corrupt every matchup analysis built on top.

Now the pairs the quiz kept, where the problems hide.

The two Ollie Robinsons show that some claims are time-stamped and the stamp has to be printed. One Ollie Robinson (b. 2026) is Sussex and England's right-arm seamer, a Test player. The other (b. 2026) is a wicketkeeper-batter in English domestic cricket. The article's claim is that only one of them has played Test cricket — true when written, and self-evidently testable now. Any 'only one' claim needs its publication date attached, or it decays silently while readers keep treating it as fact.

The two Daryl Mitchells and Mitchell Santner's joke prove namesake comedy only works between contemporaries. One Daryl Mitchell (b. 2026) captained Worcestershire in the County Championship. The other (b. 2026) is New Zealand's middle-order batter across Test, ODI and T20. Santner's joke rested on that surname, and it lands only because both men were live in the same professional ecosystem at roughly the same time. A pair separated by decades carries no comic force. That is a signal that these two names were genuinely in circulation together in the mid-2010s — which is also the window in which databases were most likely to mis-merge them.

Zaheer Abbas is a different case entirely, because here the player changed the identifier, not the database. His full name was Syed Zaheer Abbas Kirmani, and he chose to use his middle names. Syed Kirmani, India's wicketkeeper, shared the first and last elements, which is why the pair has tangled historically. This is a documented instance of an alias created by the player, and it is why historical records need an alias field rather than a single name string. A system holding one string has already lost this case.

India's Test cap numbering is a mechanism in its own right, and the quiz question rests on it. It is a board and record-keeper convention: each Test debutant receives the next sequential number in debut order. The direct consequence is that adjacent caps such as 217 and 218 debuted in the same Test or in consecutive Tests. That inference carries high confidence, because sequential debut numbering can mean nothing else — and it narrows the answer space sharply.

Here I have to take an explicit position. The quiz withheld the answer, and I will not fill it in. In the work I do, an unchecked answer is a claim, and a claim is a promise some table has to test. The day I can pull the debut scorecards for caps 217 and 218, I will write the answer with the date, the match and the innings attached. Until then, answering would mean breaking my own rule.

The weight of this exercise sits downstream, not in the quiz. Auction lists, franchise shortlists, fantasy rosters, endorsement attribution, aggregated career totals — all of these are places where a player's name functions as a primary key. Where the key is weak, every table built on it is weak. Merging Sami with Shami can put the wrong name on an auction sheet; merging Razzaq with Razzak can move a bowling average; merging Mehidy with Mahedi turns two spinners on one team into one person. Coding all 64 matches taught me where xG stops and cricket begins; that boundary was shot quality and pitch geometry. Here the boundary is different: a name can never be a primary key. Cricket has discrete wicket events, scarce balls, single innings — and on top of that, repeated names, drifting spellings, and players who rename themselves.

Contrarian: the existence of the quiz is not evidence of error

The easy conclusion is that namesake confusion must be common, because Wisden runs a quiz on it. That conclusion confuses correlation with causation. A quiz running measures whether readers recognise these names; it does not measure how often databases fail. A theme that lives in audience memory sells; it is not an error rate. I have no sample for what share of cricket records has been mis-joined on name, and when I have no sample, I do not print a number.

The sharper turn is that the exact-match rule also hides the problem. The four excluded pairs are exactly the four that most need documenting. Removing Mahedi Hasan makes the quiz clean; it does not make the database clean. For historical records, exact-name matching may be the wrong rule altogether — the right rule is probably to make date of birth, role and format mandatory fields and treat the name as a label.

Takeaway

I will leave a condition that can be checked. If caps 217 and 218 debuted in the same Test and the same innings, the shared name is not a coincidence but a line item from that scorecard — and the quiz question was pointing at a scorecard all along. If they debuted in different Tests, the shared name is genuine coincidence and should be recorded as such. Either way one question survives: when will any register print date of birth and role next to the name, so the next quiz does not have to be solved by search?