SimpleFunctions

Grüne receive at least 20% of valid second votes in the 2026 Berlin state election

At least 20% is priced at 2¢ on Kalshi. Current book: 0¢ bid, 73¢ ask, 73¢ spread. This outcome ranks #4 of 5 inside Will Grüne receive at least.

Price history

2¢ current

0¢5¢
Sep 21, 2026Sep 21, 2026

Contract brief

If the percentage of valid second votes (Zweitstimmen) received by Grüne in the 2026 Berlin state election is 20% to 100%, inclusive of both endpoints, then the market resolves to Yes.

Outcome

At least 20%

Rank

#4 of 5

Leader

At least 12% 82¢

Range

1¢-82¢

Family volume

$26

Identifier

KXVOTEBERLIN-26SEP20GRUN-20

Sep 21, 2026, 7:15 AM UTC · 0m ago

Implied probability

2¢
Latest venue quote
Sep 21, 2026, 7:15 AM UTC · 0m ago

Bid

Ask

73¢

Spread

73¢

24h volume

$5

Family rank

#4 of 5

5 outcomes · Will Grüne receive at least

Closes

Sep 20, 2027

Family volume

$26

Orderbook snapshot

0 / 73¢

Kalshi
73¢ spread
BidSize
AskSize
73¢89
74¢189
94¢89
95¢349

Contract terms

What resolves this market.

YES condition

If the percentage of valid second votes (Zweitstimmen) received by Grüne in the 2026 Berlin state election is 20% to 100%, inclusive of both endpoints, then the market resolves to Yes.

Venue

Kalshi

Closes

Sep 20, 2027

Identifier

KXVOTEBERLIN-26SEP20GRUN-20

SF Signal
Regime
neutral

Event family

Will Grüne receive at least.

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

Total volume

$26

Outcomes

5

Highest price

At least 12% 82¢

Current share

0%

Indicators

Yield, cliff risk, volatility, and regime.

Regime

neutral

Score

0.5

Related readings

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

Browse library
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.

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.

Opinioncomparison

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.

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

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.

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.