| Outcome | Probability | Yes Bid | Yes Ask | 24h Change | Volume | |
|---|---|---|---|---|---|---|
| Umass | 0% | 0¢ | 0¢ | — | $0 | Trade → |
| Richmond | 0% | 0¢ | 0¢ | — | $0 | Trade → |
This market asks which team will win the upcoming Richmond vs UMass matchup; it aggregates trader expectations and provides a real-time signal of how the public and bettors view each team's chances.
Richmond and UMass are NCAA programs with distinct recent trajectories and roster compositions; matchups between them can hinge on conference scheduling, coaching matchups, and roster turnover. Historical head-to-head results and each program's season context (e.g., nonconference scheduling, injuries, and travel) provide useful background when evaluating this contest.
Market prices reflect the balance of money and information placed by traders and will move as new information (lineups, injuries, weather, etc.) becomes available. Treat prices as a snapshot of collective expectation rather than a certainty — unexpected events can shift outcomes quickly.
The market close is listed as TBD on the event page; typically the market closes before the game begins and settlement is based on the official final result reported by the game's governing body per KALSHI's settlement rules.
This market lists two outcomes corresponding to each team winning the game; the outcome that is officially recorded as the winner at final whistle will determine settlement (platform rules cover edge cases like ties or overtime).
Venue is a key input — home teams generally have advantages from familiarity and crowd support; check the event listing for location and factor it into your assessment when the market moves.
Late injury reports, announced starting lineups, weather and travel advisories, coaching staff changes, and publicly reported matchup information (e.g., key player rest or suspension) are the most likely catalysts.
In postponement or cancellation scenarios, KALSHI's event rules apply — markets may be suspended, voided, or held open until an official result is available; consult the platform's resolution policy for the final handling.