What's new

Which, in your opinion, were the worst wickets in Test history?

Harsh Thakor

First Class Star
Joined
Oct 1, 2012
Runs
3,520
Post of the Week
2
Most difficult wickets to bat on in order of merit ion my lifetime.

1.Ahmedabad in 1983-84 West Indies-India test


2=Bangalore in 1987 Indo-Pak test. and 2017 Indo-Australia test


4.Mumbai in 1981-82 with England touring and 2004-05 with Australia touring.

5=Headingley and Trent Bridge in 1981 Ashes test series.

7=Melbourne in 1980-81 test and in 1981-82 test of Australia-West Indies



9.Headingley in 1991 with England and West Indies

10 Feroze shah Kotla ground in 1996 with Australia touring and 2015 with South Africa touring.


11.Barbados in 1992 between South Africa and West Indies and in 1999 between Australia and West Indies.

12.Oval in 1997 between England and Australia


13=Trinidad in 1995 between Australia and West Indies-both tests


15.Newlands Capetown in 2017 between India and South Africa







The Ahmedabad pitch in 1983-84 was unplayable with several cracks leading to the uneven bounce.As the game progressed one was reminded of a body being cremated.The ball either skidded or shot up disconcertingly from a length.History repeated itself with the pitch again a literal graveyard in Bangalore where Pakistan was victorious.


At Leeds the ball literally swerved or wobbled in the air on the 1st day and in 1981 hardly being a true test pitch with odd ball rising up disconcertingly from a good length.Similar at Trent Bridge in a very low scoring game of the 1st test oif the 1981 Ashes.

In Trinidad the wicket slowed down as the game progressed and on the 4th and 5th days had unpredictable bounce.This was reflected when both Australia and South Africa collapsed in their 2nd innings from apparent winning positions.


At Melbourne would behave in haphazard manner and become almost unplayable on the last day.It is worth recalling the batting collapses of Australia and West Indies out there in 1980-81 and 1981-82.


Mumbai pitch assisted seamers and spinners and would become unplayable by the 4th or fifth day.
 
The one in WI in 1993 I think where the match was called off after ten overs.
 
[MENTION=132062]Harsh Thakor[/MENTION], Headingley used to be a problem because in addition to the often lavish swing due to the usual overcast conditions, the wicket had uneven bounce. One stayed low and the next on the same length steeplejacked.

Lord’s used to be awkward because of the ridge on a fast bowler’s length, but groundsman Mick Hunt levelled it.
 
Most difficult wickets to bat on in order of merit ion my lifetime.

1.Ahmedabad in 1983-84 West Indies-India test


2=Bangalore in 1987 Indo-Pak test. and 2017 Indo-Australia test


4.Mumbai in 1981-82 with England touring and 2004-05 with Australia touring.

5=Headingley and Trent Bridge in 1981 Ashes test series.

7=Melbourne in 1980-81 test and in 1981-82 test of Australia-West Indies



9.Headingley in 1991 with England and West Indies

10 Feroze shah Kotla ground in 1996 with Australia touring and 2015 with South Africa touring.


11.Barbados in 1992 between South Africa and West Indies and in 1999 between Australia and West Indies.

12.Oval in 1997 between England and Australia


13=Trinidad in 1995 between Australia and West Indies-both tests


15.Newlands Capetown in 2017 between India and South Africa







The Ahmedabad pitch in 1983-84 was unplayable with several cracks leading to the uneven bounce.As the game progressed one was reminded of a body being cremated.The ball either skidded or shot up disconcertingly from a length.History repeated itself with the pitch again a literal graveyard in Bangalore where Pakistan was victorious.


At Leeds the ball literally swerved or wobbled in the air on the 1st day and in 1981 hardly being a true test pitch with odd ball rising up disconcertingly from a good length.Similar at Trent Bridge in a very low scoring game of the 1st test oif the 1981 Ashes.

In Trinidad the wicket slowed down as the game progressed and on the 4th and 5th days had unpredictable bounce.This was reflected when both Australia and South Africa collapsed in their 2nd innings from apparent winning positions.


At Melbourne would behave in haphazard manner and become almost unplayable on the last day.It is worth recalling the batting collapses of Australia and West Indies out there in 1980-81 and 1981-82.


Mumbai pitch assisted seamers and spinners and would become unplayable by the 4th or fifth day.


Needs lot more home work for this one man. Where is Kingston of 1976?
 
The one in Nagpur 2015 between India and SA was as terrible as it gets. It started turning square right from bowl one. I mean 40 wickets went and not a single batsmen managed to cross the digit of 40 over a course of four innings.

And it is funny, OP picking Newland for 2018 tour of SA when it was JohannesBurg that was worst of all the test venues.
 
There was this series Ind vs Aus in India. i guess 2004
India were 2-0 down in a 3 match series and they made a dust bowl. IIRC only Laxman and Tendulkar scored half centuries and M Clarke took 6 wickets for 9 runs. In the end Australia couldn't chase 110 odd in 4th innings and were bowled out for 93
 
Like my list?Kingston was a very quick pitch,but not the amongts the work.Am I mistaken?

It was under prepared but extremely fast, which made the bounce uneven. In terms of playing quality (excluding physical injury threats), I think there are so many that you hardly can rank - in recent times Pune wicket was shocker, while the CTG wicket of last Test wasn't great either. Then the Mumbai wicket of 2004 (?), when AUS failed to chase 108 ...

In general, Kingston wicket is considered to be worst, because there had been several injuries and probably couple of Tests were abandoned there.
 
Back
Top