Mumbai's Ranji Squad: Mhatre's Hamstring, Jaiswal's India A Duty, and the Dharamsala Pace Equation

Walk into the HPCA Stadium in Dharamsala on an October morning and the first thing you notice is not the pitch but the air. At roughly 1,300 metres above sea level, the thin, cool breeze amplifies swing on the new ball, which is why Dharamsala occupies a strange place in Indian first-class cricket: here it is the seamers, not the spinners, who set the tempo. Mumbai begin their Ranji Trophy fixture against Himachal Pradesh on October 18. The squad was announced before the match, and that short release hides more than a first read suggests.

Whenever I arrive at a ground, I walk the empty concourse until the silence becomes a formation. That habit began in 2026, at the World Cup final in Moscow. Croatia lost that day, but for the final twenty minutes I watched only Luka Modric — a 33-year-old with the Golden Ball in his hands and the trophy in his eyes. That was when I understood that the real story starts after the noise stops. In cricket, that lesson taught me to read a squad list through its absences, not its presences.

I still carry my 'Pitch Silences' notebook into press boxes. At a ground like Dharamsala, the true key of a match is played in the first hour of the morning, when the stands are almost empty and the new ball speaks loudest. That notebook taught me that where there is less sound, there is more arithmetic.

So my first question about Mumbai's list was not who came in, but who is missing, and why. The release names Suryansh Shedge and Angkrish Raghuvanshi in the squad. In effect, they take the places of two men: Ayush Mhatre and Yashasvi Jaiswal.

Mhatre's absence is the heaviest data point in the story, and not only because of his batting. Before the season began, he was named the team's vice-captain. He injured his right hamstring during the match against Chandigarh, and the medical report describes a Grade 4 tear requiring four to six weeks of rest.

This needs to be stated plainly. Standard clinical grading for hamstring strains runs from Grade 1 to Grade 3 — Grade 1 mild, Grade 3 a complete rupture. 'Grade 4' does not denote a recognised clinical category. The injury is clearly serious; the label itself is not authoritative enough to be quoted verbatim. Announcement language and medical language are not the same, and in journalism that distinction matters.

Do the arithmetic and the picture sharpens. An injury in mid-October plus four to six weeks of rest places Mhatre's return somewhere between late November and early December. He misses a substantial block of the Ranji group stage, not one fixture. If Mumbai lose this single match, that is an event; if the absence stretches to two months, that is a season story.

The second absentee, Yashasvi Jaiswal, is a completely different case. No injury, no loss of form — he is unavailable because of the India A tour of New Zealand. What is worth noting here is the order of priority: national duty always outranks domestic obligation.

That chain of priority is a permanent feature of Indian cricket's architecture. National team, then India A, then the domestic side, then the franchise — a player's calendar is largely divided along that hierarchy. For Mumbai the bridge tends to function smoothly, because its players circulate through all three tiers regularly.

That is what makes the Jaiswal detail interesting. For a settled Test opener, an India A tour can mean one of three things: maintaining red-ball rhythm, preparing for a New Zealand series, or a phase of rebuilding form. The release states the tour, not the reason. So the sensible move is to log the signal without rushing to a conclusion.

The two replacements are not equivalent either. Suryansh Shedge arrives from India A duty against Australia A, meaning his red-ball match fitness is fresh. For Angkrish Raghuvanshi there is no such indication; he has been called up, but his readiness is not described. That small asymmetry says the two roles differ — Shedge comes to hold a rhythm, Raghuvanshi comes to seize an opportunity.

The full list shows that Mumbai's depth is not accidental. Siddhesh Lad leads, with Sarfaraz Khan, Raghuvanshi, Shedge, Mushir Khan and Parkar in the batting group. Two wicketkeepers are named — Akash Anand and Hardik Tamore. The spin all-rounder core is Shams Mulani, Tanush Kotian and Ankolekar, while the seam group comprises Tushar Deshpande, Mohit Awasthi, Sylvester Dsouza and Omkar Tarmale.

Mumbai are the most successful side in Ranji Trophy history, with a record 42 titles. That number is not merely a boast; it is evidence of process. A system that has produced players for this long cannot be producing depth by accident. So even with two first-choice batters missing, the men replacing them are India A-calibre — the ordinary output of that system.

Dharamsala is Himachal Pradesh's home ground, so the advantage of conditions will not sit with the visiting side. The home team knows which end the wind comes from and which session the swing dies down. For Mumbai, the first hour of the first day is therefore a test of adaptation as much as of cricket.

Yet against the Dharamsala backdrop, the composition looks slightly odd. The first ninety minutes with the new ball are the most valuable passage of the match here, and conditions reward pace. Mumbai have named three spin-bowling all-rounders and four specialist seamers. That is not a mistake, but it is a wager — one in which the team trusts its batting depth more than the soil and the air.

Mumbai's choice is less an announcement than an assumption — that their batting will post a large first-innings score at Dharamsala and that spin will work its way back into the game. If the assumption holds, the spinners matter in the fourth innings; if it fails, the match may drift away in the first session.

In the four-day red-ball format, decisions are made by session, not by over. New ball, declaration, follow-on — these are the real vocabulary here. The second new ball is when spinners carry extra load, and that is exactly where Mulani, Kotian and Ankolekar will be tested. Selection errors in this format are not small errors; one wrong seamer or one extra spinner can reshape an entire session's plan.

Naming two wicketkeepers is another signal. Either it is rotation, or the first-choice gloves are not yet settled. That the question is still open this deep into the season means at least one position inside this Mumbai side remains under examination.

The vice-captaincy vacancy is less discussed but just as real. Mhatre was appointed deputy before the season; his absence leaves the second layer of leadership empty. Lad is experienced, so the damage is limited — but who the deputy will be across a long season is a question the team has not answered.

In December 2026, in Doha, I watched Morocco's semi-final. Morocco lost, but Sofyan Amrabat's 11.2 kilometres covered and the 40,000 supporters who sang for thirty minutes afterwards taught me that structure and emotion are not separate things. Regragui's 4-3-3 block was arithmetic; the singing in the stands was that arithmetic answering back. Mumbai's squad can be read the same way — what is a decision on paper becomes emotion on the field.

Taken together, what this release teaches me is not a list but a flow. The way players move between Mumbai, India A, the national team and the IPL is the actual news. A Ranji squad list is not only a domestic team's paperwork; it is a scouting bulletin for IPL franchises and national selectors. For players of the age of Raghuvanshi, Mushir Khan and Parkar, four days at Dharamsala can settle a great deal of the conversation that follows.

This is where I part company with the conventional read. We usually interpret such an announcement as a display of depth — Mumbai lost two first-choice batters and did not wobble, and that is the praiseworthy part. But the same information can be read another way: twenty-three and twenty-four-year-olds are carrying domestic cricket, India A series, IPL camps and national training in a single season, and the final accounting of that load lands on their bodies.

Mhatre's injury is the lesson here. After a high-grade hamstring tear, the risk of recurrence rises markedly, particularly in a young player. His return should therefore be staged, not rushed. Rest is not weakness in this system; rest is part of the system.

My scepticism about how young talent is valued is old. When a player enters talks for a huge contract after only a handful of big matches, that is not investment, it is gambling. Setting a large price on the basis of fewer than fifty top-level appearances is a habit football shares with cricket. Big decisions on small samples, and the cost is finally paid by the player's body.

Dharamsala's weather is a quieter risk. In late October, rain is possible at this hill venue, and in a red-ball match the morning session often decides the outcome. A reserve day prevents abandonment, but it cannot prevent a loss of rhythm.

Administratively, nothing here is unusual. There is no reported dispute over releasing players, and the selection process is routine. Relations between the Mumbai Cricket Association and the board are currently smooth — that too is information, even if it is silent. But smoothness and fairness are not the same thing, and the question of player load still sits with the administrators.

Three things I will keep watching. First, Mhatre's recovery timeline — anything beyond six weeks raises a larger question about load management. Second, Jaiswal's pathway from India A back to the senior side — that will clarify the trajectory of his career. Third, the performances of Shedge and Raghuvanshi in this fixture.

Because Dharamsala is a window for the seamers. Deshpande, Awasthi, Dsouza, Tarmale — for some of them, these four days can shift the conversation of the next few months. The match will end, the crowd will fill the stands, and then it will empty again.

Standing in that empty concourse, what remains is not the scorecard but the weight of a decision. The answer to Mumbai's choice will arrive in December, when Mhatre returns and it becomes clear where Jaiswal stands. Until then one question hangs in the air: if the team's depth is genuinely this strong, why is the young body pushed this hard?