Twitter reacts as Jason Roy takes down Umpire after his century
It was a stellar batting performance by England as they posted a mammoth total of 386 runs and opener Jason Roy found his form back and went on to score a thumping 153. While running his 100th run, Roy rammed into the umpire and Twitterati went berserk after witnessing the same.
Unusual way to celebrate a 100!
That's one way to celebrate a world cup hundred... 😂 #bbccricket #CWC19 #ENGvBAN pic.twitter.com/ajF1EidpKw
— Test Match Special (@bbctms) June 8, 2019
He just rammed into the umpire!
Talking about comedy of errors, #Roy smashed 100 and knocked down the #Umpire 🤣🤣#ENGvBAN
— MrFazz (@FazzFizzy) June 8, 2019
Being Indian!
That's how indian drama's love story begins!!🤣 La La La LaLaLaaaa!!👬
— Aisha Zaman💥 (@AishaZaman96) June 8, 2019
Feeling sorry for the umpire!! 🕴#ENGvBAN #cwc19 #WeAreEngland #RiseOfTheTigers #Bangladesh #England pic.twitter.com/CKrCaFDYPY
Quite Funny!😒
A Roy breaking Bengali hearts. That doesn't happen too often! #EngVBan
— Joy Bhattacharjya (@joybhattacharj) June 8, 2019
Bangladesh must be regretting their decision to bowl first!
England is playing a completely different brand of cricket. Their relentlessness when it comes to hitting is scary...batting first gives them more teeth. #CWC19 #EngvBan
— Aakash Chopra (@cricketaakash) June 8, 2019
What decision BTW?
Worst decision ever by a Bangladeshi Captain @BCBtigers. Game is over. #ENGvBAN
— Hillol (@HillolNaha16) June 8, 2019
7th consecutive 300+
ENG get their usual 350+ total, their 7th consecutive 300+ as well! Jeez these guys can tonk the ball! #ENGvBAN #CWC19
— Anish Telkikar (@telkikar_anish) June 8, 2019
LoL!
Jason Roy's innings in numbers:
— Matthew Conroy (@MattConroy6) June 8, 2019
153 runs
121 balls
14 fours
5 sixes
1 umpire flattened#bbccricket
Poor Bangladesh!
Bangladesh putting pace on the ball is exactly what England want ... #OnOn
— Michael Vaughan (@MichaelVaughan) June 8, 2019
Incredible!
New record. 7 consecutive 300 plus scores for England. SPARTAAAAA #ENGvBAN
— Gaurav Kapur (@gauravkapur) June 8, 2019
Comments
Leave a comment0 Comments