Mumbai's Squad Ledger: Mhatre's Hamstring, Jaiswal's Absence and the Dharamsala Clock
**মূল উত্তর:** মুম্বই তাদের পরের রঞ্জি ম্যাচের জন্য সূর্যাংশ শেডগ ও অঙ্কুশ রাঘুবংশীকে দলে নিয়েছে, কারণ আয়ুষ মাথরে ডান হ্যামস্ট্রিং টিয়ারে চার-ছয় সপ্তাহ বাইরে এবং যশস্বী জয়সওয়াল নিউজিল্যান্ডে ভারত-এ দলের ব্যস্ততায় অনুপস্থিত। ম্যাচটি ১৮ অক্টোবর ২০২৬ থেকে ধারসালায় হিমাচল প্রদেশের বিপক্ষে। **মূল তথ্য:** - আয়ুষ মাথরে ডান হ্যামস্ট্রিং “গ্রেড ৪” টিয়ারে আক্রান্ত; বিশ্রাম চার-ছয় সপ্তাহ, এবং তিনি দলের ভাইস-ক্যাপ্টেন ছিলেন। - যশস্বী জয়সওয়াল নিউজিল্যান্ডে ভারত-এ দলের সফরের কারণে মুম্বইয়ের হয়ে খেলছেন না, চোটের কারণে নয়। - সূর্যাংশ শেডগ ভারত-এ বনাম অস্ট্রেলিয়া-এ থেকে ম্যাচ-ফিট ফিরেছেন; অঙ্কুশ রাঘুবংশীর প্রস্তুতির কথা প্রতিবেদনে নেই। - ম্যাচটি ১৮ অক্টোবর ২০২৬ থেকে ধারসালার HPCA Stadiumে, যা পেস ও সিম-সুইংয়ের জন্য পরিচিত উইকেট। - সিদ্ধেশ লাদ দলের ক্যাপ্টেন; স্কোয়াডে দুই উইকেটকিপার ও তিন স্পিনিং All-rounders আছেন। **উৎস:** মুম্বই রঞ্জি দলের স্কোয়াড ঘোষণা (প্রকাশ্য বোর্ড/রাজ্য সংস্থা কভারেজ), অক্টোবর ২০২৬; ম্যাচের তারিখ ১৮ অক্টোবর ২০২৬। | Cross-checked: cricsultan.com **সম্ভাব্য Next প্রশ্ন:** প্রশ্ন: আয়ুষ মাথরে কতদিন বাইরে থাকবেন? উত্তর: প্রতিবেদন অনুযায়ী চার-ছয় সপ্তাহ, অর্থাৎ সম্ভাব্য ফেরা নভেম্বরের শেষ থেকে ডিসেম্বরের শুরুতে। প্রশ্ন: যশস্বী জয়সওয়াল কেন খেলছেন না? উত্তর: তিনি নিউজিল্যান্ড সফরে ভারত-এ দলের ব্যস্ততায় আছেন, কোনো চোটের কারণে নয়। প্রশ্ন: ধারসালার উইকেট কেমন? উত্তর: HPCA Stadium প্রায় ১৩০০ মিটার Heightয় এবং সিম-সুইং ও পেস-সহায়ক পরিবেশের জন্য পরিচিত (cricsultan.com ভেন্যু Profile)।
When the squad sheet surfaced on my feed, my eye did not stop at the list of names — it stopped at a blank space. The name that should have sat near the top of Mumbai's order was missing. Ayush Mhatre — the man handed the vice-captain's badge before the season began — is out with a right hamstring injury. Another name is absent from the same sheet: Yashasvi Jaiswal, currently with India A on the New Zealand tour. So when Mumbai walk out against Himachal Pradesh in Dharamsala from October 18, 2026, they will do so without two first-choice batters. What the headline sells as a “squad update” is, in ledger terms, a debt relocation: the batting shortfall is being booked onto two young men's accounts.

I have spent years watching Ranji sessions on screen, and every time the same thing stands out — in this format teams win session by session, not over by over. The context needs stating plainly, because the Ranji Trophy is not franchise cricket. It is India's premier domestic first-class competition, four-day red-ball cricket. Mumbai are the most successful side in its history, with more than twenty titles. For a team with that ledger, the absence of two batters rarely causes a stir — and that is precisely where the real story hides.
The venue quietly rewrites every calculation. The HPCA Stadium in Dharamsala sits at roughly 1,300 metres; in thin, cool air the ball swings and seams off the new ball. Among India's first-class grounds it is one of the rare ones where seam, not spin, decides the game. Mid-October in Dharamsala brings both autumn chill and rain risk; in that case the first morning session often settles the match.
Mhatre's injury is the single most valuable data point in this story — because it empties two columns at once. First, Mumbai lose a regular top-order batter; second, they lose their deputy leadership. The player named vice-captain before the season tore his right hamstring against Chandigarh, and reports call it a “Grade 4” tear — four to six weeks out. A professional caution is due here: the standard clinical grading for hamstring strains runs from one to three. Grade 1 is mild, Grade 2 partial, Grade 3 a complete rupture. There is no standard “Grade 4.” It may be a journalistic error, or a federation simplification. What does not change is the severity implied — four to six weeks means this is not a mild strain but a near-complete-grade injury.
This is where the clock matters. A release clause is a clock with a price tag, not a promise — and the same rule applies to injury. Four to six weeks from mid-October puts the return in late November to early December. In the Ranji group stage that is not one match but a block. The ground may stop, but the contract clock does not — just as football stopped in March while the expiry wall kept ticking through the silence. If Mumbai's batting collapses in this window, questions about load management will follow. For a young player, the recurrence risk after a high-grade hamstring tear is materially higher — a long-term asset-management question, not merely a medical one.
Jaiswal's absence looks simple at first — he is out through commitment, not injury, called up for India A's tour of New Zealand. But the reason itself reveals the structure: the priority ladder in the Indian cricket calendar is national team, then A team, then domestic side. For an established Test opener, that call could signal either a plan to keep his red-ball rhythm or preparation for an upcoming New Zealand series. The report states the fact of the call, not the reason.
There is a quiet asymmetry between the two replacements. Suryansh Shedge arrives from India A's red-ball series against Australia A — he is match-fit in the long format. Angkrish Raghuvanshi's readiness is nowhere stated. The two names sit side by side in the headline, but in the ledger they are two different lines — one arriving with proven rhythm, the other called on potential. That difference will show in who adapts fastest in Dharamsala's first innings.

The squad's composition raises the loudest question. Mumbai have brought three spin-bowling all-rounders — Shams Mulani, Tanush Kotian, Ankolekar — and four seamers — Tushar Deshpande, Mohit Awasthi, Sylvester Dsouza, Omkar Tarmale. Four seamers at a pace-friendly Dharamsala surface is reasonable, but a spin-heavy core means the side is built to a home template; today that template faces hostile soil. Captain Siddhesh Lad leads, with two wicketkeepers — Akash Anand and Hardik Tamore — either rotation or an unresolved first-choice glove question. Sarfaraz Khan's experience steadies the batting unit, but the Mhatre-Jaiswal pairing is a different thing.
This bench depth is not accidental. A cycle runs here — Ranji to India A, India A to the IPL, and back to Ranji. That a side can lose two first-choice batters at once and still field India A-calibre replacements is the structural advantage of the Mumbai system. So the question is not only about this match — it is how sustainable that cycle is, and how much of it rests on a few men's hamstrings.
Here is what no one is saying. Everyone is counting who came in and who dropped out. But what Mumbai have lost is more than two batters — it is a leadership vacuum. Naming a side with the vice-captaincy left empty means extra weight on Siddhesh Lad and a missing deputy voice in mid-innings decisions. Second, no one is questioning the “Grade 4” label; yet building a headline on a non-standard diagnosis means turning unverified information into fact. Third, carrying a spin-heavy squad to pace-friendly Dharamsala is itself a gamble that never made the headline. In the transfer world I know, the €222m ledger never balanced; it just moved the debt to a different column. The same thing is happening here — the shortfall has not vanished, only shifted onto two young shoulders.
The forward sum is simple but unforgiving. Mhatre's return date is now Mumbai's real clock — push past six weeks and selectors must sit again, with the vice-captaincy question resurfacing. Watch Dharamsala's first morning session: if Mumbai's top order wobbles against the new ball, we will see who is paying down the two batters' debt. And on Jaiswal there is one question — is the India A tour preparation, or a signal? The answer arrives in the next squad sheet.

