Royal Challengers Bengaluru went into the final over against Mumbai Indians on 10 May 2026 needing 15 runs. Raj Angad Bawa needed ten deliveries to complete six legal balls. Rasikh Salam eventually ran the winning two, taking Bengaluru to 167/8 and securing victory by two wickets.
Three wides and a no-ball contributed five of those 15 runs. That detail disappears in the final score.
Two other IPL matches provide a contrast: one had its target revised under DLS, while the other ended without a result. For people following live cricket markets on bizbet during these games, the score alone would not explain how different types of bets might be settled. The three matches show why legal deliveries, revised targets and abandonment rules need to be considered separately.
The Over That Took Ten Deliveries
Mumbai finished on 166/7. Krunal Pandya had earlier made 73 off 46 balls, but at 152/7 Bengaluru still needed 15 from the last over.
According to the IPL’s official ball-by-ball record, Bawa’s over began with a wide and a no-ball before a legal delivery had been completed. There were more wides later, including one that cost two runs. The record shows four extra deliveries in total, worth five runs. Bhuvneshwar Kumar then struck a six, and Rasikh Salam ran two from the last legal ball to finish the match.
Of the 15 runs, five were extras and ten came from legal balls. Romario Shepherd also fell during the over, leaving Bengaluru eight wickets down at the finish.
An over-total market normally includes extras; a batter-runs market does not credit wides or no-ball penalties to batters. And four attempted deliveries here never advanced the legal-ball count. The exact market rules decide the settlement.
Mobile access matters most when match details are changing ball by ball. An Android user who visits bizbet download for android while setting up mobile betting access may also follow the IPL’s delivery log to track the legal-ball count. During Bawa’s final over, that count remained unchanged through the wides and no-ball, even as Bengaluru’s total increased.
The delivery log explains how Bengaluru found those final 15 runs. What it cannot tell us is which prices were available on a betting screen while Bawa was bowling.
Rain Changed the Arithmetic in Lucknow
Three days earlier, Mitchell Marsh hit 111 off 56 as Lucknow Super Giants reached 209/3. Rain repeatedly halted play, reducing the match to 19 overs a side.
Bengaluru came out to chase 213 under the DLS calculation. Rajat Patidar contributed 61 from 31 balls, but the visitors stopped at 203/6. Lucknow’s winning margin was recorded as nine runs.
The innings totals were only six runs apart. That wasn’t the number used to determine the result. After the rain adjustment, 212 would have tied the match. Bengaluru finished nine runs below that mark, despite coming within six of Lucknow’s original total.
The starting required rate was about 11.21 runs per over. Compare that with 8.35 for Bengaluru’s 167-run chase against Mumbai across 20 overs. The difference was 2.86 runs per over before either team had faced the first ball of those chases.
For mobile betting, the updated target becomes essential to understanding the match-winner market. An innings-total selection may have different conditions when rain shortens play. The IPL scorecard supplies the revised figures, while the operator’s market terms determine how a particular wager is handled.
In Kolkata, There Was No Result at All
The 6 April fixture between Kolkata Knight Riders and Punjab Kings never reached a chase. Kolkata were 25/2 after 3.4 overs when rain stopped play. Punjab didn’t bat, and the match ended without a result.
Xavier Bartlett had already dismissed Finn Allen and Cameron Green. Those wickets remained part of the match record even though the contest was abandoned. The notation 3.4 means three completed overs and four legal balls, or 22 deliveries, rather than a decimal fraction.
The IPL’s 2026 playing conditions generally require the side batting second to have the opportunity to face at least five overs for a rain-shortened result, unless the result is achieved earlier. Kolkata’s first innings had barely started, leaving no adjusted chase to evaluate.
A betting slip introduces another question. A match-winner selection and a market concerning events that already occurred aren’t automatically handled the same way after an abandonment. Whether a wager stands or is void depends on its specific conditions. The final score of 25/2 cannot answer that on its own.
What the Three Matches Tell Us
The comparison brings out three different situations:
- Bengaluru-Mumbai, 10 May: ten deliveries, six legal balls and five extras in the final over; Bengaluru won from the last ball.
- Lucknow-Bengaluru, 7 May: 209/3 against 203/6, but a DLS target of 213 produced a nine-run margin.
- Kolkata-Punjab, 6 April: two wickets fell in 22 legal deliveries before rain ended the match without a result.
All three involved numbers that were accurate but incomplete when viewed without the surrounding match information.
During a tight finish, switching between betting markets and ball-by-ball commentary makes it useful to know which figure has changed. In Bengaluru’s final over, the extras added to the team total without being credited to the batters. At Lucknow, the target displayed for the chase had changed after rain.
This comparison covers three matches rather than a full season of results. The scorecards also have their limits: they don’t show precisely when bookmakers changed their prices or how quickly different mobile feeds reported each delivery.
What they do show is that three apparently similar score updates can have very different meanings for a wager. An extra delivery changes the over without using a legal ball. DLS changes the target without changing the runs already scored. An abandoned match leaves recorded wickets but no winner.
A bettor still has to check the conditions attached to the selected market. The match record can explain what happened on the field, but it cannot remove the uncertainty of the next delivery or the risk of losing a stake.
