IND vs AUS | Ravindra Jadeja ruled out of Border-Gavaskar Test series

no image

Ahead of the fourth Test at the iconic Gabba, the BCCI have revealed that their star all-rounder Ravindra Jadeja has been ruled out of the rest of the series. The statement also added that the all-rounder would consult a hand specialist before returning to the NCA in Bengaluru.

Following the historic draw in Sydney, saving the game from jaws of defeat, The BCCI have on Monday, stated that all-rounder Ravindra Jadeja has been ruled out of the ongoing Border-Gavaskar Trophy with a blow to thumb dislocation. Ahead of the fourth Test at the Gabba, the BCCI stated that the all-rounder will consult a hand specialist before heading to NCA for further recovery.

"Ravindra Jadeja suffered a blow to his left thumb while batting on Day 3 of the third Border-Gavaskar Test that concluded on Monday. He later went for scans and the results have shown that he has dislocated his thumb," stated BCCI's press release.

"The all-rounder will now consult a hand specialist in Sydney before he returns to India. He will then head to the National Cricket Academy in Bengaluru for further management of his injury," it added.

"Jadeja will not be available for the fourth and final Test against Australia to be held in Brisbane from January 15-19 at the Gabba," it concluded. 

Comments

Leave a comment

0 Comments

read previousVaibhav Suryavanshi Continues His Unreal Masterclass in the U19 Asia Cup
Vaibhav Suryavanshi showed his masterclass once again for the Indian team. He played a magnificent knock for India in the Under-19 Asia Cup, smashing 171 runs against UAE Under-19. This also comes in as yet another ton scored by the youngster in 2025.
Reports | BCCI source reveals details of racist abuse on Siraj during the Sydney Testread next
Following the conclusion of the Sydney Test, the BCCI sources, as per TOI’s reports, have stated that the crowd used ‘brown dog’ and ‘big monkey’ as the two racist slurs to Mohammed Siraj. The sources also added that the players immediately reported after they were affected by the incident.
View non-AMP page