Kapil Dev raised a sensitive issue when he questioned Sachin Tendulkar's match-winning ability after India sneaked a draw in the rain-affected Lord's Test earlier this week. Tendulkar's class and sheer talent have never been in doubt, but increasingly queries are being raised over his ability to turn it on when the team needs him most. Tendulkar's failure in the second innings at Lord's was yet another instance of a low score from him in the fourth innings of a Test, and it has invariably led to more questions and debates.
At the very outset, the point needs to be made that performance in the fourth innings isn't the only measure of a batsman's ability under pressure. (Steve Waugh, for instance, averages a paltry 25.54 in the fourth innings, but there aren't too many who question his ability to be up for a fight.) The first innings of a Test comes with pressures of its own, and is often a critical one: the pitch and the bowlers are fresh, and frequently a strong batting display there sets the tone for the rest of the match. Tendulkar averages 72.49 in the first innings, which is ample proof that he passes that test; when it comes to batting at the end to save or win the match, though, his success-rate is significantly lower.
Tendulkar has so far batted in the last innings of Tests 40 times, yielding a total of 976 runs. (His overall tally of 10,975 runs means he has scored 9999 runs in the first three innings.) In those 40 innings, only four times has he made it past 50, with the last of those instances being more than five years ago, when he made 86 against West Indies at Kingston. His fourth-innings average of 33.65 compares poorly with the top names in the list below.
The table also shows another great batsman of this era in poor light - Brian Lara is the leading run-scorer in the fourth innings, but his average is only marginally better than Tendulkar's. Some of the others, though, have fared much better: Ricky Ponting averages nearly 60, and along with Sunil Gavaskar is the only batsman to have four hundreds batting in the fourth innings.
|Ricky Ponting||32||1132||59.57||4/ 3|
|Geoff Boycott||34||1234||58.76||3/ 7|
|Sunil Gavaskar||33||1398||58.25||4/ 8|
|Gordon Greenidge||38||1383||53.19||3/ 6|
|Matthew Hayden||36||1165||48.54||1/ 8|
|Rahul Dravid||38||1194||47.76||1/ 9|
|Graham Gooch||29||1121||44.84||3/ 5|
|Desmond Haynes||45||1092||43.68||2/ 4|
|Shivnarine Chanderpaul||32||1061||42.44||2/ 6|
|Michael Atherton||39||1375||41.67||2/ 9|
|Justin Langer||33||1053||40.50||2/ 6|
|Brian Lara||46||1440||35.12||2/ 7|
|Alec Stewart||39||1134||34.36||1/ 6|
Gavaskar's average in the fourth innings is immense, but how many of those runs were scored in games which were petering out into draws or had small run-chases? The table below excludes such instances so that the numbers take into account only those Tests in which India had to battle to save or win the match. As the average of 56.60 shows, Gavaskar's stats hardly change when they are placed under the microscope in this manner.
The table below amply demonstrates that Gavaskar had little trouble in summoning his best in the last innings of a match. His unbeaten 117 at Bridgetown helped India bat 103 overs to save the game, the 102 at Port-of-Spain was instrumental in achieving a famous win, and his 221 at The Oval in 1979 is still ranked among the finest innings played at the ground. He finished in style too - his final Test innings, at Bangalore, was one of immense skill in extremely difficult conditions.
|Score||Team total/ overs batted||Opposition & venue||Result|
|117*||221-5/ 103||West Indies, Barbados||Draw|
|53||145-8/ 50||England, Lord's||Draw|
|0||174-6/ 101||England, The Oval||Won|
|58||182/ 85.1||England, Old Trafford||Lost|
|0||118/ 42.5||West Indies, Bangalore||Lost|
|8||202/ 77.1||West Indies, Bombay||Lost|
|102||406-4/ 147||West Indies, Trinidad||Won|
|24||83/ 38.5||England, Madras||Lost|
|113||324/ 84.7||Australia, Brisbane||Lost|
|29||445/ 141.4||Australia, Adelaide||Lost|
|1||125-7/ 46.2||West Indies, Madras||Won|
|221||429-8/ 150.5||England, The Oval||Draw|
|25||200-4/ 63.2||Australia, Calcutta||Draw|
|21||364-6/ 131||Pakistan, Delhi||Draw|
|5||135-8/ 75||Australia, Adelaide||Draw|
|12||190/ 75.3||New Zealand, Wellington||Lost|
|83*||170-3/ 83||England, Calcutta||Draw|
|1||103/ 47.1||West Indies, Ahmedabad||Lost|
|19||198/ 66.2||Sri Lanka, Colombo||Lost|
|54||174-5/ 78||England, Edgbaston||Draw|
|90||347/ 86.5||Australia, Madras||Tie|
|96||204/ 93.5||Pakistan, Bangalore||Lost|
|Total runs 1132||Average 56.60|
Tendulkar's numbers pale in comparison. Discounting the soft runs - two examples are unbeaten knocks of 44 and 32 when India were chasing small targets at home - Tendulkar's average drops even further, to just 26.85.
The start of the list is similar for both players - Gavaskar's unbeaten 117 is matched by Tendulkar's 119 not out as a precocious 17-year-old at Old Trafford in 1990. Since then, though, it has been largely a string of disappointments for Tendulkar, with several single-digit scores - in fact, of the 27 scores listed below, there are 13 of ten or less, and five more below 20. His 136 against Pakistan at Chennai in 1999 was an epic, despite the fact that India lost, but since then the cupboard's been almost entirely bare, with just two half-centuries.
The other aspect which stands out is when you compare Gavaskar's India and Tendulkar's India with regard to the number of overs batted in the fourth innings. With Gavaskar around, India consistently batted more than 100 overs - there are six such instances, with four of them exceeding the 130-over mark. During Tendulkar's time, though, the team has tumbled to some embarrassing collapses, ten times being bowled out in less than 60 overs, including four instances when they couldn't even last 40.
In many ways, then, Tendulkar's struggle in the fourth innings is reflective of the manner in which the entire team has floundered when batting to save or win a Test.
|Score||Team total/ overs||Opposition & venue||Result|
|27||224/ 62||England, Lord's||Lost|
|119*||343-6/ 90||England, Old Trafford||Draw|
|17||333/ 100.1||Australia, Adelaide||Lost|
|5||141/ 55.1||Australia, Perth||Lost|
|1||141-4/ 82||South Africa, Johannesburg||Draw|
|10||114/ 35.2||West Indies, Mohali||Lost|
|2||137/ 53.3||South Africa, Calcutta||Lost|
|4||66/ 34.1||South Africa, Durban||Lost|
|9||144/ 66.2||Cape Town||Lost|
|4||81/ 35.5||West Indies, Barbados||Lost|
|8||281-5/ 100||Sri Lanka, Colombo||Draw|
|7||173/ 56.4||Zimbabwe, Harare||Lost|
|136||258/ 95.2||Pakistan, Chennai||Lost|
|9||232/ 79.1||Pakistan, Calcutta||Lost|
|0||110/ 38.1||Australia, Adelaide||Lost|
|52||195/ 89.3||Australia, Melbourne||Lost|
|17||155-8/ 41.1||Australia, Chennai||Won|
|42||126-6/ 45.5||Zimbabwe, Delhi||Won|
|86||252/ 88.3||West Indies, Jamaica||Lost|
|12||397/ 109.4||England, Lord's||Lost|
|37||233-6/ 72.4||Australia, Adelaide||Won|
|2||200/ 53.3||Australia, Nagpur||Lost|
|16||214/ 90||Pakistan, Bangalore||Lost|
|26||265/ 58.4||Pakistan, Karachi||Lost|
|34||100/ 48.2||England, Mumbai||Lost|
|0||179/ 55.1||South Africa, Durban||Lost|
|16||282-9/ 96||England, Lord's||Drawn|
|Total runs 698||Average 26.85|
S Rajesh is stats editor of Cricinfo.