India came into the second Test in Colombo with one job on their mind — finish the series.
After the 165-run win in Galle, Shubman Gill’s side had already taken a 1-0 lead. Sri Lanka, meanwhile, needed a much better performance at the Sinhalese Sports Club if they were going to keep the series alive.
The second Test has not been as straightforward as the scorecard might suggest.
India won the toss and chose to bat, but Sri Lanka’s bowlers found enough movement early on to make life uncomfortable. There were wickets, missed chances and even an injury scare for Rishabh Pant.
And yet, once again, Devdutt Padikkal stood between Sri Lanka and a breakthrough opportunity.
The Karnataka batter followed his sensational 167 in Galle with another hundred in Colombo, scoring 117 from 193 balls. It was his second Test century in as many matches and the innings that gave India the platform they needed.
India’s innings has continued into Day 2, with the latest live score showing 321/6 after 90.4 overs, with Rishabh Pant batting alongside Dhruv Jurel. (NDTV Sports)
That means one thing is already clear: Sri Lanka have had their opportunities, but India have repeatedly found a way to stay ahead.
Padikkal Has Gone From Opportunity to India’s Biggest Batting Story
A couple of weeks ago, Devdutt Padikkal was still trying to establish himself as a Test cricketer.
Now, after two Tests, he has become one of the biggest talking points of India’s Sri Lanka tour.
His first Test century came in Galle, where he made 167, followed by 44 in the second innings.
Then came Colombo.
Another hundred.
This time, 117 off 193 deliveries, with 12 fours.
The numbers are impressive, but the circumstances make the innings even better.
Padikkal was not batting on a completely flat surface where the ball came nicely onto the bat. The SSC pitch offered movement and bounce, particularly earlier in the innings, and Sri Lanka’s seamers managed to trouble India’s top order. (The Times of India)
Padikkal had to work for his runs.
He did.
And once he settled, Sri Lanka struggled to get him out.
This Was a Different Hundred From Galle
The most encouraging thing about Padikkal’s two centuries is that they haven’t looked like copies of each other.
In Galle, he was able to build a huge innings and eventually reach 167.
Colombo asked different questions.
There was more movement early on. Sri Lanka’s seamers were able to get the ball to nip around, and India lost KL Rahul and Yashasvi Jaiswal relatively early.
Padikkal responded by slowing things down.
He didn’t try to force the scoring rate.
He stayed close to the ball.
He defended when he needed to.
And when Sri Lanka gave him something to work with, he put it away.
That is exactly the kind of batting India will want from a No. 3.
Not just pretty strokeplay.
Not just one big innings.
The ability to understand what the match needs.
Sri Lanka Had Their Chances — Padikkal Made Them Pay
There was another interesting element to Padikkal’s innings.
He was given more than one life.
Sri Lanka had opportunities to remove him early, but they couldn’t hold on to them. Once those chances went begging, Padikkal became increasingly difficult to dislodge.
That is one of those old Test cricket lessons that never really changes.
You get a chance.
You take it.
If you don’t, the batter makes you pay.
Padikkal did exactly that.
And considering what he had already done in Galle, Sri Lanka would have been painfully aware that they could not afford to let him settle.
Padikkal’s Back-to-Back Hundreds Have Changed the No. 3 Conversation
This is probably the biggest story coming out of Colombo.
India’s No. 3 position had been one of the areas under discussion before the series.
Sai Sudharsan was expected to be part of India’s plans but was unavailable because of injury.
That opened the door for Padikkal.
He has now walked through it in a very convincing fashion.
167 in Galle.
117 in Colombo.
Two Tests.
Two centuries.
And suddenly, the question is no longer whether Padikkal can handle Test cricket.
The question is how difficult it will be to leave him out when Sai Sudharsan returns.
Even India’s batting coach Sitanshu Kotak has acknowledged that Padikkal has given the team plenty to be pleased about, while also pointing out that India could have avoided some of the dismissals around him. (icc)
That is a good problem for India to have.
Shubman Gill’s Half-Century Was Just as Important
Padikkal got the headlines, but Shubman Gill played a very useful supporting role.
Gill scored 50 from 108 balls and shared a 120-run partnership with Padikkal.
It was not the most explosive innings.
It didn’t need to be.
India had already lost Rahul and Jaiswal, so Gill’s job was to settle things down and allow Padikkal to continue building.
The pair did exactly that.
At one point, India had been reduced to 66/2.
By the time Gill was dismissed, India had reached 186/3.
That is the sort of partnership that can change the feel of a Test innings.
Sri Lanka had the early momentum.
Gill and Padikkal slowly took it away.
India’s Middle Order Has Had to Do More Work Than Expected
The basic idea before the match was probably simple.
India had won the first Test convincingly.
Their top order was in good form.
Padikkal was coming off 167.
Sri Lanka were already missing important batters.
But Test cricket rarely follows the script.
India lost wickets at regular intervals.
Gill departed after his half-century.
Padikkal eventually fell for 117.
Ravindra Jadeja made 43 before Asitha Fernando dismissed him.
Saransh Jain, making his Test debut, was then removed for six.
At the latest verified score, India were 321/6, with Rishabh Pant and Dhruv Jurel at the crease. (NDTV Sports)
So while India are clearly in a strong position, this has not been a completely one-sided batting display.
They have had to rebuild more than once.
Rishabh Pant’s Injury Scare Added Another Twist
One of the biggest talking points from the opening day was Rishabh Pant’s injury.
Pant was struck on his left wrist by a short delivery from Lahiru Kumara and initially retired hurt. That immediately created concern because Pant is not only India’s wicketkeeper but one of their most important attacking batters.
Thankfully, the situation was not as serious as it first appeared.
Pant returned to bat and remained unbeaten at the latest score.
That is a major relief for India.
Because if Pant is available, India’s lower middle order suddenly looks much more dangerous.
He doesn’t need many overs to change a Test match.
A couple of boundaries can quickly turn a steady total into a huge one.
Pant Could Be the Player Who Changes the Tempo
This is where Day 2 becomes particularly interesting.
India have already done the hard work.
They have batted through the difficult periods.
They have built partnerships.
Now they have an opportunity to accelerate.
Pant is exactly the sort of batter who can do that.
At the latest score, he was unbeaten on 13 from 26 balls, with a six already to his name.
That may not look like much on paper.
But it tells you that Pant is back at the crease and looking to play his natural game.
If he gets 50 quickly, India’s total could move away from Sri Lanka very quickly.
And if Dhruv Jurel stays with him, India have another batter capable of putting pressure back on the bowlers.
Dhruv Jurel Has Another Opportunity to Show His Red-Ball Value
Jurel has quietly become an important part of India’s Test plans.
He doesn’t have Pant’s attacking reputation, but his ability to play a long innings can be extremely useful.
At the latest score, Jurel was unbeaten on 15 from 41 balls.
That is exactly what India need from him at this stage.
There is no reason to rush.
If Jurel can stay at the crease and allow Pant to attack at the other end, India could quickly move from a good position to a dominant one.
And if Pant falls, Jurel’s ability to bat with the tail could become even more important.
Sri Lanka’s Fast Bowlers Have Actually Done a Decent Job
It would be unfair to look at India’s score and say Sri Lanka’s bowling attack has been poor.
Asitha Fernando has been the standout.
He has taken four wickets and has consistently asked questions with the new ball and older ball. At the latest score, he had figures of 4/51 from 18 overs.
Lahiru Kumara has also picked up a wicket.
The bigger problem for Sri Lanka has been the lack of support.
When one bowler creates pressure, the other end needs to keep it going.
That hasn’t always happened.
And that has allowed India’s batters to recover after losing wickets.
Jayasuriya Has Bowled Plenty — But Hasn’t Got the Reward
Prabath Jayasuriya has once again been asked to do a huge amount of work.
At the latest score, he had bowled 27 overs for 90 runs without a wicket.
That’s a long spell.
And while the wickets haven’t come, his role has still been important.
He has kept one end under control and tried to build pressure.
The problem is that when a spinner bowls that many overs without taking a wicket, the pressure eventually shifts back onto the captain.
Sri Lanka needed someone to partner Jayasuriya with wickets.
Instead, Asitha Fernando has been doing most of the damage.
Sri Lanka’s Fielding Has Not Helped
This has been another frustration for the hosts.
Sri Lanka had chances.
Some were difficult.
Others were definitely takeable.
And against a batter in the kind of form Padikkal is enjoying, missed opportunities are expensive.
Once a player has made 100 in one Test and walks into the next match looking confident, you cannot afford to give him extra lives.
Sri Lanka did.
Padikkal punished them.
India’s Approach Has Been More Patient Than Aggressive
One thing that stands out from the innings is India’s scoring rate.
At 321/6 after 90.4 overs, India were scoring at around 3.54 runs per over.
That may not sound spectacular in modern Test cricket.
But it makes sense in context.
India lost two early wickets.
The pitch offered movement.
Gill and Padikkal needed to rebuild.
There was no reason to throw wickets away.
The job was to get through the difficult period first.
Then accelerate later.
That is a sensible approach when batting first in a Test.
The Big Question: How Far Can India Push the First Innings?
This is where the match could take another turn.
India already have enough runs to put Sri Lanka under pressure.
But they will want considerably more.
The first Test showed how valuable a big first-innings score can be in Sri Lankan conditions.
India made 462 in Galle and eventually won by 165 runs.
This time, the surface may become increasingly difficult as the Test progresses.
That means India’s goal should be to bat once and bat big.
A total in the region of 400-plus would give their bowlers a lot of room.
If they can move beyond 450, Sri Lanka could find themselves under serious pressure.
But India Should Not Rush a Declaration
There has been talk around the possibility of India declaring early to expose Sri Lanka’s batting to a deteriorating pitch.
That sounds attractive.
But there is a balance to find.
India are already 1-0 up.
They don’t need to chase a dramatic victory at all costs.
A massive first innings gives them security.
At the same time, batting too long can allow Sri Lanka to spend less time batting on the difficult part of the pitch.
That is the calculation Shubman Gill and the Indian management will have to make.
The weather could also play a part.
Rain and thunderstorms had been forecast around Colombo before the match, making time management another factor for both sides. (Cricket Times)
Sri Lanka’s Batting Problem Is Getting Bigger
The hosts were already weakened before the Test started.
Kusal Mendis was unavailable because of a hamstring injury, while Dinesh Chandimal missed the match following the concussion he suffered in Galle.
Pathum Nissanka was also unavailable after wrist surgery.
That leaves Sri Lanka without some of their more experienced batting options.
If India put 400-plus on the board, this weakened batting order will have to deal with a fresh Indian attack.
And that could be a serious problem.
Manav Suthar Will Be One to Watch Again
After his sensational 10-wicket match haul in Galle, Manav Suthar has already shown that he can be a major threat in Sri Lankan conditions.
The Colombo pitch will eventually turn more.
If India can get a sizeable first-innings lead, Suthar could become even more dangerous later in the match.
Ravindra Jadeja and Kuldeep Yadav also give Gill plenty of spin options.
That is why Sri Lanka cannot simply focus on surviving the first 20 overs against the Indian seamers.
There will be another problem waiting once the ball gets older.
What Day 2 Tells Us About India’s Bigger Picture
The most interesting part of this Test is not simply the possibility of another Indian victory.
It is what Padikkal’s performances are doing to India’s batting plans.
Before this tour, there was uncertainty around No. 3.
Now Padikkal has scored 284 runs in his first two Tests of the series, including two centuries.
That is not a small sample anymore.
It is still early in his international career, but the signs are extremely encouraging.
And it puts genuine pressure on the selectors when Sai Sudharsan becomes available again.
Padikkal’s Numbers Are Starting to Look Serious
Let’s put the two Test performances together:
First Test, Galle
167 + 44
Second Test, Colombo
117
That is already 328 runs in three innings.
The first innings of the second Test alone was enough to make him the first visiting batter to score multiple centuries at No. 3 in a two-Test series in Sri Lanka, according to the latest statistical reports.
That is remarkable company for a player still trying to establish himself.
The important thing is not the record itself.
It is what the record represents.
Padikkal is showing that he can handle different conditions and different match situations.
Day 3 Could Be the Turning Point
If India can push the score beyond 400 and then strike early with the ball, the Test could move rapidly in their favour.
Sri Lanka’s first innings will be crucial.
If their top order collapses, India could potentially force a follow-on conversation.
If Sri Lanka bat well and reduce the deficit, the match becomes much more competitive.
Either way, India’s bowlers will have a lot of responsibility.
The pitch should offer more assistance to spin as the Test progresses.
That is exactly the situation India will want.
What Should India Do Next?
The strategy should be fairly simple.
First, finish the innings strongly.
There is no need to panic.
Pant and Jurel can attack when the field spreads.
The lower order can then add another 50 or 60 runs.
Once India reach a total they are comfortable with, the bowlers can attack.
The second objective will be to get early wickets.
Sri Lanka cannot afford another slow start if they are chasing a huge first-innings total.
And then comes the spinners.
Suthar, Jadeja and Kuldeep could become the most important players of the match once the surface starts breaking up.
Sri Lanka Need a Big Spell From Someone
Sri Lanka’s bowlers have already put in plenty of work.
But they need wickets.
Not just pressure.
Not just dot balls.
Wickets.
Asitha Fernando has four.
Jayasuriya has bowled 27 overs without one.
Keshara Nuwantha has also bowled a long spell and taken a wicket.
The hosts need someone to produce a spell that changes the innings.
Otherwise, India will keep adding runs.
And every extra 50 runs will make Sri Lanka’s task harder.
A Note on the 412/5 Scoreline
The 412/5 at stumps with Padikkal on 118 mentioned in the supplied match summary does not match the latest verified live score available at the time of writing.
The current score feed has India at 321/6 after 90.4 overs, with Padikkal already dismissed for 117, Jadeja out for 43 and Saransh Jain dismissed for six.
So for an article being published as a latest Day 2 update, I would use the verified score rather than the 412/5 figure.
That also changes the headline slightly: this is less about India already having a massive 400-plus total and more about India building towards one after Padikkal’s second straight century.
Final Verdict
India have not completely blown Sri Lanka away in Colombo.
And honestly, that makes the performance more interesting.
Sri Lanka have bowled well in spells.
They have taken wickets.
Asitha Fernando has been particularly impressive.
But India have been better at absorbing the pressure.
And once again, Devdutt Padikkal has been the difference.
His 117 off 193 balls was the backbone of India’s innings. It was not a flashy hundred. It was a proper Test hundred — built through patience, good defence and the ability to cash in when Sri Lanka offered scoring opportunities.
Shubman Gill’s 50 gave him valuable support.
Rishabh Pant‘s return after his wrist scare is a major positive.
Dhruv Jurel is still at the crease.
And India’s lower order is yet to have its say.
The latest score of 321/6 leaves India in a strong position, but there is still work to do before they can call the first innings a complete success.
For Sri Lanka, the equation is becoming uncomfortable.
They need wickets quickly.
They need to prevent India from getting 400 or more.
And once they bat, they will have to deal with an Indian attack that already showed in Galle just how dangerous it can become as a Test wears on.
For India, though, the biggest takeaway is sitting at No. 3.
Devdutt Padikkal has gone from filling in for an injured player to looking like he belongs.
Two Tests.
Two hundreds.
And another big statement in Colombo.
The next question is no longer whether Padikkal can make runs.
It is whether India have finally found their long-term No. 3.
