He has been part of seven of India’s last ten run-outs in Tests, the latest one coming as India’s top order did battle under grey skies at Lord’s
ESPNcricinfo staff17-Jan-2018England v India, Lord’s, 2018
Cheteshwar Pujara run out 1
After a washed out first day, India got off to a shaky start on day two of the second Test at Lord’s, losing both their openers to James Anderson under grey London skies. Pujara was never at his fluent best over his 25-ball stay, battling for survival against England’s quicks on a stop-start day. Just before another spell of rain would pause proceedings, Pujara tapped one to point and started running. Kohli initially responded, but, with both men halfway down the length of the pitch, turned back, leaving Pujara stranded. Another Test match, another addition to Pujara’s run-out tally.South Africa v India, Centurion, January 2018
Cheteshwar Pujara run out for 19
Pujara became the first batsman to be run out twice in a Test since December 2000. In a tough chase of 287, he had managed to survive 47 balls and, with three top-order wickets already lost, was crucial to India having any chance of reaching the target. His partner, Parthiv Patel, played the ball to third man, where Lungi Ngidi made a good sliding stop and parried the ball to AB de Villiers. Pujara, inexplicably given the match situation, went for a third run, and despite a dive was found short.ESPNcricinfo LtdSouth Africa v India, Centurion, January 2018
Cheteshwar Pujara run out for 0
Pujara denied himself the chance of batting on a dry pitch that may have suited his game by getting run-out first ball. He defended the ball firmly to mid-on and, perhaps in an attempt to show the “intent” his captain had encouraged from his players, set off for a single that was not there. Ngidi, on debut, picked up the ball and hit the stumps direct, leaving Pujara well out of his crease.Sri Lanka v India, Colombo, August 2017
KL Rahul run out for 57
On the first day of the second Test of India’s 2017 tour of Sri Lanka, India were in a commanding positon at 109 for 1. KL Rahul pushed a Rangana Herath delivery to extra cover and set off for a run. Pujara, at the other end, set off too, but then changed his mind and sent Rahul back, in effect leaving his partner stranded. Rahul could be heard shouting “my call” as he walked back, miffed. Pujara made up for the mix-up by scoring a century.India v Australia, Dharamsala, March 2017
Pujara run out for 0
Pujara ended a prolific series with a duck, and it was poor running that did him in again. With India chasing 106 to win the Test and the Border-Gavaskar Trophy, he played the fifth ball he faced to point and set off for a quick single. But mid-way, he stuttered, giving Glenn Maxwell just enough time to nail the stumps at the non-strikers’ end. India were left 46 for 2 and under a bit of pressure, but they won by eight wickets in the end.India v New Zealand, Indore, October 2016
M Vijay run out for 19
This time it was M Vijay who was sent back by Pujara after he had set off for a quick single. Vijay had got a leading edge into the cover region and hared out of his crease. He did not seem to see Pujara sending him back and when he eventually did, a sharp pick up and throw from Martin Guptill had dismissed him. India were in a dominant position, though, after getting a 258-run first-innings lead, and Pujara scored a second-innings century to set up a win.West Indies v India at Kingston, July 2016
Pujara run out for 46
After toiling for 159 balls, Pujara missed out on a half-century because of a misjudged single. He tapped a delivery from Jason Holder to square leg and went for the run, but, despite a dive, was found short by Roston Chase’s direct hit at the non-striker’s end. India went on to score 500 in their first innings at a run-rate of less than three an over. After rain washed out the fourth day, the match was drawn. Pujara was dropped for the next Test, with India opting for Rohit Sharma in his place.
