At Chennai, he walked in at six for two. At Cape Town, India were soon 58 for five. At Perth, eight wickets had fallen with only 159 on the board. At Sharjah, a place in the final depended on how far he could carry the chase.
Sachin Tendulkar answered with 136, 169, 114 and 143.
Yet somehow, “he didn’t perform under pressure” became a refrain.
It is a curious way to remember a batsman: begin with the occasions he failed, discount the crises he survived, and make him answer for wickets that fell after he was gone. To examine that accusation properly, return to the moment he took guard—the scoreboard, the bowling attack and what India needed from him.
Sharjah in April 1998 offers an obvious starting point. Against Australia, Tendulkar scored 143 off 131 balls, carrying India into the triangular tournament’s final despite losing the match. Two days later, he delivered 134 off 131 as India chased 273 to lift the trophy. Qualification pressure followed by a final, answered with consecutive centuries. His strike rate in the first innings was 109.16, correcting the 143 mistakenly given in the original statistical post. The achievement needs no embellishment.
Ten years later, he provided another answer in Australia. In the first Commonwealth Bank Series final at Sydney, Tendulkar made 117 not out off 120 balls, guiding India to a six-wicket victory. He stayed until the chase was complete, converting his hundred into the result India required.
The twelve ODI innings in the supplied selection total 914 runs, including three centuries. They are selected examples, rather than a comprehensive measure of pressure performance. Their significance lies in the circumstances they represent: tournament qualification, finals and demanding opposition.
Test cricket broadens the argument. Pressure can mean chasing victory, repairing a collapse or spending hours keeping defeat away.
At Old Trafford in 1990, India faced a target of 408. Tendulkar arrived at 109 for four, and the innings subsequently deteriorated to 183 for six. Alongside Manoj Prabhakar, he added an unbeaten 160 for the seventh wicket, finishing on 119 not out as India saved the Test. He was seventeen. Before his career had properly unfolded, he had already demonstrated the concentration required to protect a match on its final day.
At Perth in 1992, the challenge was more physical. Against McDermott, Hughes, Whitney and Reiffel, India slipped to 159 for eight in reply to Australia’s 346. Tendulkar scored 114 off 161 balls in a total of 272. The other ten Indian batters contributed 135 between them. While the innings crumbled, he scored at a strike rate of 70.81.
Johannesburg later that year produced another revealing comparison. Tendulkar made 111 of India’s 227; his ten teammates managed 107, with nobody else passing 25. His hundred helped limit the first-innings deficit in a Test India eventually drew.
At Edgbaston in 1996, India began their second innings 99 behind. Tendulkar entered at 17 for two, and the score soon became 36 for four. He responded with 122 off 177 balls. India’s total was 219; the other ten batters contributed 83, and the next-highest individual score was 18. Defeat followed, but the scorecard preserves an exceptional individual response to a desperate situation.
Cape Town in 1997 brought an even larger burden. South Africa declared at 529 for seven, before reducing India to 58 for five. Tendulkar made 169, sharing a 222-run partnership with Mohammad Azharuddin against an attack including Donald, Pollock and Klusener. At Bloemfontein in 2001, he counterattacked from another crisis: India were 68 for four before his partnership with debutant Virender Sehwag yielded 220. Tendulkar’s contribution was 155 off 184 balls.
Then comes Chennai in 1999, where the ending has too often swallowed the innings. Chasing 271 against Pakistan, India were six for two, then 82 for five. Tendulkar scored 136 against Wasim Akram, Waqar Younis and Saqlain Mushtaq. The other ten batters contributed 86. When he fell, India needed 17 with three wickets remaining. They added four. His dismissal was consequential; so was the extraordinary work that had brought victory within reach.
Chennai in 2008 supplied the finish that had escaped him nine years earlier. Set 387 by England, India received an attacking start from Sehwag before Tendulkar and Yuvraj Singh completed the pursuit. Their unbeaten 163-run partnership secured a six-wicket victory. Tendulkar finished on 103 not out, reaching his century with the winning boundary.
The late-career evidence is equally substantial. At Bengaluru in 2010, Australia had scored 478 when India slipped to 38 for two. Tendulkar answered with 214, helping secure a first-innings lead. At Cape Town in 2011, with the series tied 1–1, he made 146 against Steyn and Morkel after India had fallen to 28 for two. India edged ahead by two runs, and the deciding Test ended drawn.
The twelve Test innings previously selected total 1,660 runs. Combined with the supplied ODI selection, they amount to 2,574 runs across 24 illustrative innings. That collection cannot establish his success rate across every pressure situation. It can decisively challenge an absolute claim.
Tendulkar failed in important matches. Those failures belong in any honest assessment, alongside the finals he shaped, the collapses he resisted and the chases he completed.
Debate how often Sachin succeeded under pressure. The scorecards have already answered whether he could.
Thank You
Faisal Caesar
No comments:
Post a Comment