Rd Blaster won the match by 11 run
Player of the Match: Shivans
| Team | Rd Blaster |
| Points | 78.0 |
| Runs | 8 (5) |
| Sixes | 1 |
| Fours | 0 |
| Strike Rate | 160.00 |
| Wickets Taken | 2 |
| Economy Rate | 3.00 |
| Catches | 0 |
| Stumpings | 0 |
| Run Outs | 0 |
Cric'O Scoring
| Team | Rd Blaster |
| Points | 50.0 |
| Runs | 0 (0) |
| Sixes | 0 |
| Fours | 0 |
| Strike Rate | 0.00 |
| Wickets Taken | 2 |
| Economy Rate | 9.00 |
| Catches | 0 |
| Stumpings | 0 |
| Run Outs | 0 |
| Team | Rd Blaster |
| Points | 34.0 |
| Runs | 4 (5) |
| Sixes | 0 |
| Fours | 0 |
| Strike Rate | 80.00 |
| Wickets Taken | 1 |
| Economy Rate | 4.00 |
| Catches | 0 |
| Stumpings | 0 |
| Run Outs | 0 |
| Team | Rd Emirates |
| Points | 60.0 |
| Runs | 0 (0) |
| Sixes | 0 |
| Fours | 0 |
| Strike Rate | 0.00 |
| Wickets Taken | 2 |
| Economy Rate | 4.00 |
| Catches | 0 |
| Stumpings | 0 |
| Run Outs | 0 |
| Team | Rd Emirates |
| Points | 40.0 |
| Runs | 0 (2) |
| Sixes | 0 |
| Fours | 0 |
| Strike Rate | 0.00 |
| Wickets Taken | 2 |
| Economy Rate | 11.00 |
| Catches | 0 |
| Stumpings | 0 |
| Run Outs | 0 |
Rd Emirates won the toss and opted to Bowl first.
Rd Blaster won the match by 11 run
Player of the match: Shivans
Rd Blaster faced off against Rd Emirates in a recent cricket match. Rd Blaster won the match by 11 runs. This analysis focuses solely on the provided match data to objectively summarise the key aspects of the game.
The Rd Blaster innings saw varying contributions from its batsmen. Yadnesh scored 9 runs off 13 balls, maintaining a strike rate of 69.2, with no boundaries (4s or 6s). Shivans contributed 8 runs from 5 balls, achieving a strike rate of 160, including one six. Sarthak P scored 4 runs off 6 balls, with a strike rate of 66.7, and no boundaries.
Rd Emirates' chase involved Sohamb scoring 6 runs off 10 balls, resulting in a strike rate of 60, with no boundaries. Parth scored 4 runs off 5 balls, achieving a strike rate of 80, also without any boundaries. Kunala scored 3 runs off 2 balls, registering a strike rate of 150, and similarly, no boundaries.
The provided data does not contain any information regarding specific fielding events during the match. Therefore, no analysis of catches, run-outs, or other fielding contributions can be made.
Rd Blaster won the match against Rd Emirates by a margin of 11 runs. The analysis is based solely on the batting and bowling performance data provided.
A closer look at Rd Blaster's batting reveals a struggle to accelerate the scoring rate. Yadnesh's innings, while providing some stability, lacked the boundary hitting needed to build momentum. His strike rate of 69.2 indicates a focus on rotating the strike rather than attacking the bowlers. Shivans' brief cameo provided a much-needed injection of aggression, with his strike rate of 160 highlighting his intent to score quickly. The single six he hit was a valuable contribution. Sarthak P's innings was similar to Yadnesh's, prioritizing stability but lacking the impetus to increase the run rate. The overall batting performance suggests a need for more aggressive intent from the top order to set a more challenging target.
Rd Emirates' chase was characterized by a similar struggle to score quickly. Sohamb's innings of 6 runs off 10 balls indicates a slow start, with a strike rate of just 60. This lack of early momentum put pressure on the subsequent batsmen. Parth's innings, while slightly more fluent with a strike rate of 80, still lacked the boundary hitting needed to accelerate the scoring. Kunala's brief innings showed intent to score quickly, with a strike rate of 150, but he was unable to convert this into a significant contribution. The absence of boundaries throughout the innings highlights a difficulty in finding the gaps in the field and putting pressure on the Rd Blaster bowlers. The chase ultimately fell short due to a combination of slow scoring rates and a lack of boundary hitting.
The bowling statistics for both teams are uniformly zero across all categories. Kartik, Shravan, and Tanmay for Inning 1, and Shivans, Kalp, and Om G for Inning 2, all recorded 0 wickets, conceded 0 runs, bowled 0 overs, and therefore had an economy of 0. This uniform lack of data prevents any meaningful analysis of bowling performance. It is impossible to determine which bowlers were effective, which spells were crucial, or how the bowling attack contributed to the final result based on the information provided.
As previously noted, the absence of fielding data significantly limits the scope of this analysis. Fielding can often be a crucial factor in determining the outcome of a cricket match, with sharp catches, timely run-outs, and efficient ground fielding all contributing to restricting the opposition's score and building pressure. Without information on the number of catches taken, run-outs executed, or the overall quality of the fielding performance, it is impossible to assess the impact of fielding on the match result. In future analyses, the inclusion of comprehensive fielding statistics would provide a much more complete picture of the game.
Inning1:
Inning2:
