"He [Praji] was an old-fashioned military man and while he viewed the AT walkers as graceless brutes he had to admit they were effective, particularly in subduing the unruly Leffingites in the Battle of Almak."
―Dr. Gabrel Treon in Tinker, Tailor, Soldier, Praji: A Cartel of Genes[src]

The Battle of Almak was fought on the[1] Mid Rim[2] planet Almak sometime between 19 BBY and 1 BBY, during the reign of the Galactic Empire. An Imperial unit under the command of Nahdonnis Praji, a Human officer of the Empire, participated in the subjugation of Almak's native sentient species, the Leffingites. The Imperials used All Terrain walkers to great effect during the battle and were able to defeat the Leffingite resistance. Praji viewed the walkers as brutish and without grace but nonetheless found them effective in the battle.[1] In 104 ABY,[3] the historian Dr. Gabrel Treon mentioned the battle in Tinker, Tailor, Soldier, Praji: A Cartel of Genes, an article he wrote about the House Praji family, which he published in the Byblos Journal of Historical Science.[1]

Behind the scenesEdit

The first and only mention of the Battle of Almak was in Nathan O'Keefe's Hyperspace-exclusive in-universe history article titled Tinker, Tailor, Soldier, Praji, which was published on February 5, 2009.[1]


Notes and referencesEdit

  1. 1.00 1.01 1.02 1.03 1.04 1.05 1.06 1.07 1.08 1.09 1.10 HyperspaceIcon "Tinker, Tailor, Soldier, Praji" on Hyperspace (article) (content removed from and unavailable)
  2. Star Wars: The Essential Atlas Online Companion
  3. The last section of Tinker, Tailor, Soldier, Praji is titled "Inheritance (10–104 ABY)". StarWarsDotComBlogsLogoStacked "TTSP Endnotes: Volume 1" – Tinker, Tailor, Soldier, Fanboy, Nathan O'Keefe's Blog (content now obsolete; backup link on states that the in-universe article was published in 104 ABY.
In other languages

Ad blocker interference detected!

Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.