Battle of Khwar Pass

The Battle of Khwar Pass was a failed ambush set up by Ashraf Hotaki during his retreat in the aftermath of his defeat at Mihmandoost. Gathering what forces lay on his route, Ashraf pulled together another formidable fighting force around the remains of his badly bloodied force, even having enough men to spare for an ambush set up at a narrow pass east of Varamin.

Battle of Khwar Pass
Part of Nader's Campaigns

Persian sharpshooters
Date1729
Location
Persia
Result Persian victory
(Ashraf's ambush failed)
Belligerents
Safavid Loyalists Hotaki dynasty
Commanders and leaders
Nader Ashraf Hotaki
(not present at time of battle)
Casualties and losses
Minimal

Heavy

  • all guns & baggage

Battle

Placing hidden guns and sharpshooters on the high ground overlooking the pass and fortifying the narrow pathway Ashraf even left a significant body of cavalry behind in order to hunt down the survivors of the ambush. Nader's spies however reported on Ashraf's designs at Khwar. Skirting around the ambush Nader, personally taking command, launched a two-pronged assault utilising musketeers with artillery support, catching the Afghans in an ambush of his own, forcing the Pashtuns to flee leaving their guns and baggage behind.

Consequences
The Four-cornered Citadel of Varamin as seen by Jane Dieulafoy

As a result of the battle, Nader's advance into the heart of Iran and onto the capital Isfahan lay open. Nader however chose to take a longer route further to the west for reasons of superior logistical support. This also had the benefit of surprise with the defeated Afghans unable to mount a serious obstacle to Nader's advance on Isfahan until he had already reached Murcheh-Khort, a town just a mere few kilometres north of Isfahan itself.

Sources
  • Michael Axworthy, The Sword of Persia: Nader Shah, from Tribal Warrior to Conquering Tyrant Hardcover 348 pages (26 July 2006) Publisher: I.B. Tauris Language: English ISBN 1-85043-706-8
gollark: As I said: code filtering is *possible*, but not really against someone who is actively attempting to circumvent it.
gollark: Poorly!
gollark: PotatOS does code filtering without terrible performance losses, but it only really works since the programs in question don't update to avoid it.
gollark: We already have string metatable access.
gollark: More to the point, *how* would you modify the BIOS for that?

See also
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.