Why was the toss conducted twice in Jammu & Kashmir vs Vidarbha Ranji Trophy match; reason revealed

Ranji Trophy 2026–27: Jammu & Kashmir-Vidarbha Match Sees an Unusual Second Toss

A rare procedural mix-up added an unexpected twist to the Ranji Trophy 2026–27 fixture between Jammu & Kashmir and Vidarbha, when the captains had to take part in the toss twice. Jammu & Kashmir won the first toss and chose to field, but a mistake in the team sheet prompted officials to conduct the toss again. Vidarbha won the second toss and also elected to bowl first.

The unusual sequence drew attention because a toss is normally a one-time decision that sets the conditions for the start of a cricket match. In this case, however, the issue was not simply about who had called correctly. It concerned the submitted playing XI and the rules governing changes to a team after it has been nominated for a multi-day fixture.

Why Was the Toss Conducted Twice?

According to a report by Kashmir Sports Watch, Jammu & Kashmir’s team sheet reportedly listed one player’s name twice. The error came to light after the first toss, when Jammu & Kashmir captain had chosen to field. Vidarbha’s team management noticed the apparent duplication and brought it to the attention of their captain.

Because the playing XI nomination was affected, the match officials had to address the team-sheet issue before proceeding. Under the BCCI’s men’s multi-day playing conditions, a player named in the nominated XI cannot simply be replaced without the opposing captain’s consent. Clause 1.2.1 states: “No player (member of the playing eleven) may be changed after the nomination without the consent of the opposing captain.”

With the original team submission requiring clarification, the toss was held again. Vidarbha won the second toss and, like Jammu & Kashmir had done earlier, opted to bowl. The repeated decision meant the initial toss result no longer determined which side would field first.

A team-sheet error with match-day consequences

Team sheets are a routine but important part of match administration. They confirm which players are eligible to take part and give officials and the opposing side a clear record of each team’s selection. In a multi-day match, where a playing XI is formally nominated, an error can have consequences beyond a simple correction on paper.

The episode is a reminder that even a small administrative oversight can interrupt the pre-match routine and require officials to consult competition regulations. It also highlights why captains and team staff carefully review submitted line-ups: the rules are designed to protect both sides and ensure that any change is transparent and agreed upon.

Not the First Time Cricket Has Seen a Second Toss

Although unusual, a toss being repeated is not without precedent in Indian cricket. During an IPL Qualifier 2 between Gujarat Titans and Rajasthan Royals, officials reportedly held the toss again after the match referee could not clearly hear the captain’s call amid the noise. A similar incident occurred before the 2011 World Cup final between India and Sri Lanka. Match referee Jeff Crowe did not hear Sri Lanka captain Kumar Sangakkara’s call properly, leading to a second toss.

Those cases involved uncertainty over what had been called or heard. The Jammu & Kashmir-Vidarbha situation was different: the reported trigger was a team-sheet mistake and the regulations governing nominated players. That distinction made the Ranji Trophy incident a particularly unusual example of how match procedures and playing conditions can intersect.

Vidarbha Win a Low-Scoring Contest by Three Wickets

The administrative drama was only one part of a tightly contested match at the Sher-e-Kashmir Cricket Stadium in Srinagar. Vidarbha eventually secured a three-wicket victory in a low-scoring game, with bowlers playing a major role across the innings.

Jammu & Kashmir seamer Sunil Kumar delivered an outstanding performance, taking four wickets in the first innings and adding another four in the second. His eight-wicket match haul kept his side in contention and put sustained pressure on Vidarbha’s batting line-up.

Vidarbha’s Nachiket Bhute was equally influential with the ball. He claimed three wickets in the first innings and five in the second, finishing with eight wickets for the match. His ability to take wickets at key moments helped restrict Jammu & Kashmir and kept Vidarbha within reach of the target.

Samarth’s first-innings century proved decisive

While the bowlers dominated much of the contest, Vidarbha opener Ravikumar Samarth supplied the match’s most substantial batting contribution. He scored 143 from 202 balls in the first innings, providing the stability and runs that shaped the direction of the game. In a low-scoring match, his innings carried added value, giving Vidarbha a foundation when scoring was difficult.

Vidarbha were set a target of 79 for victory. The chase was not entirely straightforward, as Jammu & Kashmir continued to take wickets, but the visitors reached the required total with three wickets remaining. Harsh Dubey stayed unbeaten on 22 from 40 deliveries, helping guide Vidarbha across the line.

Match Prediction and Takeaways

In retrospect, the match prediction hinged less on the toss than on the contributions of Samarth and Vidarbha’s bowlers. Samarth’s 143 gave his team a valuable platform, while Bhute’s eight wickets ensured that Jammu & Kashmir could not build enough of a cushion to defend the final target. Sunil Kumar’s impressive haul made the contest close, but Vidarbha’s lower-order resistance proved decisive.

The second toss may have been the headline-grabbing moment, yet the result was ultimately settled through familiar elements of first-class cricket: patience at the crease, disciplined bowling and composure during a tense chase. For fans following the Ranji Trophy, the incident also offered a practical lesson in the importance of accurate team nominations and the regulations that govern changes after a playing XI has been submitted.