← Tons of Consequence

Alastair Cook

33 Test hundreds. Of the 33 we can measure, 4 were tons of consequence.

Who against, and where

HundredsTons of consequence
Top tier (England, Australia, India)122
Second tier (New Zealand, South Africa)61
Third tier (Sri Lanka, West Indies, Pakistan)130
Other (Bangladesh, Zimbabwe, Ireland, Afghanistan and the rest)21
At home151
Away173
Neutral ground10

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. 127 v Pakistan, Manchester, 2006 · At home · Won

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

  2. 116 v Australia, W.A.C.A, 2006 · Away · Lost

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

  3. 105 v Pakistan, Lord's, 2006 · 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.

  4. 104* v India, Nagpur, 2006 · Away · Drawn

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

  5. 118 v Sri Lanka, Galle, 2007 · Away · Drawn

    A good ton. The match was drawn. On the facts we have, the hundred didn't save the match.

  6. 106 v West Indies, Manchester, 2007 · At home · Won

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

  7. 105 v West Indies, Lord's, 2007 · 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.

  8. 160 v West Indies, Chester-le-Street, 2009 · At home · Won

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

  9. 139* v West Indies, Bridgetown, 2009 · Away · Drawn

    A good ton. The match was drawn, against a lower-tier side: a hundred doesn't save a draw against a side like that.

  10. 118 v South Africa, Durban, 2009 · Away · Won

    A ton of consequence: rescued the innings. England were 0 for 0 when he came in, 343 behind. He made 118, 21% of the 574, and England won by an innings and 98 runs. Another hundred came in the same innings.

  11. 235* v Australia, Brisbane, 2010 · Away · Drawn

    A good ton. The match was drawn. On the facts we have, the match didn't hinge on it.

  12. 173 v Bangladesh, Chattogram, 2010 · Away · Won

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

  13. 148 v Australia, Adelaide, 2010 · Away · Won

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

  14. 110 v Pakistan, The Oval, 2010 · At home · Lost

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

  15. 109* v Bangladesh, Mirpur, 2010 · Away · Won

    A ton of consequence: chased it down. In at 0 for 0, 208 behind. He made 52% of the team's 209. The team won by 9 wickets. The series was still to be settled in this Test. The rest of the team added only 100.

  16. 294 v India, Birmingham, 2011 · At home · Won

    A ton of consequence: carried the innings. In at 0 for 0, 224 behind. He made 41% of the team's 710. The team won by 242 runs. As an opener he put on 186 for the first wicket, and the second opener was not out until 710.

  17. 189 v Australia, Sydney, 2011 · Away · Won

    A good ton. The match was won. On the facts we have, the match didn't hinge on it.

  18. 133 v Sri Lanka, Cardiff, 2011 · At home · Won

    A good ton. The match was won. On the facts we have, the match didn't hinge on it.

  19. 106 v Sri Lanka, Lord's, 2011 · 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.

  20. 190 v India, Eden Gardens, 2012 · Away · Won

    A ton of consequence: carried the innings. He made 190, 36% of England's 523, after coming in at 0 for 0 with the team 316 behind. England won by 7 wickets.

  21. 176 v India, Ahmedabad, 2012 · Away · Lost

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

  22. 122 v India, Wankhede, 2012 · Away · Won

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

  23. 115 v South Africa, The Oval, 2012 · At home · Lost

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

  24. 130 v New Zealand, Leeds, 2013 · At home · Won

    A good ton. The match was won. On the facts we have, the match didn't hinge on it.

  25. 116 v New Zealand, Dunedin, 2013 · Away · Drawn

    A good ton. A good ton in a drawn match, not one that saved it.

  26. 263 v Pakistan, Abu Dhabi, 2015 · Neutral ground · Drawn

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

  27. 162 v New Zealand, Lord's, 2015 · At home · Won

    A good ton. The match was won. On the facts we have, the match didn't hinge on it.

  28. 105 v West Indies, Bridgetown, 2015 · Away · Lost

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

  29. 130 v India, Rajkot, 2016 · Away · Drawn

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

  30. 105 v Pakistan, Manchester, 2016 · At home · Won

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

  31. 244* v Australia, Melbourne, 2017 · Away · Drawn

    A good ton. A dead rubber (the series was already decided) that his side did not win.

  32. 243 v West Indies, Birmingham, 2017 · At home · Won

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

  33. 147 v India, The Oval, 2018 · At home · Won

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