FANDOM


"It took 85 men less than an hour to bring so much chaos and disarray to Ebenmal that the defenders—over 3,000 Rebels—surrendered."
Imperial Atrocities and Other Noble Pursuits, by Chen Ming-di[src]

Ebenmal was a planetoid[2] located in the Ebenmal system of the Mid Rim's Irnaj sector.[1] It was on Ebenmal that a battle between the Galactic Empire and the Rebel Alliance was fought[2] sometime between the years 2 and 1 BBY.[3] The ancient citadel of Ebenmal, which was said to have never fallen to an invader for over ten thousand years, was attacked by eighty-five Imperial jumptroopers, who brought chaos and disarray. In one hour's time, 3,000 Rebels surrendered. The battle was later mentioned in Imperial Atrocities and Other Noble Pursuits, by historian Chen Ming-di.[2]

Behind the scenesEdit

Ebenmal was first mentioned in the "jump trooper" entry in the in-game databank of the PlayStation 3/Xbox 360 versions of the LucasArts video game Star Wars: The Force Unleashed II, which was released on October 26, 2010. More information about the location of the planetoid was released in Star Wars: The Essential Atlas Online Companion, an appendix to be used to further expand the reference book The Essential Atlas.

AppearancesEdit

Notes and referencesEdit

  1. 1.0 1.1 1.2 1.3 1.4 SWCustom-2011 Star Wars: The Essential Atlas Online Companion on StarWars.com (article) (backup link) — Based on corresponding data for Ebenmal system
  2. 2.0 2.1 2.2 2.3 2.4 2.5 Star Wars: The Force Unleashed II (PS3/Xbox 360 "Jumptrooper" databank entry)
  3. Star Wars: The Force Unleashed comic shows that the Rebel Alliance was founded in 2 BBY. According to Star Wars: The Force Unleashed II comic, the events of Star Wars: The Force Unleashed II happened in 1 BBY. Thus, the battle happened between the two years.

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.