135,091pages on
this wiki
Add New Page
Talk0 Share
"BN-749 to pilot, courier is aboard."
―BN-749 reports the arrival of C1-10P[src]

BN-749 was the designation of a male stormtrooper who served the Galactic Empire's Stormtrooper Corps on the planet Lothal. He was stationed on the Sentinel-class landing craft Lagos which was used to transport droid couriers to communications ships in orbit while all long-distance communication on the planet was disabled. When a group of rebels replaced one of the couriers with their own droid C1-10P, BN-749 ignored the rebel droid's lack of an escort and allowed it onboard the Lagos. The shuttle then traveled to an Imperial light cruiser in orbit, where C1-10P successfully discovered the location of the Imperial prisoner Kanan Jarrus and escaped.


"There's the courier, where's his escort?"
"Not our problem, we're running late as it is."
―BN-749 dismisses his partner's concerns[src]

The male stormtrooper designated BN-749 served the Galactic Empire's Stormtrooper Corps on the planet Lothal[1] around five years before the Battle of Yavin.[2] After a group of rebels active on Lothal managed to hijack the planet's Imperial Communications Center and use it to broadcast anti-Imperial propaganda, Grand Moff Wilhuff Tarkin had the structure destroyed,[3] disabling all long-distance communication on Lothal. This forced the Imperials on Lothal to start using Imperial Press Corps astromech droids as couriers. BN-749 was assigned to the Sentinel-class landing craft Lagos, which was responsible for transporting the droid couriers from Lothal's surface to communications ships in orbit.[1]

Hoping to learn the location of their crew mate Kanan Jarrus who had been captured by the Empire, the rebels who had hijacked the tower captured one of the Empire's droid couriers and stunned its escort. They replaced the Imperial droid, who was designated 264, with their own astromech, the C1-series astromech droid C1-10P, who was painted to resemble the courier. When C1-10P arrived at the landing bay where the Lagos was parked, BN-749 and another stormtrooper were standing guard at the ship's entry ramp. As the astromech approached the other stormtrooper questioned why the astromech was not accompanied by an escort, but as the Lagos was already running late BN-749 ignored the issue and allowed the droid onboard. The Lagos then transported the two stormtroopers and C1-10P to a communications vessel in orbit, where the droid managed to download information regarding Jarrus's whereabouts before escaping through an airlock into space where he was picked up by the rebel vessel Ghost.[1]

Personality and traitsEdit

BN-749 was willing to ignore C1-10P's lack of an escort due to the fact the Lagos was already running late.[1]


BN-749 wore standard stormtrooper armor and carried an E-11 blaster rifle.[1]

Behind the scenesEdit

BN-749 first appeared in the Star Wars Rebels episode Rebel Resolve, which aired in 2015. The two stormtroopers guarding the Lagos were credited as "Shuttle troopers #1 and #2" and were voiced by Steve Blum and Keith Szarabajka respectively, although it is not made clear which trooper is BN-749.


Notes and referencesEdit

  1. 1.0 1.1 1.2 1.3 1.4 1.5 1.6 1.7 1.8 1.9 Rebels-mini-logo Star Wars Rebels – "Rebel Resolve"
  2. TwitterLogo @HolocronKeeper (Leland Chee) on Twitter. “0 10 10-13 13 27 32 35 36” (screenshot)—The tweet in question refers to the number of in-universe years between the canon films and television shows. Star Wars Rebels is set as Year 27, and Star Wars: Episode IV A New Hope is set as Year 32. The heist in Capital City, which takes place at the beginning of the premiere film Star Wars Rebels: Spark of Rebellion, can be deduced as taking place five years before the Battle of Yavin, which takes place in A New Hope.
  3. Rebels-mini-logo Star Wars Rebels – "Call to Action"
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.