Eerie similarities between Tests at Cape Town and Melbourne featuring India
Eerie similarities between Tests at Cape Town and Melbourne featuring India
The Bharat Army — India’s answer to England’s Barmy Army — have shared an interesting similarities about India’s ongoing Melbourne Test against Australia and India’s 1997 Test against South Africa at Cape Town. In 1997 at Cape Town, hosts South Africa batted first and scored 529 in their first innings. In 2014 at Melbourne,...
Written by Cricket Country Staff Published: Dec 29, 2014, 10:42 AM (IST) Edited: Dec 29, 2014, 10:42 AM (IST)
The Bharat Army â Indiaâs answer to Englandâs Barmy Army â have shared an interesting similarities about Indiaâs ongoing Melbourne Test against Australia and Indiaâs 1997 Test against South Africa at Cape Town.
Add Cricket Country as a Preferred Source
In 1997 at Cape Town, hosts South Africa batted first and scored 529 in their first innings.
In 2014 at Melbourne, hosts Australia batted first and scored 530 in their first innings.
In 1997 at Cape Town, Indiaâs # 4 batsman, Sachin Tendulkar, scored 169 in the first innings.
In 2014 at Melbourne, Indiaâs #4 batsman, Virat Kohli, scored 169 in the first innings.
In 1997 at Cape Town, when Sachin Tendulkar, Indiaâs best batsman, scored his hundred, he had only three hundreds at home.
In 2014 at Melbourne, when Virat Kohli, Indiaâs best batsman, scored his hundred, he had only three hundreds at home.
In 1997 at Cape Town, a player from Karnataka [Dodda Ganesh] made his Test debut.
In 2014 at Melbourne, a player from Karnataka [Lokesh Rahul] made his Test debut.
In 1997 at Cape Town, Nayan Mongia, the Indian wicketkeeper, took four catches in the South African first innings.
In 2014 at Melbourne, Mahendra Singh Dhoni, the Indian wicketkeeper, took four catches in the Australian first innings.
This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.
Strictly Necessary Cookies
Strictly Necessary Cookie should be enabled at all times so that we can save your preferences for cookie settings.
If you disable this cookie, we will not be able to save your preferences. This means that every time you visit this website you will need to enable or disable cookies again.