SimpleFunctions

Baltimore · KXNFLTEAMDPTS-LEAST27

Baltimore is priced at 32¢ on Kalshi. Current book: 11¢ bid, 12¢ ask, 1¢ spread. This outcome ranks #3 of 16 inside KXNFLTEAMDPTS-LEAST27.

Price history

32¢ current

+28¢
0¢25¢
Sep 8, 2026Sep 11, 2026

Contract brief

If the Baltimore Pro Football Team allows the fewest points scored in the 2026-27 Pro Football regular season, then the market resolves to Yes.

Outcome

Baltimore

Rank

#3 of 16

Leader

Houston 24¢

Range

1¢-24¢

Family volume

$1K

Identifier

KXNFLTEAMDPTS-LEAST27-BAL

Sep 12, 2026, 6:38 AM UTC · 11m ago

Implied probability

32¢
Latest venue quote
Sep 12, 2026, 6:38 AM UTC · 11m ago

Bid

11¢

Ask

12¢

Spread

Reported volume

$878

Family rank

#3 of 16

16 outcomes · KXNFLTEAMDPTS-LEAST27

Closes

Jan 18, 2027

Family volume

$1K

Orderbook snapshot

11 / 12¢

Kalshi
1¢ spread
BidSize
100¢111
11¢434
2¢546
AskSize
12¢27
24¢100
25¢100
39¢90
57¢425

Contract terms

What resolves this market.

YES condition

If the Baltimore Pro Football Team allows the fewest points scored in the 2026-27 Pro Football regular season, then the market resolves to Yes.

Venue

Kalshi

Closes

Jan 18, 2027

Identifier

KXNFLTEAMDPTS-LEAST27-BAL

SF Signal
SF Index
1150.46
Regime
neutral

Indicators

Yield, cliff risk, volatility, and regime.

IY (Yes)

2300.9%

IY (No)

35.1%

Adj IY

1150%

CRI

8

Overround

-0.0%

Regime

neutral

Score

0.5

Full indicator table

2300.9%
35.1%
Adj IY
1150%
8
Overround
-0.0%

Odds pages

Related prediction questions

Browse odds

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.

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.

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.

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.