SimpleFunctions

New England allow 0 points in a single game · KXNFLTSPEC-27NE

New England allow 0 points in a single game is priced at 45¢ on Kalshi. Current book: 3¢ bid, 45¢ ask, 42¢ spread. This outcome ranks #1 of 10 inside KXNFLTSPEC-27NE.

Price history

45¢ current

+43¢
0¢25¢50¢
Aug 3, 2026Aug 8, 2026

Contract brief

If New England 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

New England allow 0 points in a single game

Rank

#1 of 10

Leader

New England allow 0 points in a single game 3¢

Range

3¢-3¢

Family volume

$0

Identifier

KXNFLTSPEC-27NE-PTS0

Aug 8, 2026, 10:38 PM UTC · 1m ago

Implied probability

45¢
Latest venue quote
Aug 8, 2026, 10:38 PM UTC · 1m ago

Bid

Ask

45¢

Spread

42¢

Reported volume

$21

Family rank

#1 of 10

10 outcomes · KXNFLTSPEC-27NE

Closes

Jan 25, 2027

Family volume

$0

Orderbook snapshot

3 / 45¢

Kalshi
42¢ spread
BidSize
100¢200
3¢5
2¢150
AskSize
45¢500
46¢500
60¢90
96¢5.0K
97¢48

Contract terms

What resolves this market.

YES condition

If New England 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 25, 2027

Identifier

KXNFLTSPEC-27NE-PTS0

SF Signal
SF Index
3477.60
Regime
neutral

Indicators

Yield, cliff risk, volatility, and regime.

IY (Yes)

6955.2%

IY (No)

6.7%

Adj IY

3478%

CRI

32

Overround

-0.7%

Regime

neutral

Score

0.5

Full indicator table

6955.2%
6.7%
Adj IY
3478%
32
Overround
-0.7%

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.