Peruvian grenadier
📖 Overview
Most common grenadier in the Eastern central Pacific but occurs in very deep waters that it is not regularly taken by trawlers . Maximum TL of at least 30 cm .
🔬 Taxonomy
🐟 Physical Description
Dorsal spines (total): 2; Anal spines: 0. Snout short, moderately pointed, with stout scutes at its tip and lateral angles; underside of the snout and suborbital anteriorly naked. Light organ not well-developed externally; no scaleless fossa between the pelvic-fin bases. Pyloric caeca 21 to 32. Body scales with conical spinules in 10 to 12 slightly convergent rows.: elongated; Cross section: circular.
🌀 Behaviour
Behavioural data for Peruvian grenadier is currently being reviewed.
🦐 Diet
🥚 Reproduction
🌍 Habitat & Distribution
Marine; bathydemersal; non-migratory; depth range 600 - 1870 m . Deep-water; 27°N - 34°S, 112°W - 70°W south to Chile, including the Cocos and Galapagos islands.
🌿 Ecology
📐 Morphometrics
🌡️ Water Parameters & Tolerance
📊 Population Risk & Fisheries
🌐 Names & Taxonomy
| Language | Common Names |
|---|---|
| 🇬🇧English | Peruvian grenadier |
| 🌍CES | nezumie peruánská |
Scientific Synonyms
| Scientific Name | Author | Year | Status |
|---|---|---|---|
| Lionurus convergens | Garman | 1899 | Synonym |
| Lionurus cuspidatus | Garman | 1899 | Synonym |
| Lionurus trichiurus | Garman | 1899 | Synonym |
| Macrurus convergens | Garman | 1899 | Synonym |
| Macrurus cuspidatus | Garman | 1899 | Synonym |
| Macrurus trichiurus | Garman | 1899 | Synonym |
| Nezumia cuspidata | Garman | 1899 | Synonym |
| Nezumia trichiura | Garman | 1899 | Synonym |
| Sphagemacrurus trichiurus | Garman | 1899 | Synonym |
🔍 Similar Species
🗺️ Global Occurrence Map
Occurrence records from the Global Biodiversity Information Facility (GBIF) - 5 records indexed .
👥 Community & Contribute
No observations yet - be the first to log one!
View all observations for Peruvian grenadier ↗Spotted incorrect or outdated data? Submit a correction and our editorial team will review it. Approved edits go live within 48 hours.
Found a factual error, broken data, or inappropriate content? Let us know and we will investigate promptly.