New 🐟 Mercury Safety Guide & Omega-3 Rankings Updated for 2026. View Omega-3 Rankings →

🌿 Sustainable Seafood ⚡ Omega-3 Rankings 🔬 Mercury Safety 🏆 World Records 🎣 Fishing Licenses
API Docs
Get API Key →
💧 Freshwater Least Concern 🌡️ Tropical

Ancistrus Claro

Ancistrus claro Knaack, 1999
← All Species
Max Length
6.6 cm
Max Weight
—
Lifespan
—
Trophic Level
—
Depth
—
Climate
Tropical
Resilience
—
Vulnerability
20.00/100
Typical Length
—
Depth Zone
demersal

📖 Overview

Overview information for Ancistrus Claro is currently being compiled by our editorial team.

Scientific Name
Ancistrus claro
Authority
Knaack, 1999
Habitat
Freshwater
Climate
Tropical
IUCN Status
LC
Max Length
6.6 cm
Vulnerability
20.00/100
Salinity
0–0.5 ppt

🐟 Physical Description

Physical description for Ancistrus Claro is currently being compiled.

🌀 Behaviour

Behavioural data for Ancistrus Claro is currently being reviewed.

🦐 Diet

Diet information for Ancistrus Claro is currently being compiled.

🥚 Reproduction

Reproduction data for Ancistrus Claro is currently being compiled.

🌍 Habitat & Distribution

Freshwater; demersal. Tropical South America: Cuiabá River basin in upper Paraguay River drainage, Brazil.

🌿 Ecology

Zone Preferences
💧 Freshwater ⬇️ Benthic

📐 Morphometrics

Length–Weight Relationship: W = 0.01479 × L2.98 (TL)
Max TL
6.6cm

🌡️ Water Parameters & Tolerance

Salinity Range
0–0.5ppt

🛡️ Conservation Assessment

IUCN Category
Least Concern
Assessment Date
2018

📊 Population Risk & Fisheries

Fishing Vulnerability
20.00/100
Low vulnerability
Climate Zone
Tropical
Described By
Knaack, 1999

👥 Community & Contribute

Aquareap Community Observations
0 Observations logged on Aquareap

No observations yet — be the first to log one!

View all observations for Ancistrus Claro ↗
Suggest an Edit

Spotted incorrect or outdated data? Submit a correction and our editorial team will review it. Approved edits go live within 48 hours.

Link to a scientific paper, FishBase, or other authoritative source
Report an Issue

Found a factual error, broken data, or inappropriate content? Let us know and we will investigate promptly.