- Kings XI Punjab 134 for 7 wickets in 20 overs
- Deccan Chargers 133 for 8 wickets in 20 overs
- Scoreboard
- Photos
Target of 135 runs to be scored in 20 overs
Score at end of 7 overs ... 49 for the loss of 2 wickets
Batting Resources still available was 70 % ... Remaining Chase Target % was 64 %
Hence at end of 7 overs ... Resource Clock favors Deccan
Score at end of 13 overs ... 79 for the loss of 3 wickets
Batting Resources still available was 45 % ... Remaining Chase Target % was 42 %
Hence at end of 13 overs ... Resource Clock still favors Deccan
Opening Overs and Middle Overs the "Resource Clock" indicated clearly that Deccan was ahead of the Resource Clock and was likely to win.
But Yuvraj's hat-trick turned the tables on Deccan. From the 14th over the Resource Clock turned against them and they could never catch up therafter despite Rohit Shrma's heroics.
In the End-Game Deccan did not manage their "Batting Resources" and paid the price.
========================================
Match 50 T20 - Delhi DareDevils Vs Rajasthan Royals at Bloemfontein - Delhi DareDevils won by 14 runs
- Delhi DareDevils 150 for 3 wickets in 20 overs
- Rajasthan Royals 136 for 9 wickets in 20 overs
- Scoreboard
Target of 151 runs to be scored in 20 overs
Score at end of 7 overs ... 26 for the loss of 3 wickets
Batting Resources still available was 64 % ... Remaining Chase Target % was 83 %
Hence at end of 7 overs ... Resource Clock against Rajasthan
Score at end of 13 overs ... 81 for the loss of 4 wickets
Batting Resources still available was 41 % ... Remaining Chase Target % was 46 %
Hence at end of 13 overs ... Resource Clock still in favor of Bangalore.
Opening Overs and Middle Overs the "Resource Clock" indicated clearly that Rajasthan was likely to lose.
Rajasthan Royals did not manage their "Batting Resources" efficiently ...they were behind of the "Resource Clock" for 19 of the 20 overs completed.
No comments:
Post a Comment