| Outcome | Probability | Yes Bid | Yes Ask | 24h Change | Volume | |
|---|---|---|---|---|---|---|
| Butler | 60% | 59¢ | 61¢ | — | $636 | Trade → |
| Creighton | 43% | 40¢ | 42¢ | — | $515 | Trade → |
This market tracks the head-to-head result of the college basketball game Creighton at Butler and matters to traders who want to express views on which team will win. It aggregates real-time information and market sentiment about the matchup.
Creighton and Butler are conference opponents with a history of competitively matched games; both programs have distinct styles that influence how individual matchups play out. Recent form, roster availability, and where the game is played (Butler home court in this case) are common context drivers bettors and analysts watch closely.
Market prices represent the collective judgement of participants about which team will win and will change as new information arrives; they are snapshots of sentiment, not guarantees. Traders use prices to compare how the market values different information (injuries, matchups, news) relative to their own view.
The market close time is listed as TBD; the platform will display the official cutoff once set. Check the event page or your account notifications for the exact closing timestamp and any last-minute changes.
With two outcomes, the market represents which team wins the game outright; settlement follows the official game result (including overtime) unless the market specifies otherwise.
Material lineup news typically prompts rapid price movement as traders update expectations; major absences that change rotations or strategy will be quickly incorporated into market prices.
Recent head-to-head trends and each team’s performance at home versus on the road provide useful context, but weigh them alongside current-season form, roster status, and situational factors like travel and rest.
Settlement in those scenarios follows the platform’s rules: markets may be suspended, voided, or settled based on the official determination of the game’s status. Refer to KALSHI’s event resolution policy for the exact procedures.