135,027pages on
this wiki
Add New Page
Talk1 Share

The title of this article is a nickname, call sign, or alias.

This article is about a subject that lacks an official name and was known only by its nickname, call sign, or alias.

"Looks like TK-486 is in trouble…"
―One of TK-486's squadmates[src]

TK-486 was the designation of a stormtrooper commander in the Galactic Empire.[2] In the year 0 BBY,[3] TK-486 was stationed as a sandtrooper in Mos Eisley on the desert planet of Tatooine, and the soldier was once cornered by a trio of Jawas outside of Chalmun's Cantina. When one Jawa reached for the strap of TK-486's[1] T-21 light repeating blaster,[4] the stormtrooper demanded them to stop, catching the attention of one of TK-486's squadmates.[1]

As a sandtrooper officer in the Stormtrooper Corps, TK-486 wore a backpack, an orange pauldron,[2] and augmented stormtrooper armor.[5]

Behind the scenesEdit

TK-486 first appeared in Bounty Hunt, a young readers activity book written by Katrina Pallant, illustrated by Robert Ball, and published by Egmont UK Ltd on April 7, 2016.[6]


Notes and referencesEdit

  1. 1.0 1.1 1.2 1.3 1.4 1.5 Bounty Hunt
  2. 2.0 2.1 Bounty Hunt depicts TK-486 wearing an orange pauldron, which, according to Ultimate Star Wars, represented the stormtrooper military rank of unit leader.
  3. In Bounty Hunt, the Death Star's superlaser is fully operational, and Star Wars: Galactic Atlas establishes that the events of Rogue One: A Star Wars Story, and thus the completion of the superweapon, take place in 0 BBY. Since the Death Star was destroyed in the Battle of Yavin (Star Wars: Episode IV A New Hope), it can be assumed that the events in Bounty Hunt also take place in 0 BBY.
  4. Star Wars: Galactic Defense
  5. StarWars-DatabankII Sandtroopers in the Databank
  6. Amazon favicon Star Wars Bounty Hunt: Lift the Flap on

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.