Will there be a NATO-Russia military clash by 2026? [ resolves 2026-01 – 2026-12 ]
NATO x Russia military clash by December 31, 2026?
polymarket: [C] single source·reporting consensus methodology ›
distribution · by resolution date · marks: daily snapshot
polymarket 6 markets
| market | resolves | P(YES) | vol (24h) | vol (cum) | RCG | venue id | ||
|---|---|---|---|---|---|---|---|---|
| In 2025 | 2026-01-01 | 100.0% | — | $630K | C | 0xafa3f2…dbaa | ||
| By March 31, 2026 | 2026-04-01 | 0.1% | — | $539K | C | 0xd3320f…bdb9 | ||
| By June 30, 2026 | 2026-07-01 | 0.2% | — | $1.19M | C | 0xbad704…5732 | ||
| By August 31, 2026 | 2026-09-01 | 0.0% | $49K | $309K | C | 0xcd6c66…d420 | ||
| By October 31, 2026 | 2026-10-31 | 11.0% | $21K | $62K | C | 0x2a4fcd…9e94 | ||
| By December 31, 2026 | 2026-12-31 | 25.0% | $18K | $1.08M | C | 0xf2bf04…4e52 |
resolution architecture
| venue | proposer | source | citation | arbitration | class | analyst notes |
|---|---|---|---|---|---|---|
| polymarket | Whitelisted Proposers | uncommitted | not provided | Optimistic Oracle (UMA) | Other | — |
verbatim rules
polymarket
This market will resolve to "Yes" if there is a military encounter between the military forces of a NATO country and Russia between September 23 and December 31, 2025, 11:59 PM ET. Otherwise, this market will resolve to "No".
A "military encounter" is defined as any incident involving the use of force such as missile strikes, artillery fire, exchange of gunfire, or other forms of direct military engagement between NATO and Russian military forces. Non-violent actions, such as airspace violations, firing of warning shots (such as the June, 2021 Black Sea Confrontations between Russian forces and HMS Defender), or cyberattacks will not qualify.
Interception of missiles or other one-way attack or loitering munitions (e.g. Shahed drones) which are targeting a 3rd party other than the listed countries or their respective forces will not alone qualify. Shooting down UAVs which are not munitions (e.g. MQ-9, Orlan 10, Orion, Bayraktar TB2, etc.) will qualify.
Intentional physical collisions, including aerial interceptions and naval ramming without the direct use of weaponry, such as the 2023 Black Sea incident—where a Russian Su-27 damaged a U.S. MQ-9 Reaper drone's propeller, leading to its crash— will not qualify regardless of damage.
Military contractors will qualify only if confirmed to be operating under the direct command or coordination of the respective state’s armed forces (e.g. the Battle of Khasham would not qualify).
The resolution source for this market will be a consensus of credible reporting.
platform source field
polymarket.resolutionSource → ∅ no committed source — see rules text above resolution history
| outcome | market | venue | resolved | final price |
|---|---|---|---|---|
| NO | NATO x Russia military clash by August 31, 2026? | polymarket | 2026-09-01 | 0% |
Resolution dates are the venue's settlement timestamps (1 resolved market). Rows shown as "by [date]" carry the contract deadline: the venue no longer exposes a settlement time for them. PENDING upgrades to a final outcome on the next refresh.
recent wire items
- NATO-Russia clash by Oct 31 holds low at 14% 14% · $71K 24h
- At 14%, Polymarket assigns low but non-trivial odds to a NATO-Russia military clash within the next 70 days.
- 24h volume of $71K is 33% of all-time, notable fresh interest on a longer-dated contract than the Aug 31 sibling.
- The Oct 31 contract's 14% vs. the Aug 31 contract's 3% illustrates the market pricing meaningful but distant escalation risk.
- Geopolitical catalysts driving the Aug 31 spike likely also pulled fresh capital into this extended time horizon.
- NATO-Russia clash by Aug 31 stays a long shot at 3% 3% · $1.1M 24h
- At 3%, Polymarket assigns near-zero probability to direct military confrontation within 10 days.
- 24h volume of $1.1M is 66% of all-time, one of the largest single-day concentrations this contract has seen.
- Surge likely reflects a specific geopolitical trigger or headline driving hedgers and speculators to size up tail risk.
- Contract resolves Aug 31; extreme near-term deadline amplifies the binary stakes of any escalation news.
programmatic access · four surfaces, same payload
One canonical record at every surface — embedded JSON-LD, REST, MCP, and /llms.txt.
| HTML | browsers, AI grounded search, crawlers (embedded JSON-LD @type: Dataset) | https://clearmarket.fyi/events/nato-x-russia-military-clash-in-2025/ |
| JSON | REST API for developers | https://api.clearmarket.fyi/v1/events/nato-x-russia-military-clash-in-2025 |
| MCP | agentic AI tool call (Claude Desktop, Cursor, Continue) | clearmarket.get_event("nato-x-russia-military-clash-in-2025") |
| AGENT | AI crawler discovery index | /llms.txt |
Snapshot 2026-08-04. Venue data via Kalshi + Polymarket APIs. Editorial fields (tags, editorial_notes) are ClearMarket-drafted with AI assistance under editorial review. Derived fields (venues_covered, resolution_clarity_grade, rcg_score) computed at serve time. Full per-field map in the JSON record under field_provenance.
raw JSON record · same payload returned by REST endpoint {
"event_id": "CM-EVT-0XQBBK1P10",
"slug": "nato-x-russia-military-clash-in-2025",
"question": "Will there be a NATO-Russia military clash by 2026?",
"category": "geopolitics",
"tags": [
"nato-russia-conflict",
"geopolitics",
"military-escalation",
"2025",
"trump",
"international-security"
],
"venues_covered": [
"polymarket"
],
"market_count": 6,
"cumulative_volume_usd": 3811661,
"resolution_clarity_grade": "C",
"rcg_score": 14,
"rcg_caps": [
"discretionary_trigger_no_source",
"adversarial_ground_truth",
"commitment_uncommitted_placeholder"
],
"resolution_source": null,
"resolution_source_url": null,
"source_status": "no_committed_source",
"source_of_record": null,
"resolution_source_list": null,
"arbitration_model": "uma_oracle",
"proposer_model": "managed_whitelist",
"field_provenance": {
"question": {
"source": "clearmarket_editorial"
},
"tags": {
"source": "clearmarket_editorial",
"ai_drafted": true
},
"resolution_clarity_grade": {
"source": "derived",
"method": "rcg_v2_7factor"
},
"venues_covered": {
"source": "derived"
}
}
}