Warscape
Daily briefing·· from today's news

Azerbaijan vs Turkey, Armenia: Defender holds after 310 days

In today's run Azerbaijan attack Turkey, Armenia; the model ends in defender holds after 310 days.

Attacks
Azerbaijan
Defends
Turkey + Armenia
Outcome
Defender holds
Length
310 days

What happened today

Today's defence and geopolitics headlines, in the outlets' own words (linked):

Those stories name the sides in today's run.

The scenario we ran

Azerbaijan attack Turkey, Armenia in autumn, mobilization full / partial, the United States stays out, nuclear weapons disabled, 365-day limit. Everything else is the engine's realistic default.

How the model played it out

War timeline · 310 days
Stalemate
Stalemate
A
B
DAY 1◆ turning pointDAY 310
Phases are the engine's own labels. Lanes show each side's operational tempo: bright = attacking, dim = pausing or defending.
Losses within the model · aggregate
Azerbaijan
Turkey + Armenia
3.8k
Personnel
13.8k
31
Tanks
144
33
Aircraft
106
26
Artillery
56
Territory: Azerbaijan -11 cells · Turkey + Armenia +11 cells. Cohesion at the end: 40% vs 44%.

Result: Defender holds after 310 simulated days (prolonged stalemate). Aggregate personnel losses within the model: 3,785 for Azerbaijan and 13,811 for Turkey + Armenia.

The war moved through initial strike from day 1, then rapid mobilization from day 3, then attrition phase from day 8, then stalemate from day 21, then contested front from day 23, then attrition phase from day 24.

Turning points:

  • Day 12: Turning point: a shift in momentum. This moment mattered because momentum shifted durably toward Turkey + Armenia: a combination of local factors.

What decided it

What decided it · separation between the sides
◀ favours Azerbaijanfavours Turkey + Armenia ▶
Deployed combat power
16 vs 121 model units.
Air situation
23%.
Logistics
12% vs 57%.
Mobilisation
223,074 vs 483,816.
Economic resilience
0.94 vs 0.78.
Political cohesion
58% vs 57%.
Bar length is the engine's normalised difference on that factor over the whole war; direction shows who it favoured.
Side A objectives · Azerbaijan
Capture the capital of Armenia0%
Secure a border corridor inside Armenia0%
Reduce opposing deployed combat capacity below 50%0%
Side B objectives · Turkey + Armenia
Retain at least 90% of pre-war territoryachieved
Reduce the attacker's offensive capacity below 55%9%
Restore pre-war bordersachieved
  • Deployed combat power (favoured Side B): Average deployed combat power: 16 vs 121 model units.
  • Air situation (favoured Side B): Average share of air control for Azerbaijan: 23%.
  • Logistics (favoured Side B): Average front-line supply efficiency: 12% vs 57%.
  • Mobilisation (favoured Side B): Reservists mobilised: 223,074 vs 483,816.
  • Economic resilience (favoured Side A): Average economic stability index: 0.94 vs 0.78.

The same countries, one on one

WARSCAPE keeps a permanent page for every land border in Europe, each holding its own simulated war:

Try it yourself

Open the exact run and scrub the timeline, ask why at any event, or branch an alternate timeline from a turning point. Or change one assumption in the builder and run it again.

Sources and limits

This is a model result on public, aggregate, country-level data under the stated assumptions. It is not a prediction, and no operational information is used.

Model-generated simulation on public, country-level data. Not a prediction. Headlines are linked and summarised, never reproduced. Assembled from the engine's report.