forecasting
agent
← back to scans

EU country blames Russia for new sabotage attack by October 31?

polymarketWorld·2026-09-28·view on polymarket ↗
47%
Agent
45%
Market Price
+1.8%
Edge
54%
Confidence
22,211
Volume
2.0c
Spread
33
Days to resolution
2
Markets in event
final rationale
Mean of 5 draws (0.47, 0.48, 0.47, 0.46, 0.46). (0) No source shows the condition met. Germany's Leipzig attribution came on Sept 1-2, before the market opened on Sept 19, so it cannot count, and the resolution-source read confirms no qualifying post-creation attribution. Every newer case is still hedged: the Polish Starlink arson (prosecutors cite 'reasonable suspicion' of orders from Russian services), the Munich arson (FAZ reports investigators suspect the GRU, but prosecutors decline to confirm), and the Dutch rail and Danish airport incidents (not linked to Russia). (a) About 33 days remain until Oct 31. (b) If nothing changes, the market resolves No. (c) No scenario: investigations stall at 'likely/modus operandi' language, prosecutors keep charges generic (arson, criminal damage), and attribution lags for months, as with Marywilska. (d) Yes scenario: Polish prosecutors charge suspects in the Starlink fire with acting on behalf of Russian intelligence (a common Polish charging formula), or Munich prosecutors or German ministers formally name the GRU. Other candidates are Slovakia's Skyeton cell and the Wunstorf probe; any of these could cross the bar quickly given the current political willingness to name Moscow. The market sits at 45% and has drifted down from 54% as the week passed without an attribution. The December market at 67% implies a consistent hazard rate. The unusually dense pipeline of primed cases slightly offsets the strict wording bar, so I stay near the anchor.
price vs. prediction
market price agent forecast at t+0
20 follow-ups
re-scan context
This market has been scanned before. Previous predictions:
datepredictedmarket priceconfidence
2026-09-21 56% 56% 54%
1. Planner Opus 5.5 · picks the research tools
Tools chosen: polymarket_direct resolution_source wikipedia gdelt_news polymarket_related kalshi_related
Planner reasoning
The Polymarket price is the anchor, and the resolution source is official statements from EU governments. A Wikipedia list of Russian sabotage incidents in Europe gives a base rate for how often governments formally attribute attacks. GDELT can catch recent foreign-language reporting of formal attributions or prosecutor charges since August 2026, and related markets add cross-venue signal.
2. Research parallel tool calls + 4 web research loops (Sonnet 5) · read raw by the forecasters
at a glance
RESEARCH DIGEST (built in code: tool summaries and each report's bottom line; the forecasters read the full tool outputs and reports) Tools - polymarket_direct: ## This Market's Polymarket Data **EU country blames Russia for new sabotage attack by October 31?** - Current price (probability): 45.00% (live; bid 44% / ask 46%) - 7-day price change: -4.50% - 30-day price change: -3.50% - Total volume: $22,211 (USD notional) - Price range: 45.00% - 54.00% - Data points: 10 days - resolution_source: already_resolved=unclear; matches_criteria=False; last_updated=2026-09-26 (Spokesman-Review); 2026-09-02 (ADN/AP). The sources describe Germany officially blaming Russia for a foiled explosive-drone attack at Leipzig/Halle Airport on Aug. 4, 2026 (attribution made early September 2026), and broader reporting on rising hybrid attacks/sabotage suspicions attributed to Russia (e.g., Polish factory fi - wikipedia: Fetched 2 Wikipedia entries (1 missing pages). - gdelt_news: GDELT: 45 articles across 3 queries (lookback=60d). 'prosecutors charge sabotage on behalf of Russian intelligence': 15 hits | 'government attributes arson sabotage to Russia GRU': 15 hits | 'Poland sabotage Russia charged': 15 hits - polymarket_related: Polymarket search over 3 keyword(s), kept 6 matches. keyword 'Russia sabotage': 2 markets | keyword 'Russia attack NATO': 0 markets | keyword 'Russia Europe': 4 markets - kalshi_related: 1 related markets / summaries. keyword 'Russia sabotage': no matches | keyword 'Russia NATO': ok Research loops, bottom lines - current state: As of Sept. 28, 2026, the clearest qualifying-style attribution (Germany/Leipzig, Sept. 2) occurred before the Sept. 19 market-creation window and cannot itself resolve "Yes"; several subsequent incidents (Munich arson, Brandenburg grid sabotage, Hannover drone, Danish airport arson, Romanian drone incursion) remain at the "suspected/strong indications/not yet linked" stage rather than formal government attribution, meaning no new qualifying attack has yet been officially blamed on Russia since - base rate: Over the past ~18 months the reference class shows a qualifying-style government attribution (explicit "carried out/ordered/directed by Russia" statement or matching criminal charges) occurring roughly every 1–3 months somewhere in the EU (Poland Nov 2025, Germany Sept 2026, plus earlier Lithuanian/Polish arson prosecutions), even though many more incidents are only described as "suspected" or "consistent with" Russian activity and thus would not qualify; this suggests a moderately high per-6-we - yes case: The strongest Yes path is that one of several already-open, fast-moving investigations (Munich arson prosecution, Poland's Exatel/Starlink fire, or the Wunstorf drone probe) crosses from "suspected/hallmarks/likely" language into a formal "ordered/directed by Russia" statement or matching criminal charge before Oct. 31 — a transition that recent precedent (Poland's 2-4 day investigator-to-attribution lag, Germany's Sept. 1 Leipzig move) shows can happen quickly once evidence is judged sufficient - no case: In the nine days since market creation, every newly reported incident that might otherwise qualify (Wola Krobowska Starlink arson, Munich, Dutch rail sabotage, Lolland-Falster) has stalled at "suspected/reasonable suspicion/likely" language or remains unattributed, while the one unambiguous state-attributed incident (Gedser) does not meet the sabotage/territory definition — showing a real gap between frequent hybrid incidents and the rarer, slower step of formal unequivocal government attributio
tools
toolstatustimeitemssummary
polymarket_direct OK 0.3s 1 ## This Market's Polymarket Data **EU country blames Russia for new sabotage attack by October 31?** - Current price (probability): 45.00% (live; bid 44% / ask 46%) - 7-day price change: -4.50% - 30-day price change: -3.50% - Total volume: $22,211 (USD notional) - Price range: 45.00% - 54.00% - Dat
resolution_source OK 43.7s 1 already_resolved=unclear; matches_criteria=False; last_updated=2026-09-26 (Spokesman-Review); 2026-09-02 (ADN/AP). The sources describe Germany officially blaming Russia for a foiled explosive-drone attack at Leipzig/Halle Airport on Aug. 4, 2026 (attribution made early September 2026), and broader
wikipedia OK 0.3s 2 Fetched 2 Wikipedia entries (1 missing pages).
gdelt_news OK 174.1s 45 GDELT: 45 articles across 3 queries (lookback=60d). 'prosecutors charge sabotage on behalf of Russian intelligence': 15 hits | 'government attributes arson sabotage to Russia GRU': 15 hits | 'Poland sabotage Russia charged': 15 hits
polymarket_related OK 0.3s 6 Polymarket search over 3 keyword(s), kept 6 matches. keyword 'Russia sabotage': 2 markets | keyword 'Russia attack NATO': 0 markets | keyword 'Russia Europe': 4 markets
kalshi_related OK 0.6s 1 1 related markets / summaries. keyword 'Russia sabotage': no matches | keyword 'Russia NATO': ok
research loops · 4/4 ok · 19 searches · 4 page reads
dimensionstatustimesearchespage readsreport
current state OK 43s 5 1 5723 chars
base rate OK 44s 4 2 5993 chars
yes case SNIPPETS 38s 5 0 5534 chars · no page read; snippets only
no case OK 45s 5 1 6615 chars
report: current state
- [2026-09-02] Germany's government formally attributed the Aug. 4 Leipzig/Halle Airport explosive-drone incident to Russia; Interior Minister Dobrindt said intelligence showed "people being involved who acted on behalf of Russian state entities," and Berlin announced it would close a Russian consulate. Dobrindt told reporters that intelligence points to "people being involved who acted on behalf of Russian state entities," and said "the police investigations, the pattern and intelligence findings prove a Russian responsibility for the attempted attack at Leipzig airport." This attribution predates the Sept. 19 market-creation date and so cannot itself trigger a "Yes" (only qualifies as a prior fact/backdrop). Source: npr.org. - [2026-09-03] A Munich arson/explosive-device attack near defense firms Rohde & Schwarz and Helsing was reported by German media as having "strong indications of hybrid background" linked to a Russian secret service, but this was sourced to media/security-service leaks, not a formal government attribution. "there are strong indications that the arson attack near an arms company in Munich could also have been perpetrated on behalf of a Russian secret service" Source: miningawareness.wordpress.com (citing Tagesschau/ARD). - [2026-09-08] A Henry Jackson Society write-up states "Germany blames Russia for energy grid sabotage as attacks across Europe intensify, raising fears of escalating hybrid warfare" regarding rocket/IED devices found at a Brandenburg power substation — but this too predates market creation (Sept. 19) and would count only as background, not a new triggering event. - [2026-09-18 to 09-22] German investigators were reportedly probing a drone found near Hannover/Wunstorf air base for links to the original Leipzig case, with explosives "likely found" near the base by Sept. 22, per Ukrainian-language reporting citing German press — no new formal government attribution announced. Source: news.liga.net. - [2026-09-25] German outlet FAZ reported further investigative detail (per Critical Threats' Sept. 27 roundup) on the Leipzig case, and German security services reportedly assess GRU officer Denis Smolyaninov is likely responsible — but this is intelligence-source reporting, not a fresh official government statement, and concerns the already-attributed Leipzig incident. Source: criticalthreats.org. - [2026-09-26] Danish police (South Zealand and Lolland-Falster district) confirmed investigating an attempted arson attack on a plane wing at Lolland-Falster Airport but explicitly stated they have not yet linked it to Russia. "Danish police are investigating an attempted arson attack against the wing of a plane at Lolland-Falster Airport but have not yet linked the incident to Russia." Source: criticalthreats.org. - [2026-09-27] Romanian Ministry of National Defense reported an unidentified drone crossing into Romanian airspace near Chilia Veche on Sept. 26; authorities have not attributed this to Russia, and in any case drone incursions are explicitly excluded from the market's "qualifying attack" definition. "Romanian authorities have not publicly attributed the incursion to Russia, but the incident is likely part of the Kremlin's continued efforts to normalize European airspace violations." Source: criticalthreats.org. - [2026-09-26] A USA Today/Spokesman-Review feature published Sept. 26 recaps the Leipzig attribution and broader hybrid-war concerns but reports no new qualifying attribution since market creation; quoted officials (Kallas, Tsahkna) still discuss the Leipzig case and general Russian sabotage patterns, not any fresh incident-specific blame. Source: spokesman.com. - [2026-09-27] Polish authorities are separately described as having "recently blamed Russia for starting a fire at a factory producing weapons for Ukraine" (Polish drone-factory fire, first reported early September), which per USA Today's framing appears to be treated as part of the same wave — exact attribution date and whether it meets the "official government" qualifying bar (vs. police/agency statement) is unclear from available sources. Source: spokesman.com. - [2026-09-08] UK-linked reporting (Henry Jackson Society) notes ongoing UK cases (Starmer-linked vandalism, London warehouse arson) already resolved via criminal prosecution attributing Russian financing — these are prior, pre-market attributions and would not count as new qualifying events even if referenced again. Source: henryjacksonsociety.org. BOTTOM LINE: As of Sept. 28, 2026, the clearest qualifying-style attribution (Germany/Leipzig, Sept. 2) occurred before the Sept. 19 market-creation window and cannot itself resolve "Yes"; several subsequent incidents (Munich arson, Brandenburg grid sabotage, Hannover drone, Danish airport arson, Romanian drone incursion) remain at the "suspected/strong indications/not yet linked" stage rather than formal government attribution, meaning no new qualifying attack has yet been officially blamed on Russia since market open. Given the extremely high recent frequency of such incidents and Germany's demonstrated willingness to attribute quickly, a fresh qualifying attribution before Oct. 31 is plausible but not yet confirmed. NOT FOUND: No official EU-member-state government statement or criminal charge dated after Sept. 19, 2026 that meets the strict "ordered/directed by the Russian state" qualifying-attribution bar (as opposed to "suspected," "hallmarks of," or unnamed-official framing) could be located as of this research; could not confirm the exact date/wording of the Polish drone-factory-fire attribution or whether Munich's Sept. 3 case has since been escalated to formal government attribution.
report: base rate
- [2026-09-01] Germany's Interior Minister Alexander Dobrindt made the first formal government-level accusation directly naming Russia for the August Leipzig/Halle Airport drone-bomb incident, marking a rare full attribution: the German government on Sept. 1 officially accused a Russian intelligence service of attempting to carry out a drone attack at Leipzig/Halle Airport in early August, marking the first time Berlin has directly blamed Moscow for the incident, citing "clear indications from our intelligence services and partner agencies" (https://kyivindependent.com/germany-officially-blames-russia-for-drone-attack-attempt-at-leipzig-airport/). - [2025-11-16] Poland's government formally attributed a railway sabotage (explosives on Warsaw–Lublin line near Mika/Puławy) to Russian intelligence, and prosecutors charged suspects accordingly: The Polish government said both events were "acts of sabotage," and blamed Russian intelligence for carrying out the attack; two Ukrainian men working for the Russian Federal Security Service (FSB) were formally accused of the attacks by Polish prosecutors (https://en.wikipedia.org/wiki/2025_Russian_railway_sabotage_in_Poland). - [2025-12-19] Denmark issued its first-ever formal attribution to Russia, but for cyberattacks (non-qualifying under this contract's cyber exclusion): Denmark accused Russia on Thursday of cyberattacks on water utility and election websites, marking the first time Copenhagen publicly attributed such attacks to Moscow (https://euronews.com/2025/12/19/denmark-blames-russia-for-cyberattacks-on-water-utility-and-election-websites). - [2025-09] A GPS-jamming incident affecting von der Leyen's plane over Bulgaria was blamed on Russia by Bulgaria, but this is a non-qualifying electronic-interference case: Almost 24 hours after the incident, Bulgaria pointed a finger at the Kremlin, accusing it of being responsible (https://www.npr.org/2025/09/01/nx-s1-5524884/eu-blasts-russia-for-interference-of-plane-carrying-european-commission-president). - [2026-08-31/09-03] A fire at Poland's WB Electronics drone-parts plant was called sabotage by PM Tusk, but Russian state responsibility itself was only "linked," not formally attributed: Prime Minister Donald Tusk says investigators have established deliberate arson and sabotage; Tusk linked the incident to Russian efforts to destabilise Europe, but Russian responsibility has not been established (https://europeanrelations.com/quick-brief/poland-suspects-russia-in-factory-sabotage/) — illustrating how many incidents stop short of a qualifying attribution. - [2026-09] A former senior NATO official noted such direct blame is historically infrequent: It is very rare that Germany actually calls Russia out on one of these sabotage attempts (https://www.pbs.org/newshour/show/european-countries-confront-russian-sabotage-and-shadow-warfare). - [2026-09] Reporting on the frequency of the broader incident base: In late 2025, the Associated Press counted 145 sabotage attacks, including explosions, fires, drone incursions, and cut undersea cables, while a confidential German police report showed 321 suspected cases of sabotage registered in 2025 alone , yet only a small subset produced formal state-to-state Russia attributions (https://euobserver.com/236326/not-every-incident-is-russian-sabotage-but-it-suits-the-defence-sector-to-say-so/). - [2026-09-26] U.S./European reporting frames the Leipzig case as a notable behavioral shift, since previously European governments "stopped short" of official blame despite years of suspicion: after an explosives-laden drone was discovered near a Ukrainian cargo plane at a German airport, European leaders did something they'd stopped short of doing before: publicly blame Russia; for years they'd suspected that Putin was behind acts of sabotage across Europe, but there was little or no evidence to prove it (https://www.spokesman.com/stories/2026/sep/26/us-europe-worry-russia-is-testing-nato-with-hybrid/). - [2024-05→2025-11] Historical precedent of qualifying attributions/charges also exists from 2024–2025: Lithuania's IKEA arson (GRU-directed, per prosecutors) and Poland's Marywilska mall arson (ordered by a GRU officer) both drew formal state attributions/prosecutorial charges, per the Wikipedia sabotage-operations summary describing Lithuanian prosecutors' "terrorism" charge tied to GRU and Polish investigators finding the fire "ordered by a GRU officer in Russia" (https://en.wikipedia.org/wiki/Russian_sabotage_operations_in_Europe). - [2026-09] Scale of the base incident pool remains large and rising, per IISS: the Associated Press counted 145 sabotage attacks, including explosions, fires, drone incursions, and cut undersea cables since 2022, of which only a minority (several per year) result in an unambiguous "ordered/directed by the Russian state" statement rather than hallmark/suspicion language. BOTTOM LINE: Over the past ~18 months the reference class shows a qualifying-style government attribution (explicit "carried out/ordered/directed by Russia" statement or matching criminal charges) occurring roughly every 1–3 months somewhere in the EU (Poland Nov 2025, Germany Sept 2026, plus earlier Lithuanian/Polish arson prosecutions), even though many more incidents are only described as "suspected" or "consistent with" Russian activity and thus would not qualify; this suggests a moderately high per-6-week base rate for a new qualifying attribution, but with real risk that any given incident in the window stays at the "suspected/hallmarks" stage rather than a full official attribution. NOT FOUND: No dedicated public tracker or historical win/loss record specifically for this Polymarket "EU country blames Russia for sabotage" contract series (or its likely predecessor markets) with a documented resolution history was found; could not confirm whether any qualifying attribution has already occurred since the market's Sept 19, 2026 creation date.
report: yes case
YES means: the national government of an EU member state (via an authorized official acting officially, or via criminal charges from state prosecutors) issues a qualifying attribution — stating an attack was "carried out, ordered, or directed" by Russian state/intelligence/military — for a new sabotage/arson/explosive/physical attack occurring on/after Aug. 1, 2026, with the statement made after Sept. 19, 2026 (market creation) and before Oct. 31, 2026. - [2026-09-03] The Munich arson near Rohde & Schwarz/Helsing (two incendiary devices thrown from a car) already produced two Bulgarian suspects in pretrial detention, giving Germany a live prosecutorial vehicle that could culminate in formal GRU-attribution charges before Oct. 31, mirroring the pattern of Poland's Nov. 2025 railway case where Polish prosecutors initiated an investigation into "acts of sabotage of a terrorist nature" directed against railway infrastructure and committed for the benefit of foreign intelligence . Source: english.nv.ua. - [2026-09-25] FAZ reporting (via multiple outlets) states German investigators believe the Main Directorate of the General Staff of Russia's Armed Forces, or GRU, was behind a September 3 attack on defense companies in Munich — but crucially the Munich Public Prosecutor General's Office "declined to confirm the reported Russian connection, citing the ongoing investigation" (english.nv.ua), showing the case is one prosecutorial step away from a qualifying attribution, not there yet. - [2026-09-25] Bavaria's interior minister Joachim Herrmann has already gone on record that the 38-year-old man and 28-year-old woman face charges of criminal damage and attempted arson... alongside other investigators, stated there were political motives behind the incident , indicating state officials (not just anonymous leaks) are already speaking publicly about the case — a short remaining step to explicit Russia-state language would trigger Yes. - [2026-09-23/24] Poland's Exatel/Starlink ground-station fire shows the fastest-escalating alternate path: within a day, Deputy PM Gawkowski told media "the modus operandi in this case is clearly Russian" and "is another element of the hybrid warfare we are facing" , and PM Tusk said there was "no doubt" the fire was caused deliberately, and that Russia was likely behind it — demonstrating Warsaw's political leadership is willing to name Russia almost immediately, needing only slightly firmer wording ("ordered/directed" vs. "likely/modus operandi") to cross the qualifying threshold. - [2026-09-18/23] Germany opened a fresh investigation into a drone/explosives find near the Wunstorf/Bundeswehr base explicitly "echoing Leipzig," per The Insider's timeline of "German prosecutors open new investigation after drone wreckage found near military base, echoing Leipzig incident" (Sept. 18) — this is a second active German federal probe that, if resolved before Oct. 31, could independently generate a new qualifying attribution distinct from the pre-market Leipzig case. - [2026-09] Germany's own internal count shows the incident pool feeding this pipeline is large and growing: an internal Federal Criminal Police Office assessment found more than 165 suspected sabotage cases in Germany between the beginning of 2026 and the end of August , meaning any one of many ongoing German investigations (Munich, Wunstorf, others) could produce the next formal attribution. - [2025-05] Precedent shows Poland's attribution process from "suspected sabotage" to formal government blame can move fast once investigators finish: the Marywilska mall fire went from suspicion to the Ministry of Foreign Affairs in Warsaw announced... an investigation had found that Russian intelligence services had orchestrated a massive fire at a shopping centre in capital Warsaw in May 2024 , and Poland's rail sabotage went from Saturday's blast to Tuesday's full Tusk attribution with named suspects (Nov. 2025) — a roughly 2-4 day investigator-to-official-statement lag once evidence solidifies, which is well within the Oct. 31 window for either Munich or the Exatel fire. - [2026-09-27] Slovakia's parallel case (foiled Skyeton drone-factory arson plot, three suspects detained Aug. 25) is also under GRU-network scrutiny per FAZ reporting linking it to the same Slovakia-based cell as Munich, giving a third EU government (Slovakia) a potential independent path to a qualifying attribution if its prosecutors formally charge the detainees with acting for Russian intelligence. BOTTOM LINE: The strongest Yes path is that one of several already-open, fast-moving investigations (Munich arson prosecution, Poland's Exatel/Starlink fire, or the Wunstorf drone probe) crosses from "suspected/hallmarks/likely" language into a formal "ordered/directed by Russia" statement or matching criminal charge before Oct. 31 — a transition that recent precedent (Poland's 2-4 day investigator-to-attribution lag, Germany's Sept. 1 Leipzig move) shows can happen quickly once evidence is judged sufficient, and multiple candidate cases are already primed just below that bar. NOT FOUND: No confirmed instance, as of Sept. 28, 2026, of any EU government moving from "suspected/likely/hallmarks" language to the strict qualifying "ordered/directed" statement or matching prosecutorial charge for any post-Aug.-1 incident since Sept. 19 market creation; could not find a specific announced timeline for when German or Polish prosecutors expect to conclude the Munich or Exatel investigations.
report: no case
YES means: at some point between market creation (2026-09-19) and 2026-10-31, an EU national government issues a fresh, unhedged public statement (or files criminal charges) declaring that a specific post-Aug-1, 2026 act of sabotage/arson/explosive attack/physical attack on its own territory was "carried out, ordered, or directed by the Russian state," rather than merely "suspected," "likely," "bears the hallmarks of," or attributed via anonymous officials. - [2026-09-25] The most significant post-market-creation incident, the Sept. 23 arson at the Starlink ground station in Wola Krobowska, Poland, was only characterized by the National Prosecutor's Office spokesman as "reasonable suspicion" the attackers "acted on the orders of Russian special services" — language that falls squarely into the market's excluded "suspected/likely" category rather than a qualifying direct attribution. Source: https://globalreconreport.substack.com/p/russias-hybrid-campaign-against-the - [2026-09-03] Germany's Munich arson/incendiary-device attack near Rohde & Schwarz produced only "strong indications" that Russian services were running the suspects as "low-level agents," per German authorities — again hedged language, not a formal government attribution, even three-plus weeks after the incident. Source: https://globalreconreport.substack.com/p/russias-hybrid-campaign-against-the - [2026-09-22] New German investigative reporting (Süddeutsche Zeitung/NDR/WDR) on Leipzig suspects and a Wunstorf drone/explosives find added detail but did not constitute any *new* official government attribution — it concerned the already-attributed Leipzig case and remained framed as media/investigative disclosure, not a state statement. Source: https://globalreconreport.substack.com/p/russias-hybrid-campaign-against-the - [2026-09-14] The Gedser incident — a Russian corvette firing flares at a Danish helicopter — is the "clearest case" of Russian state action in the window per one tracker, but it occurred in international waters (not EU territory) and involved a naval/military encounter, not sabotage/arson/explosives/physical attack on persons or property as defined, and Denmark's Defense Ministry response stopped at summoning the ambassador rather than alleging Russian-state-directed sabotage. Source: https://globalreconreport.substack.com/p/russias-hybrid-campaign-against(...) - [2026-09-15] The Netherlands' Sept. 15 rail-sabotage case (metal pipes tied to tracks nationwide) drew only a "disruptive and life-threatening" characterization from PM Jetten and an open AIVD/police/prosecutor investigation — no attribution to Russia at all as of the report date, despite fitting the "qualifying attack" definition if later attributed. Source: https://globalreconreport.substack.com/p/russias-hybrid-campaign-against-the - [2026-09-26] Danish police explicitly stated they have "not yet linked" the Lolland-Falster Airport arson attempt to Russia, illustrating the pattern of investigators declining to attribute quickly even for attacks squarely matching the qualifying definition. Source: https://www.criticalthreats.org (per colleague research, corroborated independently) - [2026-09-23] Poland's helicopter airspace incursion near Braniewo and its characterization as Russia "testing" air defenses is explicitly excluded from the market definition (airspace violations), showing that even Poland's most assertive statements that week fell into a non-qualifying category. Source: https://globalreconreport.substack.com/p/russias-hybrid-campaign-against-the - [2026-09-16] Lithuania's Kruonis-area drone shootdown produced only President Nausėda's statement it was "most likely" a Russian Gerbera drone "based on the information currently available," with the military declining to confirm origin before the investigation closed — a textbook non-qualifying "likely/probable" statement. Source: https://globalreconreport.substack.com/p/russias-hybrid-campaign-against-the - [2026-08-31] The dronexl.co analysis of Poland's WB Electronics fire warns explicitly against expecting fast attribution, noting "Poland took a year to name Russia over Marywilska, and that was a case with people already in custody," underscoring long historical attribution lags even in well-evidenced cases. Source: https://dronexl.co/2026/08/31/poland-abw-sabotage-probe-wb-electronics-drone-fire/ - [2026-09-24] Denmark's own Defence Intelligence Service assessment (DDIS) described only a "low but growing risk" of a future limited Russian attack "in the coming months" and stressed no invasion-preparation indicators exist — an official acknowledging continued uncertainty rather than declaring any completed attack as Russian-directed. Source: https://globalreconreport.substack.com/p/russias-hybrid-campaign-against-the - [2026-09-22] Romania's SRI reported disrupting a Russian-coordinated sabotage plot (announced Sept. 8) and a UK CPS charge (Sept. 9) against a suspect for "preparing sabotage" — both fall before market creation and, per the Romanian case, concern a foiled/disrupted plot rather than a carried-out qualifying attack, while the UK case predates Sept. 19. Source: https://globalreconreport.substack.com/p/russias-hybrid-campaign-against-the - [2026-09-27] A Critical Threats Project roundup shows German security services privately assessing a named GRU officer as "likely responsible" for Leipzig — intelligence-community language, not a fresh government statement, and tied to the already-attributed (pre-market) Leipzig case, which cannot itself trigger "Yes" per the rules' bar on "re-attributions regarding previously attributed attacks." BOTTOM LINE: In the nine days since market creation, every newly reported incident that might otherwise qualify (Wola Krobowska Starlink arson, Munich, Dutch rail sabotage, Lolland-Falster) has stalled at "suspected/reasonable suspicion/likely" language or remains unattributed, while the one unambiguous state-attributed incident (Gedser) does not meet the sabotage/territory definition — showing a real gap between frequent hybrid incidents and the rarer, slower step of formal unequivocal government attribution. NOT FOUND: No EU government statement dated 2026-09-19 or later that meets the strict "carried out/ordered/directed by Russia" bar (as opposed to suspicion/hallmark language) could be located; could not confirm whether Polish prosecutors have since escalated the Wola Krobowska "reasonable suspicion" language to a firmer attribution, nor whether any criminal indictment naming Russian state services has since been filed for a post-Aug-1 incident.
3. Forecasters 5 draws · Opus 5.5 + GPT-5.6 Sol · plain mean
claude-opus-5-5
50% conf
Yes 47%
No 53%
(0) No source shows the condition met. Germany's Leipzig attribution came on Sept 1-2, before the market opened on Sept 19, so it cannot count, and the resolution-source read confirms no qualifying post-creation attribution. Every newer case is still hedged: the Polish Starlink arson (prosecutors cite 'reasonable suspicion' of orders from Russian services), the Munich arson (FAZ reports investigators suspect the GRU, but prosecutors decline to confirm), and the Dutch rail and Danish airport incidents (not linked to Russia). (a) About 33 days remain until Oct 31. (b) If nothing changes, the market resolves No. (c) No scenario: investigations stall at 'likely/modus operandi' language, prosecutors keep charges generic (arson, criminal damage), and attribution lags for months, as with Marywilska. (d) Yes scenario: Polish prosecutors charge suspects in the Starlink fire with acting on behalf of Russian intelligence (a common Polish charging formula), or Munich prosecutors or German ministers formally name the GRU. Other candidates are Slovakia's Skyeton cell and the Wunstorf probe; any of these could cross the bar quickly given the current political willingness to name Moscow. The market sits at 45% and has drifted down from 54% as the week passed without an attribution. The December market at 67% implies a consistent hazard rate. The unusually dense pipeline of primed cases slightly offsets the strict wording bar, so I stay near the anchor.
claude-opus-5-5
45% conf
Yes 48%
No 52%
(0) Not resolved yet. Germany's Sept 1-2 Leipzig attribution came before the Sept 19 market creation, and a drone case may be excluded anyway. The Sept 8 Brandenburg grid item also predates creation. No post-creation statement meeting the strict "carried out, ordered, or directed" bar was found. (a) About 33 days remain until Oct 31. (b) If nothing changes, the market resolves No: every live case sits at "strong indications," "reasonable suspicion," "likely," or "not yet linked." (c) NO scenario: Munich prosecutors keep declining to confirm the GRU link and Polish officials stay at "modus operandi clearly Russian" or "likely." The Dutch rail and Danish airport cases stay unattributed, and attribution lags (a year for Marywilska) outlast the window. (d) YES scenario: German prosecutors formally charge the Munich suspects (FAZ says investigators believe the GRU was behind it) as acting for Russian intelligence. Alternatively, Polish prosecutors charge suspects in the Sept 23 Starlink arson under espionage/sabotage-for-foreign-intelligence provisions, which qualifies as criminal charges; their "reasonable suspicion" wording is the language Polish charging decisions typically use. Slovakia's Skyeton cell is a third path. The pipeline is unusually full, and Poland has moved from incident to formal blame within days before. Still, the base rate for strict qualifying attributions is roughly one every 1-3 months EU-wide. I anchor on the 45% price, which is consistent with the 67% December market. I nudge up slightly for the several cases primed just below the bar, especially the Polish prosecutorial route.
claude-opus-5-5
42% conf
Yes 47%
No 53%
(0) Resolution check: no source shows a qualifying attribution made after the Sept 19 market creation. Germany's Leipzig attribution (Sept 1-2) came before creation and involves a drone, so it cannot count. Poland's Wola Krobowska Starlink arson (Sept 23) drew only 'reasonable suspicion' and 'likely' language, and Munich only 'strong indications'. The Dutch rail and Lolland-Falster cases are unattributed. (a) About 33 days remain until Oct 31. (b) Status quo: nothing yet qualifies, so if no government hardens its language, this resolves No. (c) NO scenario: Munich, Starlink, Wunstorf and the Dutch rail probes all stay at 'suspected' or 'hallmarks' wording, or unnamed-source leaks like the FAZ GRU reporting, through October. Attribution lags are often months long; Marywilska took about a year. (d) YES scenario: Germany's federal prosecutor charges the detained Bulgarian Munich suspects with acting for the GRU, or Polish prosecutors file charges for the Starlink fire alleging the suspects acted for Russian services. Poland commonly charges under foreign-intelligence articles, and politicians in Warsaw name Russia quickly. The incident tempo is also very high (165+ suspected cases in Germany in 2026). The market anchor is 45% (drifting down), and the Dec 31 sibling at 67% implies a consistent hazard rate. I see no unpriced information strong enough to move far. I lean marginally up because several prosecutions are already one step from qualifying charge language, and 'reasonable suspicion' in Polish prosecutor communications often accompanies formal charges.
gpt-5.6-sol
66% conf
Yes 46%
No 54%
(0) No qualifying attribution is documented: the resolution-source review and current-state research found that Germany’s Leipzig attribution predates the September 19 market creation, while subsequent cases remain hedged, unofficial, or excluded. (a) About 33 days remain until October 31 at 11:59 PM ET, during which an EU government or prosecutor must unequivocally attribute a qualifying post-August 1 attack to Russian direction. (b) If nothing changes, the market resolves No because the Munich, Polish Starlink-station, Dutch rail, and Danish airport cases have not crossed the contract’s strict attribution threshold. (c) No results if these investigations remain open or officials continue using language such as “likely,” “reasonable suspicion,” or “strong indications,” consistent with the historically slow and cautious attribution process. (d) Yes results if Germany formally charges the Munich suspects as GRU-directed, or Poland upgrades its near-explicit statements about the Starlink-station arson into an unhedged official attribution; multiple active investigations make this plausible within the window. I anchor on Polymarket’s 45% Yes price and move only slightly upward to 46% because the unusually dense pipeline of near-threshold cases modestly outweighs the demonstrated gap between suspicion and qualifying official blame.
gpt-5.6-sol
68% conf
Yes 46%
No 54%
(0) No qualifying attribution is documented as of September 28: the resolution-source review and current-state research found that Germany's Leipzig attribution preceded the September 19 market opening, while subsequent cases remain hedged, unofficial, or excluded. (a) About 33 days remain until October 31 at 11:59 PM ET, during which an EU government must unequivocally attribute a qualifying post-August 1 attack to the Russian state or prosecutors must file equivalent charges. (b) If nothing changes, the market resolves No because reports concerning Munich, Poland's Starlink-site fire, Dutch rail sabotage, and Danish airport arson have not crossed the contract's strict attribution threshold. (c) The No scenario is that investigations continue past the deadline or officials retain formulations such as 'likely,' 'reasonable suspicion,' or 'strong indications,' consistent with the historically slow and cautious attribution process. (d) The Yes scenario is that German or Polish authorities formalize already-reported evidence in the Munich or Starlink-fire investigation, or another EU prosecutor files charges explicitly alleging Russian direction. I anchor on Polymarket's 45% Yes price and move only slightly to 46% because several live investigations create credible near-term pathways, but there is no confirmed post-opening attribution and the strict wording materially limits qualification.
4. Final plain mean of 5 draws
47% (54% confidence)
Yes: 47% No: 53%
Mean of 5 draws (0.47, 0.48, 0.47, 0.46, 0.46). (0) No source shows the condition met. Germany's Leipzig attribution came on Sept 1-2, before the market opened on Sept 19, so it cannot count, and the resolution-source read confirms no qualifying post-creation attribution. Every newer case is still hedged: the Polish Starlink arson (prosecutors cite 'reasonable suspicion' of orders from Russian services), the Munich arson (FAZ reports investigators suspect the GRU, but prosecutors decline to confirm), and the Dutch rail and Danish airport incidents (not linked to Russia). (a) About 33 days remain until Oct 31. (b) If nothing changes, the market resolves No. (c) No scenario: investigations stall at 'likely/modus operandi' language, prosecutors keep charges generic (arson, criminal damage), and attribution lags for months, as with Marywilska. (d) Yes scenario: Polish prosecutors charge suspects in the Starlink fire with acting on behalf of Russian intelligence (a common Polish charging formula), or Munich prosecutors or German ministers formally name the GRU. Other candidates are Slovakia's Skyeton cell and the Wunstorf probe; any of these could cross the bar quickly given the current political willingness to name Moscow. The market sits at 45% and has drifted down from 54% as the week passed without an attribution. The December market at 67% implies a consistent hazard rate. The unusually dense pipeline of primed cases slightly offsets the strict wording bar, so I stay near the anchor.
Pipeline Timing
Total pipeline time: 196.6s
Per-tool research timings shown in the Research section above.