Best printers for Home

Best Mixer Grinder

Best wired Earphones

Best 43 Inch TV in India

Best Wi Fi Routers

Best Home Theatre in India

Smart Watch under 5000

Best Laptops for Education

Best Laptop for Students

It is the first time in over two decades that India will tour England without <keyword id="118008" type="PERSON" weightage="40" keywordseo="Sachin-Ramesh-Tendulkar">Sachin Ramesh Tendulkar</keyword>. The last time India were in England for a four-Test series in 2011, they were beaten 0-4 despite <keyword id="2727" type="PERSON" weightage="40" keywordseo="Rahul-Dravid">Rahul Dravid</keyword> scoring three Test centuries. 
 That series, billed around Tendulkar's impending 100th century in international cricket, saw India's pace spearhead <keyword id="12644" type="PERSON" weightage="40" keywordseo="Zaheer-Khan">Zaheer Khan</keyword> pull out with a hamstring injury on the opening day of the first Test at Lord’s. It triggered India's most colossal drubbing since 1959. India returned empty handed as they lost their No. 1 Test rank to England. Andrew Strauss was at the helm of affairs for England then. 
 
A lot of water has flown under the bridge. As India prepare for the first Test starting July 9, England skipper Alastair Cook is under immense scrutiny after his side's 0-1 loss to Sri Lanka. What has made things worse is his own form. He has managed just 601 runs in the last 24 innings, averaging just 25 runs an innings. 
 England have picked a pace-oriented attack for the first Test and may influence the Indian think tank to respond in kind, picking <keyword id="6359948" type="PERSON" weightage="40" keywordseo="Ravindra-Jadeja">Ravindra Jadeja</keyword> as the only spin bowling option at Trent Bridge. India's pace attack will be chosen among Ishant Sharma, Mohammed Shami, Bhuvneshwar Kumar, Varun Aaron, Pankaj Singh and Ishwar Pandey. 
 
 
Yet, it is this attack that is India's biggest concern at the moment. Pankaj Singh and Ishwar Pandey are yet to make their debuts while Shami, Bhuvneshwar and Aaron have never played a Test in England leaving Ishant (55 Tests) to spearhead the Indian attack in the grueling series. 
 
If coach Duncan Fletcher is to be believed, this inexperience brings the unpredictability and excitement. "It is nice sometimes, because being unpredictable they will play some exciting cricket. There are some very exciting cricketers in the squad who would go on to become very good cricketers for India," Fletcher said ahead of the series. 
 
Ishant has shown his mettle in the past – two six-wicket hauls in New Zealand will have boosted his confidence amply. Bhuvneshwar has impressed everyone with his swing and ability to hit the right length. Shami has had a fairly good run in Test cricket and will relish bowling in England. Varun Aaron is the fastest of the Indian pacers and can bring a cutting edge to the attack. 
 
Pandey, from Rewa in Madhya Pradesh, is a promising fast-medium bowler and can carry the burden of the Indian attack. He has been rewarded for claiming 78 wickets in Ranji Trophy over the last two seasons. Similarly, Pankaj Singh has been picked since he had a very good first class season behind him. 
 
Former India captain and former Chairman of selectors, Dilip Vengsarkar highlighted his concern about this attack before the series. "It will be tough for India. We need to have bowlers who can get them out twice but unfortunately I don't see any bowler," Vengsarkar said. The bowlers on tour will have to prove that they were chosen on merit and the belief that they can raise their game.

India Face Pace Conundrum In English Test

It is a good wager that paceman Varun Aaron and off-spinner <a href="http://www.gocricket.com/player/ravichandran-ashwin/4001/26007">R Ashwin</a> will have had to deal with conflicting thoughts of having been left out of the Indian XI for the third Investec Test against England at the Ageas Bowl in Southampton. They would have been both disappointed and at once relieved that they did not have to overcome the challenge of having to bowl on a flat deck. 
 
In <a href="http://www.gocricket.com/player/ishant-sharma/4001/4094">Ishant Sharma</a>'s absence with an ankle injury, <a href="http://www.gocricket.com/player/ms-dhoni/4001/4057">Mahendra Singh Dhoni</a> should have gone in with someone who could intimidate England and that would have been Varun Aaron. His fellow-Jharkhand player has the pace to take the pitch out of the equation. The Indian captain could have used him in short spells on a track that offered the seamers little assistance. 
 
Ashwin's guile - way ahead of <a href="http://www.gocricket.com/player/ravindra-jadeja/4001/32004">Ravindra </a><a href="http://www.gocricket.com/player/ravindra-jadeja/4001/32004">Jadeja</a>'s - could have tested England's left-handers <a href="http://www.gocricket.com/player/alastair-cook/3001/3056">Alastair Cook</a> and <a href="http://www.gocricket.com/player/gary-ballance/3001/73003">Gary Ballance</a> who shared a 158-run stand for the second wicket. But Dhoni's mind seems made up against including the off-spinner in his plans. Did India pay for that? Only time will answer that question over the next few days. 
 
To be fair, there is no denying that the strapping <a href="http://www.gocricket.com/player/pankaj-singh/4001/4100">Pankaj Singh</a> did a good fist of bowling within his limitations but India needed someone who could be among the wickets on a track like this. In <keyword id="11685" type="PERSON" weightage="40" keywordseo="Ishant-Sharma">Ishant Sharma</keyword>'s absence, it had to be Aaron. He has the pace to consistently overcome a flat deck and harry the batsmen into making mistakes. 
 
It was tragic that India's reluctance to position the slip fielders better came in the way of Pankaj claiming his maiden Test wicket in his opening spell. It can only be hoped that India will learnt from the mistakes and return on Monday with a more aggressive intent. That will quash any aspirations that Cook and his men have of pulling one back and levelling the series. 
 It was even more tragic that Pankaj's appeal for leg before against Ian Bell in the final session was turned down by Australian umpire Rod Tucker. Well as Pankaj bowled, the fact is that India did not pick enough bowlers who would take 20 wickets in this Test. It is clear that India have preferred to wait until they get to <keyword id="2023" type="PERSON" weightage="40" keywordseo="Old-Trafford">Old Trafford</keyword> to make a push to notch up another win. 
 
In picking <a href="http://www.gocricket.com/player/rohit-sharma/4001/4095">Rohit Sharma</a> ahead of off-spinner Ashwin and <keyword id="258548" type="PERSON" weightage="40" keywordseo="Stuart-Binny">Stuart Binny</keyword>, Dhoni has sought to bolster the batting in a bid to ensure that the 1-0 lead can be protected. It is clearly a defensive tactic, aimed at improving India's specialist batsmen's chances of keeping the England bowlers at bay for long enough to be able to protect the 1-0 lead. 
 
With each passing over, it was becoming clear that the Indian batsmen will have to come up with a strong response to ensure that the threat of the follow-on is averted and that the challenge of having to bat last on a track that does not appear to be the sort that will deteriorate much. The ball, as the cliche goes, is in the Indian batsmen's court. 
 
After the first day when England made 247 for two, India can only hope that their batsmen will deal with pressure when it is piled on them in the coming days. There can be no doubting that Dhoni could have given his limited attack better fields to challenge England, even on the flat pitch that held little by way of encouragement for the bowlers.

Did Dhoni Miss Aaron Or Ashwin On Day 1 In Southampton?

You can help me make a decision since I am caught between two emotions. Should I laugh or cry? 
 Before you ask me why, let me tell you that a couple of questions have been dominating the mind from the time the <keyword id="81008" type="ORGANIZATION" weightage="20" keywordseo="Board-of-Control-for-Cricket-in-India">Board of Control for Cricket in India</keyword> (<keyword id="6354756" type="CITY" weightage="20" keywordseo="BCCI">BCCI</keyword>) made changes to the <a href="http://www.gocricket.com/teams/india/4001/home">Indian team's </a>coaching staff and sparked the laugh-or-cry debate in my mind. 
 
In the first place, <a href="http://www.gocricket.com/news/England-vs-India-2014-Ravi-Shastri-to-be-in-charge-of-Indian-team-for-England-ODIs/articleshow/40390445.cms">installing </a>former India allrounder <keyword id="19692" type="PERSON" weightage="20" keywordseo="Ravi-Shastri">Ravi Shastri</keyword> as Director of the Indian team and sidelining the bowling and fielding coaches, Joe Dawes and Trevor Penny respectively, ahead of the limited-over series against England is an attempt to pull wool over our eyes rather than balm to hearts and souls wounded by dismal showing in three successive Tests. 
 
It is no secret that the Indian limited-overs team is more competitive than the Test team has been for a while now, especially in overseas series. Surely, no one needs reminding that <a href="http://www.gocricket.com/player/ms-dhoni/4001/4057">Mahendra Singh Dhoni's</a> team has won six and lost 14 of 28 overseas Tests. Even more surely, it is the Test side that is in greater need of guidance than the squad that plays white-ball cricket. 
 Since batsmen M Vijay, <keyword id="13839" type="PERSON" weightage="20" keywordseo="Gautam-Gambhir">Gautam Gambhir</keyword> and <keyword id="75027" type="PERSON" weightage="20" keywordseo="Cheteshwar-Pujara">Cheteshwar Pujara</keyword>, pace bowlers <keyword id="11685" type="PERSON" weightage="20" keywordseo="Ishant-Sharma">Ishant Sharma</keyword>, Pankaj Singh and <keyword id="6370607" type="PERSON" weightage="20" keywordseo="Varun-Aaron">Varun Aaron</keyword> as well as reserve wicketkeepers Wriddhiman Saha and Naman Ojha have returned home ahead of the ODIs, and a fresh crew has flown in, it will be unfair to compare the work of the coaches who have been given a break with that of the new staff. 
 
Besides this <a href="http://www.gocricket.com/news/India-vs-England-ODI-series-My-job-is-to-find-out-what-went-wrong-and-file-a-report-says-Ravi-Shastri/articleshow/40492231.cms">clumsy attempt</a> to pull wool over the eyes of fans of Test cricket, the appointment of <keyword id="945851" type="ORGANIZATION" weightage="20" keywordseo="Indian-Premier-League-Governing-Council">Indian Premier League Governing Council</keyword> member Shastri as Director of the Indian team and let him pick coaching staff for the ODI team in England comes across as a classic case of not looking beyond the BCCI's favourite child, <keyword id="6354312" type="CITY" weightage="20" keywordseo="IPL">IPL</keyword> and an erstwhile favourite, the National Cricket Academy (NCA). Assistant coach Sanjay Bangar and fielding coach R Sridhar both earned their place in the spotlight thanks to the run of <keyword id="13883" type="COMPANY" weightage="20" keywordseo="Kings-XI-Punjab">Kings XI Punjab</keyword> in IPL 2014 while B Arun, ostensibly the bowling coach now, has been with the NCA for many years now. Of course, Sridhar has also been in the NCA and, like Arun, worked with junior India teams. 
 
If critics of the IPL have blamed the inadequate technique of the Indian batsmen against the swinging and seaming cricket ball on IPL, its proponents have cited improved fielding - not slip catching, for sure - standards as a result of the IPL. It does look like everyone, critic and defendant alike, have come to regard the IPL as the be all and end all of Indian cricket. 
 
Shastri's interview with ESPNcricinfo's Nagraj Gollapudi – "I had no reservations about the job. I insisted on the coaching staff I wanted. I went (for domestic Indian coaches) because I felt they can contribute," he said – is a confirmation that the BCCI and its contracted commentators do not pay attention to first-class cricket in the country. 
 Karnataka coach J <keyword id="26593" type="PERSON" weightage="20" keywordseo="Arun-Kumar">Arun Kumar</keyword> would surely have done something right for the team to win not only the Ranji Trophy after 15 years but also the Irani Cup and Vijay Hazare Trophy titles in 2013-14, a rare hat-trick of titles in a season. Does his missing out on being with an IPL team have anything to do with his not landing an assignment with any Indian team? 
 
The IPL can run on its own steam and does not need any molly-coddling from the BCCI, except to ensure that it is run in a transparent manner and stays clean. These attempts to prop up the IPL as only a harbinger of good cricket because it lets domestic players rub shoulders with international stars are little more than dramatic. 
 
Perhaps the real solution lies in ensuring that the Test players do not show up in domestic cricket only sporadically. As a Ranji Trophy star pointed out, those who are making so much noise about the quality of pitches in domestic cricket have not been looking at the tracks in Ranji Trophy where seam and swing bowlers pose severe challenges to batsmen. Is there no cricket beyond the IPL? Are there no coaches beyond NCA?

BCCI Forgets That There Is More To Indian Cricket Than Just IPL

In cricketing parlance it's often said that teams should not change winning combinations because more often than not it breaks the momentum. Come to think of it, India's travails began in England only when they made changes to the winning eleven of the second game at Lord's. 
 
After the high of the Lord's win, their first at the hallowed ground in 28 years, <a href="http://www.gocricket.com/player/ms-dhoni/4001/4057">MS Dhoni</a> and the team management left out <a href="http://www.gocricket.com/player/stuart-binny/4001/31034">Stuart Binny</a>, whose 78 in the second innings of the first Test at Trent Bridge blew away the clouds of defeat hovering over the team. <a href="http://www.gocricket.com/player/ishant-sharma/4001/4094">Ishant Sharma</a>, the hero at Lord's for his career-best 7 for 74 in the second innings, also had to miss out the Southampton Test on account of an ankle injury. While leaving Binny out was the team's decision, Ishant's unavailability couldn't be helped. 
 
In hindsight, those two changes changed India's series. The men who replaced Binny and Ishant were batsman <a href="http://www.gocricket.com/player/rohit-sharma/4001/4095">Rohit Sharma</a> and medium pacer <a href="http://www.gocricket.com/player/pankaj-singh/4001/4100">Pankaj Singh</a> and both had an outing to forget. Rohit made 28 and 6, while Pankaj returned 0 for 146 and 0 for 33 as India lost the match by 266 runs. 
 At Old Trafford, India this time made three changes, bringing in <keyword id="13839" type="PERSON" weightage="20" keywordseo="Gautam-Gambhir">Gautam Gambhir</keyword>, R Ashwin and <keyword id="6370607" type="PERSON" weightage="20" keywordseo="Varun-Aaron">Varun Aaron</keyword> in places of <keyword id="17805" type="PERSON" weightage="20" keywordseo="Shikhar-Dhawan">Shikhar Dhawan</keyword>, Rohit and Mohammed Shami. Things went from bad to worse and they were thumped by an innings and 54 runs inside three days. Clearly, those five changes didn't prove to be propitious for <keyword id="6397" type="PERSON" weightage="20" keywordseo="Dhoni">Dhoni</keyword>. 
 
Having that in mind, now the question arises whether India should make changes once again for the fifth and final encounter at The Oval starting Friday. Gambhir had a horrible outing at Old Trafford; offspinner Ashwin, even though he did well with the bat, failed to take any wicket. However, Aaron impressed a lot, showing plenty of pace and his wicket of Moeen Ali with a vicious inswinger will stay as one of the moments of the series. 
 
The suspects this time are Gambhir, Ashwin and Pankaj, who despite breaking his wickets drought at Old Tafford, failed to inspire any confidence. Medium-pacer Ishwar Pandey and wicketkeeper-batsman Naman Ojha, who piled on the runs for India A against Australia A recently with scores of 219, 101 and 110 in two matches and was drafted into the squad as a replacement for the injured Wriddhiman Saha, are the only players in the squad not to have got a game yet. Should India hand them Test debuts at The Oval or, having learnt from their experiences in the series, they stick to the team that played at Old Trafford are questions that must be bothering Dhoni a great deal. 
 
By the look of things at present, sadly, India aren't likely to be going into the match unchanged. The cases of Pankaj and Gambhir need to be looked at with a magnifying glass. They looked very poor in the Old Trafford defeat. But then some would argue what's the guarantee that their replacements would revive the team. That the damage has already been done with the tourists trailing 2-1 in the series and bringing back Dhawan, Rohit, Shami or Binny is unlikely to do any good to the team. 
 
But in view of the proverbial fact that losing squads are kept getting tinkered with, a couple of changes look to be on the cards. There is no update on Ishant's fitness but he gets fit in time, Pankaj will have to go. Even if Ishant is not fit, Pandey should be considered on the basis of his accuracy and better swinging skills. Dhawan should be brought back in place of Gambhir for one simple reason that Gambhir looks to be way past his prime, and if the team management has to pick between two uncertainties, it should go for the younger and futuristic option that is Dhawan, who not long ago looked in good touch in New Zealand. The third suspect, Ashwin, should be retained considering he can contribute with the bat and looking at the team's current batting crisis playing him won't be a bad idea. 
 
The Oval Test seems to Dhoni's last chance at redemption and he can't afford to fail this time. Another loss or probably even a draw will certainly be the end of his captaincy. The selectors can't keep turning a blind eye to the fact that he has lost 12 Tests against one win outside the subcontinent in the last three years. Hopefully, Dhoni manages to assemble an eleven that brings an end to India's predicament.

To Change Or Not To Change, That's The Question For Dhoni

It's just getting worse and worse for India. After the ignominy of Southampton, they have yet again succumbed to a crushing defeat against England at Manchester. They now trail England 1-2 in the five-match series. Gocricket.com takes a look at how each member of the Indian team fared at Old Trafford. 
 
<a href="http://www.gocricket.com/player/murali-vijay/4001/4102">Murali Vijay </a> It seems ages ago when <keyword id="57265" type="PERSON" weightage="20" keywordseo="Murali-Vijay">Murali Vijay</keyword> impressed everyone with his defiant knocks in the first two Tests at Trent Bridge and Lord's. At Manchester he scored a total of 18 runs including a duck in the first innings. He was at the receiving end of a peach of a delivery from James Anderson in the first innings and in the second, fell to Chris Woakes. His slump has come at a wrong time. Among all the specialist Indian batsmen on the tour, he has been one of the two brightest spots. With the other openers failing, he needs to get his touch back if India hope to do well in the fourth Test. 
 
<a href="http://www.gocricket.com/player/gautam-gambhir/4001/4043">Gautam Gambhir </a> Questions were raised when Gambhir was selected for the England tour as a reserve opener. Those questions were put to rest when the first choice opener in <keyword id="17805" type="PERSON" weightage="20" keywordseo="Shikhar-Dhawan">Shikhar Dhawan</keyword> failed. The reasons, for which he lost his place in the national side, seem to be valid even today. A batsman of his repute, on his return to international cricket after almost two years, should perform but he could muster only 22 runs in two innings. Both the times he fell to short deliveries. In the first innings, his dismissal brought back memories of the 2011 tour of England when he repeatedly was caught in the slip cordon and his second dismissal left everyone frustrated as he needlessly gloved one from Anderson to be caught by the wicketkeeper. 
 
<a href="http://www.gocricket.com/player/cheteshwar-pujara/4001/4106">Cheteshwar Pujara</a> He was the second Indian batsmen to be out for a duck in the first dig after <keyword id="52757" type="PERSON" weightage="20" keywordseo="Stuart-Broad">Stuart Broad</keyword> lured him to edge one to Chris Jordan in the slips. In the second innings, he was a bit unlucky to be given out lbw as replays showed the ball from Moeen Ali was missing the leg stump. He managed 17. His technique on seaming, pacy tracks is under intense scrutiny after yet another failure. 
 
<a href="http://www.gocricket.com/player/virat-kohli/4001/25007">Virat Kohli</a> 
Seems Kohli is not willing to learn and improve. People have lost count of the number of times his weakness against outside off deliveries has been exploited England bowlers. He is the designated superstar of a star-studded Indian line-up. But where is that performance? In both the innings, Anderson got the better of him. He scored a duck in the first and managed seven in the second before pushing at a delivery that went safely into the hands of Ian Bell at second slip. Someone needs to tell him that he need not go after every delivery, especially those outside off. Let better sense prevail. 
 
<a href="http://www.gocricket.com/player/ajinkya-rahane/4001/32045">Ajinkya Rahane </a> 
Smile is infectious. Replace 'smile' with 'failure' for Rahane. When everyone around him seems to be hell bent on playing loose, rash strokes, could he have avoided playing one of his own? Yes. But he couldn't. In the first innings with his team in dire straits, he gifted Chris Jordan his wicket after scoring 24 in a partnership with captain Dhoni that gave a flickering hope of a recovery. In the second, another loose shot put him on the way back to the dressing room after he had managed a single. All we can hope is that his failure at Manchester is just a one-off incident. 
 
<a href="http://www.gocricket.com/player/ms-dhoni/4001/4057">MS Dhoni</a> 
Dhoni's knock of 71 runs in the first innings will be counted among his best in Tests. When everything around him crumbled, he was the lone warrior before he pulled one that ended his fight. In the second, he again saved India from the ignominy of being bowled out for double figures. However, his wicketkeeping and captaincy was questionable. Not utilising bowlers effectively apart from his performance behind the stumps is not helping the team. After the low of Southampton, it was expected that he would rejig things. But, under his watch, India slipped further into the abyss. Lord's is a distant memory now for him and the Indian fans. 
 
<a href="http://www.gocricket.com/player/ravindra-jadeja/4001/32004">Ravindra Jadeja</a> 
Anderson has gained much out of his spat with India allrounder Jadeja. The Englishman has flourished. On the other hand, Jadeja's only significant contribution was trapping Anderson after being meted out a similar treatment by the pacer in India's first innings. He took one wicket in the entire match and scored four runs including a 14-ball duck in the first innings. His pairing with R Ashwin on Indian tracks is deadly. In England where Moeen Ali has trapped India in a web of spin, he has been nothing short of ordinary. 
 
<a href="http://www.gocricket.com/player/bhuvneshwar-kumar/4001/25023">Bhuvneshwar Kumar</a> 
Bhuvneshwar continues to toil hard and he is reaping rewards for his efforts. He seems to be the only member of the Indian team who is aware of his limitations and is taking the most out of his abilities. He took three wickets at Manchester where England batted once. Two of those (Sam Robson and Bell) were a result of some wonderful bowling. He has lost his 'midas touch' with the bat as scores of 0 and 10 would suggest. But he cannot be expected to hide the failures of the batsmen every single time. His job is to bowl, not score runs. Unfortunately he has been forced to do the additional job as well and the effect is the dip in his intensity. 
 
<a href="http://www.gocricket.com/player/varun-aaron/4001/30019">Varun Aaron</a> 
Back in the team after a gap of almost three years, Aaron impressed with his lively pace. He bowled consistently above 140 km/hr and occasionally troubled the batsmen with his bounce. The delivery with which he cleaned up Moeen Ali was one of the few moments to cherish for India from the Test. He picked 3/97 in 26 overs and made an impressive return, although straying away on occasions. 
 
<a href="http://www.gocricket.com/player/ravichandran-ashwin/4001/26007">R Ashwin</a> 
Include Ashwin and things will get better was the mantra after the loss at Southampton for India. He was selected and bowled well but went wicketless even as his counterpart (Moeen) ended with four scalps. However, it was his batting that was much talked about. He put to shame the Indian top order in both the innings. In the first his 40 runs took the team past 150 runs and he followed it with an unbeaten 46 which was the highest score by any Indian batsman in the second dig. 
 
<a href="http://www.gocricket.com/player/pankaj-singh/4001/4100">Pankaj Singh</a> 
His painful wait for a wicket finally ended on the third day when he removed Joe Root for 77. He, again, started well but his workhorse attitude didn't translate into anything significant. On a pitch where England bowlers murdered Indian batting, his efforts at best can be summed up as below par. He bowls well but not good enough that will force the selectors to give him an extended run. Mind you – he is bowling in helpful conditions and not on lifeless subcontinent tracks. If <a href="http://www.gocricket.com/player/ishant-sharma/4001/4094">Ishant Sharma</a> gets fit, Pankaj, who took two wickets in the Test, will surely sit out at The Oval.

A Report Card Of India's Defeat At Manchester

Following an embarrassing 3-1 defeat to England, Gocricket.com has the Indian players' report cards ready here. 
 
<a href="http://www.gocricket.com/player/shikhar-dhawan/4001/28004">Shikhar Dhawan</a>: 5/10 
 Dhawan was India's highest run-scorer in the two-Test series against New Zealand with 215 from four innings. However, the Delhi batsman couldn't create the same impact against England: he managed 122 runs at an average of 20 with a highest of 37. His technical flaws were widely exposed by <keyword id="80896" type="PERSON" weightage="20" keywordseo="James-Anderson">James Anderson</keyword>, who gave Dhawan a tough time outside the offstump. While he looked good in patches during his innings of 29 at Trent Bridge, 31 at Lord's and 37 at The Ageas Bowl, he couldn't convert them into anything productive. Most of his dismissals came in the initial part of the innings which dented India's hopes of getting off to a decent start. 
 
<a href="http://www.gocricket.com/player/murali-vijay/4001/4102">Murali Vijay</a>: 7/10 
 
Dhawan's opening partner got off to a start few imagined him to. His 146 at Trent Bridge was his fourth century in Tests and first in England. He followed it up with consecutive half-centuries - 52 in the second innings and 95 at Lord's - but lost his bearings thereafter. In the next seven innings, Vijay made just 109 runs and his average - which at one point in the series touched 80 - dropped to 40.20. He wasn't troubled much at Trent Bridge and Lord's but in Southampton, Vijay was unlucky to play on and get run out. It was at Old Trafford and The Oval that he looked out of sorts, throwing his bat at away-going deliveries and flummoxed by those that darted in. A decent series all in all, but it could have been better. Considering the way his team-mates performed, Vijay was one of the few positives for India. 
 
<a href="http://www.gocricket.com/player/stuart-binny/4001/31034">Gautam Gambhir</a>: 0/10 
 
Returning after an 18-month absence, Gambhir showed so signs of improvement. He was the most unconvincing among the Indian batsmen. His replacing Dhawan for the last two Tests raised many eyebrows. He remained persistent with his tendency to poke at balls outside offstump and looked like a sitting duck in each innings. An edge to gully, a run-out and a caught behind while trying to leave the ball, such dismissals indicate that Gambhir may have played his last Test for India. 
 
<a href="http://www.gocricket.com/player/cheteshwar-pujara/4001/4106">Cheteshwar Pujara</a>: 4/10 
 
Pujara has endured one of the toughest series of his young career. He started off well with scores of 38, 55, 28 and 43 but Southampton, much like it did for India, led to his downward spiral. He had problems with the incoming delivery and even his rock-solid forward defence couldn't come to his rescue. Pujara was out caught behind on six occasions and fell prey to Moeen Ali's offspin twice. With a total of just 222 runs in 10 innings, India's No 3 looked very shaky. 
 
<a href="http://www.gocricket.com/player/virat-kohli/4001/25007">Virat Kohli</a>: 2/10 
 
The first real forgettable tour for India's most prolific batsman of the current era. The fact that Kohli couldn't score even a single half-century in 10 innings speaks volumes about his failure. With 134 runs at an average of 13.40, statistically he is India's worst batsman on tour. James Anderson had his number throughout the series, dismissing him four times. Kohli was twice out without troubling the scorers and the cobwebs in his head were clearly visible. Twice he was dismissed offering no shot - bowled by Liam Plunkett at Lord's and out lbw to Chris Jordan at The Oval. 
 
Apart from his batting, his goof-ups in the slip cordon added to Kohli's woes. A gloomy series like this can be excused, especially after the string of success he has experienced, but Kohli must realise that a major chunk of India's batting revolves around him. His getting back among the runs is crucial if India are to have any chances in Australia later this year. 
 
<a href="http://www.gocricket.com/player/ajinkya-rahane/4001/32045">Ajinkya Rahane</a>: 7/10 
 
Another example of a batsman who squandered away a decent beginning. Rahane, in only his second Test in England, registered his name on the Lord's Honours Board, courtesy a match-winning century on day one to revive India splendidly. Two fifties followed in Southampton but the promising run was brought to a halt in the last two Tests with Rahane managing 21, 4, 0 and 1. He showed a lot of promise with 299 runs at 33.22 and but the team needs more from him. 
 
<a href="http://www.gocricket.com/player/stuart-binny/4001/31034">Stuart Binny</a>: 2/10 
 
Much was said about Binny after his selection in the 18-member squad, and as it would turn out, he was another hyped-up player. His only substantial knock came at Trent Bridge - a match-saving 78 in the second innings. He played a horrible shot in the first innings at Lord's and his credentials of an allrounder also took a big blow as he struggled with the ball and went wicketless in all three Tests he got. 
 
<a href="http://www.gocricket.com/player/ms-dhoni/4001/4057">MS Dhoni</a>: Batting 7.5/10, Captaincy 5/10 
 While <keyword id="6397" type="PERSON" weightage="20" keywordseo="Dhoni">Dhoni</keyword> the batsman raised his game in England, Dhoni the captain was another major setback in away matches. With four half-centuries in five matches, the India skipper had one of his best overseas series. His 82 at Trent Bridge was followed by 50 in Southampton where his biggest slip was falling early on day four when India needed him to stay in the middle. At Old Trafford and The Oval, his innings of 71 and 82 were one of only three Indian scores in double digits as the rest of the batsmen crumbled around him. 
 Dhoni's captaincy though looked lifeless yet again. His five-bowler strategy never really came to India's aid, and the decision to ignore Ishwar Pandey raised questions. After leading India to their fifth consecutive overseas series loss, this might mark the end of the road for Dhoni the <keyword id="195040" type="POSITION" weightage="20" keywordseo="Test-captain">Test captain</keyword>. 
 
<a href="http://www.gocricket.com/player/ravindra-jadeja/4001/32004">Ravindra Jadeja</a>: 5/10 
 
Despite the fact that he and Anderson kept on getting each other out, Jadeja's only meaningful contribution came in the second Test at Lord's, where his counter-attacking fifty set the game up in favour of India. With the ball, he was inconsistent. His wickets either were down to poor shots or the need for quick runs. Ian Bell and Jos Buttler took him apart in Southampton, where he was either too short or generous down the legside. Jadeja remains a strong contender at home but a doubtful starter for away matches. 
 
<a href="http://www.gocricket.com/player/rohit-sharma/4001/4095">Rohit Sharma</a>: 1/10 
 
Our very own flat-track bully was drafted into the team at The Ageas Bowl in place of Binny and what did he do? Played a silly shot to Ali in the first innings and fell early on day five to Anderson in the second. Might be a cinch to play on Indian wickets, but his modes of dismissal are only worsening his case of playing abroad. 
 
<a href="http://www.gocricket.com/player/ravichandran-ashwin/4001/26007">Ravichandran Ashwin</a>: 6/10 
 
Ashwin managed to surprise in a role-reversal of sorts. While at Old Trafford he impressed one and all with his batting, The Oval saw Ashwin get back among the wickets. He forged a 66-run partnership with Dhoni for the seventh wicket in the fourth Test and played textbooks shots. Ashwin played second fiddle to Dhoni, who at the other end took calculated risks. Ashwin scored 46 in the second innings as India went down by an innings and 54 runs. At The Oval, Ashwin finally took his first wicket since 2012 and his 3/72 kept things tight. 
 
<a href="http://www.gocricket.com/player/bhuvneshwar-kumar/4001/25023">Bhuvneshwar Kumar</a>: 8/10 
 
The conditions in England were supposed to ideal for Bhuvneshwar's style of bowling and he proved the theory right with figures of 5/82 and 6/82 in the first two Tests. But as soon as the English batsmen came into their own, the Uttar Pradesh bowler was a tired figure out in the middle. Once the batsmen negotiated with his early movement, scoring became easy. And even though in the third and fourth Test he took 3/101 and 3/75, Bhuvneshwar lacked support at the other end. 
 
To see him bat nicely in the series was a pleasant surprise. Scores of 63, 58 and 52 in the first three innings of the series were an added bonus for the team. With 19 wickets at 26.63 and 247 runs at 27.44, Bhuvneshwar had a series to remember. 
 
<a href="http://www.gocricket.com/player/ishant-sharma/4001/4094">Ishant Sharma</a>: 7/10 
 
Ishant was supposed to spearhead the Indian attack in England and many believed that the win at Lord's - where he took a career best 7/74 - had finally established Ishant as India's premier fast bowler. But an unlikely injury after the historic triumph was a case of bad luck for India. And when Ishant came back, it was fairly evident that he wasn't the same bowler who etched his name of on the Lord's Honours Board. At The Oval, he was predictably short and Stuart Broad took the attack to him despite batting with a broken nose. Ishant looked a bit ragged in his 4/96. 
 
<a href="http://www.gocricket.com/player/varun-aaron/4001/30019">Varun Aaron: 5/10</a> 
 
The Jharkhand fast bowler made a return to Tests after December 2011 with plenty of calls for his inclusion for the fourth Test, in Ishant's absence. And even though he dismissed Ali with a peach of a delivery and broke Broad's nose, Aaron was mostly erratic, wasting energy on bowling far too many short balls. He bagged five wickets at an average of 50 - which included him conceding runs at over five an over at The Oval. But there is no doubt that he caught a few eyes with his pace. 
 
<a href="http://www.gocricket.com/player/pankaj-singh/4001/4100">Pankaj Singh</a>: 4/10 
 Known as a workhorse in domestic circuit, Pankaj bowled with a lot of heart in Southampton after getting a debut in place of an injured Ishant. He was unlucky twice after Jadeja put down <keyword id="9234" type="PERSON" weightage="20" keywordseo="Alastair-Cook">Alastair Cook</keyword> in the first session followed by an umpiring error that reprieved Bell. Pankaj finally tasted success after toiling for 47 overs in Southampton and almost 23 overs in Manchester, where he bowled bad balls too frequently and went over four an over. 
 
<a href="http://www.gocricket.com/player/mohammed-shami/4001/30030">Mohammed Shami</a>: 2/10 
 
Shami bowled with good pace in three Tests but was overall ordinary. His five wickets in the series came every 115 deliveries and at the cost of 73.20 runs. But with the next series taking place against the West Indies, he might return on the basis of what he did against them last year.

You Searched For "Aaron Pankaj Singh" and got 6 results

India Face Pace Conundrum In English Test

gocricket

Did Dhoni Miss Aaron Or Ashwin On Day 1 In Southampton?

G Rajaraman

BCCI Forgets That There Is More To Indian Cricket Than Just IPL

gocricket staff

To Change Or Not To Change, That's The Question For Dhoni

gocricket staff

A Report Card Of India's Defeat At Manchester

Feroz Khan

Indian Players' Report Cards After England Debacle

gocricket staff

Popular Keywords

Buying Guides