Sports

VIDEO: Hardik Pandya Boasted Of Captaincy, Abused Senior Player

PBKS Vs GT: In cricket, captains often get angry with their fellow players for poor bowling and fielding. In the past, this incident was seen between Punjab Kings (PBKS) and Gujarat Titans (GT). In fact, during the bowling in the 20th over, Gujarat’s senior player Mohit Sharma has seen fielding.

During this time, he got a little confused about his position, after which Gujarat captain Hardik Pandya attacked him. They were so enraged that they even ended up abusing them. This whole matter was caught on camera, and a related video has also become a topic of discussion.

Hardik Pandya Raging On Senior Player

In yesterday’s match, the teams of Punjab Kings and Gujarat Titans were face-to-face with each other. Gujarat won the toss and decided to bowl first; Hardik Pandya handed the ball to Joshua Little for the 20th over during the bowling. Senior player Mohit Sharma was fielding in the deep cover during that time. He was confused, after which he stood apart from his position.


However, when Hardik Pandya saw it, he got angry at Mohit Sharma. At first, Hardik asked him to go to his position, and after that, he also abused the senior player a lot in anger. Whose video was captured in the camera, and now that video of Hardik is going viral very fast on social media.

Gujarat Crushed Punjab At Home

Talking about yesterday’s match, the Punjab team, which came out to bat first, scored 153 runs in 20 overs after losing 8 wickets. For Punjab, Mat Short, Jitesh Sharma and Shah Rukh Khan played brilliant innings of 36, 25 and 22 runs, respectively.

On the other hand, Gujarat Titans, who came to compete with Punjab, won this match by 6 wickets. For Gujarat, Shubman Gill, Wriddhiman Saha and Sai Sudarshan played innings of 67, 30 and 19 runs, respectively.

OM Prakash is responsible for maintaining and improving News Waker's website. He ensures the site is user-friendly, accessible, and up-to-date with the latest web technologies.

Related Posts

1 of 326
function redirect_on_click() { ?>