Monday, May 20, 2013

Large Scale Fixing Gets Established



What is being reported in the media is as if there was astray spot-fixing only involving three bowlers alone, and only one over in each of the three matches.  It can’t be so for following simple reasons and facts.
1.       How could bookies know well in advance that these particular players would be playing in those matches, the trio not being the regular team members? That is if the deals were struck in advance, well before the toss when the teams are announced. Police may enlighten on this aspect.
2.       A bowler alone can never ensure how many runs will be scored of a particular ball or in an over, unless it is wide enough to be out of reach of batsman and/or wicketkeeper. There was not a single such ball in these three overs reported. So for scoring of particular runs, complicity of batsmen is necessary. Fielders complicity also may or may not be necessary, depending on what shot is played and what is the involvement of the fielder/s for a particular shot.
3.       Chandila Over: He was to concede 14 runs in second over of his spell. And conceded exactly 14. Without batsmen knowing how many runs were to be scored of the over, Chandila alone couldn’t ensure that, without the involvement of the two batsmen since the strike changed twice through the over. Chandila as a bowler alone could ensure scoring of 14 runs only if it is guaranteed in game of cricket that a particular ball will get a particular fate i.e. if batsman and fielders are of no consequence. We all know it is not so. For example it was not in Chandila’s hands that Finch would successfully attempt a sweep for a boundary of the last ball.
4.       Sreesanth’s Over: He was to concede 14 or more runs in his second over. He conceded 13 runs and bookies were happy as per police. Once again, bowler alone can only bowl lose balls but can’t ensure how many runs will be scored of a ball. Not going far, as reported, in this over itself first, third, and fourth balls were such that could be hit for boundaries, but were not. Similarly Gilchrist could or could not hit the 5th and the 6th balls for boundaries. It was not in Sreesanth’s hands. Why were bookies happy even though contractual runs were not scored? I shall address this also subsequently.
5.       Chavan’s Over:  He was to concede at least 13 runs in his second over. 15 runs were scored of this over and bookies must have been happy.  14 runs were scored of first 3 balls, and many more could be scored of the next 3 but only 1 run more was scored.
6.       Each time why second over of the bowler’s spell? As it turns out to be, these were the 3rd, 4th and 3rd overs of the first innings of the match (in each case) respectively. Now here it is necessary to know and understand how the illegal betting market, that is so much talked about to be the reason behind fixing in the sub-continent (though I know for sure it is not limited to sub-continent), works. The standard, regular and large scale betting takes place for runs to be scored in a continuous number of overs known as session (or bracket). The current standard practice is that the first session for betting consists of first 10 overs. Sometimes, though not very common, it may be 9 or 8 or may be even 7 or 6 overs as decided by the bookies depending on how fixing has taken place (scripting has been done). There is no worthwhile betting taking place for runs to be scored in one particular over. This fact has already come out in British journalist, Hawkins’ book also.
Session betting mostly starts after first over. The bookie offers a particular score, say 66-67
 for the session. That means one can bet either for 67 or more runs to be scored or less than 66 runs to be scored at the end of the session (10 overs). (If exactly 66 are scored, bookie would win and you will lose whatever was your bet). This score on offer by the bookie varies with each ball (i.e. may vary). Suppose a 4 is scored of next ball, then the session score may change to 68-69 or 69-70 as per bookie’s choice. Similarly if next 2 balls are dots, the session score may come down to 65-66 or so. In other words, the session score on offer at a time would be score on board + adopted (by the bookie) average per over x the remaining overs of the session +/- a small number depending on the momentum of the game or bookie’s whims. The betting returns are 1:1, that is for a rupee bet you lose a rupee or win a rupee.
Coming back to why 2nd over of the spell? Because these were the 3rd, 4th, and 3rd overs of the innings and the session, as mentioned and explained above. And as it turns out, these were the first overs in the session to start high scoring. 16 runs before this Chandila over had been scored in 2 overs before that, 11 runs in 3 overs had been scored before Sreesanth’s over in question, and 10 runs had been scored in 2 overs before Chavan’s 2nd over. The fixed overs thus were the first in the session to start high scoring. This is how scoring took place for the remaining overs of the session after these overs:
After Chandila’s over:     13,7, 11,5,8,6,12   a total 62 in 7 overs 
After Sreesanth’s over:  4,9,14,7,7,9            a total 50 in 6 overs
After Chavan’s over:        2,8,14, 11,6, 7, 8   a total 56 in 7 overs    
So the high scoring starting with the overs in question continued till the end of the session such that more than average runs per over adopted for first session (usually 7) were scored thereafter. That corroborates that fixing for this over was not something in isolation as that would have no meaning, but a part of the larger session fixing. This is also corroborated further by the fact that when Chandila (or Chavan) talked to the bookie after doing the job, the bookie told him to wait till session was over. Something like that was told by the Delhi CP in his first press conference on the subject. 
Once it is clear that fixing of this over was a part of session fixing, a very pertinent and explosive question arises? How could these bookies know that 2nd over by these bowlers would be the 3rd or the 4th over of the innings? For all that matters, they could start bowling after the 10th over. And it is none’s but a captain’s prerogative when a bowler bowls. Therefore the captain of the fielding side, whosoever he may be, had to be in the knowhow.  
7.       Next, bookies won’t have paid these players without having ensured scoring pattern for the remaining overs of the session. Fixing just one over gives them no returns. That fixing was for the larger session is confirmed by the wording of the contracts of the fixers with Sreesanth and Chavan at least. Not any exact number of runs but ‘14 or more’ and ‘at least 13.’ Further why were bookies happy even if less than 14 runs were scored in his over? Because one run less at this stage didn’t matter much in final session score that could be covered/adjusted through remaining overs.
That would mean fixing of the first ten overs of these three matches at least, involving a number of bowlers and fielders of the fielding side, i.e. almost whole side of Rajasthan Royals, and at least all the batsmen who batted during those 10 overs from Pune, Punjab, and Mumbai. That would include a big chunk of players, based on available evidence itself (supported with irrefutable logical deductions).
8.       On the larger canvass, once existence of session betting is established through utterances of CP, Delhi Police, the existence of continuous fixing with involvement of all gets established. Simply, the session betting can’t exist and continue for years as it has been, if the bookies didn’t have support of fixing. While for a match result, the bookies could control the odds based on bets being received to save them from any loss, no such book making could be possible in session betting (which is a larger market than match result as per bookies’ accounts themselves on national channels recently) and bookies would run the risk of heavy losses if they couldn’t control the scoring pattern. It is very simple and requires nothing but common-sense to understand all above.

While I write above, a bookie telling the world that it was not spot fixing but session fixing, is being telecast on Times-Now. 

Sunday, May 19, 2013

Proof of Fixing is in Cricket Played



Royal Challengers Bangalore 106/2 (8/8 ov); Chennai Super Kings 82/6 (8/8 ov)
Royal Challengers Bangalore won by 24 runs

One doesn't have to go far to look for evidence of fixing. What is required is a little knowledge of/about cricket, seeing the cricket being played over some continuous period of time, a little common sense and its application. Knowledge about betting is not necessary now-a-days as fixing becomes too obvious in the cricket being played itself. This match comes under that category.

CSK win the toss, put RCB in and feed them with bowling to allow them to score 106 runs in an 8 overs a side match. Let us assume that is natural cricket as a result of RCB batsmen clicking that particular day.

One would suppose that CSK were playing to win. How do they go about chasing this big score with a number of distinguished hitters being in their ranks and all of them being in form, having come good this season. A boundary is scored first ball. Fine. No boundary is hit/attempted next 7 balls in an 8 over game, and chasing with required run rate of more than 13 runs per over. Then conveniently two quick wickets are lost, and next boundary is hit in the last ball of the 3rd over when required run rate has already touched impossible proportions. 

CSK captain, the super hero, Dhoni doesn't promote himself this time and comes to bat only after nothing is there to bat for. He hits 24 of 10 balls, a few big hits towards the end, before getting out. Had he come up the order and scored those runs, the odds would have had changed a lot, but his scoring as he did had no effect on the odds since match was already over.

What would any punter have expected from natural cricket in an 8 overs a side match? A number of fluctuations in the prospects of the two teams and a very close match, and would have placed bets accordingly. But early in the match, by 3rd over or so of RCB batting, the match swung in favour of one team and continued so without even a far competition by the best batting side of the tournament.

The Mighty bite the Dust



Kings XI Punjab 183/8 (20/20 ov); Mumbai Indians 133 (19.1/20 ov)
Kings XI Punjab won by 50 runs

MI won the toss and put KXIP in who were soon 6/2 in 2.2 overs, the odds in f/o MI, the pre-match favourites, still being as high as 1.37. And from there on they lost the plot, their best bowler Malinga going for 20 runs in his first over, the 8th of the innings. Mandeep Singh once again (was it consecutively 3rd time?) opened the batting to get out very early. KXIP went on to score an impressive 183, their scoring having decelerated a bit towards the end for session manipulation.

With the pitch and the ground, and MI's strong and performing batting, it was considered just above par score and accordingly the odds were high at 1.8, this time in f/o Punjab. By the 10th over, MI had lost their 4th wicket for 69 and the match had decisively gone in favour of Punjab. It continued so, Punjab winning by a big margin of 50 runs over one of the strongest teams. 

MI scored well in first 6 overs, scoring 14 runs in the 6th over, to be a healthy 51/2 at the end of this session and well in hunt. Can be said to be natural, though the natural phenomenon of high scoring in power-play overs doesn't happen about 8 times out of 10. But what is worth noting is how scoring dropped suddenly after 6th over even though same set batsmen were batting. Only 11 runs were scored in next 2.3 overs before next wicket was lost.

Interestingly, with similar 15.4 runs required per over in last 5 overs as was the case in their match against SRH when 15.5 runs were required in last 4 overs, with Pollard being on the crease in both the cases, the odds were around 1.1 in f/o the opposing team this time compared to 1.35 earlier. And MI had gone on to win comfortably from there on against SRH.

   


Saturday, May 18, 2013

Staged Cricket Continues



Sunrisers Hyderabad 136/9 (20/20 ov); Rajasthan Royals 113/9 (20/20 ov)
Sunrisers Hyderabad won by 23 runs


After arrest of RR players for fixing, one would have thought that RR won't dare to indulge in it again. One couldn't be more naive. 

Before the start of the match, Rahul Dravid, the captain of RR proclaimed that they would bounce back. And they did, by reducing the SRH, having the weakest middle and late order batting line up among all the participating teams, to 5/3 in 2.4 overs. With the great track record of RR in chasing this season, the match appeared to be all over for SRH. The captain, Cameron White, with his team at 5/2 had played as irresponsible a shot as any. duly controlling the power of the shot such that the ball didn't fly over boundary, to get himself out for zero.

From there on it was the turn of SRH to bounce back. They recovered well scoring without any problem, yet their greatest hitter Perera having been hitting sixes with ease in the tournament, scratched around in the end, not even attempting a single boundary of the 13 balls he faced. As a result, they scored just 7 runs in the last over to manipulate the session score (to great advantage of the fixers).

Samantray, the top scorer and backbone of SRH batting this innings, was run out as early as in the 6th over through a direct hit, getting back in the crease very casually and carelessly, but no one appealed. Clearly this run out happened as a result of carelessness of Samantray or the fielder hitting the stumps, and was not scripted. And none of the close-in fielders appealing would also mean that all of them were aware what the script was.

While chasing RR were comfortable till the 8th over, though scoring a bit slowly, inspite of having scored 13 runs in the 5th over, before Dravid got himself run out. And suddenly the match turned on its head to leave punters trapped. Next wicket went soon after and RR were 61/4 in the 14th over, with the main threat Watson also having gone. The consistently successful chasers of IPL 6 collapsed to 113 chasing a small total of 136.

This is how Rahul Dravid and his men bounced back.




Match after the Scandal



Kings XI Punjab 171/4 (20/20 ov); Delhi Daredevils 164/7 (20/20 ov)
Kings XI Punjab won by 7 runs

It was the first match held after the arrests of the playing IPL players of Rajasthan Royals including Sreesanth. If one would have thought that this match had to be clean and couldn't be fixed, one couldn't be farther from the truth. The small irritants of sting operations and police becoming active out of nowhere, haven't had any effect on the much larger picture of continuous staged cricket in the past, and didn't have any effect this time also. 

DD won the toss and put the opposition in, to lose the match as comfortably as they have been losing most of their matches this season. The last season they were on the top of the table. 

KXIP batted well to start with, slumped in middle overs, and scored heavily in last 5 overs (68 runs), in contrast to what they had been doing in most of the matches this season. Some may find/claim it to be natural, but not those who understand session betting.

When DD start batting chasing 171, what would a punter expect? Obviously expectation will be for them to score well in the first 6 overs of power play, these overs constituting the session as well. And what happens? They score only 11 runs in 2.3 overs even before losing a wicket, after losing one score only 1 run in next 6 balls before losing the pinch hitter, who had otherwise been batting well and hitting sixes in his last few outings. Then the captain Warner walks in and very clearly gives catching practice to one of the slips. DD are 12/3 in 4 overs, and a mere 21/3 in the session of 6 power-play overs. What is being termed as spot-fixing by media and others is this session-fixing, that covers most of the match. And if it is taking place all the time as it is coming out of the scandal, it is clear that total fixing is taking place. Let us not deceive ourselves.

When DD required 61 runs of last 4 overs, the odds were less than 1.10 in f/o KP, and they lost one-sided as expected, Jayawardene losing wicket first ball after the break by controlling power of his shot to hit straight to the fielder. The margin of 7 runs would make one feel that it was a close match, but it wasn't. Most of the runs were scored by DD towards the end when match had gone out of their reach, the odds remaining below 1.05 in last 3 overs. 

The other day, when MI required to score at about same rate against SRH, the odds were as high as 1.35 in f/o SRH, and MI went on to win that match, the batsmen hitting sixes/fours off virtually every  ball at will against one of the best bowling teams of the tournament.




Friday, May 17, 2013

A match under Cloud



Mumbai Indians 166/8 (20/20 ov); Rajasthan Royals 152/7 (20/20 ov)
Mumbai Indians won by 14 runs

The match is already under fixing cloud. Dravid dropped a sitter of Tare in the 7th over. But alas! there is no recording of a conversation with a bookie to tell it was on purpose. We won't believe our eyes but will believe only when after years some conversation is recorded somewhere or some agency tells us something. The book 'Inside the Boundary Line' suddenly appears to have come alive. The sign language, the mafia running the fixing from abroad, another big scandal being brushed under the carpet naming it just some astray spot-fixing, all is there.

81 runs were scored in the first session of 10 overs, much higher than the usual or average in the tournament, especially for MI who had been scoring slowly in the first session so far. And it was for this purpose that Chavan was made to bowl as he did in his second over. I doubt if betting is done for score in a particular over. No doubt, all had to be involved in this session manipulation as always is/has to be the case. The bookie telling Chandila/Chavan to wait till session was over, also clearly points to that the end purpose was session score.  

As mostly happens, the dropped batsman Tare hurt RR much to the extent that they lost in the end, even though MI, uncharacteristic of them in this tournament, faltered badly in the end overs, playing dots, to score only 27 in last 4, in contrast to big hitting at will just in the last match to win that from almost an impossible situation. That was the session manipulation and fixing to make punters lose badly through that 10-20 overs session betting as well.

How precisely Rayudu hit the ball to get caught just inside the boundary! Such precision one can see almost in every match, and in thousands of catches having been given, through past recordings. 

Obviously the script had demanded RR to lose this match, and they batted to lose in a one-sided affair without much fight, having successfully chased in many earlier matches.

The odds never or hardly ever went beyond starting odds of 1.7 in f/o MI such that punters expecting RR to chase well as in previous matches, and backing RR hardly got chance to come to a win-win position or cover their losses.

PW Try Hard but Don't Lose



Pune Warriors 170/4 (20/20 ov); Kolkata Knight Riders 163/7 (20/20 ov)
Pune Warriors won by 7 runs

Before I post analysis/observations about this match, another match-fixing scandal, conveniently named spot-fixing as usual, has come out. Irrespective of that, the staged cricket is to continue as usual. About that, may be later. 

To viewers of this match, it would have appeared that PW were bowling and fielding to lose this match also. But still they won as KKR did better to lose it when it had come well under their control. After bowling two wides for 10 runs in the opening over and then coming to clear ascendancy with KKR 29/3 in the 5th over, PW again let the match slip, by bowling into strong areas of Yusuf Pathan rather than in his weak areas, and continuous misfielding. 

Then with match in their grasp with 122/3 in 15 overs, Pathan and Doeschate well set and in total control, it was KKR's turn to commit harakiri. They did so well and lost in the end, Doeschate getting himself run out and Pathan getting himself out for obstructing the fielder.  Was it and could it be natural? See the recordings and decide for yourself. Is Yusuf Pathan so dumb as a cricketer?

Punters must have got trapped twice, first when match appeared to be in total control of PW and secondly when KKR were in a very comfortable position as mentioned above.

PW batting was seemingly a normal game, session scoring being subtly and aptly manipulated unnaturally.