Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
Rajasthan Royals captain, Sanju Samson, on Wednesday (April 16), retired wounded against Delhi capitals at the Arun Jaitley Stadium in Delhi.
The incident took place in the sixth in the entrances of Rajasthan Royals when he was in front of Viraj Nigam, of the spinist of his legs.
In the third ball of the overwhelming, Delhi Capital Spinner tilted a faster Googly that was outside the strain.
Your daily dose of cricket!
Sanju tried to go down, but he could not contact the ball. In the process, he ended up doing it.
Shortly after losing his shot, Sanju Samson looked at pain and saw his left arm stretch while seeing that he suffered an injury next to him.
Also read: Clock: Sandeep Sharma shot the ball to Maheesh Theekshana after it leaves Tristan Stubbs
Physio went out into the field to attend the Batsman on the right. Sanju Samson was seen to have a tablet before practicing his bat ray to ensure he was OK to continue. For the relief of Rajasthan Royals, his captain decided to continue, but happiness was short.
He hit the next ball from overcoming to Long Off but decided to take a single one. He looked back in pain and decided to get out of the field.
Rajasthan Royals will desperately wait for the injury to be not serious and his captain remains available for the next games. Sanju Samson also played the first three games of the ongoing season only as Batsman due to an injury.
Before retiring, the right hand had a good touch. Broke 31 runs of only 19 balls with the help of two four and three six. Rajasthan Royals was 61/0 when his captain left the pitch.
At the time of writing this report, they were 88/1 in tenth place with Yasasvi Jaiswal and Nitish Rana Batting in the center. After Samson’s departure, the Royals also lost the Riyan Parag wick. Parag was cleaned to Axa Patel for 8 runs. At the beginning of the game, Delhi Capitals finished his entrance in 188/5.
– Cricalk (@cricalk7) April 16, 2025
– Cricalk (@cricalk7) April 16, 2025
– Cricalk (@cricalk7) April 16, 2025