Bangladesh Stuns Australia in Historic ODI Win as 2026 Series Kicks Off
The cricketing world witnessed a significant upset as Bangladesh clinched a historic 86-run victory over Australia in the opening One-Day In...
Longstanding Friendship: Virat Kohli and Ishant Sharma, both hailing from West Delhi, share a deep bond dating back to their Under-17 cricket days.
Pre-Match Reunion: The two players shared a passionate hug and conversation in the dugout before the RCB vs GT clash.
Historical Stats: In their past IPL encounters (2008-2024), Kohli has largely dominated Ishant, scoring 112 runs off 76 balls at a strike rate of 147.4, hitting 12 boundaries and 5 sixes, while Ishant has dismissed Kohli only once.
Early Setback for RCB: Despite the pre-match camaraderie, Kohli faced an early exit in the match, dismissed in the second over by GT's Arshad Khan.
Why this matters: The reunion highlights the strong personal bonds that exist within the competitive IPL environment. Kohli's early dismissal, however, was a significant blow to RCB's start and silenced the home crowd, underscoring the unpredictable nature of T20 cricket.
The reunion between Virat Kohli and Ishant Sharma served as a poignant reminder of their shared history before the high-stakes RCB vs GT encounter in IPL 2025. Ishant Sharma previously reminisced about their early days, stating, "We used to play Under-17s together in Kolkata and of course, we did not have much money. There we would eat egg rolls and have soft drinks after practice, and enjoy it. I've seen that side of Virat."
While their friendship was evident, the on-field battle took an unexpected turn. Historically, Kohli has had the upper hand against Sharma in the IPL. However, in this match, Kohli didn't get a chance to face his friend. He was dismissed early for just a few runs.
Facing a short delivery aimed at his body from GT pacer Arshad Khan, Kohli attempted his characteristic whip shot towards the leg side. Unfortunately for RCB fans, he hit it straight to Prasidh Krishna at deep backward square leg, who took a simple catch. This dismissal left RCB reeling at 13/2 in the third over, stunning the Chinnaswamy crowd and putting early pressure on the home team.
Q: Which teams were playing in the match?
A: Royal Challengers Bengaluru (RCB) were playing against Gujarat Titans (GT).
Q: Why was the reunion between Kohli and Ishant Sharma significant?
A: They are both prominent cricketers from Delhi and have been friends since their junior cricket days, making their pre-match interaction a notable moment of sportsmanship and camaraderie.
Q: How was Virat Kohli dismissed?
A: He was caught at deep backward square leg by Prasidh Krishna off the bowling of Arshad Khan early in the innings.
Personal connections often transcend on-field rivalries, as seen with Kohli and Ishant.
Even star players like Virat Kohli can face unexpected early dismissals, highlighting the unpredictable nature of IPL matches.
An early wicket of a key player can significantly impact a team's momentum and the atmosphere in the stadium.
The bond between players adds another layer to the excitement of the IPL. Do you think early setbacks like Kohli's dismissal define the outcome of a match? Let us know!
Share this article with others who need to stay ahead of this trend!
Source: Delhi Boys Reunite! Virat Kohli Gives Warm Hug To Ishant Sharma Ahead Of RCB Vs GT Clash | OneCricket target="_blank"
The cricketing world witnessed a significant upset as Bangladesh clinched a historic 86-run victory over Australia in the opening One-Day In...
Bangladesh has commenced its 2026 white-ball series against Australia with a resounding 86-run victory in the first One Day International (O...
Venkatesh Iyer, the left-handed all-rounder who played crucial innings during Royal Challengers Bengaluru’s (RCB) IPL 2026 playoff run, was ...
Royal Challengers Bengaluru (RCB) launched a stunning assault in the IPL 2026 final, setting a new record for the fastest team fifty in an I...
⚠ Disclaimer: Yanuki provides article summaries and links for reference only. Yanuki does not endorse, verify, or guarantee the accuracy of third-party sources. Please review original sources and verify information independently. Managed by the Yanuki Data Engine. Full Disclaimer