Starodub War (Fifth Muscovite–Lithuanian War)(1537)

August 1534 - February 1537

General Operation
First Party — Command Staff

Grand Duchy of Moscow Forces

Commander: Regent Elena Glinskaya / Voivode Prince Ivan Ovchina-Telepnev-Obolensky

Mercenary / Legionnaire: %8
Sustainability Logistics63
Command & Control C258
Time & Space Usage67
Intelligence & Recon54
Force Multipliers Morale/Tech61

Initial Combat Strength

%47

Analysis Parameter: Raw combat force projection only. Does not reflect the mathematical average of operational quality scores.

Decisive Force Multiplier: Pomestye cavalry system and rapid fortification engineering (Sebezh, Velizh) provided strategic depth.

Second Party — Command Staff

Grand Duchy of Lithuania and Kingdom of Poland Allied Forces

Commander: Grand Hetman Jerzy Radziwiłł / Hetman Andrzej Niemirowicz

Mercenary / Legionnaire: %37
Sustainability Logistics49
Command & Control C262
Time & Space Usage58
Intelligence & Recon57
Force Multipliers Morale/Tech64

Initial Combat Strength

%53

Analysis Parameter: Raw combat force projection only. Does not reflect the mathematical average of operational quality scores.

Decisive Force Multiplier: Polish mercenary reinforcements and heavy cavalry (proto-hussars) combined with artillery superiority.

Final Force Projection

Post-battle strength after attrition and strategic wear

Operational Capacity Matrix

5 Military Metrics — Staff Scoring System

Sustainability Logistics63vs49

Moscow sustained the long campaign through interior-line supply via the pomestye system; Lithuania suffered logistical breakdown by autumn 1536 due to Sejm tax approval delays and mercenary pay crises.

Command & Control C258vs62

The Lithuanian hetman system offered a more professional command chain; on the Muscovite side, boyar factionalism during the regency weakened command unity, but Ovchina-Telepnev's personal authority compensated.

Time & Space Usage67vs58

From the second year of the war, Moscow consolidated terrain control by rapidly constructing the Sebezh and Velizh fortresses; Lithuanian forces failed to achieve deep penetration beyond the Starodub operation.

Intelligence & Recon54vs57

Lithuania correctly read the Muscovite regency crisis as a casus belli; however, it underestimated Moscow's mobilization speed and the loyalty of its Tatar allies (Qasim Khanate).

Force Multipliers Morale/Tech61vs64

Polish heavy cavalry and modern artillery served as decisive multipliers for Lithuania; Moscow countered with masses of light cavalry, native fortification engineering, and the morale multiplier of dynastic-religious legitimacy.

Strategic Gains & Victory Analysis

Long-term strategic gains assessment after battle

Strategic Victor:Grand Duchy of Moscow Forces
Grand Duchy of Moscow Forces%54
Grand Duchy of Lithuania and Kingdom of Poland Allied Forces%41

Victor's Strategic Gains

  • Moscow succeeded in fortifying its western frontier by constructing strategic new strongholds at Sebezh and Zavolochye.
  • The Glinskaya regency consolidated political legitimacy by preserving territorial integrity despite internal crisis.

Defeated Party's Losses

  • Lithuania exhausted its treasury without securing lasting territorial gains despite the destruction of Starodub.
  • The Krakow-Vilnius axis postponed its strategic objective of reclaiming Smolensk for another generation.

Tactical Inventory & War Weapons

Critical weapons systems and combat vehicles engaged in battle

Grand Duchy of Moscow Forces

  • Pomestye Cavalry
  • Pishchal Musketeer Infantry
  • Saadak Composite Bow
  • Light Field Artillery (Pishchal)
  • Fortification Engineering Corps
  • Qasim Khanate Tatar Cavalry

Grand Duchy of Lithuania and Kingdom of Poland Allied Forces

  • Heavy Polish Cavalry
  • Lithuanian Boyar Cavalry
  • Bombard Siege Cannon
  • Mercenary German Landsknecht Infantry
  • Tatar Light Cavalry
  • Polish Arquebusier Units

Losses & Casualty Report

Confirmed and estimated casualties sustained by both parties as a result of battle

Grand Duchy of Moscow Forces

  • 7500+ PersonnelEstimated
  • Entire Starodub GarrisonConfirmed
  • 14x Field GunsIntelligence Report
  • 2x Strategic Cities LostConfirmed
  • 1100+ PrisonersEstimated

Grand Duchy of Lithuania and Kingdom of Poland Allied Forces

  • 4200+ PersonnelEstimated
  • Sebezh Siege ForceConfirmed
  • 8x Siege CannonsIntelligence Report
  • 1x Strategic City - Gomel RetakenClaimed
  • 700+ PrisonersEstimated

Asian Art of War

Victory Without Fighting · Intelligence Asymmetry · Heaven and Earth

Victory Without Fighting

Lithuania chose war over diplomacy upon Vasili III's death; however, its failure to escalate Muscovite internal strife forfeited the chance of victory without battle. Both sides closed negotiation channels too early.

Intelligence Asymmetry

Sun Tzu's 'know yourself and your enemy' principle was incompletely applied by both; Lithuania underestimated Moscow's mobilization capacity, while Moscow accurately predicted the scale of Polish reinforcements.

Heaven and Earth

The harsh winter of 1534-1535 disrupted Lithuanian siege operations; the Polesia marshes and Desna basin offered natural defensive depth, tilting the 'Earth' factor in favor of the East.

Western War Doctrines

Attrition War

Maneuver & Interior Lines

Lithuanian forces exploited interior lines in the concentrated Starodub strike; Moscow's build-and-defend maneuver on the Sebezh-Velizh axis emerged as a dynamic counter. Napoleonic corps-style systems were absent on both sides.

Psychological Warfare & Morale

Moscow's 'Third Rome' ideology and dynastic loyalty reduced Clausewitzian friction; Lithuania's high mercenary ratio created morale fragility, and pay delays triggered desertions.

Firepower & Shock Effect

Lithuanian artillery produced decisive shock at the Starodub siege, with the fortress falling in 1535; however, the tactical success was not converted into strategic pursuit, leaving the firepower synthesis incomplete.

Adaptive Staff Rationalism

Center of Gravity · Intelligence · Dynamism

Center of Gravity

Lithuania's Schwerpunkt was the Starodub-Chernigov axis and succeeded there; Moscow correctly identified its own center of gravity not at the Smolensk defensive belt but in the northwestern (Sebezh-Velizh) fortification program.

Deception & Intelligence

No significant deception operation occurred; both sides adhered to classical siege and raid doctrines. Crimean Tatar diversionary threats on the southern frontier created limited intelligence pressure on Moscow.

Asymmetric Flexibility

The Muscovite regency, after weathering the initial shock, asymmetrically adapted to a defense-fortification doctrine; Lithuania maintained classical siege doctrine and failed to respond flexibly to changing conditions.

Section I

Staff Analysis

The war began with a Lithuanian-Polish offensive exploiting the internal instability of the regency of Elena Glinskaya, who governed in the name of the young Ivan IV following the death of Vasili III in December 1533. Lithuanian forces under Hetmans Niemirowicz and Radziwiłł seized the initiative along the Seversk-Smolensk axis and captured Starodub in 1535. However, Muscovy, under the command of Prince Ovchina-Telepnev-Obolensky, executed a strategic counter-move by constructing the fortresses of Sebezh and Velizh. The defensive victory at Sebezh in February 1536 became the turning point of the war, with Lithuanian forces annihilated on the frozen lake.

Section II

Strategic Critique

The Lithuanian command staff failed to convert the tactical capture of Starodub into a strategic pursuit toward Chernigov-Bryansk, missing the opportunity to translate tactical success into strategic gain. Sigismund I's reliance on Sejm approval for taxation disrupted campaign tempo. The Muscovite regency, although initially defensive and surrendering the initiative, proved its staff intelligence by shifting the geographic center of gravity through the construction of Sebezh and Velizh. Both sides avoided decisive battle, resulting in an attritional stalemate; the armistice terms confirmed the Muscovite fortification doctrine as the true strategic victor.