Caps 217 and 218: The Namesake Register Indian Cricket Never Maintains

Somewhere around 2 a.m., between a buffering video and a hunch, I got stuck on a quiz page. The question was small: India's men's Test caps 217 and 218 — what name do they share? I have written scouting reports for fifteen years. My folders hold clips named "left-arm-2026-unnamed-4.mp4", and I can open one and tell you the angle at which the bowler's front arm drops. But I could not name two cap numbers. The shame was not the quiz's. It was mine.

The page carried no answer. It carried the question, links to four or five other quizzes, and a rule: the name has to match exactly. I closed the tab and reopened it. What bothered me was not the missing answer. It was that I work in a profession where the name is the identity, and I had never spent an hour fixing how my own system resolves identity.

This piece is that hour of digging.

A cap number is a debut serial, not a ranking

Start with what the quiz gives and what it withholds.

A Test cap is not a ranking. It is a sequence number. India's register begins with C.K. Nayudu, cap No. 1, when India played their first Test in 2026; every new Test player since has taken the next number. It is a BCCI and record-keeper convention, not a measure of performance.

Caps 217 and 218 therefore mean two players entered the debut register back to back. That yields one hard structural point: consecutive cap numbers usually belong to players who debuted in the same Test, or in consecutive Tests. That is an inference from how sequential debut numbering works, and it narrows the answer space sharply. Anyone chasing the answer first has to decide which decade of Indian debutants they are looking at.

Everything else is absent. No scoreline, no venue, no pitch, no weather, no toss, no DLS, no ranking, no transfer, no governance decision. My daily tools — frame-by-frame footage, seam position, the batter's level, sample size — are useless here. Where a source contains no performance data at all, a technique judgment is not just impossible; it should not be attempted.

So what is left? The quiz's own rule.

That rule says namesakes must match exactly, and then explicitly excludes four pairs: Mehidy Hasan against Mahedi Hasan, Claire Taylor against Clare Taylor, Abdul Razzaq against Abdur Razzak, and Mohammad Sami against Mohammed Shami. This is not a cricket rule. It is a data-classification rule, and it is the most analytically transferable element in the entire piece.

The quiz's scope is its own warning. It deliberately pulls Test, ODI, T20, women's internationals and the English County Championship under one roof. Namesake trivia is format-agnostic, which suits a quiz. For anyone who will later merge these names into a database, it is a real hazard: formats, eras and genders would dissolve into a single record. The first law of analytics is to keep them apart.

There is a second signal. On one short page Wisden links five separate quizzes — on the Sharmas of international cricket, on Test-playing Smiths, and so on. That editorial patterning treats the surname as a franchise theme. It is a comment on the publisher's engagement strategy, not on the sport. It may weakly suggest the intended answer is a common Indian surname rather than an obscure one. That is editorial habit, not evidence, and I will not use it as evidence.

Eleven names, six traps

Now the excavation the quiz itself did not do.

Pair one: two Ollie Robinsons. One is the Sussex and England right-arm fast bowler, born 2026, who debuted in Tests in 2026. The other is a wicketkeeper-batter born 2026 who has played English domestic cricket for Durham and Kent. Same country, same league system, same window. No foreign-player filter rescues you here. When I was tagging footage as a talent analyst at the 2026 Under-19 World Cup, our team had one simple rule: date of birth in every clip filename. That rule still runs in my system, and pairs like this are why.

Pair two: two Daryl Mitchells. One born 2026, Worcestershire captain and a County Championship top-order batter. The other born 2026, a New Zealand middle-order batter. Mitchell Santner's joke rests on this pair, and it lands because both men were contemporaries in the same professional ecosystem. A joke does not work across a gap of decades. That small fact says something large: namesake confusion intensifies with contemporaneity.

Pair three is the most interesting, because no database made the error. Zaheer Abbas's full name was Syed Zaheer Abbas Kirmani; he chose to use his middle names. The identifier under which he is recorded was chosen by the player, not by a record-keeper. Sharing a first and last name with the Indian wicketkeeper Syed Kirmani of the same era was coincidence. The lesson is not: the author of a name is not only the record-keeper; it can be the player. That is why historical records need an alias field rather than a single name string.

Pair four: Claire Taylor and Clare Taylor. Both England women's internationals. This is the most dangerous pair in the set, for a technical reason: a team filter cannot separate them, because the team is the same. A gender filter cannot separate them either. Only exact spelling and date of birth remain. The day your database normalises names — and almost every database does — these two become one.

Pair five: Abdul Razzaq and Abdur Razzak. The first, Pakistan's right-arm fast-medium all-rounder from 2026. The second, Bangladesh's left-arm spinner from 2026. Near-identical name, completely different function. This is a modelling problem, not a sentimental one. Pool these two and you corrupt both the economy-rate baseline and the left-right matchup structure. In cricket analytics, bowling type is a structured field, not a comment.

Pair six is the worst: Mehidy Hasan Miraz and Mahedi Hasan. Both Bangladesh spin-bowling all-rounders, both active from around 2026-18, names almost letter-for-letter identical. When the name matches and the function matches, no filter works. This is where the quiz's exact-match rule collapses in the real world, because in the real world people do not type exactly.

Pair seven: Mohammad Sami and Mohammed Shami. Both right-arm fast bowlers, one for Pakistan from 2026, the other for India from 2026. It is the highest-traffic confusion pair of the 2010s. I remember a franchise shortlist where the name column jammed exactly like this — three people spent twenty minutes deciding which spreadsheet row belonged to whom. In an auction room that is not funny. It is a money error.

Using the name as a primary key is the original sin

One conclusion runs through all seven pairs, and it goes to the foundation of scouting: a player's identity should never be resolved by name. A name is a label, not a key. Any system that uses it as a primary key will break; the only question is when.

The fields that actually matter are dull: date of birth, bowling type and arm, batting position, format, debut date, and the team debuted for. None of them makes a highlight reel. Which may be exactly why nobody fills them in properly.

Take my own work. Across the clips I have tagged in recent years, the most time has gone not into technique and not into filenames but into deciding whose clip it is. Once, a 2026 county clip landed in the wrong Ollie Robinson's folder. Nobody noticed, because nobody checked. I caught it two weeks later, when gloves appeared in the frame and I realised the man I had filed as a fast bowler was in fact a wicketkeeper. Not a thrilling story. But that is the actual work.

There is a commercial edge here, and I will flag it as inference rather than something the quiz states. IPL auction lists and franchise shortlists are keyed on names. Where names nearly collide — Sami/Shami, Razzaq/Razzak, Mehidy/Mahedi — there is a real mis-selection risk in auction-room and scouting workflows. The day a franchise bids on the wrong player, this stops being a quiz and becomes a boardroom question.

What the quiz does not say

The easy move here is to turn one quiz into proof of a data crisis in Indian cricket. I am tempted, because my brain builds large structures out of small finds. But thirteen information points is not proof of a crisis. The four excluded pairs were probably chosen because the compiler has seen real confusion, not invented it. That is a hypothesis, and I will call it one.

Second: withholding the answer is an editorial choice. An answer ends the argument; no answer keeps the comment section alive. This is an engagement product, not a research product. There is nothing wrong with that. The wrong move would be extracting analysis the product does not contain.

Third, and sharpest: our disambiguation systems are built for the wrong threat. The industry watches Sami/Shami because it is loudest — most traffic, most jokes, most comments. The real risk sits in Claire and Clare Taylor, where team and gender filters both fail. We fund fixes for the noisiest error and ignore the most expensive one.

Fourth: there is no money in any of this. A franchise can easily justify a bid on an 18-year-old quick by showing you the video. It is nearly impossible to show what an alias field prevented. Nobody funds an invisible save, so the same error returns in the next auction, the next fantasy app, the next scouting report.

Where this goes

I did not get the answer. I also know that any answer I gave without opening the cap register would be a guess, and I will not commit the exact error this piece is about. The day I open the BCCI cap register, the question resolves in two minutes. That is the real point: the answer exists. What does not exist is one agreed place that holds it.

Because the interesting question is not who 217 and 218 are. It is: when a fantasy app next pays out on the wrong Shami, or a franchise drops the wrong Razzaq's economy rate into its model — who corrects the record? And will that correction have a name, or will it sit in a folder like any other unnamed file?