India's tour carried by three batsmen
India lost the Border-Gavaskar Trophy by going down 0-2 in Australia. Here's a rating of the performances of players who made those results
9
Scored 692 runs with four centuries at 86.50. Most runs in a four-Test series by a visiting batsman in Australia. Joint most centuries by an Indian in an away series, and the second highest run aggregate. Second man to score two hundreds on Test captaincy debut. Loses a mark for not being able to adjust as a captain to counter some ordinary bowling by his bowlers.
8.5
The man who contributed a lot to Kohli's success. Left alone 234 balls in the series, more than the next two batsmen put together. Made sure Kohli was not exposed to the new ball. Scored close to 500 runs. Nearly pulled off a miracle chase in Adelaide. Could have easily scored two more hundreds. Seems like he has the temperament to be a slip fielder, but not the results to show for it.
8
India's most consistent batsman since the overseas sojourn began in South Africa at the end of 2013. Scored 399 runs at 57. Took Mitchell Johnson on in Melbourne when the fast bowler was trying to break Kohli's concentration. Saved the Sydney Test when India were on the verge of an encore of the horrible sessions they have been encountering. Also copped some bad calls from the umpires, paying the price for India's unaccepting attitude towards technology.
5
That India's best bowler averaged 48 says everything you need to know about their bowling in this series. Ishant was the only quick bowler to operate with a semblance of control.
After one of the most nervous Test debuts ever, he came back well to score a hundred in Sydney, which went a long way to help India save the Test.
4
Wasn't as poor as he was in England. At least did the first part of his job often enough: to keep Cheteshwar Pujara away from the new ball. Had four starts out of six innings but failed to convert any of those into a big one. Took good catches at second slip.
India's highest wicket-taker. The only Indian bowler with a sub-40 average but kept releasing pressure by bowling short and wide or down leg side. His economy rate of 4.24 says it all.
3.5
Averaged 34 for his 201 runs in three Tests, but kept throwing away starts by playing loose shots. Should have kicked on especially after India had a decent opening stand in each of the first innings.
Helped save the Melbourne Test and then retired mid-way. Took two diving catches, effected an innovative run-out, but also showed he wasn't too keen to go for catches dying in front of first slip.
Showed he is an organised batsman and a wicketkeeper, but couldn't quite kick on as a batsman. Good as a wicketkeeper for the quicks, but there are concerns over his keeping standing up to the stumps.
3
Kept finding soft ways to get out. Never really looked out of his league, but never part of it either. India's Shane Watson with the bat. Averaged 29 for his 173 runs. Took up the challenge of batting at No. 3 when Pujara was dropped.
2
Rushed back to Test cricket out of desperation. With no seam or swing on offer, and his pace down, he was easy meat for Australia's batsmen, who took 168 runs in his 42 overs for the loss of one wicket.
The quickest Indian bowler and the most expensive too. Economy rate of 5.6, average of 72.4. Just five wickets in two Tests.
Not as quick as Aaron but just as wayward. Economy rate of 4.6, average of 50. The pair might still be worth investing in, but will need to show massive improvement with regards to how they want to take wickets.
1
Never looked like getting a wicket in his debut Test, on a pitch that Nathan Lyon took 12. Bowled flat and flatter, showing why he averages two wickets per match in first-class cricket. A pick based on IPL performances.
0
A rating equivalent to the runs he scored. Lasted only four balls in two innings at the SCG.
Sidharth Monga is an assistant editor at ESPNcricinfo