| Outcome | Probability | Yes Bid | Yes Ask | 24h Change | Volume | |
|---|---|---|---|---|---|---|
| EXSAD Gaming | 0% | 0¢ | 0¢ | — | $0 | Trade → |
| Atreides | 0% | 0¢ | 0¢ | — | $0 | Trade → |
This market asks which team will win the matchup between EXSAD Gaming and Atreides on KALSHI, offering a crowd-sourced view of who is expected to win. It matters to fans and traders because it aggregates public information and reactions into tradable prices.
EXSAD Gaming and Atreides are the two competitors in a single-headline match; the event sits within their broader competitive calendar and may be part of a league, tournament, or standalone fixture. Factors such as recent match results, roster continuity, patch or rule changes, and the match's stakes all shape expectations heading into the contest.
Market prices represent the current consensus of traders about the likely outcome and will move as new information arrives; they are signals, not guarantees, and their informativeness depends on market liquidity and the timeliness of information.
The market close and match start are listed by the event organizer and on the KALSHI event page; because the posted close is TBD, monitor the official match schedule and the market page for the announced start time and closing window.
This market has two mutually exclusive outcomes: one for an EXSAD Gaming win and one for an Atreides win; consult the contract terms on KALSHI for resolution rules, including how ties or cancellations are handled.
Treat official roster confirmations as high-impact information: verify the source, assess the incoming player's experience and role fit, and expect the market to react quickly once the change is public.
Head-to-head history provides useful context but is most informative when roster, patch, and format are similar; combine it with recent form and current-team composition rather than relying on it alone.
Low liquidity typically means larger price impact for trades, wider effective spreads, and greater sensitivity to individual bets or news—use smaller sizes, limit orders, and keep an eye on announcements that could trigger abrupt moves.