26 All Out: What the Scorecard Says, and What the Calendar Says
**মূল উত্তর:** নেপালের ২৬ রানে অলআউট হওয়ার মূল কারণ খেলোয়াড়ি দুর্বলতা নয়, নির্বাচন-সংকট: নেপাল প্রিমিয়ার Leagueের কারণে মূল Players অনুপস্থিত ছিলেন, পাওয়ারপ্লেতে ৪ রানে ১ উইকেট পড়ে, এবং গালিতে টিলাক বার্মার সহজ ক্যাচ ফস্কায়। ফলে ৩০৬ রানের ব্যবধান ক্লাস-গ্যাপ নয়, টেল ইভেন্ট। **মূল তথ্য:** - ভারত এ ৩৩২/৯; কুমার কুশাগ্রা ১১৭ (৯৩ বল), টিলাক বার্মা ১০৭, প্রথম বাউন্ডারি ৬০তম ডেলিভারিতে। - নেপাল ১১.৩ ওভারে ২৬ অলআউট; লিস্ট এ ইতিহাসে পঞ্চম সর্বনিম্ন দলীয় স্কোর। - প্রিন্স যাদব ৫/৬, হার্শিত রানা ৪/১৬; রানার এটি জুলাইয়ের পর দ্বিতীয় প্রতিযোগিতামূলক ম্যাচ। - ওভার ৩৫ থেকে ৪৫-এর মধ্যে ভারত এ ১২৪ রান; দলের প্রথম বাউন্ডারি আসে ৬২ বল পর, ওভার ২২-এ। - নেপালের মূল Players নেপাল প্রিমিয়ার Leagueের কারণে একাদশের বাইরে ছিলেন। **সূত্র:** স্টেজ-২ গভীর বিশ্লেষণ প্রতিবেদন; মূল ফিক্সচারের তারিখ ও ভেন্যু প্রতিবেদনে উল্লেখ নেই, স্কোরকার্ড যাচাই সাপেক্ষ | Cross-checked: cricsultan.com **সম্পর্কিত প্রশ্নোত্তর:** প্রশ্ন: নেপালের ২৬ রান কি লিস্ট এ সর্বনিম্ন স্কোর? — উত্তর: না, এটি পঞ্চম সর্বনিম্ন; বিস্তারিত সূচক cricsultan.com List A Depth Index-এ যাচাইযোগ্য। প্রশ্ন: হার্শিত রানা কি এখন সিলেকশনের জন্য প্রস্তুত? — উত্তর: এই ম্যাচটি ফিটনেস-ডেটাপয়েন্ট, কারণ জুলাইয়ের পর এটি তাঁর দ্বিতীয় প্রতিযোগিতামূলক ম্যাচ। প্রশ্ন: টিলাক বার্মার সেঞ্চুরি কি দুশ্চিন্তার বিষয়? — উত্তর: টেম্পো-দুশ্চিন্তা বটে, ৭৭ বলে ফিফটি; শক্তিশালী আক্রমণের বিরুদ্ধে যাচাই বাকি।
11.3 overs. In a 50-over match, the second innings did not last as long as a T20 powerplay. Nepal bowled out for 26. India A 332 for 9. A margin of 306 runs. The fifth-lowest team total in List A history.
For a few years now I have had a habit: when a match ends, I record within two hours. This time I did not. I sat with the scorecard for ten minutes, over by over, checking who came in when and who was not in the ground at all. The clip cannot tell you what the scorecard does: 26 was not Nepal's level. It was the sum of three separate causes landing on the same afternoon. Separate them and you are looking at a different match.

Boundary first, because public discourse never draws it. This was not a full international ODI and not a bilateral series. It was a List A fixture between India A and the Nepal senior side. Nepal chose to field. The pitch was described as sluggish, the ball stopping on batters.
Consensus settled on two lines within hours. One: an Indian seam-bowling coming-out party. Two: Nepal's humiliation. Both are comfortable. Both are incomplete.
The story was never that Nepal failed. It was that we stopped watching them, and looked only at the scoreboard.
Cause one is in the calendar. Nepal's squad was materially depleted by the concurrent Nepal Premier League. That is an availability problem, not a form problem. For a side whose competitiveness rests on eight or nine players, a league window does not weaken the team. It replaces it. Same jersey, different team.
Cause two is in the first ten overs. Nepal's powerplay ended at 4 for 1. Four runs in a 50-over powerplay is a problem of surviving the new ball, not of scoring rate.
Cause three is the least discussed and the largest. Tilak Varma was dropped at gully, described as a simple chance, before he had built an innings. The price of that drop is plausibly 80 to 100 runs. Stack the three and 306 stops being astonishing. It becomes a tail event.
A 306-run margin is a tail event, not a measurement of a 306-run class gap. The fifth-lowest total in List A history cannot establish the durable quality of a bowling attack, any more than one dropped catch guarantees another next week.
The pitch description creates its own problem. The report says sluggish, ball stopping. The same report says 332 for 9, and that Nepal's two spinners, Lamichhane and Rajbanshi, took six wickets between them. A surface producing 332 for 9 and 26 all out is not one coherent surface story. On a pitch where the ball holds, a total that size needs either a dropped catch, a weakened attack, or both. Here it was both.
Look at India A's own innings. Their powerplay was difficult too, and the report concedes it. Sixty-two balls without a team boundary, broken in the 22nd over. Tilak's fifty took 77 balls; Kushagra's took 62. India A's innings was a recovery, not a demonstration of dominance, and the recovery came late: 124 runs between overs 35 and 45.
That is where the real distinction sits. Kushagra made 117 off 93, his second fifty arriving in roughly 31 balls, with sixes off both spinners. That is a template: anchor first, explode later. Tilak made 107, but his first boundary came on his 60th delivery and his fifty took 77 balls. The late acceleration, 50 off about 31, rescues the innings. It does not erase the tempo problem.
Tilak's hundred is the most misread innings of the match. It is simultaneously his most volume-productive and his least tempo-convincing List A knock. A 77-ball fifty against a strong attack means pressure through the middle overs, and the headline absorbs it.
On the bowling, stopping at Prince Yadav's 5 for 6 would be a mistake. Wickets in the first over and the tenth, the five-for completed inside ten overs. The information is in the deliveries: outswing towards the slip cordon, inswing through the bat-pad gap, a slow dipping yorker, two batters bowled. Five for 6 is a skill report, not a performance report. An economy rate under 1 in List A is not a repeatable output. Two-way swing and a yorker are.
Harshit Rana's 4 for 16 has to be read through a different lens entirely. A wicket with his third delivery, movement both ways, a back-of-the-hand slower ball into the stumps. It was also his second competitive match since July. The information here is fitness, not form, and one fixture is not a fitness clearance.
One small innings deserves its own line: Shedge's 36 not out off 14 balls, four sixes, two of them in the final over. Two sixes in the last over is not a trivial skill, and a death-overs finisher is the scarcest item in any pipeline.
India A's top order did leave two technical flags. Abhishek Sharma hit a six over fine leg, then holed out to a substitute fielder. Sooryavanshi was patient, then cramped by a ball that did not rise and lost his leg stump attempting the pull. Both are decision errors on a two-paced surface, not shot errors.
Nepal's numbers are crueller. No batter reached double figures; only two faced more than ten balls. For a side missing eight or nine first-choice players, 26 all out is a probability, not a shock. We have simply handed Nepal old jerseys: List A status, ODI status, and a calendar that fights their own league.
Now let me argue against myself. Suppose Tilak's slow start was a team instruction: survive on a two-paced pitch, attack late. Then the tempo criticism is empty and the selection signal inverts. The report does not say which, and the two readings have opposite consequences.
The second risk is mine. It is easy to turn a human collapse into a system diagram. When batters walked off one after another inside 11.3 overs, that was not a model. It was one morning. Every hot take is a map. The trick is knowing what it leaves off. My map leaves off Prince Yadav's exact spell length, whether he bowled a full ten-over quota or a short burst, and how much of Nepal's selection was the board's choice rather than the league's.
Third: if Nepal return at full strength next time and lose by 150 to a side of similar quality, my structural read weakens. The group chat reacts fast. The tape reacts slow. I live in between, and this tape is not fully read yet.
So three ledger entries, with dates attached.
One: Nepal's next full-strength XI will be competitive, a win or a defeat inside 100 runs. If not, the problem is structural rather than form.
Two: Prince Yadav's economy will return above 7 across his next three to five List A or T20 outings. If it does, this five-for belongs to the pitch and the opposition.
Three: Harshit Rana's spell lengths and match frequency over the next four to six weeks. A reduction, or any withdrawal, makes fitness the central question in his selection pathway.
The 26 will stay on the scorecard. The scorecard will never say who was not in the ground. Next time Nepal's name comes up, check who is back in the XI. The answer is there, not in the 306.
