SimpleFunctions

Cleveland allow 0 points in a single game · KXNFLTSPEC-27CLE

Cleveland allow 0 points in a single game is priced at 15¢ on Kalshi. Current book: 3¢ bid, 98¢ ask, 95¢ spread. This outcome ranks #3 of 9 inside KXNFLTSPEC-27CLE.

Price history

15¢ current

+7¢
0¢10¢
Aug 21, 2026Sep 19, 2026

Contract brief

If Cleveland Pro Football Team allow 0 points in a single game in the 2026-27 Pro Football regular season, then the market resolves to Yes.

Outcome

Cleveland allow 0 points in a single game

Rank

#3 of 9

Leader

Shedeur Sanders records 1500+ passing yards 52¢

Range

3¢-52¢

Family volume

$0

Identifier

KXNFLTSPEC-27CLE-PTS0

Sep 20, 2026, 7:08 AM UTC · 25m ago

Implied probability

15¢
Latest venue quote
Sep 20, 2026, 7:08 AM UTC · 25m ago

Bid

Ask

98¢

Spread

95¢

Reported volume

$446

Family rank

#3 of 9

9 outcomes · KXNFLTSPEC-27CLE

Closes

Jan 18, 2027

Family volume

$0

Orderbook snapshot

3 / 98¢

Kalshi
95¢ spread
BidSize
100¢200
3¢5
2¢150
AskSize
98¢150
99¢200

Contract terms

What resolves this market.

YES condition

If Cleveland Pro Football Team allow 0 points in a single game in the 2026-27 Pro Football regular season, then the market resolves to Yes.

Venue

Kalshi

Closes

Jan 18, 2027

Identifier

KXNFLTSPEC-27CLE-PTS0

SF Signal
SF Index
4904.00
Regime
neutral

Indicators

Yield, cliff risk, volatility, and regime.

IY (Yes)

9808.0%

IY (No)

9.4%

Adj IY

4904%

CRI

32

Overround

-0.2%

Regime

neutral

Score

0.5

Full indicator table

9808.0%
9.4%
Adj IY
4904%
32
Overround
-0.2%

Related readings

Matched from SimpleFunctions blog, opinions, technical guides, concepts, and learn pages.

Browse library
Blogmarkets

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.

Technicalguide

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.

Opinionanalysis

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.

Blogmarkets

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.

Opinionanalysis

Market Making on Polymarket: Why Maker Status Cuts Loss Probability by 36 Points — and Why Spreads Persist Anyway

Akey et al.'s most economically significant finding: moving from pure taker to pure maker status reduces the probability of losing money by ~36 percentage points on Polymarket. Resolution-spec risk is why cross-platform spreads persist at 1.5–4.5% and why even Susquehanna and Jump can't fully arb them.

Opinionanalysis

Implied Yield vs Raw Probability: Why Bond-Adjacent Prediction Markets Need a Different Lens

Why fixed-income-adjacent prediction-market contracts need to be priced in implied yield, not raw probability, with two real Kalshi Fed-decision contracts as a case study.

SimpleFunctions context

Index, screen, query, and monitor.

Open index

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.