Kalyani Bengaluru Blasters to win the toss against Coastal Kings Mangaluru on June 29, 2026. Toss result settles per final match outcome rules; if the toss is not decisive for the match result, the market remains unresolved until completion.
Outcome | Odds | Spread | 24h Change | 24h Volume | Total Volume | Liquidity | |
|---|---|---|---|---|---|---|---|
| Maharaja T20 Trophy: Kalyani Bengaluru Blasters vs Coastal Kings Mangaluru | Kalyani Bengaluru Blasters | — | — | — | — | — | |
| Maharaja T20 Trophy: Kalyani Bengaluru Blasters vs Coastal Kings Mangaluru - Who wins the toss? | Kalyani Bengaluru Blasters | — | — | — | — | — | |
| Maharaja T20 Trophy: Kalyani Bengaluru Blasters vs Coastal Kings Mangaluru - Completed match? | Yes | — | — | — | — | — |
This market refers to the cricket match between Kalyani Bengaluru Blasters and Coastal Kings Mangaluru scheduled for June 29 2026 in Maharaja T20 Trophy. 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.