Shardul Thakur on Hardik’s IPL absence: Team call ultimately decides

The Indian Premier League 2026 has been a springboard for fresh talent and a proving ground for seasoned stars as franchises shape their squads ahead of a dense international calendar. Yet, not every established Indian campaigner has found form this season. A couple of high-profile names—Hardik Pandya and Suryakumar Yadav among them—have struggled to replicate the influence they showed during India’s T20 World Cup 2026 title run, and their difficulties have weighed on their franchise fortunes.

For the Mumbai Indians, the situation has grown particularly tough. After a run of setbacks, they are now mathematically out of the qualification picture with another challenging campaign for the five-time champions. Mumbai sit ninth in the standings, having managed only four wins from their first 12 matches. Their most recent success came in a strong 201-run chase against Punjab Kings, a result that did not end Punjab’s hopes as they continue to chase a top-four berth despite recent turbulence.

Punjab Kings, who began the season with real momentum—remaining unbeaten in their opening seven outings—have since lost momentum sharply. The defeat that followed this match marked their fifth straight loss, underscoring how quickly the balance of power has shifted for the side over the past weeks.

How the match unfolded at Dharamshala

  1. Before the game, the biggest talking point was Mumbai Indians’ captaincy call: Hardik Pandya was left out, with Jasprit Bumrah finally handed the leadership role.
  2. Bumrah’s captaincy debut came after he had served as the backbone of Mumbai’s bowling attack since making his debut for the franchise in 2013.
  3. Suryakumar Yadav also missed the fixture against Punjab Kings due to personal reasons following the birth of his child.
  4. Mumbai’s chase turned into a statement performance, driven by Tilak Varma, who finished unbeaten on 75 off 33 balls to keep the innings under total control.
  5. The win extended the pressure on the Shreyas Iyer-led side’s qualification hopes, while also adding to the difficulties Mumbai have faced at Dharamshala Cricket Stadium across their recent outings.
  6. Bumrah’s first outing as skipper was further enhanced by a fresh burst of effectiveness from Mumbai’s bowling unit, an area that had been below par for them earlier in the season.
  7. Shardul Thakur spearheaded the bowling effort, making maximum use of the conditions and delivering a decisive spell that returned figures of 4 wickets for 39 runs.

Shardul’s impact did not stop at the match. In the post-game press conference, he addressed why Hardik did not travel with the full group and offered a clear timeline for the star all-rounder’s return. He suggested that Hardik’s absence was injury-related, explaining that the captain had missed a couple of matches and had been training in Mumbai since then.

Shardul explains Hardik’s absence

Shardul said: “Hardik is injured, so he could not travel for a couple of games. He went to Raipur [for the game against Royal Challengers Bengaluru (RCB) on May 10], but could not play. He is training in Mumbai now, and I expect him to be back in Kolkata and play against the Kolkata Knight Riders (KKR) next Wednesday. Players like them, we always miss the quality.”

When questioned about whether Hardik could be involved in a trade in the next IPL cycle, Shardul dismissed speculation quickly. He remarked that online chatter continues in waves, adding that the final word always rests with the franchise’s management.

While fans wait to see how Mumbai Indians handle Hardik’s future—both as a player and as captain after a turbulent second stint following his 2024 return—his current form has also slipped. This season, his contributions with both bat and ball have not matched the level expected from a proven match-winner and explosive middle-order presence.

With the bat, Hardik has scored only 146 runs across eight matches, at a strike rate of roughly 136—well below the impact associated with his reputation. With the ball, he has struggled to deliver decisive moments, taking just four wickets while conceding at an economy rate near 12.