← Tons of Consequence

Dinesh Chandimal

16 Test hundreds. Of the 16 we can measure, 3 were tons of consequence.

Who against, and where

HundredsTons of consequence
Top tier (England, Australia, India)52
Second tier (New Zealand, South Africa)10
Third tier (Sri Lanka, West Indies, Pakistan)31
Other (Bangladesh, Zimbabwe, Ireland, Afghanistan and the rest)70
At home92
Away50
Neutral ground11

The tiers are a fixed grouping of countries, not a rating on the day. Where it was played is only known for the hundreds we have the match record for.

Every hundred

  1. 116* v Bangladesh, Galle, 2013 · At home · Drawn

    A good ton. A draw against a lower-tier side: a hundred doesn't save a draw against a side like that.

  2. 102 v Bangladesh, Colombo (RPS), 2013 · At home · Won

    A good ton. His side trailed by 171 when his innings began. He made 30% of the team's runs. The match was won by 7 wickets. On the facts we have, the match didn't hinge on it.

  3. 100* v Bangladesh, Chattogram, 2014 · Away · Drawn

    A good ton. A draw against a lower-tier side: a hundred doesn't save a draw against a side like that.

  4. 162* v India, Galle, 2015 · At home · Won

    A ton of consequence: carried the innings. In at 4 for 92, 100 behind. He made 44% of the team's 367, and no one else came close. The team won by 63 runs. He scored at 96 runs per 100 balls.

  5. 151 v West Indies, Galle, 2015 · At home · Won

    A good ton. He made 31% of the team's runs. The match didn't hinge on it: he came in at 2 for 101.

  6. 132 v Australia, Colombo (SSC), 2016 · At home · Won

    A ton of consequence: rescued the innings. In at 4 for 24, 24 ahead. He made 37% of the team's 355. The team won by 163 runs. The series was already won by his side. A slow grind at 37 runs per 100 balls.

  7. 126 v England, Chester-le-Street, 2016 · Away · Lost

    A good ton. A loss: even a great hundred can't be a ton of consequence in a defeat.

  8. 164 v India, Delhi, 2017 · Away · Drawn

    A good ton. A draw, and his side was never in danger of losing, so the hundred didn't save anything.

  9. 155* v Pakistan, Abu Dhabi, 2017 · Neutral ground · Won

    A ton of consequence: rescued the innings. In at 3 for 61, 61 ahead. He made 37% of the team's 419, and no one else came close. The team won by 21 runs. A slow grind at 42 runs per 100 balls.

  10. 138 v Bangladesh, Colombo (PSS), 2017 · At home · Lost

    A good ton. A loss: even a great hundred can't be a ton of consequence in a defeat.

  11. 119* v West Indies, Gros Islet, 2018 · Away · Drawn

    A good ton. A draw against a lower-tier side: a hundred doesn't save a draw against a side like that.

  12. 206* v Australia, Galle, 2022 · At home · Won

    A good ton. He came in comfortably, and the team did not depend on him.

  13. 124 v Bangladesh, Mirpur, 2022 · Away · Won

    A good ton. He made 25% of the team's runs. The match didn't hinge on it: he came in at 5 for 266.

  14. 102* v Ireland, Galle, 2023 · At home · Won

    A good ton. His side already led by 348 when the innings began. He made 17% of the team's runs. The match didn't hinge on it: he came in at 3 for 348.

  15. 116 v New Zealand, Galle, 2024 · At home · Won

    A good ton. He made 19% of the team's runs. The match didn't hinge on it: he came in at 1 for 2.

  16. 107 v Afghanistan, Colombo (SSC), 2024 · Won

    A good ton. Sri Lanka won by 10 wickets. On the facts we have, the hundred didn't decide the match.