Epex Spot officially adopts 5-minute day-ahead power trading.
Epex Spot noted that moving from 15-minute to 5-minute day-ahead trading is logical but costly. A formal regulatory or exchange market-design rule change implementing 5-minute trading resolves this.
Across 6 frontier models answering independently, the panel has all but ruled it out: the median is 10%.
They broadly agree, 23 points between GPT at 29% and Gemini at 6%.
Nothing is settled until 2 Oct 2027, when the outcome is checked against sources and every number above gets a permanent score.
What each one said
-
GPTOpenAI
EU day-ahead reform is moving toward finer granularity, but EPEX-wide 5-minute adoption needs a costly, coordinated rule change.
- EPEX, national regulators and EU market-coupling operators must align products, algorithms, settlement and data systems before go-live.
- The 15-minute MTU took years to standardize across Europe; a one-year window is short for a further threefold increase in auctions.
- Odds rise sharply if ACER or the European Commission mandates a 5-minute market time unit in an adopted implementing rule by 2027.
29% -
QwenAlibaba
ACER/ENTSO-E regulatory timeline and Epex Spot's own cost concerns make a 12-month window too tight for full implementation.
- Epex Spot has publicly called 5-min DA trading 'logical but costly,' signaling no near-term commitment; exchange rule changes of this scale typically require 18-36…
- The EU Electricity Balancing Regulation (EBGL) and subsequent ACER decisions have pushed toward shorter intervals, but no binding mandate with a 2027 deadline exists…
- Precedent: the 15-min intraday switch took years of coordination across NEMOs and TSOs; a similar multi-stakeholder process for day-ahead makes completion by Oct 2027…
18% -
GrokxAI
EPEX 5-min DA needs ACER/NEMO/TSO rule change plus IT overhaul after 15-min SDAC just landed.
- 15-min day-ahead coupling only went live in 2025; a further MTU cut requires new CACM/algorithm specs and pan-European testing that historically take 3+ years.
- EPEX itself called 5-min logical but costly; no public consultation, ACER decision or go-live date exists as of Oct 2026.
- Only a surprise ACER mandate or German/French TSO push in Q1 2027 would move the needle; otherwise the 2027 window is too short.
12% -
DeepSeekDeepSeek
No EU power exchange has even moved to 15-minute day-ahead MTUs; 5-minute is a decade-plus away.
- EPEX's own 15-minute day-ahead products only launched in 2025, so the 5-minute step is at least one full MTU cycle later.
- ACER and ENTSO-E must first amend the CACM/EB GL single-day-ahead-coupling rules, a multi-year comitology process not yet started.
- Precedent: intraday 15-minute MTUs took roughly a decade from pilot to binding EU-wide go-live, and day-ahead lags intraday.
7% -
GeminiGoogle
SDAC algorithm complexity and NEMO governance prevent scaling from 15-minute to 5-minute day-ahead trading within one year.
- ACER, ENTSO-E, and NEMO regulatory approvals require multi-year consultation cycles that have not yet formally commenced.
- Solving the Euphemia market coupling algorithm at 5-minute granularity exceeds current computational limits within the clearing window.
- A binding ACER decision ordering 5-minute SDAC implementation before late 2027 would materially raise these odds.
6% -
ClaudeAnthropic
Needs a formal EU/NRA market-design rule change plus Epex implementation, unlikely within one year.
- EU day-ahead markets only recently shifted to 15-minute standard (2025), and no active mandate exists for 5-minute granularity.
- Epex itself calls the move costly and has not announced a timeline or regulatory filing to transition further.
- Regulatory/market-design changes of this scale typically take multiple years from proposal to adoption across EU TSOs/NRAs.
6%
6 of 6 models answered · 23 points between the highest and lowest. None was shown the market price.
Question sourced from a news sweep on 2 Oct 2026. Forecast by google/gemini-3.8-flash, anthropic/claude-sonnet-5, openai/gpt-5.6-terra, x-ai/grok-4.6, deepseek/deepseek-v4.1-flash, qwen/qwen3.8-max-0902 via OpenRouter.