HomeAsian CricketTwenty-Six Catches: Where the Schedule Outweighs the Skill

Twenty-Six Catches: Where the Schedule Outweighs the Skill

**মূল উত্তর:** তিলক বর্মা টি-টোয়েন্টিতে এক ক্যালেন্ডার বছরে ফিল্ডার হিসেবে ২৬টি ক্যাচ নিয়ে রেকর্ড Averageেছেন, যা ইন্দোনেশিয়ার দানিলসন হাওয়ের ২০২৫ সালের ২৫ ক্যাচের সর্বোচ্চটি ভেঙেছে। তবে এই সংখ্যাটি মূলত ম্যাচ-সূচি ও নির্বাচন ধারাবাহিকতার ফল, শুদ্ধ ফিল্ডিং দক্ষতার প্রমাণ নয়। **মূল তথ্য:** - তিলক বর্মা এক ক্যালেন্ডার বছরে ২৬টি ক্যাচ নেন; আগের সর্বোচ্চ ছিল দানিলসন হাওয়ের ২৫টি (২০২৫)। - ২০২৪ সালে সংযুক্ত আরব আমিরাতের মুহাম্মদ ওয়াসিম ২৪টি ক্যাচ নিয়েছিলেন। - তালিকায় আছেন মালয়েশিয়ার শারভিন মুনিয়ান্ডি, উগান্ডার ব্রায়ান মাসাবা ও বাংলাদেশের তানজিদ হাসান (২০টি, ২০২৫)। - দ্বিতীয় টি-টোয়েন্টিতে ভারত টস জিতে ফিল্ডিং নেয়; প্রথম তিন ওভারেই সাইফার্ট ও মিচেলের ক্যাচ নেন তিলক। - ক্যাচ এফিশিয়েন্সি, ড্রপ রেট বা রান সেভের কোনো তথ্য প্রতিবেদনে নেই। **সূত্র:** টাইমস অব ইন্ডিয়া প্রতিবেদন, "Tilak Varma breaks world record during India vs New Zealand 2nd T20I"; প্রকাশের সুনির্দিষ্ট তারিখ প্রতিবেদনে উল্লেখ নেই, শুধু 'শনিবার' উল্লেখিত। **সম্পর্কিত প্রশ্নোত্তর:** প্রশ্ন: তিলক বর্মার ২৬ ক্যাচের রেকর্ড কি তাঁর ফিল্ডিং দক্ষতার প্রমাণ? উত্তর: না—শীর্ষ পাঁচে সহযোগী সদস্য দেশের আধিপত্য দেখায় যে এটি মূলত ম্যাচ-সংখ্যা ও নির্বাচন ধারাবাহিকতার ফল। প্রশ্ন: এই ম্যাচে তিলকের ক্যাচ দুটি কেন গুরুত্বপূর্ণ ছিল? উত্তর: পাওয়ারপ্লেতে ত্রিশ গজের বাইরে মাত্র দুই ফিল্ডার থাকায় রিং বা স্লিপে নেওয়া ওই দুটি ক্যাচ সাইফার্ট ও মিচেলের মতো টপ-অর্ডার ব্যাটারকে দ্রুত ফেরায়। প্রশ্ন: ফিল্ডিং মূল্যায়নের জন্য কোন মেট্রিকগুলো বেশি নির্ভরযোগ্য? উত্তর: ক্যাচ-সুযোগের অনুপাত, ড্রপ রেট, রান সেভ এবং পজিশনভিত্তিক কাঠিন্য—এগুলো কাঁচা ক্যাচ-সংখ্যার চেয়ে বেশি অর্থবহ।

Three overs. Twice the pencil came down on the same page of the scorebook—'c Tilak'. First Seifert, then Mitchell. I left the bowler's column blank, because at that moment I still did not know who had bowled; I only knew both catches had gone to the same pair of hands, eighteen balls apart. I had the notebook open on a tea-stall bench, a thin evening drizzle outside. The silence that settled after the second catch was not the silence of celebration. It was the silence of someone checking the arithmetic.

Then the headline surfaced on the phone screen: world record. A cricketer had taken more catches in a calendar year than anyone before. I looked down at the page. There was no score on it. No runs, no result, no over-by-over account beyond the fall of wickets. The match that produced so large a record had left no record of its own outcome.

That is where my interest begins. This is a record report, not a match report—and that distinction is one of the quietest crises in cricket journalism today.

India against New Zealand, second T20I. India won the toss and chose to field. Three changes in the Indian XI: Vaibhav Sooryavanshi in for the injured Ishan Kishan, Prince Yadav in for Mayank Yadav, and Shreyas Iyer leading. New Zealand's XI had no Williamson, no Conway, no Rachin Ravindra; it had Finn Allen, Tim Seifert, Daryl Mitchell, Glenn Phillips, Bevon Jacobs, Michael Bracewell, Mitchell Santner. Adam Milne was also outside the eleven.

Read those two teamsheets together and one thing becomes plain: both sides were rotating. This was not a full-strength contest. It was an examination of squad depth. For New Zealand, managing senior batters' workloads on an Indian tour is an old habit; for India, dropping new names into the international frame is the current project.

Twenty-Six Catches: Where the Schedule Outweighs the Skill

I need to be explicit about something, because it is how I work. The report carries a 'New Delhi' dateline. A dateline is a bureau's address, not a venue's. Where the match was played, what the pitch did, whether there was dew, day or night—none of it is in the information. Nineteen years of watching the game have taught me that without venue and conditions, the two powerplay catches can be written as events but not as explanations. So I will state what can be stated, and label what is inference as inference.

The record itself: 26 catches as a fielder in a calendar year in T20I cricket. The previous best was 25, by Indonesia's Danilson Hawoe, in 2026. In 2026, the UAE's Muhammad Waseem took 24. The list also carries Malaysia's Sharvin Muniandy, Uganda's Brian Masaba, and Bangladesh's Tanzid Hasan—20, in 2026. Those figures come from the Times of India report, and the report credits no statistical source.

That leaderboard is the argument. A record whose historical top five is three-quarters associate-nation is not a record of skill; it is a record of scheduling. Indonesia, Malaysia, Uganda, the UAE—their calendars are dense with regional qualifiers, where a dozen or more T20Is are played in a year, where the same eleven walks out almost every match, where there is barely room to rest a fielder.

Twenty-Six Catches: Where the Schedule Outweighs the Skill

Tanzid Hasan's name deserves a second look. Twenty catches in a year for Bangladesh means Bangladesh also played a great many T20Is that year. That number says less about the quality of Tanzid's fielding than about the shape of the schedule. I remember the domestic conversation around him in that period was about his batting, not his fielding. Yet his name appears on this list through fielding volume. That gap between the use of a number and its meaning is exactly where the story sits.

So what does this record actually measure? Four things at once. The number of matches played in a year. Guaranteed selection. Fielding rather than wicketkeeping—because a keeper's catches are counted separately. And the bowling attack's dismissal mix: if the bowlers produce catch-dominant deliveries, catches rise by default.

Not one of those four conditions is a clean measure of skill, and together they produce a number that is not comparable with any other number in the game. Setting a raw catch count beside a batting average or a bowling economy is bookkeeping across two different currencies.

An honesty note is required here. The list places a 2026 figure of 26 beside 2026 figures of 25 and 20. The year is not internally clean, and the report carries no date beyond 'Saturday'. I will not present any calendar-dependent conclusion as settled; verification is pending. If you are reading this, please do not treat an unverified number as proof.

Catches are, in fact, the weakest available indicator of fielding quality. The metrics that genuinely separate elite fielders—catch efficiency, drop rate, runs saved, position-adjusted difficulty—are all absent. They are hard to measure; 'most catches' is easy. Fielding remains the least reliably quantified discipline in cricket: where the ball landed, how far the fielder ran, how many runs were saved—reliable data for all of it still does not exist everywhere. The easy sum becomes the headline.

And yet, after every caveat, one thing cannot be argued away: inside the match, those two catches were high-leverage. Seifert and Mitchell inside three overs—an aggressive opener and a top-order anchor. In the powerplay only two fielders may stand outside the thirty-yard circle. A fielder taking catches that early is almost certainly stationed in the ring or at slip, not in the deep. That means Tilak is trusted as a close catcher in the powerplay; he is not merely a boundary rider. That is a conscious coaching decision, and it carries more meaning than the record.

The new-ball attack was Bhuvneshwar Kumar, Arshdeep Singh and Prince Yadav; two catches inside three overs suggests some lateral movement or awkward bounce. That is inference—there is no pitch report in front of me. India chose to field after winning the toss, which is consistent with dew-awareness, but without venue and start time it remains a possibility, not a fact.

The consequence? New Zealand's middle order then rested on Jacobs, Bracewell and Santner, with no Williamson, Conway or Ravindra. In T20, that profile tends to lower the middle-over scoring ceiling and push risk into the death overs. Also inference, not measurement, because the score is unknown to us. And there the story sticks: the process can be praised, the outcome cannot be verified.

So what is the biggest news in this report? Not the thing the headline says. The real news is that 26 catches in a year means roughly one per match—which means he was effectively undroppable for an entire year. No rest, no omission, no injury. To a selector, that is worth no less than a batting average. The headline does not touch it.

The second thing left behind is the nature of the match itself. The captain was Shreyas Iyer, not the regular T20I captain. Three of the eleven were new or near-debut level. India fielded first and made two changes. Taken together, this was a rotation fixture in which experimentation outweighed the pressure to win. A record broken in such a match is a good story, but it is not evidence about where the team actually stands.

Mayank Yadav's continued absence deserves separate attention. The repeated unavailability of India's fastest bowler is not a one-off; it is a structural risk in the pace pipeline. The report gives no reason—injury, rest or rotation, nothing is said. The gap is not small, because a fast-bowling pool is a team's scarcest asset, and uncertain availability makes planning uncertain too.

And Vaibhav Sooryavanshi? He came in for the injured Kishan. There is no detail on the nature or duration of Kishan's injury, and no performance data for Sooryavanshi. Nineteen years in this trade have taught me that where there is no information, neither praise nor criticism is available. Narratives built around teenage talent are the easiest to inflate and the least evidenced.

The largest gap, though, is not statistical but generic. Eleven of nineteen information points concern the catching record and its leaderboard; the rest are toss, eleven, and a commercial footer. No score, no result, no player of the match, no bowling or batting figure. This did not happen by accident. Record headlines draw more clicks, so the record report displaces the match report. Readers learn how many catches a fielder took; they do not learn who won.

Here I want to reverse the easy reading. The easy reading is this: Tilak Varma is India's best fielder, and the record proves it. I tested that reading against two independent witnesses. One, the composition of the leaderboard—associate-nation dominance. Two, the complete absence of efficiency metrics. Two separate witnesses, one verdict: the number is a product of opportunity, not proof of ability.

The second reversal is more uncomfortable. We archive the catches; we do not archive the non-catches. The ball the fielder could not reach, the catch spilled in the eighteenth over, the dive he did not attempt—none of it reaches a list. Memory in the field is biased, and statistics give that bias the dignity of a number.

Twenty-Six Catches: Where the Schedule Outweighs the Skill

And a prediction that follows from the record's own structure: it will be broken within two or three seasons, most likely by an associate-nation player in a qualifier-heavy year. Because the record is schedule-driven, not skill-driven. Star fielders from the major sides will not appear on this list however well they field, simply because they do not play enough matches.

The final over is not a countdown; it is a confession—and the confession here is that we turned a sum into a story while forgetting to write down the result.

Looking forward, the question is clean. If India genuinely want to know how good a fielder Tilak Varma is, counting catches will not tell them. They need catch-to-chance ratio, drop rate, and position-adjusted difficulty. Fielding is where cricket still measures least and narrates most. As long as the instruments stay weak, records like this will keep returning—and each time we will make the same error, mistaking the number for the skill.

And I go back to my notebook. Twice on the same page, 'c Tilak'. The bowler's column blank. Below it, the result column blank too. The silence between balls is where the real documentary begins—and here that silence says more than the record does. The scorebook closes, the archive opens, and memory starts its own league. The question remains: will we remember the fielding, or only the fielder's catch count?