SimpleFunctions

Tottenham · KXEPLTOP-27TOP2

Tottenham is priced at 14¢ on Kalshi. Current book: 9¢ bid, 13¢ ask, 4¢ spread. This outcome ranks #5 of 5 inside KXEPLTOP-27TOP2.

Price history

14¢ current

+10¢
0¢10¢
Jun 27, 2026Jul 20, 2026

Contract brief

If Tottenham is a top 2 finisher in the 2026-27 EPL season, then the market resolves to Yes.

Outcome

Tottenham

Rank

#5 of 5

Leader

Manchester United 20¢

Range

9¢-20¢

Family volume

$65

Identifier

KXEPLTOP-27TOP2-TOT

Jul 20, 2026, 8:38 PM UTC · 18m ago

Implied probability

14¢
Latest venue quote
Jul 20, 2026, 8:38 PM UTC · 18m ago

Bid

Ask

13¢

Spread

Reported volume

$495

Family rank

#5 of 5

5 outcomes · KXEPLTOP-27TOP2

Closes

Jun 14, 2027

Family volume

$65

Orderbook snapshot

9 / 13¢

Kalshi
4¢ spread
BidSize
9¢29
8¢69
6¢188
AskSize
13¢5
14¢807
30¢1
49¢87
50¢54

Contract terms

What resolves this market.

YES condition

If Tottenham is a top 2 finisher in the 2026-27 EPL season, then the market resolves to Yes.

Venue

Kalshi

Closes

Jun 14, 2027

Identifier

KXEPLTOP-27TOP2-TOT

SF Signal
SF Index
624.72
Regime
neutral

Event family

KXEPLTOP-27TOP2.

The same race as a probability stack: rank, volume, and where this contract sits against the other outcomes.

Total volume

$65

Outcomes

5

Highest price

Manchester United 20¢

Current share

52%

Indicators

Yield, cliff risk, volatility, and regime.

IY (Yes)

1124.4%

IY (No)

11.0%

Adj IY

625%

CRI

10

RV

557%

VR

1.56

Regime

neutral

Score

0.5

Full indicator table

1124.4%
11.0%
Adj IY
625%
10
RV
557%
VR
1.56
IAR
0.2/h
Overround
-0.4%
LAS
0.44

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

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.

Blogtech

MCP Servers for Prediction Markets: Connect Claude Code to Kalshi and Polymarket

Connect Claude Code, Cursor, or Cline to Kalshi and Polymarket prediction markets via MCP. One-line setup, 18 tools, real-time market data for AI agents.

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.