Sachin Cricket Trivia from the Web
*****
Setting records has become commonplace for Sachin Tendulkar. He is the all time leader for runs and centuries in both five dat Tests and one day internationals. He has reached 30,000 runs in all forms, with his closest rival, Ricky Ponting of Australia, still 6000 behind.
*****
Sachin has five calendar years with 1000 or more runs - 2008 (1063), 2002 (1392), 1999 (1088) and 1997 ( 1000 runs). Sunil Gavaskar is the only other indian with four seasons of 1000+ runs. Only Tendulkar, Hayden, Ponting and Lara have five seasons with 1000 or more runs in Test cricket.
*****
Sachin has scored centuries against all Test playing countries. He is the third batsman to achieve this distinction after Steve Waugh and Gary Kirsten. The current list also includes Lara, Ponting, Dravid, Kallis, Gilchrist and Atapattu.
*****
Saturday, December 12, 2009
Fundamental Analysis ... 2009 India Vs SriLanka ... T20 - 2nd Match
India Vs Sri Lanka played at Mohali, Chandigarh - India won by 6 wickets
- Sri Lanka 206 for 7 wickets in 20 overs
- India 211 for 4 wickets in 19.1 overs
- Scoreboard
- Photos
Target of 207 runs to be scored in 20 overs
Score at end of 7 overs ... 66 for the loss of one wicket
Batting Resources still available was ... 75 %
Score at end of 7 overs ... 66 for the loss of one wicket
Batting Resources still available was ... 75 %
Remaining Chase Target % was ... 68 %
Hence at end of 7 overs ... Resource Clock favors India
Score at end of 13 overs ... 142 for the loss of 2 wickets
Batting Resources still available was ... 48 %
Hence at end of 7 overs ... Resource Clock favors India
Score at end of 13 overs ... 142 for the loss of 2 wickets
Batting Resources still available was ... 48 %
Remaining Chase Target % was ... 31 %
Hence at end of 13 overs ... Resource Clock continues to favor India significantly
Opening Overs and Middle Overs the "Resource Clock" clearly indicated that India was ahead of the Resource Clock and was likely to win.
In the End-Game India kept the momentum and did manage their "Batting Resources" better and it was quite sufficient.
Hence at end of 13 overs ... Resource Clock continues to favor India significantly
Opening Overs and Middle Overs the "Resource Clock" clearly indicated that India was ahead of the Resource Clock and was likely to win.
In the End-Game India kept the momentum and did manage their "Batting Resources" better and it was quite sufficient.
Overall India dominated the chase and were ahead of the "Resource Clock" for all the 19 overs, to win the game with 6 wickets and 5 balls to spare.
Saturday, December 5, 2009
Amit's ... Did You Know ........... (5)
Cricket Trivia from the Web
*****
Which cricketer faced the first ball in One Day Cricket...?
Geoff Boycott of England was the one who faced the first ball.
Graham Mckenzie of Australia was the bowler.
*****
In the first ever Test match in 1877, Australia defeated England by 45 runs.
100 years later, in the Centenary test, the result was exactly the same.
*****
Which style of play is known as a "MANKAD" ...?
The running out of a non-striking batsman who leaves his crease before the bowler has released the ball is called doing a "MANKAD".
It is named after Indian Test all-rounder Vinoo Mankad, who used this method controversially in a Test match.
*****
*****
Which cricketer faced the first ball in One Day Cricket...?
Geoff Boycott of England was the one who faced the first ball.
Graham Mckenzie of Australia was the bowler.
*****
In the first ever Test match in 1877, Australia defeated England by 45 runs.
100 years later, in the Centenary test, the result was exactly the same.
*****
Which style of play is known as a "MANKAD" ...?
The running out of a non-striking batsman who leaves his crease before the bowler has released the ball is called doing a "MANKAD".
It is named after Indian Test all-rounder Vinoo Mankad, who used this method controversially in a Test match.
*****
Saturday, November 28, 2009
Fundamental Analysis ... 2009 New Zealand Vs Pakistan ... 1st Test
1st Test New Zealand Vs Pakistan at University Oval, Dunedin - New Zealand won by 32 runs
Top Order Average
Lower-Order Average
Performance Metric Difference ........ Almost Zero neither team outperformed the other significantly
- New Zealand 1st Innings 429
- Pakistan 1st Innings 332
- New Zealand 2nd Innings 153
- Pakistan 2nd innings 218
- Scoreboard
- Photos
Top Order Average
New Zealand............................. 16.5 runs
Pakistan .................................... 11.2
Difference ................................. 5.3
Middle Order Average
Pakistan .................................... 11.2
Difference ................................. 5.3
Middle Order Average
New Zealand............................. 41.9 runs
Pakistan .................................... 57.9
Difference ................................. -16.0
Lower-Order Average
New Zealand............................. 31.7 runs
Pakistan .................................... 13.0
Difference ................................. 18.7
Performance Metric Difference ........ Almost Zero neither team outperformed the other significantly
Fundamental Analysis ... 2009 India Vs Sri Lanka ... 2nd Test
2nd Test India Vs New Zealand at Green Park, Kanpur - India won by an innings and 144 runs
Top Order Average
- India 1st Innings 642
- Sri Lanka 1st Innings 229
- Sri Lanka 2nd Innings 269
- Scoreboard
- Photos
Top Order Average
India ............................................ 147.3 runs
Sri Lanka .................................... 20.7
Difference .................................... 126.7
Middle Order Average
Sri Lanka .................................... 20.7
Difference .................................... 126.7
Middle Order Average
India .................................................. 43.5 runs
Sri Lanka ........................................... 33.3
Difference .......................................... 10.2
Lower-Order Average
Sri Lanka ........................................... 33.3
Difference .......................................... 10.2
Lower-Order Average
India ............................................... 08.7 runs
Sri Lanka ....................................... 20.1
Difference ...................................... -11.5
Performance Metric Difference ........ 8.7 in favor of India
Sri Lanka ....................................... 20.1
Difference ...................................... -11.5
Performance Metric Difference ........ 8.7 in favor of India
Amit's ... Did You Know ........... (4)
Cricket Trivia from the Web
*****
Pakistani speedster Mohammad Sami bowled seven wides and four no-balls to concede twenty-two runs in his 17 ball over against Bnagladesh in an Asia Cup 2004 match.
*****
In a Pakistan Vs England ODI at Perth in January 1987, Ramiz Raja was caught of a no-ball, but failing to hear the umpire's call, left his crease to return to the pavilion. He was then given out, run out by the square leg umpire.
*****
Former captains, David Gower of England, Stephen Fleming of New Zealand and India's Ajit Wadekar, another left hander, were all born on Apeil Fool's Day (April 1).
*****
*****
Pakistani speedster Mohammad Sami bowled seven wides and four no-balls to concede twenty-two runs in his 17 ball over against Bnagladesh in an Asia Cup 2004 match.
*****
In a Pakistan Vs England ODI at Perth in January 1987, Ramiz Raja was caught of a no-ball, but failing to hear the umpire's call, left his crease to return to the pavilion. He was then given out, run out by the square leg umpire.
*****
Former captains, David Gower of England, Stephen Fleming of New Zealand and India's Ajit Wadekar, another left hander, were all born on Apeil Fool's Day (April 1).
*****
Saturday, November 7, 2009
Amit's ... Did You Know ........... (3)
Cricket Trivia from the Web
The only stadium to witness a first ball dismissal on its debut as a Test Match cenre is the Sawai Man Singh stadium in Jaipur. Sunil Gavaskar was caught by Javed Miandad off Imran khan on the first ball of the India-Pakistan test match in1987 which was the stadium's first match.
*****
The match between New Zealand and India at Auckland on Feb 14 1981 was the first in New Zealand in which colored clothing, white balls, and black sight screens were employed.
*****
In a West Indies vs. England match at Scarborough, a throw from the boundary by Michael Holding hit one set of stumps and went on to hit the other set as well. The batsmen were out of their creases but the umpires were too confused to give either out.
*****
Geoff Boycott confused both scorers and umpires when he took strike at the wrong end, following a drinks interval, England vs. Australia at Sydney December 1979.
*****
Geoff Boycott confused both scorers and umpires when he took strike at the wrong end, following a drinks interval, England vs. Australia at Sydney December 1979.
*****
2009 India Vs Australia ... ODI ... 5
November 05 2009 ... India Vs Australia at Hyderabad - Australia India won by 3 runs
Analytics Behind India's Chase
Target of 351 runs to be scored in 50 overs
Score at end of 17 overs ... 113 for the loss of 2 wickets
Batting Resources still available was 71 % ...
- Australia 350 for 4 wickets in 50 overs
- India 347 all out in 49.4 overs
- Scoreboard
- Photos
Analytics Behind India's Chase
Target of 351 runs to be scored in 50 overs
Score at end of 17 overs ... 113 for the loss of 2 wickets
Batting Resources still available was 71 % ...
Remaining Chase Target % was 68 %
Hence at end of 17 overs ... Resource Clock is in favor of India
Score at end of 34 overs ... 235 for the loss of 4 wickets
Batting Resources still available was 39 % ...
Hence at end of 17 overs ... Resource Clock is in favor of India
Score at end of 34 overs ... 235 for the loss of 4 wickets
Batting Resources still available was 39 % ...
Remaining Chase Target % was 33 %
Hence at end of 34 overs ... Resource Clock is still in favor of India
During the Opening Overs and Middle Overs India chased their target well by being ahead of the Resource Clock Index. But during the End Overs, India kept losing wickets and despite being ahead marginally of the "Resource Clock" lost the match by 3 runs with 2 balls to spare.
Hence at end of 34 overs ... Resource Clock is still in favor of India
During the Opening Overs and Middle Overs India chased their target well by being ahead of the Resource Clock Index. But during the End Overs, India kept losing wickets and despite being ahead marginally of the "Resource Clock" lost the match by 3 runs with 2 balls to spare.
2009 India Vs Australia ... ODI ... 4
November 02 2009 ... India Vs Australia at Mohali, Chandigarh - Australia India won by 24 runs
Analytics Behind India's Chase
Target of 251 runs to be scored in 50 overs
Score at end of 17 overs ... 89 for the loss of 2 wickets
Batting Resources still available was 71 % ...
- Australia 250 all out in 49.2 overs
- India 226 all out in 46.4 overs
- Scoreboard
- Photos
Analytics Behind India's Chase
Target of 251 runs to be scored in 50 overs
Score at end of 17 overs ... 89 for the loss of 2 wickets
Batting Resources still available was 71 % ...
Remaining Chase Target % was 65 %
Hence at end of 17 overs ... Resource Clock is in favor of India
Score at end of 34 overs ... 155 for the loss of 5 wickets
Batting Resources still available was 35 % ...
Hence at end of 17 overs ... Resource Clock is in favor of India
Score at end of 34 overs ... 155 for the loss of 5 wickets
Batting Resources still available was 35 % ...
Remaining Chase Target % was 38 %
Hence at end of 34 overs ... Resource Clock is now against India
During the Opening Overs India chased their target well by being ahead of the Resource Clock Index. But during the Middle Overs the "Resource Clock" clearly indicated that that India was NOT chasing their target well by losing wickets and were well behind the Resource Clock.
India kept losing wickets during the End-Overs phase as well and lost the match by 24 runs, though India was ahead of the "Resource Clock" for 26 overs and were behind in 21 of them.
Hence at end of 34 overs ... Resource Clock is now against India
During the Opening Overs India chased their target well by being ahead of the Resource Clock Index. But during the Middle Overs the "Resource Clock" clearly indicated that that India was NOT chasing their target well by losing wickets and were well behind the Resource Clock.
India kept losing wickets during the End-Overs phase as well and lost the match by 24 runs, though India was ahead of the "Resource Clock" for 26 overs and were behind in 21 of them.
2009 India Vs Australia ... ODI ... 3
October 31 2009 ... India Vs Australia at Feroz Shah Kotla, Delhi - India won by 6 wickets
Analytics Behind India's Chase
Target of 230 runs to be scored in 50 overs
Score at end of 17 overs ... 64 for the loss of 3 wickets
Batting Resources still available was 64 % ...
- Australia 229 for 5 wickets in 50 overs
- India 230for 4 wickets 48.2 overs
- Scoreboard
- Photos
Analytics Behind India's Chase
Target of 230 runs to be scored in 50 overs
Score at end of 17 overs ... 64 for the loss of 3 wickets
Batting Resources still available was 64 % ...
Remaining Chase Target % was 72 %
Hence at end of 17 overs ... Resource Clock is clearly against India
Score at end of 34 overs ... 147 for the loss of 3 wickets
Batting Resources still available was 42 % ...
Hence at end of 17 overs ... Resource Clock is clearly against India
Score at end of 34 overs ... 147 for the loss of 3 wickets
Batting Resources still available was 42 % ...
Remaining Chase Target % was 36 %
Hence at end of 34 overs ... Resource Clock now clearly favors India
During the Opening Overs Australia was defending their target by taking wickets regularly. But during the Middle Overs the "Resource Clock" clearly indicated that that India was chasing the target well and were well ahead of the Resource Clock and were likely to win.
India led the chase well and were ahead of the "Resource Clock" for 38 overs and were behind in 11 of them, to win the game by 6 wickets.
Hence at end of 34 overs ... Resource Clock now clearly favors India
During the Opening Overs Australia was defending their target by taking wickets regularly. But during the Middle Overs the "Resource Clock" clearly indicated that that India was chasing the target well and were well ahead of the Resource Clock and were likely to win.
India led the chase well and were ahead of the "Resource Clock" for 38 overs and were behind in 11 of them, to win the game by 6 wickets.
Saturday, October 31, 2009
Amit's ... Did You Know ........... (2)
Cricket Trivia from the Web
Making his debut for England against Bangladesh in 2005, Chris Tremlett took two wickets in two balls. On his hat trick ball Mohammed Ashraful defended the ball which bounced on the ground, then actually landed on the stumps but the bails did not fall, and so Tremlett was denied a hat trick.
*****
English Test cricketer Alan Hill dismissed Nat Thomson for 1 to take the first test wicket.
*****
New Zealand played their first ever Test Match in 1930 not long before India played her first Test match in 1932.
*****
Sri Lanka used different wicket keepers in each Test match when they hosted the India-Sri Lanka 3 test series in 1994 - Ashley de Silva, Pubudu Dassanayake, and Romesh Kaluwitharna
*****
2009 India Vs Australia ... ODI ... 2
October 28 2009 ... India Vs Australia at Jamtha Stadium, Nagpur - India won by 99 runs
Analytics Behind Australia's Chase
Target of 355 runs to be scored in 50 overs
Score at end of 17 overs ... 81 for the loss of 3 wickets
Batting Resources still available was 35 % ... Remaining Chase Target % was 56 %
Hence at end of 34 overs ... Resource Clock now clearly favors India and Australia is way behind
During the Opening Overs and Middle Overs the "Resource Clock" clearly indicated that that India was defending the target and Australia was well behind the Resource Clock and was liklely to lose.
India dominated the defense and put Australia under pressure during the entire match and were ahead of the "Resource Clock" for all but 4 overs, to win the game by 99 runs.
- India 354 for 7 wickets in 50 overs
- Australia 255 all out in 48.3 overs
- Scoreboard
- Photos
Analytics Behind Australia's Chase
Target of 355 runs to be scored in 50 overs
Score at end of 17 overs ... 81 for the loss of 3 wickets
Batting Resources still available was 64 % ... Remaining Chase Target % was 77 %
Hence at end of 17 overs ... Resource Clock strongly is against Australia
Score at end of 34 overs ... 156 for the loss of 5 wickets
Hence at end of 17 overs ... Resource Clock strongly is against Australia
Score at end of 34 overs ... 156 for the loss of 5 wickets
Batting Resources still available was 35 % ... Remaining Chase Target % was 56 %
Hence at end of 34 overs ... Resource Clock now clearly favors India and Australia is way behind
During the Opening Overs and Middle Overs the "Resource Clock" clearly indicated that that India was defending the target and Australia was well behind the Resource Clock and was liklely to lose.
India dominated the defense and put Australia under pressure during the entire match and were ahead of the "Resource Clock" for all but 4 overs, to win the game by 99 runs.
2009 India Vs Australia ... ODI ... 1
October 25 2009 ... India Vs Australia at Reliance Stadium, Vadodara - Australia won by 4 runs
Analytics Behind India's Chase
Target of 293 runs to be scored in 50 overs
Score at end of 17 overs ... 87 for the loss of 2 wickets
Batting Resources still available was 71 % ... Remaining Chase Target % was 70 %
Hence at end of 17 overs ... Resource Clock marginally favors India
Score at end of 34 overs ... 167 for the loss of 3 wickets
Batting Resources still available was 42 % ... Remaining Chase Target % was 43 %
Hence at end of 34 overs ... Resource Clock now marginally favors Australia
During the Opening Overs and Middle Overs the "Resource Clock" clearly indicated that that both the teams were neck and neck with regard to Resource Clock and a close match was likely.
Australia dominated the defense and put India under pressure during the End Overs and were ahead of the "Resource Clock" for all but 10 overs, to win the game by 4 runs. At the the end of 49 overs India were 284 for 7 and were slightly ahead of the Resource Clock, but India scoring only 4 runs during the last over put Australia ahead.
- Australia 292 for 8 wickets in 50 overs
- India 288 for 8 wickets in 50 overs
- Scoreboard
- Photos
Analytics Behind India's Chase
Target of 293 runs to be scored in 50 overs
Score at end of 17 overs ... 87 for the loss of 2 wickets
Batting Resources still available was 71 % ... Remaining Chase Target % was 70 %
Hence at end of 17 overs ... Resource Clock marginally favors India
Score at end of 34 overs ... 167 for the loss of 3 wickets
Batting Resources still available was 42 % ... Remaining Chase Target % was 43 %
Hence at end of 34 overs ... Resource Clock now marginally favors Australia
During the Opening Overs and Middle Overs the "Resource Clock" clearly indicated that that both the teams were neck and neck with regard to Resource Clock and a close match was likely.
Australia dominated the defense and put India under pressure during the End Overs and were ahead of the "Resource Clock" for all but 10 overs, to win the game by 4 runs. At the the end of 49 overs India were 284 for 7 and were slightly ahead of the Resource Clock, but India scoring only 4 runs during the last over put Australia ahead.
Saturday, October 24, 2009
Amit's ... Did You Know ........... (1)
*****
The first laws of cricket were written in 1774. Since then they have been modified on numerous occasions. Pretty much everything has changed. The early versions of the cricket bat were long curved pieces of wood, resembling a thick hockey stick. The stumps consisted of two wickets and one bail in between. The only law of the game that has remained constant is the length of the pitch at twenty two yards.
*****
Sachin Tendulkar, Waqar Younis, and Salil Ankola all made their Test Match debut at Karachi in 1989.
*****
Sri Lankan ex-skipper Marvan Atapattu's first six Test innings scores were 0,0,1,0,0,0.
*****
There are ten ways in which a batsman can dismissed or get out: Caught, Bowled, LBW, Run-Out, Stumped, Handling The Ball, Obstructing The Field, Hit The Ball Twice, Hit-Wicket, Timed Out
*****
In the 1997-98 Test Match at Faisalabad, Mushtaq Ahmed was bowling to Pat Symcox. Symcox missed the ball, which went between the stumps , knocking back the middle stump. However the heat had fused together the bails, which did not fall. The middle stump bounced back into place, and Symcox continued on his way to 81 - his second highest Test score.
*****
The first laws of cricket were written in 1774. Since then they have been modified on numerous occasions. Pretty much everything has changed. The early versions of the cricket bat were long curved pieces of wood, resembling a thick hockey stick. The stumps consisted of two wickets and one bail in between. The only law of the game that has remained constant is the length of the pitch at twenty two yards.
*****
Sachin Tendulkar, Waqar Younis, and Salil Ankola all made their Test Match debut at Karachi in 1989.
*****
Sri Lankan ex-skipper Marvan Atapattu's first six Test innings scores were 0,0,1,0,0,0.
*****
There are ten ways in which a batsman can dismissed or get out: Caught, Bowled, LBW, Run-Out, Stumped, Handling The Ball, Obstructing The Field, Hit The Ball Twice, Hit-Wicket, Timed Out
*****
In the 1997-98 Test Match at Faisalabad, Mushtaq Ahmed was bowling to Pat Symcox. Symcox missed the ball, which went between the stumps , knocking back the middle stump. However the heat had fused together the bails, which did not fall. The middle stump bounced back into place, and Symcox continued on his way to 81 - his second highest Test score.
*****
Saturday, October 3, 2009
2009 Champions Trophy...Australia Vs Pakistan
September 30 2009 ... Champion's Trophy - Australia Vs Pakistan at Supersport Park, Centurion - Australia won by 2 wickets
Analytics Behind Australia's Chase
Target of 206 runs to be scored in 50 overs
Score at end of 17 overs ... 85 for the loss of 2 wickets
Batting Resources still available was 71 % ... Remaining Chase Target % was 59 %
Hence at end of 17 overs ... Resource Clock favors Australia
Score at end of 34 overs ... 144 for the loss of 3 wickets
Batting Resources still available was 42 % ... Remaining Chase Target % was 30 %
Hence at end of 34 overs ... Resource Clock still favors Australia
During the Opening Overs and Middle Overs the "Resource Clock" clearly indicated that Australia was ahead of the Resource Clock and was likely to win.
Overall Australia dominated the chase and were ahead of the "Resource Clock" for all but 2 overs, to win the game by 2 wickets. At the the end of 46 overs Australia were 188 for 8 and were behind the Resource Clock, but scoring 14 runs during overs 48 and over 49, put them ahead.
- Pakistan 205 for 6 wickets in 50 overs
- Australis 206 for 8 wickets in 50 overs
- Scoreboard
- Photos
Analytics Behind Australia's Chase
Target of 206 runs to be scored in 50 overs
Score at end of 17 overs ... 85 for the loss of 2 wickets
Batting Resources still available was 71 % ... Remaining Chase Target % was 59 %
Hence at end of 17 overs ... Resource Clock favors Australia
Score at end of 34 overs ... 144 for the loss of 3 wickets
Batting Resources still available was 42 % ... Remaining Chase Target % was 30 %
Hence at end of 34 overs ... Resource Clock still favors Australia
During the Opening Overs and Middle Overs the "Resource Clock" clearly indicated that Australia was ahead of the Resource Clock and was likely to win.
Overall Australia dominated the chase and were ahead of the "Resource Clock" for all but 2 overs, to win the game by 2 wickets. At the the end of 46 overs Australia were 188 for 8 and were behind the Resource Clock, but scoring 14 runs during overs 48 and over 49, put them ahead.
Saturday, September 19, 2009
SriLanka Vs India ... ODI...Compaq Cup Final
September 14 2009 ... ODI Compaq Cup Final - Sri Lanka Vs India at Premadasa Stadium Colombo - India won by 46 runs
Analytics Behind Sri Lanka's Chase
Target of 320 runs to be scored in 50 overs
Score at end of 17 overs ... 129 for the loss of 4 wickets
Batting Resources still available was 56 % ... Remaining Chase Target % was 60 %
Hence at end of 17 overs ... Resource Clock against Sri Lanka
Score at end of 34 overs ... 211 for the loss of 6 wickets
Batting Resources still available was 28 % ... Remaining Chase Target % was 34 %
Hence at end of 34 overs ... Resource Clock against Sri Lanka
During the Opening Overs and Middle Overs the "Resource Clock" clearly indicated that Sri Lanka was behind the Resource Clock and was likely to lose.
Overall India dominated the defense and were ahead of the "Resource Clock" for all but 10 overs, to win the game by 46 runs.
- India 319 for 5 wickets in 50 overs
- SriLanka 273 all out in 46.4 overs
- Scoreboard
- Photos
Analytics Behind Sri Lanka's Chase
Target of 320 runs to be scored in 50 overs
Score at end of 17 overs ... 129 for the loss of 4 wickets
Batting Resources still available was 56 % ... Remaining Chase Target % was 60 %
Hence at end of 17 overs ... Resource Clock against Sri Lanka
Score at end of 34 overs ... 211 for the loss of 6 wickets
Batting Resources still available was 28 % ... Remaining Chase Target % was 34 %
Hence at end of 34 overs ... Resource Clock against Sri Lanka
During the Opening Overs and Middle Overs the "Resource Clock" clearly indicated that Sri Lanka was behind the Resource Clock and was likely to lose.
Overall India dominated the defense and were ahead of the "Resource Clock" for all but 10 overs, to win the game by 46 runs.
Saturday, August 29, 2009
Fundamental Analysis ... England Vs Australia ... 5th Test
5th Test England Vs Australia at Kennington Oval - England won by 197 runs
- England 1st Innings 332
- Australia 1st Innings 160
- England 2nd Innings 373 for 9 wickets declared
- Australia 2nd Innings 348
- Scoreboard
- Photos
England Top Order Average ... 37.5 runs
Australia ..................................... 40.2
Difference ..................................... -2.7
England Middle Order Average ... 33.7 runs
Australia ........................................... 25.3
Difference ........................................... 8.4
England Lower-Order Average ... 40.7 runs
Australia ........................................ 12.9
Difference ........................................ 27.8
Performance Metric for England .......... 5.9
......................................... Australia ......... 4.8
Saturday, August 22, 2009
Fundamental Analysis Srl Lanka Vs N.Zealand ... 1st Test
1st Test Sri Lanka Vs New Zealand at Galle - Sri Lanka won by 202 runs
- Sri Lanka 1st Innings 452
- N.Zealand 1st Innings 299
- Sri Lanka 2nd Innings 259 for 4 wickets declared
- N.Zealand 2nd Innings 210
- Scoreboard
- Photos
Sri Lanka Top Order Average ... 54.8 runs
N.Zealand ..................................... 23.5
Difference ..................................... 31.3
Sri Lanka Middle Order Average ... 66.0 runs
N.Zealand ........................................... 20.5
Difference ........................................... 45.5
Sri Lanka Tail-Enders Average ... 13.7 runs
N.Zealand ........................................ 34.0
Difference ........................................ -20.3
Performance Metric for New Zealand ... 4.1
......................................... Sri Lanka ......... 6.6
Sunday, June 28, 2009
West Indies Vs India ... ODI 1 & 2
June 28 2009 ... ODI 2 - West Indies Vs India at Kingston Jamaica - West Indies won by 8 wickets
Target of 189 runs to be scored in 50 overs
Score at end of 17 overs ... 109 for the loss of 1 wicket
Batting Resources still available was 75 % ... Remaining Chase Target % was 42 %
Hence at end of 17 overs ... Resource Clock favors West Indies significantly
Score at end of 34 overs ... 186 for the loss of 2 wickets
Batting Resources still available was 45 % ... Remaining Chase Target % was 2 %
Hence at end of 34 overs ... Resource Clock overwhelmingly in favor of West Indies
During the Opening Overs and Middle Overs the "Resource Clock" clearly indicated that West Indies was ahead of the Resource Clock and was likely to win.
Overall West Indies dominated the chase and were ahead of the "Resource Clock" for all the 34 overs, to win the game with 8 wickets and 95 balls to spare.
- India 188 all out in 48.2 overs
- West Indies 192 for 2 wickets in 34.1 overs
- Scoreboard
- Photos
Target of 189 runs to be scored in 50 overs
Score at end of 17 overs ... 109 for the loss of 1 wicket
Batting Resources still available was 75 % ... Remaining Chase Target % was 42 %
Hence at end of 17 overs ... Resource Clock favors West Indies significantly
Score at end of 34 overs ... 186 for the loss of 2 wickets
Batting Resources still available was 45 % ... Remaining Chase Target % was 2 %
Hence at end of 34 overs ... Resource Clock overwhelmingly in favor of West Indies
During the Opening Overs and Middle Overs the "Resource Clock" clearly indicated that West Indies was ahead of the Resource Clock and was likely to win.
Overall West Indies dominated the chase and were ahead of the "Resource Clock" for all the 34 overs, to win the game with 8 wickets and 95 balls to spare.
============
June 26 2009 ... ODI 1 - West Indies Vs India at Kingston Jamaica - India won by 20 runs
Target of 340 runs to be scored in 50 overs
Score at end of 17 overs ... 105 for the loss of 2 wickets
Batting Resources still available was 71 % ... Remaining Chase Target % was 69 %
Hence at end of 17 overs ... Resource Clock favors West Indies marginally
Score at end of 34 overs ... 212 for the loss of 4 wickets
Batting Resources still available was 39 % ... Remaining Chase Target % was 38 %
Hence at end of 34 overs ... Resource Clock very slightly in favor of West Indies
During the Opening Overs and Middle Overs the "Resource Clock" clearly indicated that West Indies was marginally ahead of the Resource Clock and a win was possible.
- India 339 for 6 wickets in 50 overs
- West Indies 319 all out 48.1 overs
- Scoreboard
- Photos
Target of 340 runs to be scored in 50 overs
Score at end of 17 overs ... 105 for the loss of 2 wickets
Batting Resources still available was 71 % ... Remaining Chase Target % was 69 %
Hence at end of 17 overs ... Resource Clock favors West Indies marginally
Score at end of 34 overs ... 212 for the loss of 4 wickets
Batting Resources still available was 39 % ... Remaining Chase Target % was 38 %
Hence at end of 34 overs ... Resource Clock very slightly in favor of West Indies
During the Opening Overs and Middle Overs the "Resource Clock" clearly indicated that West Indies was marginally ahead of the Resource Clock and a win was possible.
During the Ending Overs West Indies steadily lost wickets and fell behind the "Resource Clock" significantly and subsequently lost the match by 20 runs.
West Indies initially dominated the chase and were ahead of the "Resource Clock" but could not maintain the tempo after the 35 th over.
West Indies initially dominated the chase and were ahead of the "Resource Clock" but could not maintain the tempo after the 35 th over.
Sunday, June 21, 2009
World Cup T20 Finals - Pakistan Win Defeating Sri Lanka
World Cup Finals - Pakistan Vs Sri Lanka at Lords - Pakistan won by 8 wickets
Target of 139 runs to be scored in 20 overs
Score at end of 7 overs ... 48 for the loss of no wickets
Batting Resources still available was 79 % ... Remaining Chase Target % was 66 %
Hence at end of 7 overs ... Resource Clock favors Pakistan significantly
Score at end of 13 overs ... 83 for the loss of 2 wickets
Batting Resources still available was 48 % ... Remaining Chase Target % was 40 %
Hence at end of 13 overs ... Resource Clock continues to favor Pakistan
Opening Overs and Middle Overs the "Resource Clock" clearly indicated that Pakistan was ahead of the Resource Clock and was likely to win.
In the End-Game Pakistan did manage their "Batting Resources" better and it was quite sufficient. Overall Pakistan dominated the chase and were ahead of the "Resource Clock" for all the 18 overs, to win the game with 6 wickets and 8 balls to spare.
- Sri Lanka 138 for 6 wickets in 20 overs
- Pakistan 139 for 2 wickets in 18.4 overs
- Scoreboard
- Photos
Target of 139 runs to be scored in 20 overs
Score at end of 7 overs ... 48 for the loss of no wickets
Batting Resources still available was 79 % ... Remaining Chase Target % was 66 %
Hence at end of 7 overs ... Resource Clock favors Pakistan significantly
Score at end of 13 overs ... 83 for the loss of 2 wickets
Batting Resources still available was 48 % ... Remaining Chase Target % was 40 %
Hence at end of 13 overs ... Resource Clock continues to favor Pakistan
Opening Overs and Middle Overs the "Resource Clock" clearly indicated that Pakistan was ahead of the Resource Clock and was likely to win.
In the End-Game Pakistan did manage their "Batting Resources" better and it was quite sufficient. Overall Pakistan dominated the chase and were ahead of the "Resource Clock" for all the 18 overs, to win the game with 6 wickets and 8 balls to spare.
Monday, June 15, 2009
2009 World Cup T20 - India Vs England
World Cup T20 Super Eights - India Vs England at Lords - England won by 3 runs
Target of 154 runs to be scored in 20 overs
Score at end of 7 overs ... 40 for the loss of 2 wickets
Batting Resources still available was 70 % ... Remaining Chase Target % was 74 %
Hence at end of 7 overs ... Resource Clock against India marginally
Score at end of 13 overs ... 78 for the loss of 3 wickets
Batting Resources still available was 45 % ... Remaining Chase Target % was 49 %
Hence at end of 13 overs ... Resource Clock still against India
Opening Overs and Middle Overs the "Resource Clock" clearly indicated that India was behind the Resource Clock and was likely to lose.
In the End-Game India did manage their "Batting Resources" better after over 14, but it was not enough. Overall India managed the chase poorly and were behind the "Resource Clock" most of the time to lose the match narrowly by three runs.
- England 153 for 7 wickets in 20 overs
- India 150 for 5 wickets in 20 overs
- Scoreboard
Target of 154 runs to be scored in 20 overs
Score at end of 7 overs ... 40 for the loss of 2 wickets
Batting Resources still available was 70 % ... Remaining Chase Target % was 74 %
Hence at end of 7 overs ... Resource Clock against India marginally
Score at end of 13 overs ... 78 for the loss of 3 wickets
Batting Resources still available was 45 % ... Remaining Chase Target % was 49 %
Hence at end of 13 overs ... Resource Clock still against India
Opening Overs and Middle Overs the "Resource Clock" clearly indicated that India was behind the Resource Clock and was likely to lose.
In the End-Game India did manage their "Batting Resources" better after over 14, but it was not enough. Overall India managed the chase poorly and were behind the "Resource Clock" most of the time to lose the match narrowly by three runs.
Monday, June 1, 2009
Cricket Legend Gavaskar at Wharton
According to Sunil Gavaskar, former cricket captain for Team India, success in any vocation requires Three Ds: discipline, which is more mental than physical; dedication to hours of practice; and determination -- because, as Gavaskar says, during the time when he was playing the game, "cricket wasn't a career option." Today, of course, that last part has changed, with top players earning millions of dollars and corporate sponsors lining up to pay them. At the recent Wharton India Economic Forum in Philadelphia, Gavaskar spoke with India Knowledge@Wharton about his career, how the business side of cricket has changed, and what he has learned about teamwork and leadership along the way.
Monday, May 25, 2009
IPL - Finals & Semi-Finals May 22-24 May 2009
IPL Finals T20 - Bangalore Royal Challengers Vs Deccan Chargers at Johannesburg - Deccan Chargers won by 6 runs
Target of 144 runs to be scored in 20 overs
Score at end of 7 overs ... 42 for the loss of 2 wickets
Batting Resources still available was 70 % ... Remaining Chase Target % was 71 %
Hence at end of 7 overs ... Resource Clock against Bangalore marginally
Score at end of 13 overs ... 91 for the loss of 4 wickets
Batting Resources still available was 41 % ... Remaining Chase Target % was 37 %
Hence at end of 13 overs ... Resource Clock now favors Bangalore
Opening Overs were against Bangalore and Middle Overs the "Resource Clock" indicated that Bangalore was ahead of the Resource Clock and was likely to win.
In the End-Game Bangalore did not manage their "Batting Resources" efficiently after over 14. They lost 4 wickets during overs 15 to 17 and fell behind the "Resource Clock" to lose the match narrowly by six runs.
- Deccan Chargers 143 for 6 wickets in 20 overs
- Bangalore Royal Challengers 137 for 9 wickets in 20 overs
- Scoreboard
Target of 144 runs to be scored in 20 overs
Score at end of 7 overs ... 42 for the loss of 2 wickets
Batting Resources still available was 70 % ... Remaining Chase Target % was 71 %
Hence at end of 7 overs ... Resource Clock against Bangalore marginally
Score at end of 13 overs ... 91 for the loss of 4 wickets
Batting Resources still available was 41 % ... Remaining Chase Target % was 37 %
Hence at end of 13 overs ... Resource Clock now favors Bangalore
Opening Overs were against Bangalore and Middle Overs the "Resource Clock" indicated that Bangalore was ahead of the Resource Clock and was likely to win.
In the End-Game Bangalore did not manage their "Batting Resources" efficiently after over 14. They lost 4 wickets during overs 15 to 17 and fell behind the "Resource Clock" to lose the match narrowly by six runs.
=======================
IPL First Semi-Finals T20 - Delhi DareDevils Vs Deccan Chargers at Supersport Park Centurion - Deccan Chargers won by 6 wickets
Target of 154 runs to be scored in 20 overs
Score at end of 7 overs ... 87 for the loss of 1 wicket
Batting Resources still available was 75 % ... Remaining Chase Target % was 44 %
Hence at end of 7 overs ... Resource Clock favors Deccan considerably
Score at end of 13 overs ... 131 for the loss of 3 wickets
Batting Resources still available was 45 % ... Remaining Chase Target % was 15 %
Hence at end of 13 overs ... Resource Clock clearly favors Deccan
Opening Overs and Middle Overs the "Resource Clock" clearly indicated that Deccan was well ahead of the Resource Clock and was likely to win.
In the End-Game Deccan did manage their "Batting Resources" very efficiently subsequently won the maych in over 18. They were always ahead of the "Resource Clock".
- Delhi DareDevils 153 for 8 wickets in 20 overs
- Deccan Chargers 154 for 4 wickets in 17.4 overs
- Scoreboard
Target of 154 runs to be scored in 20 overs
Score at end of 7 overs ... 87 for the loss of 1 wicket
Batting Resources still available was 75 % ... Remaining Chase Target % was 44 %
Hence at end of 7 overs ... Resource Clock favors Deccan considerably
Score at end of 13 overs ... 131 for the loss of 3 wickets
Batting Resources still available was 45 % ... Remaining Chase Target % was 15 %
Hence at end of 13 overs ... Resource Clock clearly favors Deccan
Opening Overs and Middle Overs the "Resource Clock" clearly indicated that Deccan was well ahead of the Resource Clock and was likely to win.
In the End-Game Deccan did manage their "Batting Resources" very efficiently subsequently won the maych in over 18. They were always ahead of the "Resource Clock".
================================
IPL Second Semi-Final T20 - Bangalore Royal Challengers Vs Chennai Super Kings at Johannesburg - Bangalore Royal Challengers won by 6 wickets
Target of 147 runs to be scored in 20 overs
Score at end of 7 overs ... 63 for the loss of 2 wickets
Batting Resources still available was 70 % ... Remaining Chase Target % was 57 %
Hence at end of 7 overs ... Resource Clock favors Bangalore
Score at end of 13 overs ... 96 for the loss of 3 wickets
Batting Resources still available was 45 % ... Remaining Chase Target % was 35 %
Hence at end of 13 overs ... Resource Clock now clearly favors Bangalore
Opening Overs and Middle Overs the "Resource Clock" indicated that Bangalore was ahead of the Resource Clock and was likely to win.
In the End-Game Bangalore did their "Batting Resources" efficiently and won the match in the 19th over. They were ahead of the "Resource Clock" during 18 out the 19 overs displaying their control of chasing the target.
- Chennai Super Kings 146 for 5 wickets in 20 overs
- Bangalore Royal Challengers 149 for 4 wickets in 18.5 overs
- Scoreboard
Target of 147 runs to be scored in 20 overs
Score at end of 7 overs ... 63 for the loss of 2 wickets
Batting Resources still available was 70 % ... Remaining Chase Target % was 57 %
Hence at end of 7 overs ... Resource Clock favors Bangalore
Score at end of 13 overs ... 96 for the loss of 3 wickets
Batting Resources still available was 45 % ... Remaining Chase Target % was 35 %
Hence at end of 13 overs ... Resource Clock now clearly favors Bangalore
Opening Overs and Middle Overs the "Resource Clock" indicated that Bangalore was ahead of the Resource Clock and was likely to win.
In the End-Game Bangalore did their "Batting Resources" efficiently and won the match in the 19th over. They were ahead of the "Resource Clock" during 18 out the 19 overs displaying their control of chasing the target.
Monday, May 18, 2009
IPL - Cricket Matches Completed on May 18 2009
Match 51 T20 - Chennai Super Kings Vs Kolkata Knight Riders at SuperSport Park Centurion - Kolkata Knight Riders won by 7 wickets
Target of 189 runs to be scored in 20 overs
Score at end of 7 overs ... 60 for the loss of 1 wicket
Batting Resources still available was 75 % ... Remaining Chase Target % was 68 %
Hence at end of 7 overs ... Resource Clock favors Kolkata
Score at end of 13 overs ... 114 for the loss of 1 wicket
Batting Resources still available was 50 % ... Remaining Chase Target % was 40 %
Hence at end of 13 overs ... Resource Clock still favors Kolkata
Opening Overs and Middle Overs the "Resource Clock" indicated clearly that Kolkata was ahead of the Resource Clock and was likely to win.
- Chennai Super Kings 188 for 3 wickets in 20 overs
- Kolkata Knight Riders 189 for for 3 wickets in 20 overs
- Scoreboard
Target of 189 runs to be scored in 20 overs
Score at end of 7 overs ... 60 for the loss of 1 wicket
Batting Resources still available was 75 % ... Remaining Chase Target % was 68 %
Hence at end of 7 overs ... Resource Clock favors Kolkata
Score at end of 13 overs ... 114 for the loss of 1 wicket
Batting Resources still available was 50 % ... Remaining Chase Target % was 40 %
Hence at end of 13 overs ... Resource Clock still favors Kolkata
Opening Overs and Middle Overs the "Resource Clock" indicated clearly that Kolkata was ahead of the Resource Clock and was likely to win.
In the End-Game Kolkata did manage their "Batting Resources" efficiently and were overall ahead of the "Resource Clock" for 19 of the 20 overs.
Sunday, May 17, 2009
IPL - Cricket Matches Completed on May 17 2009
Match 49 T20 - Deccan Chargers Vs Kings XI Punjab at Johannesburg - Kings XI Punjab won by 1 run
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.
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
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.
- 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.
Sunday, May 3, 2009
IPL - Cricket Matches Completed on May 3 2009
Match 27 T20 - Kings XI Punjab Vs Kolkata Knight Riders at Port Elizabeth - Kings XI Punjab won by 6 wickets
Analytics Behind Bangalore's Chase
Target of 150 runs to be scored in 20 overs
Score at end of 7 overs ... 54 for the loss of 1 wicket
Batting Resources still available was 75 % ... Remaining Chase Target % was 64 %
Hence at end of 7 overs ... Resource Clock in favor of Bangalore
Score at end of 13 overs ... 92 for the loss of 1 wicket
Batting Resources still available was 50 % ... Remaining Chase Target % was 39 %
Hence at end of 13 overs ... Resource Clock still in favor of Bangalore.
Opening Overs and Middle Overs the "Resource Clock" indicated clearly that Bangalore was likely to win.
Bangalore Royal Challengers managed their "Batting Resources" quite well...they were ahead of the "Resource Clock" for all of the 18 overs completed.
- Kolkata Knight Riders 153 for 3 wickets in 20 overs
- Kings XI Punjab 154 for 4 wickets in 20 overs
- Scoreboard
- Photos
Analytics Behind Punjab's Chase
Target of 154 runs to be scored in 20 overs
Score at end of 7 overs ... 59 for the loss of 2 wickets
Batting Resources still available was 70 % ... Remaining Chase Target % was 62 %
Hence at end of 7 overs ... Resource Clock favors Punjab
Score at end of 13 overs ... 102 for the loss of 3 wickets
Batting Resources still available was 45 % ... Remaining Chase Target % was 34 %
Hence at end of 13 overs ... Resource Clock still favors Punjab
Opening Overs and Middle Overs the "Resource Clock" indicated clearly that Punjab was likely to win.
In the End-Game Punjab had minor challenges but were helped by sloppy fielding on the part Of Kolkata.
Kings XI Punjab managed their "Batting Resources" very well...they were ahead of the Resource Clock for 17 overs out of the 20 completed.
========================================
Match 28 T20 - Bangalore Royal Challengers Vs Mumbai Indians at Johannesburg - Bangalore Royal Challengers won by 9 wickets
Target of 154 runs to be scored in 20 overs
Score at end of 7 overs ... 59 for the loss of 2 wickets
Batting Resources still available was 70 % ... Remaining Chase Target % was 62 %
Hence at end of 7 overs ... Resource Clock favors Punjab
Score at end of 13 overs ... 102 for the loss of 3 wickets
Batting Resources still available was 45 % ... Remaining Chase Target % was 34 %
Hence at end of 13 overs ... Resource Clock still favors Punjab
Opening Overs and Middle Overs the "Resource Clock" indicated clearly that Punjab was likely to win.
In the End-Game Punjab had minor challenges but were helped by sloppy fielding on the part Of Kolkata.
Kings XI Punjab managed their "Batting Resources" very well...they were ahead of the Resource Clock for 17 overs out of the 20 completed.
========================================
Match 28 T20 - Bangalore Royal Challengers Vs Mumbai Indians at Johannesburg - Bangalore Royal Challengers won by 9 wickets
- Mumbai Indians 149 for 4 wickets in 20 overs
- Bangalore Royal Challengers 150 for 1 wicket in 18.1 overs
- Scoreboard
- Photos
Analytics Behind Bangalore's Chase
Target of 150 runs to be scored in 20 overs
Score at end of 7 overs ... 54 for the loss of 1 wicket
Batting Resources still available was 75 % ... Remaining Chase Target % was 64 %
Hence at end of 7 overs ... Resource Clock in favor of Bangalore
Score at end of 13 overs ... 92 for the loss of 1 wicket
Batting Resources still available was 50 % ... Remaining Chase Target % was 39 %
Hence at end of 13 overs ... Resource Clock still in favor of Bangalore.
Opening Overs and Middle Overs the "Resource Clock" indicated clearly that Bangalore was likely to win.
Bangalore Royal Challengers managed their "Batting Resources" quite well...they were ahead of the "Resource Clock" for all of the 18 overs completed.
Sunday, April 26, 2009
IPL - Matches Completed on April 26 2009
Match 14 T20 - Bangalore Royal Challengers Vs Delhi Dare Devils at Port Elizabeth - Delhi Daredevils won by 6 wickets
- Bangalore Royal Challengers 149 for 7 wickets in 20 overs
- Delhi Dare Devils 150 for 4 wickets in 19.2 overs
- Scoreboard
- Photos
Target of 150 runs to be scored in 20 overs
Score at end of 7 overs ... 50 for the loss of 2 wickets
Batting Resources still available was 70 % ... Remaining Chase Target % was 67 %
Hence at end of 7 overs ... Resource Clock favors Delhi
Score at end of 13 overs ... 84 for the loss of 2 wickets
Batting Resources still available was 48 % ... Remaining Chase Target % was 44 %
Hence at end of 13 overs ... Resource Clock still favors Delhi
Opening Overs and Middle Overs the "Resource Clock" indicated clearly that Delhi was likely to win.
In the End-Game Delhi had a minor hiccup though not fatal
Score at end of 16 overs ... 107 for the loss of 4 wickets
Batting Resources still available was 28 % ... Remaining Chase Target % was 29 %
Hence at end of 16 overs ... Resource Clock was against Delhi slightly
But the next 3 overs Delhi took charge, sometimes helped by sloppy fielding.
Robin Uthappa's misjudging an easy catch of Manhas in the fifth ball of the 17th over was extremely crucial; what should have been a dot ball/wicket was four runs conceded instead. Further compounded next ball by a misfielding by Appanna to let go another boundary.
Delhi Daredevils managed their "Batting Resources" very well...they were ahead of the Resource Clock for 16 overs out of the 19 completed.
========================================
Match 15 T20 - Kings XI Punjab Vs Rajasthan Royals at Capetown - Kings XI Punjab won by 27 runs
- Kings XI Punjab 139 for 6 wickets in 20 overs
- Rajasthan Royals 112 for 7 wickets in 20 overs
- Scoreboard
- Photos
Target of 140 runs to be scored in 20 overs
Score at end of 7 overs ... 38 for the loss of 5 wickets
Batting Resources still available was 46 % ... Remaining Chase Target % was 73 %
Hence at end of 7 overs ... Resource Clock against Rajasthan
Score at end of 13 overs ... 70 for the loss of 6 wickets
Batting Resources still available was 30 % ... Remaining Chase Target % was 50 %
Hence at end of 13 overs ... Resource Clock still against Rajasthan
Opening Overs and Middle Overs the "Resource Clock" indicated clearly that Kings XI Punjab was likely to win.
Rajasthan Royals managed their "Batting Resources" quite poorly...they were behind the "Resource Clock" for 19 overs out of the 20 completed.
Thursday, April 23, 2009
IPL - Cricket Matches Completed on April 22 2009
Match 8 T20 - Bangalore Royal Challengers Vs Deccan Chargers at Capetown - Deccan Chargers won by 24 runs
- Deccan Chargers 184 for 6 wickets in 20 overs
- Bangalore Royal Challengers 160 8 wickets in 20 overs
- Scoreboard
- Photos
Tuesday, April 21, 2009
IPL - Cricket Matches Completed on April 21 2009
Match 6 T20 - Kings XI Punjab Vs Kolkata Knight Riders at Durban - Kolkata Knight Riders won by 11 runs (D/L Method)
- Kings XI Punjab 158 for 6 wickets in 20 overs
- Kolkata Knight Riders 79 for 1 wicket in 9.2 overs
- Scoreboard
- Photos
Match 7 T20 - Mumbai Indians Vs Rajasthan Royals at Durban - Draw, Rained Out
Monday, April 20, 2009
IPL - Cricket Matches Completed on April 20 2009
Match 5 T20 - Bangalore Royal Challengers Vs Chennai Super Kings at Port Elizabeth - Chennai Super Kings won by 92 runs
- Chennai SuperKings 179 for 5 wickets in 20 overs
- Bangalore Royal Challengers 87 All Out in 15.2 overs
- Scoreboard
- Photos
Sunday, April 19, 2009
IPL - Cricket Matches Completed on April 19 2009
Match 3 T20 - Kings XI Punjab Vs Delhi DareDevils at Capetown - Delhi Daredevils won by 10 wickets (D/L Method)
- Kings XI Punjab 104 for 7 wickets in 12 overs
- Delhi Daredevils 58 for No Loss in 4.5 overs
- Scoreboard
- Photos
Match 4 T20 - Deccan Chargers Vs Kolkata Knight Riders at Capetown - Deccan Chargers won by 8 wickets
- Kolkata Knight Riders 101 All Out in 19.4 overs
- Deccan Chargers 104 for 2 wickets in 13.1 overs
- Scoreboard
- Photos
Saturday, April 18, 2009
IPL - Cricket Matches Completed on April 18 2009
Match 1 - T20 - Chennai SuperKings Vs Mumbai Indians at Capetown - Mumbai Indians won by 19 runs
- Mumbai Indians 165 for 7 wickets in 20 overs
- Chennai SuperKings 146 for 7 wickets in 20 overs
- Scoreboard
- Photos
Analysis ... Mumbai Indians win the IPL opener ... Methodically
Mumbai Indians win the opener comfortably.
At the end of the 7th over and 13th over they had the "Resource Clock" in their favor and duly accomplished the target and score 165 runs, thanks to veteran Sachin and young Abhishek.
Chennai was behind the "Resource Clock" most of the time chasing 166 runs (though they were marginally ahead at the 7th over end) and by the critical 13th over they were behind and had lost Hayden...it was curtains after that.
Match 2 - T20 - Bangalore Royal Challengers Vs Rajasthan Royals at Capetown - Bangalore Royal Challengers won by 75 runs runs
- Bangalore Royal Challengers 133 for 8 wickets in 20 overs
- Rajasthan Royals 58 All Out in 15.1 overs
- Scoreboard
- Photos
Analysis ... Bangalore Royal Challengers Stun Rajasthan Royals in a low scoring Game
Batting first Bangalore Royal Challengers were always behind the "Resource Clock" to reach a target score of 150. That they managed to score 133 in 20 overs was primarily due to the contributions of 66 runs from Rahul Dravid and 32 from Kevin Pietersen.
Chasing a modest target of 134 runs proved to be an almost impossible for Rajasthan Royals. They lost wickets regularly and could not get the scoreboard to move either. They were constantly in the red with regard to effectively using their resources. The score of 58 runs summarized their rout.
Analytics - Mumbai Indians Vs Chennai SuperKings
Cricket Matches Completed on April 17 2009
5th ODI South Africa Vs Australia at Johannesburg - Australia won by 47 runs
- Australia 303 for 7 wickets in 50 overs
- S.Africa 256 All out in 45.5 overs
- Scoreboard
- Photos
Monday, April 13, 2009
Cricket Matches Completed on April 13 2009
4th ODI South Africa Vs Australia at Port Elizabeth - S.Africa won by 61 runs
- S.Africa 317 for 6 wickets in 50 overs
- Australia 256 All Out in 45.5 overs
- Scoreboard
- Photos
- Video
Thursday, April 9, 2009
Cricket Matches Completed on April 09 2009
3rd ODI South Africa Vs Australia at Newlands,Capetown - S.Africa won by 25 runs
- S.Africa 289 for 6 wickets in 50 overs
- Australia 264 for 7 wickets in 50 overs
- Scoreboard
- Photos
- Video
Tuesday, April 7, 2009
Cricket Matches Completed on April 07 2009
3rd Test New Zealand Vs India at Basin Reserve, Wellington - Match Drawn
- India 1st Innings 379
- N.Zealand 1st Innings 197
- India 2nd Innings 434 for 7 wickets declared
- N.Zealand 2nd Innings 281 for 8 wickets
- Scoreboard
- Photos
- Match Details
Fundamental Analysis & Analytics
Monday, April 6, 2009
Cricket Matches Completed on April 05 2009
2nd ODI South Africa Vs Australia at SuperSport Park,Centurion - S.Africa won by 7 wickets
- Australia 131 All Out in 40.3 overs
- S.Africa 132 for 3 wickets in 26.2 overs
- Scoreboard
- Photos
- Peter Roebuck lashes out
Friday, April 3, 2009
Cricket Matches Completed on April 03 2009
5th ODI West Indies Vs England at St.Lucia - England won by 26 runs
- England 172 for 5 wickets in 29 overs
- West Indies 146 All Out in 28 overs
- Scoreboard
- Photos
- Australia 286 for 7 wickets in 50 overs
- S.Africa 145 All Out in 33.1 overs
- Scoreboard
- Photos
Tuesday, March 31, 2009
Cricket matches Completed on March 30 2009
2nd Test New Zealand Vs India at Napier - Match Drawn
- New Zealand 1st Innings 619 for 9 wickets declared
- India 1st Innings 305
- India 2nd Innings 476 for 4 wickets
- Scoreboard
- Photos
- Match Details
Cricket Matches Completed on March 29 2009
4th ODI West Indies Vs England at Barbados - England won by 9 wickets (D/L Method)
- West Indies 239 for 9 wickets in 50 overs
- England 136 for 1 wicket in 18.3 overs
- Scoreboard
- Photos
- S.Africa 156 for 5 wickets in 20 overs
- Australia 139 for 8 wickets in 20 overs
- Scoreboard
- Photos
Friday, March 27, 2009
Cricket Matches Completed on March 27 2009
3rd ODI West Indies Vs England at Barbados - W.Indies won by 8 wickets
- England 117 All out in 41.3 overs
- West Indies 117 for 2 wickets in 14.4 overs
- Scoreboard
- Photos
1st T20I South Africa Vs Australia at Johannesburg - S.Africa won by 4 wickets
- Australia 167 for 7 wickets in 20 overs
- s.Africa 168 for 6 wickets in 19.2 overs
- Scoreboard
Sunday, March 22, 2009
Cricket Matches Completed on March 22 2009
3rd Test South Africa Vs Australia at Capetown - S.Africa won by innings and 20 runs
Cricket Matches Completed on March 21 2009
1st Test New Zealand Vs India at Hamilton - India won by 10 wickets
- New Zealand 1st Innings 279
- India 1st Innings 520
- New Zealand 2nd Innings 279
- India 2nd Innings 29 for no loss
- Scoreboard
- Photos
- Match Details
Friday, March 20, 2009
Cricket Matches Completed on March 20 2009
First ODI West Indies Vs England at Guyana - England won by 1 run by D/L Method
- England 270 for 7 wickets in 50 overs
- West Indies 244 for 7 wickets in 46.2 overs
- Details
Analytics of Sachin's Century Number 42
Whoever said that Sachin Tendulkar was over the hill, was comprehensively proved wrong by another masterly innings.
Interesting Analytics
Sachin's 42 centuries averages around 144 runs per century.
Each century on the average contributes 34% of the team's total runs scored.
This century of 160 out of total 520 contributed 31% of the runs, is only the 25th when ranked amongst centuries with highest percentage contribution.
Interesting Analytics
Sachin's 42 centuries averages around 144 runs per century.
Each century on the average contributes 34% of the team's total runs scored.
This century of 160 out of total 520 contributed 31% of the runs, is only the 25th when ranked amongst centuries with highest percentage contribution.
His 122 out of a total score 219 against England in 1996 constituting 56% of the total runs scored by the team is by far the "most valuable" century.
Whenever Sachin has scored a century only in 9 cases it has been for a losing cause and in 17 cases the match has been drawn.
Sachin's century contributing a win has been the case in 16 cases, including the likely win in New Zealand.
Sunday, March 15, 2009
Matches Completed on March 15 2009
Twenty20 West Indies Vs England at Port of Spain, Trinidad - W.Indies won by 6 wickets
- Engalnd 121 all out in 19.1 overs
- West Indies 123 for 4 wickets in 18 overs
- Details
Saturday, March 14, 2009
Fundamental Analysis - South Africa Vs Australia 2nd Test
2nd Test South Africa Vs Australia - Aussies won by 175 runs
It is clear from the above numbers that the key difference was the Top Order Match Ups which compares the performance of the first 3 batsmen of each side.
Australia was clearly superior in this department for which all credit goes to their new boy wonder Phil Hughes, who scored a century in each innings.
South Africa really suffers when their skipper and opener Graeme Smith does not contribute. Incidentally Graeme Smith broke a finger and is out of action.
South Africa outperformed the Australians in the Middle-Order Match Up, but it was not enough to make the top order deficit.
Incidentally the tail enders did not wag for either of the sides.
The session by session match ups clearly indicate Australia's superiority. South Africa had a minor breakthrough on the morning of the second day when they quickly wrapped up the lower half of Australia for 352, but their batsmen could not hold on to their advantage.
- Australia 1st Innings 352
- South Africa 1st Innings 138
- Australia 2nd Innings 331 for 5 declared
- South Africa 2nd Innings 370
- Details
It is clear from the above numbers that the key difference was the Top Order Match Ups which compares the performance of the first 3 batsmen of each side.
Australia was clearly superior in this department for which all credit goes to their new boy wonder Phil Hughes, who scored a century in each innings.
South Africa really suffers when their skipper and opener Graeme Smith does not contribute. Incidentally Graeme Smith broke a finger and is out of action.
South Africa outperformed the Australians in the Middle-Order Match Up, but it was not enough to make the top order deficit.
Incidentally the tail enders did not wag for either of the sides.
The session by session match ups clearly indicate Australia's superiority. South Africa had a minor breakthrough on the morning of the second day when they quickly wrapped up the lower half of Australia for 352, but their batsmen could not hold on to their advantage.
Australia having a Power Rating of 7 against South Africa's 4.1 clearly summed up Australia's dominance.
Matches Completed on March 14 2009
5th ODI New Zealand Vs India - New Zealand won by 8 wickets
- India 149 all out in 36.3 overs
- New Zealand 151 for 2 wickets in 23.2 overs
- Details
Wednesday, March 11, 2009
Matches Completed on March 11 2009
4th ODI New Zealand Vs India - India won 84 runs (D/L)
- New Zealand 270 for 5 wickets in 47 overs
- India 201 for 0 wickets in 23.3 overs
- Details
Tuesday, March 10, 2009
Matches Completed On March 10 2009
5th Test West Indies Vs England - Match Drawn
- England 1st Innings 546 for 6 declared
- West Indies 1st Innings 544
- England 2nd Innings 237 for 6 declared
- West Indies 2nd Innings 114 for 8
- Details
2nd Test South Africa Vs Australia - Aussies won by 175 runs
- Australia 1st Innings 352
- South Africa 1st Innings 138
- Australia 2nd Innings 331 for 5 declared
- South Africa 2nd Innings 370
- Details
Subscribe to:
Posts (Atom)
