FANDOM


R5-SK1 was an R5-series astromech droid that served as part of the Alliance to Restore the Republic's Red Squadron. It was stationed on the moon of Yavin 4 as part of the Massassi group of Rebels headquartered in the Great Temple. It participated in the battle above the planet Scarif while docked into a T-65B X-wing starfighter in the Alliance Fleet's Red Squadron.

BiographyEdit

R5-SK1[3] was a R5-series astromech droid that served the Alliance to Restore the Republic during the reign of the Galactic Empire. It was stationed with the Massassi group of Rebels on the moon Yavin 4.[2] In the year 0 BBY,[4] the astromech was part of the Alliance forces that scrambled from Yavin 4 to the planet Scarif in order to aid the recently recruited Rebel Jyn Erso and a group of Rebels who had attacked the Imperial Citadel Tower there to try and steal the plans for the Death Star superweapon.[2]

R5-SK1 arrived above Scarif docked into[2] a T-65B X-wing starfighter[1] in Red Squadron that jumped from hyperspace with the rest of the Alliance Fleet. The Rebels took heavy casualties in the battle that followed, but were able to successfully steal the plans. Several members of Red Squadron were amongst those that successfully escaped the Imperial forces afterwards.[2]

CharacteristicsEdit

R5-SK1 had white and red paneling and black sensors.[3] Like all droids in the R-series, it was manufactured by Industrial Automaton.[1]

Behind the scenesEdit

R5-SK1 was created for the stand-alone film Rogue One: A Star Wars Story, which was released on December 16, 2016.[5] The character was revealed prior to the film in the form of a figure released by Hasbro Inc. in 2015 as part of a set with three other astromechs from Rogue One as part of the Star Wars: Star Tours line.[3]

AppearancesEdit

SourceEdit

Notes and referencesEdit

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.