New: pay in USDC at checkout, next to cards — prices and invoices stay in EUR.New: pay in USDC

How it works
Low-Latency Trading Solutions
Cart
Polymarket · Climate · event

Polymarket Will the highest temperature in

Every Polymarket “Will the highest temperature in London be …” contract of the day — every trade print and every Level-2 book update, captured co-located with nanosecond venue and receive timestamps. 227 trading days as day bundles, €1 per day, bought as a guest with instant download.

Trading days
227
Coverage
May 2025 – February 2026
Archive size
693 MB
Price per day
€1
Activity & identifier

Will the highest temperature in London be … on Polymarket — 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.

Slug prefix
will-the-highest-temperature-in-london-be-
Files on latest day
4
Typical files / day
27
What's in a bundle

One purchase, the whole series for a day

A series-day bundle contains every Will the highest temperature in London be … contract that was listed on Polymarket on that UTC day — traded or not — 4 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 May 2025 – February 2026 — 227 trading days, 693 MB compressed in total. A day typically holds 27 contract files (up to 42 on the busiest day, 13.7 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.

Daily statistics

Will the highest temperature in London be … — 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 dayFilesSizeNotes
2026-02-03458.7 KBBuy day →
2026-02-02113.17 MBBuy day →
2026-02-01142.17 MBBuy day →
2026-01-3114202 KBBuy day →
2025-12-14375.4 KBBuy day →
2025-12-1310906 KBBuy day →
2025-12-12171.56 MBBuy day →
2025-12-11241.99 MBBuy day →
2025-12-10251.95 MBBuy day →
2025-12-09252.01 MBBuy day →
2025-12-08263.26 MBBuy day →
2025-12-07243.29 MBBuy day →
2025-12-06323.04 MBBuy day →
2025-12-05413.17 MBBuy day →
2025-12-04251.78 MBBuy day →
2025-12-03251.43 MBBuy day →
2025-12-02262.85 MBBuy day →
2025-12-01243.24 MBBuy day →
2025-11-30252.59 MBBuy day →
2025-11-29323.33 MBBuy day →
2025-11-28382.97 MBBuy day →
2025-11-27244.05 MBBuy day →
2025-11-26254.04 MBBuy day →
2025-11-25263.66 MBBuy day →
2025-11-24242.33 MBBuy day →
2025-11-23254.97 MBBuy day →
2025-11-22304.83 MBBuy day →
2025-11-21393.36 MBBuy day →
2025-11-20241.83 MBBuy day →
2025-11-19252.15 MBBuy day →

Trades and turnover per day appear here once our daily statistics have captured this series — normally the morning UTC after a day closes.

Contracts

Latest Will the highest temperature in London be … contracts

The 4 largest Will the highest temperature in London be … contract files recorded on 2026-02-03— 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.

Build a bot

Build a Will the highest temperature in London be … model on this data

Every Will the highest temperature in London be … event lists a ladder of strikes — one contract per range — and the rung that settles in the money is the label, so the ladder's prices read as an implied distribution rather than one probability. The day bundle holds the full order-book path and trade tape of every rung, nanosecond-stamped; the statistics on this page cover the most traded contracts per day; the bundle holds every contract listed on Polymarket that day.

Split by release or event day, never at random — every rung of one ladder settles on the same print, so the whole ladder is one example; walk forward over releases. The ladder guide works distribution labels, cross-strike features and the link to the crypto strike grids through.

Purchased data is for your own use — backtesting, research, analytics and training your own models, in-house or in your own products; the trained models and derived data you build from it are yours. The raw files and tick streams themselves may not be redistributed, resold or published. The full terms are on the data license page.

Why CryptoStruct

Why buy Polymarket Will the highest temperature in London be … 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, 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. Where a venue offers more than one order-book feed, we take the one with the lowest latency, at the depth that feed carries. Nothing sampled, 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 free full-day samples from the major venues let you test first.

Self-service for everyone

Pick the days in the Data Shop, pay by card or in USDC 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.

Agents: /llms.txt · MCP server /mcp · every page as markdown via Accept: text/markdown

FAQ

Polymarket Will the highest temperature in London be … data — FAQ

What Polymarket Will the highest temperature in London be … data can I download?

Tick-by-tick trades and Level-2 order-book depth for every contract of the Will the highest temperature in London be … series on Polymarket (4 contract files on the latest day). One bundle = one UTC day of the whole series.

How far back does the Will the highest temperature in London be … data go?

Coverage runs May 2025 – February 2026 — 227 trading days in total.

What format are the Polymarket 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 Polymarket Will the highest temperature in London be … 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. Polymarket records 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 Polymarket Will the highest temperature in London be … 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 Will the highest temperature in London be … series-days in the Data Shop, pay by card or in USDC 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 Polymarket Will the highest temperature in London be … 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.

Topics

Topic hubs featuring this series