Fandom

Wookieepedia

AG-37 fighting Floating World.jpg

135,131pages on
this wiki
Add New Page
Talk0
AG-37_fighting_Floating_World.jpg (download)‎ (640 × 302 pixels, file size: 51 KB, MIME type: image/jpeg)

SummaryEdit

File:AG-37 fighting Floating World.jpg
Information
Description

AG-37 fighting during the Battle of the Floating World

Source

Legacy 17

Original designer / artist

Brian Albert Thies

Licensing
Red copyrightThis image is an excerpt from the interior of a comic book and the copyright for it is most likely owned by either the publisher of the comic book or the writer(s) and/or artist(s) who produced the comic book in question. It is believed that the use of images of a panel or panels from the interior of a comic book to illustrate:
  • the scene or storyline depicted;
  • the copyrighted comic book character(s) or group(s) depicted on the excerpted panel(s) in question;
where no free alternative exists or can be created, on Wookieepedia, hosted on servers in the United States by Wikia, qualifies as fair use under United States copyright law. Any other uses of this image, on Wookieepedia or elsewhere, may be copyright infringement. See Copyrights for more information.

Appears on these pages
of

  • AG-37

    AG-37 was an IG-series assassin droid in operation in the aftermath of the Second Imperial Civil...

File history

Click on a date/time to view the file as it appeared at that time.

Date/TimeThumbnailDimensionsUserComment
current00:21, February 21, 2015Thumbnail for version as of 00:21, February 21, 2015640 × 302 (51 KB)Andykatib (Talk | contribs)==Summary== {{Information |attention= |description=AG-37 fighting during the Battle of the Floating World |source=''Star Wars: Legacy Volume 2 17'' |artist=Brian Albert Thies |filespecs= |licensing={{Comicpanel}} |other versions= |cat a...

Metadata

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.