- Mumbai Indians 212 for 6 wickets in 20 overs
- Rajasthan Royals 208 for 7 wickets in 20 overs
- Scoreboard
Target of 213 runs to be scored in 20 overs
Score at end of 7 overs ... 43 for the loss of 3 wickets
Batting Resources still available was ... 64 %
Score at end of 7 overs ... 43 for the loss of 3 wickets
Batting Resources still available was ... 64 %
Remaining Chase Target % was ... 80 %
Shortage of capacity At hand ... - 16%
Shortage of capacity At hand ... - 16%
Hence at end of 7 overs ... Resource Clock against Rajasthan Royals
Score at end of 13 overs ... 131 for the loss of 4 wickets
Batting Resources still available was ... 41 %
Score at end of 13 overs ... 131 for the loss of 4 wickets
Batting Resources still available was ... 41 %
Remaining Chase Target % was ... 38 %
Excess capacity At hand .... +3 %
Hence at end of 13 overs ... Resource Clock slightly favors Rajasthan Royals
Opening Overs clearly were dominated by Mumbai indians based on the "Resource Clock", and the Middle Overs clearly indicated that Rajasthan Royals had fought back magnificently and were ahead of the Resource Clock, opening up the possibility of a win.
In the End-Game too Rajasthan Royals maintained the momentum and managed their "Batting Resources" fairly well, but lost the match in the last over, when they lost 2 wickets during the first 2 deliveries of the 20th over.
Yusuf Pathan's 100 in 37 balls was clearly the highlight, and his freak run-out during the 18th over, was a turning point.
A result by such a narrow margin of 4 runs in a target of 213 runs, was very exciting to follow using analytics in real time.
Rajasthan Royals were ahead of the Resource Clock Index for 8 overs and were behind in the remaining 12 overs.
No comments:
Post a Comment