| Outcome | Probability | Yes Bid | Yes Ask | 24h Change | Volume | |
|---|---|---|---|---|---|---|
| Tigres | 43% | 36¢ | 43¢ | — | $3K | Trade → |
| Cincinnati | 40% | 29¢ | 40¢ | — | $196 | Trade → |
| Tie | 30% | 25¢ | 30¢ | — | $44 | Trade → |
This KALSHI prediction market asks which of the three outcomes will occur in the Cincinnati vs Tigres match; it gives traders and fans a way to express expectations about the game outcome and to monitor how those expectations change as new information arrives.
The matchup pairs a Major League Soccer club (Cincinnati) against a top Liga MX club (Tigres), a common cross-border pairing in friendlies, Cups, or interleague competitions. Differences in style, season timing, and roster construction between the leagues mean form and availability can shift quickly, so context from both clubs matters more than historical labels alone.
Market prices reflect the collective assessment of traders given available information and update as news arrives; they are signals of market sentiment rather than guarantees of result.
This market contains three mutually exclusive outcomes; check the KALSHI event page for the exact labels, which are typically the home win, draw, and away win (or analogous outcome names used by the event).
The event page currently lists the close time as TBD; KALSHI will publish the market close or it will automatically close at a specified cutoff such as kickoff — monitor the event page for the official close time.
Lineup and injury updates often move market sentiment quickly because they change expected strengths; follow official club communications and trusted reporters for the earliest reliable updates that traders will react to.
Head-to-head history provides context but can be misleading if teams have had major roster or coaching changes; prioritize recent form, current rosters, and match context when weighing past results.
Settlement follows KALSHI’s event rules and any notes on the event page; in many cases markets are voided or rescheduled based on the new match date — check the platform’s rulebook and the event description for the contingency policy.