Completed match? outcomes for Royal Challengers Bangalore vs Gujarat Titans on April 24, 2026. If the match ends with a definitive final result, settlement mirrors the official ESPNcricinfo result; if tied with no on-field tiebreak, resolves 50-50.
Outcome | Odds | Spread | 24h Change | 24h Volume | Total Volume | Liquidity | |
|---|---|---|---|---|---|---|---|
| Indian Premier League: Royal Challengers Bangalore vs Gujarat Titans | Royal Challengers Bangalore | — | — | — | — | — | |
| Indian Premier League: Royal Challengers Bangalore vs Gujarat Titans - Who wins the toss? | Royal Challengers Bangalore | — | — | — | — | — | |
| Indian Premier League: Royal Challengers Bangalore vs Gujarat Titans - Completed match? | Yes | — | — | — | — | — |
This market refers to the cricket match between Royal Challengers Bangalore and Gujarat Titans scheduled for April 24 2026 in Indian Premier League. This market resolves according to the finalized match result as published by https://www.espncricinfo.com/. DLS/DRS, over-rate penalties, forfeit/walkover, or any other on-field ruling that leads the competition to declare a winner are treated as ordinary wins. If the match ends tied and the playing conditions provide an on-field tiebreak (e.g., Super Over), the winner determined by that tiebreak will be used for resolution. If the match ends tied and no on-field tiebreak is used or available under the playing conditions (e.g., group-stage ODI with no Super Over), the market will resolve 50-50. If the match is postponed/rescheduled, the market remains open until the listed fixture is completed. If the match is permanently canceled or abandoned or otherwise is completed without a winner, the market resolves 50-50. The primary resolution source for this market is the official statistics of the event as recognized by the governing body or event organizers. However, if the governing body or event organizers have not published final match statistics within 2 hours after the event's conclusion, a consensus of credible reporting may be used instead.