Paramormyrops Kingsleyae
📖 Overview
Affinities: B. k. eburneensis is distinguished by number of teeth in upper jaw and soft rays of dorsal and anal fins.
🔬 Taxonomy
🐟 Physical Description
Dorsal spines (total): 0; Dorsal soft rays (total): 17 - 18; Anal spines: 0; Anal soft rays: 22 - 25. Body depth 4.2-5.0 x SL. Eye small, 6.4-8.3 x head length. Head length 4.5-5.3 x SL. Dorsal fin base 5.8-7.0 x SL, origin behind origin of anal fin. Dorsal base to anal base ratio 0.7-0.9. Pectoral shorter than head, 1.4-1.7 x pelvic fin length. Clear brown color.: fusiform / normal; Cross section: compressed.
🌀 Behaviour
Behavioural data for Paramormyrops Kingsleyae is currently being reviewed.
🦐 Diet
🥚 Reproduction
🌍 Habitat & Distribution
Freshwater; benthopelagic. Tropical endemic to the Lower Guinea.
🌿 Ecology
📐 Morphometrics
🌡️ Water Parameters & Tolerance
🛡️ Conservation Assessment
📊 Population Risk & Fisheries
🌐 Names & Taxonomy
| Language | Common Names |
|---|---|
| 🌍CES | rypoun hnědý |
| 🇷🇺Russian | Поллимир Кингслей |
Scientific Synonyms
| Scientific Name | Author | Year | Status |
|---|---|---|---|
| Brienomyrus kingsleyae | Günther | 1896 | Synonym |
| Brienomyrus kingsleyae kingsleyae | Günther | 1896 | Synonym |
| Marcusenius cabrae | Boulenger | 1900 | Synonym |
| Marcusenius kingsleyae | Günther | 1896 | Synonym |
| Mormyrus kingsleyae | Günther | 1896 | Synonym |
| Paramormyrops kingsleyae kingsleyae | Günther | 1896 | Synonym |
| Paramorpmyrops cabrae | Boulenger | 1900 | Synonym |
| Pollimyrus kingsleyae | Günther | 1896 | Synonym |
| Pollimyrus kingsleyae kingsleyae | Günther | 1896 | Synonym |
🔍 Similar Species
🗺️ Global Occurrence Map
Occurrence records from the Global Biodiversity Information Facility (GBIF) - 271 records indexed .
👥 Community & Contribute
No observations yet - be the first to log one!
View all observations for Paramormyrops Kingsleyae ↗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.