India won the first Test against Sri Lanka by 165 runs. It was India’s 600th Test. Their World Test Championship hopes are still alive. But the result is only half the story. Five days in Galle told us plenty about individual players and exposed one problem India still hasn’t fixed. India took the last wicket at 1.22 pm. The rain that came after was heavy enough that the presentation had to be moved indoors. One more hour of Sri Lankan batting and this is a draw. And a draw here would have effectively ended India’s WTC campaign. That’s how thin the margin was.
WTC 2027 points table: where India stand now
Here is the WTC points table as it stood after the Galle Test.
| Team | Points % |
|---|---|
| Australia | 77.78 |
| South Africa | 75.00 |
| New Zealand | 72.22 |
| Bangladesh | 66.67 |
| India | 53.33 |
India is fifth at 53.33%. India’s WTC points table position is fixable, but only with results in the next two weeks.
The scenario that helps India:
Win in Colombo (from 23 August) and hope Bangladesh lose to Australia (from 22 August). That combination pushes India to roughly 57.5% and up to fourth, with Bangladesh sliding to about 55%.
The scenario that hurts:
Bangladesh win again. They go to 72.22% and join New Zealand; Australia drop to 70% and fourth, and India’s climb gets a lot steeper.
So the WTC points table 2026 to 2027 doesn’t depend only on India. The Australia vs Bangladesh Test in Darwin matters just as much, because a Bangladesh win pushes them further out of India’s reach.
What makes Manav Suthar so hard to face
Ravichandran Ashwin has backed left-arm spinner Manav Suthar as a long-term prospect for India, pointing to his traditional action, his control of line and length, and the revolutions he puts on the ball. Two Manav Suthar stats from the match tracking explain most of it:
| Metric | Suthar |
|---|---|
| Average speed | ~89 kmph, quicker than both Jadeja and Kuldeep in this match |
| Balls turning more than 4.5° | ~81%, the most turn of any spinner on either side |
Those two numbers aren’t supposed to sit next to each other. The usual trade is simple: if you want more turn, you slow the ball down and give it air. Suthar is turning it more while bowling quicker. It comes down to his action. He’s very side-on, his body drives hard through the crease, and his back leg drags behind him. All that effort goes into spinning the ball rather than lobbing it up. That’s why it dips and grips at speeds where most fingerspinners get nothing off the pitch. People will compare him to Ashwin whether we like it or not, and the early numbers invite it: two five-fors and a ten-wicket match in his first two Tests. I’d rather enjoy a new bowler than measure him against a retired one. But the parallel is there, and it isn’t silly.
The open question is T20:
Everything that makes him good in Tests, the dip, the overspin, the effort on every ball, is the opposite of what short formats reward, where you bowl flatter and quicker and don’t invite the drive. That’s a problem for another day. India’s white-ball spin spots are full anyway. Red-ball specialist, for now, is exactly the right label.
Devdutt Padikkal’s 167: the innings that answered the bigger question
Padikkal was Player of the Match, and it wasn’t close. His 167 built the lead the win was constructed on. Ten wickets is the rarer feat, and matches are won by taking twenty. Suthar deserves the top billing. But India came into this India vs Sri Lanka Test series with a specific fear, and Padikkal is the one who dealt with it. India had lost two of their last three series in spin-friendly conditions at home. Whether the batters could survive on a turning surface abroad was genuinely unanswered. Padikkal answered it, and did it from No. 3, a slot India have struggled to fill since Dravid and Pujara.
The rest of the bowling
Kuldeep Yadav: the odd stat:
A wrist spinner finishing behind two fingerspinners on this pitch is strange. Sanjay Manjrekar made a point in commentary that stuck: Kuldeep is bowling faster than he used to. His slowest ball in the match was 78 kmph. A few years ago he’d have gone well below that. The theory is that he isn’t getting regular games, so he’s in a hurry to take wickets whenever he plays. That urgency puts extra effort into the body, and the ball comes out quicker and flatter than it should. If that’s the reason, no technical fix helps. He needs a run of matches so he stops bowling like every spell is an audition. His form since the IPL hasn’t been good either, and that’s fair to hold against him. But if he isn’t backed on a pitch like this one, when will he be?
Ravindra Jadeja, quietly again:
3-57 and 2-16. He’ll disappear behind Suthar’s ten-for, and that’s fine. The point about Jadeja now is that he doesn’t need to be the headline to be essential, four or five wickets a game, runs when they’re needed, and no selection question to answer.
Siraj and Prasidh:
Mohammed Siraj gave India the early breakthrough in both innings, which on a pitch like this is most of the seamer’s job. Prasidh Krishna backed him up in short bursts and kept the pressure honest. In these conditions, that’s all India needed from the quicks.
Shubman Gill: no runs, but his best match as captain
Gill failed with the bat twice. He also captained better than he has in any Test so far. Two things stood out.
The fields:
In five days, India never dropped a chance to the ground because nobody was standing there. The slips stayed. Short leg stayed. Even when nothing was happening for an hour, he kept the catchers in, and that quiet hour is usually when captains panic and send everyone to the boundary.
The bowling changes:
He used Suthar with the second new ball. He brought Siraj and Prasidh back in short, sharp bursts instead of long defensive spells. He was thinking in phases of the game, not just getting through overs.
People used to call Rohit’s captaincy clueless. Mostly what they meant was defensive. You can hide that in white-ball cricket, where the innings has a fixed end. Test cricket exposes it. Gill hasn’t been exposed. As for his runs: he hasn’t looked out of touch in a Test series since England. No technical problem, no mental problem. The runs didn’t arrive this week.
The batters who need Colombo
| Player | What Colombo asks |
|---|---|
| Yashasvi Jaiswal | 32 isn’t enough. He’s out of the other formats and nowhere near the T20 side, one long innings would settle a lot. |
| Dhruv Jurel | 51, then nothing. He has to keep scoring to hold off Sarfaraz Khan. |
| KL Rahul | Steady rather than decisive. On a tougher surface, India need him to bat time, not just start well |
Rishabh Pant: three stories in one Test
His 66 off 69 in the second innings came with wickets falling and the lead needing a push. That knock is why the margin was 165 and not something far tighter. He also became the first Indian, and fourth batter ever, to hit 100 sixes in Tests, and the fastest to get there, in his 51st Test, with a hook off Lahiru Kumara that also brought up his fifty. He got there 31 Tests faster than Ben Stokes, and 41 innings and 1660 balls faster than Adam Gilchrist. 76 of those 100 sixes came against spin, which is exactly why he’s the batter India want on surfaces like this. The bit I liked most doesn’t show up in any column. He’d just lost the vice-captaincy. On day three, with the heat and no wickets and shoulders dropping, he was the one shouting the field back into it. Not a quiet word to the captain, he just did it. A demoted player staying that involved isn’t a small thing. The other side is fair too: the shot he got out to in the first innings will restart the old argument, and after losing a leadership role, people go looking for reasons. He’s given them one less.
The problem India keeps getting away with
India’s second innings lasted about two sessions, four wickets in one, six in the next. It’s easy to file that under intent, India going hard because the lead was big. It wasn’t that. The hitting happened because the top order didn’t stick around. Once you’re that many down, swinging is the only option you have left.
And this wasn’t a rank turner.
Harsha Bhogle’s point after the match was that Galle deserved credit as a proper Test pitch: you could bat on day five if you had the temperament, and there was something in it for both seam and spin all week. So the question stays open. If Colombo is a genuine dustbowl, and Sri Lanka, one down and needing the series, has every reason to ask for one, do we trust this batting order to bat two long sessions? On day four’s evidence, not fully.
Colombo prediction: second India vs Sri Lanka Test
The bowling isn’t the worry. Sri Lanka’s batting has been thin since their opening pair broke up, and India have shown they can take twenty wickets whenever the pitch offers a fair contest. The worry is whether India’s middle order can post a total on a pitch designed to make that difficult. That’s the entire second Test in one sentence.
Prediction:
India win it. And Sarfaraz still doesn’t play.
How Bangladesh’s win over Australia helps India
While Galle was going on, Bangladesh beat Australia by nine wickets in Darwin, their first Test win in Australia, in only their third attempt, and their first Test there in 23 years. It took Bangladesh to fourth on 66.67%. Give them the credit first. Upsets are normal in T20 because the short format shrinks the gap. Test cricket doesn’t. Over five days, the distance between Australia at home and a touring Bangladesh side is supposed to be too big to cross, and they crossed it anyway. Now the India angle. That result cost Australia points at the top, which pulls the whole table closer together and lowers the percentage India eventually need to reach the top two. India are chasing a moving target, and Bangladesh just dragged it down a little. The catch is that Bangladesh moved up while doing it. So the ideal outcome for India from here is simple: Bangladesh took points off Australia in the first Test, and now lose the second one from 22 August. India then win in Colombo and go past them.