Sean Abbott played his biggest innings in T20 (Photo: Instagram/Surrey)
New Delhi: Even if there is talk of Shubman Gill’s century in India. But, the century which has been scored in England, is more stormy than the Gill one. It is the fourth fastest century in T20 cricket history. We are talking Sean Abbott Scored a blistering century from the bat of In the T20 league Vitality Blast being played in England, all-rounder Shaun Abbott scored a century for his team in a difficult time.
The match was between Surrey and Kent. Surrey came out to bat first in this match. Australian all-rounder Shaun Abbott was also part of the Surrey team. From number one to number 5 in the top order, there were such batsmen that there was little hope for Shaun Abbott to do much.
Learn here: How did Sean Abbott become the reason for the batsman’s death?
Top order failed, then the game of number six batsman showed
But, Surrey’s top order failed in this match. None of the top 5 batsmen even touched the figure of 20 runs. The result was that till the 13th over, even 100 runs were not added to his score board and 5 batsmen were sitting in the dugout.
After the surrender of Surrey’s top order, Kent’s team must have started to see their victory almost certain. But the work of turning water on his plan was done by the number six batsman Sean Abbott. As soon as Abbott stepped on the crease, he started swinging the bat and in no time the situation on the ground started turning.
Shaun Abbott scored the fourth fastest century in T20
Shaun Abbott completed his century in just 34 balls, which is the fourth fastest century scored in T20. In this case, he equaled the record of Andrew Symonds. Abbott’s full innings was of 41 balls, in which he scored 110 not out. In this inning played at a strike rate of more than 268, Abbott hit 11 sixes and 4 fours.
The partnership of 129 runs in 46 balls became the reason for the victory.
Abbott shared a 129-run partnership with Clarke for the sixth wicket in just 46 balls, which resulted in Surrey scoring 223 runs in 20 overs. Now Kent There was a mountain-like target of 224 runs in front of them. But, Kent’s team could only manage 187 runs for 7 wickets in 20 overs and lost the match by 41 runs.