Ripper II (Japanese: リッパⅡ (rippa tsuu?)) is a flame-propelled variant of a Ripper that flies at high speeds. A native of Zebes, it is found in Metroid, Super Metroid and Metroid: Zero Mission. They can be frozen with the Ice Beam in which they become platforms to stand on. Ripper IIs can also be grappled onto with the Grappling Beam and swing from them to cross over hazards and throw Samus high into the air.

With the exception of Zero Mission, there are always two variants of Ripper IIs in the games. The original Metroid featured a weak and indestructible version; while it is impossible to differentiate them visually as they are identical to one another, a single Missile or the Screw Attack can kill the weaker of the two. In Super Metroid, a weak Ripper II has a red body and blue eyes while the stronger form possesses a metallic-colored body with red eyes.

According to the 1986 Metroid manga, the Ripper II species evolved from Rippers. The Tripper appears to be a relative of Ripper IIs, and the Yumees share many traits with the latter.

Official dataEdit

Metroid manualEdit

Metroid Enemy Ripper II

Ripper II: "These Rippers are more advanced than the Rippers who appear in the rocky zone. They
can spit fire and fly at high speed. They look the same as the other Rippers but
they fly a lot faster."

1986 mangaEdit

"Evolved from the Rippers in Brinstar, it is faster than the Ripper and can't be defeated with Missiles."

Super Metroid Nintendo Player's GuideEdit

Enemy Data Description
Color HP ATK E BE M SM PB Brinstar/Norfair. Faster than a Ripper, this enemy is more difficult to avoid.
Normal 200 10 0 1 0 99 0



  • The flame engines of Ripper IIs from Super Metroid shut off when frozen with the Ice Beam. However, the Zero Mission variant's engine does not and the flame itself literally freezes, which should not be possible.


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.