FANDOM


YodaEpisodeI
More to add, have you?

It is requested that this article/section of an article be expanded. Once the article contains more information, this template will be removed.

Dengar was a Human Male Bounty Hunter during the Clone Wars and the Galactic Civil War. He teamed up with Boba Fett many times and was in his Boba Fett's Syndicate for a time.

Dengar (Clone Wars)

During the Days of the Clone Wars

BiographyEdit

Dengar was in Boba's Syndicate when they went to Beluga with Asajj Ventress to deliver something. As soon as they left on the Speedtrain they were attacked by Kage. Dengar and Asajj fight well on the back area, where the Kage attack first but Dengar is eventually knocked off.

He was later seen defending Jabba the Hutt alongside Sugi, Embo, Marrok and Latts Razzi against Shadow Collective, the four hunters eventually flee and Jabba agrees to join Darth Maul.

On Nar Shadaa, while attempting to capture Han Solo to collect a bounty, he was thrown off a rooftop by Chewbacca along with a detonating Thermal Imploder.

Dengar was hired by Darth Vader to hunt down the Falcon alongside Bossk, Boba Fett, IG-88, 4-LOM and Zuckuss. He tracked the ship to Cloud City where he was too late to collect the bounty on Solo but served Darth Vader while the Rebels attempted escape with the aid of Lando Calrissian and the Bespin Wing Guard.

Dengar was hired to secure Jabba's Palace alongside Bossk and Boba Fett when Luke Skywalker launched an attack to free Han Solo from Jabba's Custody.

He was alive after the Battle of Endor, still in the business of Bounty Hunting, although he believed that the New Republic would put Bounties on the Bounty Hunters eventually. He joined forces with Mercurial Swift but eventually turned on him and joined Jas Emari's crew along with Embo and Jeeta.

AppearancesEdit

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.