Green Bay · KXNFLH2HWINS-27GBDET
Green Bay is priced at 30¢ on Kalshi. Current book: 29¢ bid, 39¢ ask, 10¢ spread. This outcome ranks #2 of 2 inside KXNFLH2HWINS-27GBDET.
Price history
30¢ current
+8¢Contract brief
If Green Bay records more wins than Detroit in the 2026-27 Pro Football regular season, then the market resolves to Yes.
Outcome
Green Bay
Rank
#2 of 2
Leader
Detroit 65¢
Range
30¢-65¢
Family volume
$0
Identifier
KXNFLH2HWINS-27GBDET-GB
Sep 17, 2026, 10:38 PM UTC · 2m ago
Implied probability
Bid
29¢
Ask
39¢
Spread
10¢
Reported volume
$728
Family rank
#2 of 2
2 outcomes · KXNFLH2HWINS-27GBDET
Closes
Feb 1, 2027
Family volume
$0
Orderbook snapshot
29 / 39¢
Contract terms
What resolves this market.
YES condition
If Green Bay records more wins than Detroit in the 2026-27 Pro Football regular season, then the market resolves to Yes.
Venue
Kalshi
Closes
Feb 1, 2027
Identifier
KXNFLH2HWINS-27GBDET-GB
Event family
KXNFLH2HWINS-27GBDET.
The same race as a probability stack: rank, volume, and where this contract sits against the other outcomes.
Total volume
$0
Outcomes
2
Highest price
Detroit 65¢
Current share
—
Detroit
kalshi · KXNFLH2HWINS-27GBDET-DET
Green Bay
kalshi · KXNFLH2HWINS-27GBDET-GB
Indicators
Yield, cliff risk, volatility, and regime.
Regime
neutral
Score
0.5
Odds pages
Related prediction questions
Related readings
Matched from SimpleFunctions blog, opinions, technical guides, concepts, and learn pages.
Prediction market liquidity: why depth matters more than volume for serious traders
Why orderbook depth matters more than volume for prediction market traders. Real Kalshi examples, liquidity scoring framework, and how to avoid slippage.
Kalshi vs Polymarket: Which Prediction Market Should You Trade?
In-depth comparison of Kalshi and Polymarket for prediction market traders. Regulatory structure, liquidity, fees, API tooling, and cross-venue trading with SimpleFunctions.
Prediction Market Orderbook Analysis: Reading Depth, Spread, and Liquidity
How to read prediction market orderbooks. Binary settlement, spread-as-percentage, depth asymmetry, executable edge calculation, and cross-venue arbitrage analysis.
Kalshi vs Polymarket: A Developer's Comparison of APIs, Orderbooks, and Liquidity
Data-driven comparison of Kalshi and Polymarket APIs, orderbooks, rate limits, and liquidity. Code examples for building on both prediction markets.
Liquidity Availability Is the Real Edge in Prediction Markets
Implied yield, cliff risk, and overround all describe what to trade. Liquidity Availability Score describes whether the orderbook can absorb the trade. Why LAS is the indicator that decides who actually books P&L.
Kalshi vs Polymarket: Mechanics, Fees, Regulation, Liquidity (2026)
Side-by-side comparison of Kalshi and Polymarket in 2026. Fee math, calibration data, withdrawal speed, and a decision tree for picking the right venue.
SimpleFunctions context
Index, screen, query, and monitor.
Prediction Market Index
Market-wide volatility, geo risk, breadth, and activity around this contract.
Market Screener
Filter adjacent contracts by volume, expiry, IY, CRI, venue, and theme.
Event Probability API
Read 30% as a structured event probability object for agents and apps.
Realtime Data API
Prices, orderbooks, movement, heat, and liquidity indicators across venues.
World State API
Compact market-aware context packets for agent sessions and scheduled refresh.
Hedging Workflows
Map a thesis or exposure to candidate event markets and monitoring paths.
How we compute these odds
SimpleFunctions aggregates live prediction-market contracts from Kalshi and Polymarket. Each slug groups contracts that resolve on the same underlying event, identified by venue event_id.
For binary slugs, the headline probability is the liquidity-weighted mid-price across all bound contracts. For multi-outcome slugs (e.g. elections with 3+ candidates), the headline is the leader’s price; we never arithmetically average disjoint outcomes — that would produce a number with no real-world meaning.
Snapshots refresh every 5 minutes during market hours; daily aggregates are computed at 04:00 UTC. The 30-day sparkline is drawn from per-ticker daily means stored in market_indicator_daily; 24h delta and movement events are derived from the same source.