Kalshi Who will be the Jury winner at Eurovis
Every Kalshi “Who will be the Jury winner at Eurovision” contract of the day — every trade print and the complete Level-2 book, captured co-located with nanosecond venue and receive timestamps. 46 trading days as day bundles, €1 per day, bought as a guest with instant download.
Who will be the Jury winner at Eurovision on Kalshi — activity
Per-day trade and turnover statistics exist from July 2026 onward — a limit of the statistics, not of the capture: older days are archived in full (every contract, every message) without a statistics row.
One purchase, the whole series for a day
A series-day bundle contains every Who will be the Jury winner at Eurovision contract that was listed on Kalshi on that UTC day — traded or not — 35 contract files on the latest covered day. Each file carries the full raw feed: every trade print with price, size and side, plus Level-2 order-book updates, in the same zstd-compressed schema as our crypto venues. Event contracts quote 0..1; turnover is USD-normalized.
Coverage runs April 2026 – May 2026 — 46 trading days, 34.1 MB compressed in total. A day typically holds 35 contract files (up to 35 on the busiest day, 5.04 MB). Pick individual days in the shop calendar for €1 each; delivery is an instant per-file download or one archive for the whole day.
Who will be the Jury winner at Eurovision — last 30 days in the archive
Files, size, contracts traded, trades, USD turnover, buy share, quoted spread, top-of-book depth and order-book updates per UTC day, from the recorded tick data.
| UTC day | Files | Size | Notes | |
|---|---|---|---|---|
| 2026-05-16 | 35 | 5.04 MB | Buy day → | |
| 2026-05-15 | 35 | 1.35 MB | Buy day → | |
| 2026-05-14 | 35 | 1.22 MB | Buy day → | |
| 2026-05-13 | 35 | 1.31 MB | Buy day → | |
| 2026-05-12 | 35 | 1.71 MB | Buy day → | |
| 2026-05-11 | 35 | 2.10 MB | Buy day → | |
| 2026-05-10 | 35 | 1.00 MB | Buy day → | |
| 2026-05-09 | 35 | 1.16 MB | Buy day → | |
| 2026-05-08 | 35 | 772 KB | Buy day → | |
| 2026-05-07 | 35 | 703 KB | Buy day → | |
| 2026-05-06 | 35 | 535 KB | Buy day → | |
| 2026-05-05 | 35 | 982 KB | Buy day → | |
| 2026-05-04 | 35 | 728 KB | Buy day → | |
| 2026-05-03 | 35 | 633 KB | Buy day → | |
| 2026-05-02 | 35 | 281 KB | Buy day → | |
| 2026-05-01 | 35 | 895 KB | Buy day → | |
| 2026-04-30 | 35 | 698 KB | Buy day → | |
| 2026-04-29 | 35 | 610 KB | Buy day → | |
| 2026-04-28 | 35 | 572 KB | Buy day → | |
| 2026-04-27 | 35 | 960 KB | Buy day → | |
| 2026-04-26 | 35 | 550 KB | Buy day → | |
| 2026-04-25 | 35 | 551 KB | Buy day → | |
| 2026-04-24 | 35 | 606 KB | Buy day → | |
| 2026-04-23 | 35 | 483 KB | Buy day → | |
| 2026-04-22 | 35 | 492 KB | Buy day → | |
| 2026-04-21 | 35 | 514 KB | Buy day → | |
| 2026-04-20 | 35 | 441 KB | Buy day → | |
| 2026-04-19 | 35 | 650 KB | Buy day → | |
| 2026-04-18 | 35 | 584 KB | Buy day → | |
| 2026-04-17 | 35 | 727 KB | Buy day → |
Trades and turnover per day appear here once our daily statistics have captured this series — normally the morning UTC after a day closes.
Latest Who will be the Jury winner at Eurovision contracts
The 24 largest Who will be the Jury winner at Eurovision contract files recorded on 2026-05-16— every contract of the series is inside that day's bundle; single contracts can also be bought as individual day files. Per-contract trades, turnover and prices appear here once the daily statistics have captured this series.
- KXEUROVISIONJURY-26-AUS 750 KB buy file →
- KXEUROVISIONJURY-26-FIN 688 KB buy file →
- KXEUROVISIONJURY-26-BUL 635 KB buy file →
- KXEUROVISIONJURY-26-DEN 605 KB buy file →
- KXEUROVISIONJURY-26-CZE 316 KB buy file →
- KXEUROVISIONJURY-26-FRA 275 KB buy file →
- KXEUROVISIONJURY-26-ITA 107 KB buy file →
- KXEUROVISIONJURY-26-ARM 103 KB buy file →
- KXEUROVISIONJURY-26-LAT 84.2 KB buy file →
- KXEUROVISIONJURY-26-CRO 82.0 KB buy file →
- KXEUROVISIONJURY-26-EST 77.1 KB buy file →
- KXEUROVISIONJURY-26-SAN 75.4 KB buy file →
- KXEUROVISIONJURY-26-BEL 75.1 KB buy file →
- KXEUROVISIONJURY-26-LUX 74.1 KB buy file →
- KXEUROVISIONJURY-26-AZE 72.5 KB buy file →
- KXEUROVISIONJURY-26-GER 71.4 KB buy file →
- KXEUROVISIONJURY-26-AUST 69.7 KB buy file →
- KXEUROVISIONJURY-26-POR 69.4 KB buy file →
- KXEUROVISIONJURY-26-GEO 68.6 KB buy file →
- KXEUROVISIONJURY-26-POL 67.7 KB buy file →
- KXEUROVISIONJURY-26-UKR 65.9 KB buy file →
- KXEUROVISIONJURY-26-LIT 64.4 KB buy file →
- KXEUROVISIONJURY-26-SWI 63.9 KB buy file →
- KXEUROVISIONJURY-26-SER 60.4 KB buy file →
Why buy Kalshi Who will be the Jury winner at Eurovision data here
Four things every page on this site is built on — and the reason the numbers above exist at all.
We record everything
The complete public feed of each venue as it was published: every Level-2 snapshot and update at the venue's full book depth, every trade with its aggressor side, every quote, funding, mark-price and liquidation event — for every instrument the venue lists, every UTC day since we added the venue. Nothing sampled, no top-N cut, no on-demand capture.
Institutional grade
Captured co-located at the venue with the exchange timestamp and our receive timestamp in integer nanoseconds, an event-id chain that makes any gap visible, and one normalized schema across 35+ venues — the same capture our own high-frequency trading engine and enterprise feeds run on.
€1 per instrument-day
Any instrument-day is €1, series-day bundles start at €1 — no subscription, no minimum order, no tiers to unlock. Credit packs lower the effective price and never expire, and every venue has free full-day samples to test against first.
Self-service for everyone
Pick the days in the Data Shop, pay by card as a guest and download immediately — no sales call, no enterprise contract, no KYC. Coding agents buy the same files through the MCP server, and the free Agent Skill teaches them the format.
Kalshi Who will be the Jury winner at Eurovision data — FAQ
What Kalshi Who will be the Jury winner at Eurovision data can I download?
Tick-by-tick trades and Level-2 order-book depth for every contract of the Who will be the Jury winner at Eurovision series on Kalshi (35 contract files on the latest day). One bundle = one UTC day of the whole series.
What is the Kalshi series ticker for Who will be the Jury winner at Eurovision?
KXEUROVISIONJURY — every contract of the series carries this prefix in its ticker (followed by the event date and strike). Files in a day bundle are named by the full contract ticker, so a bundle holds every KXEUROVISIONJURY-* contract listed that UTC day.
How far back does the Who will be the Jury winner at Eurovision data go?
Coverage runs April 2026 – May 2026 — 46 trading days in total.
What format are the Kalshi files in?
One zstd-compressed text file per contract per UTC day, in the same normalized schema as our crypto venues — see the market-data specification; free samples on the downloads page.
Can I get Kalshi Who will be the Jury winner at Eurovision data as CSV or Parquet?
Yes — trades export as gzipped CSV or Parquet at no extra cost, with integer microsecond UTC timestamps that load straight into pandas, polars or DuckDB. Kalshi records full order-book depth without a separate BBO stream, so book data ships in the native tick file — the free reader script converts it locally. See the formats overview.
How much does Kalshi Who will be the Jury winner at Eurovision historical data cost?
€1 per series-day bundle — every contract of the series for that day — no subscription, no minimum order; buy as a guest in the Data Shop and download immediately. Credit packs lower the effective price and never expire.
Do I need an account or a sales call?
No. Pick the Who will be the Jury winner at Eurovision series-days in the Data Shop, pay by card as a guest and download immediately — no subscription, no minimum order, no KYC, no enterprise contract, no sales call. Coding agents buy the same bundles through the MCP server.
How is the Kalshi Who will be the Jury winner at Eurovision data captured?
Co-located at the venue, message by message: every Level-2 update and every trade print carries the exchange timestamp and our receive timestamp in integer nanoseconds, an event-id chain makes any gap visible, and one normalized schema across 35+ venues means a parser written for Binance reads these files unchanged. It is the same capture our own high-frequency trading engine runs on — nothing sampled, no top-N cut.