Cheteshwar Pujara
19 Test hundreds. Of the 19 we can measure, 3 were tons of consequence.
Who against, and where
| Hundreds | Tons of consequence | |
|---|---|---|
| Top tier (England, Australia, India) | 10 | 2 |
| Second tier (New Zealand, South Africa) | 3 | 0 |
| Third tier (Sri Lanka, West Indies, Pakistan) | 5 | 1 |
| Other (Bangladesh, Zimbabwe, Ireland, Afghanistan and the rest) | 1 | 0 |
| At home | 10 | 1 |
| Away | 9 | 2 |
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
206* v England, Ahmedabad, 2012 · At home · Won
A good ton. He made 40% of the team's runs. The match didn't hinge on it: he came in at 1 for 134.
159 v New Zealand, Hyderabad, 2012 · At home · Won
A good ton. He made 36% of the team's runs. The match didn't hinge on it: he came in at 1 for 49.
135 v England, Wankhede, 2012 · At home · Lost
A good ton. A loss: even a great hundred can't be a ton of consequence in a defeat.
204 v Australia, Hyderabad, 2013 · At home · Won
A ton of consequence: carried the innings. He scored 41% of the team's runs.
153 v South Africa, Johannesburg, 2013 · Away · Drawn
A good ton. A draw, and his side was never in danger of losing, so the hundred didn't save anything.
113 v West Indies, Wankhede, 2013 · At home · Won
A good ton. He made 23% of the team's runs. The match didn't hinge on it: he came in at 1 for 77.
145* v Sri Lanka, Colombo (SSC), 2015 · Away · Won
A ton of consequence: carried the innings. In at 0 for 0, level. He made 47% of the team's 312, and no one else came close. The team won by 117 runs. It was the decider of a level series. He added 104 for the 8th wicket.
124 v England, Rajkot, 2016 · At home · Drawn
A good ton. A draw, and his side was never in danger of losing, so the hundred didn't save anything.
119 v England, Visakhapatnam, 2016 · At home · Won
A good ton. He made 26% of the team's runs. The match didn't hinge on it: he came in at 1 for 6.
101* v New Zealand, Indore, 2016 · At home · Won
A good ton. His side already led by 274 when the innings began. He made 47% of the team's runs. The match didn't hinge on it: he came in at 0 for 11.
202 v Australia, Ranchi, 2017 · At home · Drawn
A good ton. The match was drawn, and his side was never in danger of losing, so the hundred didn't save anything.
153 v Sri Lanka, Galle, 2017 · Away · Won
A good ton. He made 26% of the team's runs. The match didn't hinge on it: he came in at 1 for 27.
143 v Sri Lanka, Nagpur, 2017 · At home · Won
A good ton. A slow grind: 40 runs per 100 balls off 362 balls, 100th run off ball 246, batted 3, innings 2. The match was won.
133 v Sri Lanka, Colombo (SSC), 2017 · Away · Won
A good ton. He made 21% of the team's runs. The match didn't hinge on it: he came in at 1 for 56.
132* v England, Southampton, 2018 · Away · Lost
A good ton. A loss: even a great hundred can't be a ton of consequence in a defeat.
123 v Australia, Adelaide, 2018 · Away · Won
A ton of consequence: carried the innings. In at 1 for 3, 3 ahead. He made 49% of the team's 250, and no one else came close. The team won by 31 runs. He added 62 for the 7th wicket. He faced an elite attack. The rest of the team added only 127.
106 v Australia, Melbourne, 2018 · Away · Won
A good ton. He came in comfortably, and the team did not depend on him.
193 v Australia, Sydney, 2019 · Away · Drawn
A good ton. A draw cut short by the weather: the weather saved the match, not the hundred.
102* v Bangladesh, Chattogram, 2022 · Away · Won
A good ton. His side already led by 324 when the innings began. He made 40% of the team's runs. The match didn't hinge on it: he came in at 1 for 70.