India will meet Pakistan in Asia Cup Games
In the Asia Cup, India and Pakistan will compete against one another. At the Dubai International Cricket Stadium, the game will be played on August 28, 2022.
About
On August 28, 2022, the Asia Cup is scheduled to begin in the United Arab Emirates. India and Pakistan will once more face off against one another in the continental event. Since January 2013, the teams have only faced off in multi-team events, hence their matchup has grown significantly in importance. There is a good probability that they will play each other twice again in the latter stages of the competition
Let's take a look back at all the India vs. Pakistan matches that have already occurred during the Asia Cup before the T20I action between the teams begins at the Dubai International Cricket Stadium.
India defeated Pakistan in 2016 by 5 wickets
In the T20 phase of the tournament in Mirpur, India had dismissed Pakistan for just 83 runs. In order to put India in a vulnerable situation of 3 for 8, Amir dismissed both of the openers, Rohit Sharma and Ajinkya Rahane, for individual scores of zero. Virat Kohli's 49 off 51 helped India avoid looking foolish throughout the feeble chase, and the team finally won the match by 5 wickets with 27 balls remaining.
2018: Pakistan 2-0 India
In their Group A match, India thrashes Pakistan.
In their group encounter in Dubai, India defeated Pakistan by an easy margin of 8 wickets under the leadership of Rohit Shama. Pakistan was bowled out for 162 in their opening innings as Bhuvneshwar Kumar and Kedar Jadhav each claimed three wickets. Shikhar Dhawan and Rohit Sharma led the Indian innings in response, scoring 46 and 52 respectively, and the team easily won.
India maintains its supremacy
India defeated Pakistan by 9 wickets in the Super 4s game. As a result of Jaspreet Bumrah, Kuldeep Yadav, and Yuzvendra Chahal each taking two wickets, the latter could only manage 237 for 7. India beat Pakistan to home in 39.3 overs as a result of Shikhar Dhawan's 114 and Rohit Sharma's 111 not out in response.