Carasobarbus
genus of fishes

Carasobarbus, the himris, is a small genus of ray-finned fishes in the family Cyprinidae. Its species are found in rivers, streams, lakes and ponds in Western Asia and Northwest Africa. C. canis can reach 66 cm (26 in) in total length, but most other species are up to around half or one-quarter of that size.
Like many other "barbs", it was long included in Barbus. It appears to be a fairly close relative of the typical barbels and relatives – the genus Barbus proper –, but closer still to the large hexaploid species nowadays separated in Labeobarbus. Because of the improved phylogenetic knowledge which indicates Barbus was highly paraphyletic in its wide circumscription –, Carasobarbus and some other closely related "barbs" (e.g. "Barbus" reinii) may be included in Labeobarbus to avoid a profusion of very small genera. This genus is now classified in the subfamily Torinae.
Species
Carasobarbus contains the following species:
Carasobarbus apoensis (Banister & M. A. Clarke, 1977) (Arabian himri)
Carasobarbus canis (Valenciennes, 1842) (Jordan himri)
Carasobarbus chantrei (Sauvage, 1882) (Orontes himri)
Carasobarbus doadrioi Jouladeh‐Roudbar, Kaya, Vatandoust & Ghanavi, 2024
Carasobarbus exulatus (Banister & Clarke, 1977) (Hadramaut himri)
Carasobarbus fritschii (Günther, 1874)
Carasobarbus hajhosseini Jouladeh‐Roudbar, Kaya, Vatandoust & Ghanavi, 2024
Carasobarbus harterti (Günther, 1901)
Carasobarbus kosswigi (Ladiges, 1960) (Kisslip himri)
Carasobarbus luteus (Heckel, 1843) (Mesopotamian himri)
Carasobarbus moulouyensis (Pellegrin, 1924).
Begin with the source’s own compact description: “Carasobarbus” is genus of fishes. The dossier treats that line as a proposition to test through Carasobarbus, genus and fishes, not as a finished interpretation.
Why this record matters
The phrase “genus of fishes” supplies a clear boundary for inquiry. It also exposes the unanswered questions: who defined that boundary, when it became stable and which sources sit outside it.
The date and method of observation matter as much as the stated conclusion, especially where classification or consensus has changed. The source revision retrieved here is dated May 18, 2026. The linked authority identifier is Q5037734. None of the 0 selected statements returned an explicit reference. The first chronological checks are 1977, 1842, 1882 and 2024.
Scientific names, classifications and consensus can change while older terminology persists in catalogues and historical literature. The source lead contains qualifying language; that uncertainty should survive quotation, summary and reuse. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Check terminology, classification and the date of the cited evidence. Scientific names and technical consensus can change while older records retain historical value.
- Current terminology
- Classification context
- Finding cited technical literature
Primary datasets, specimen catalogues, standards bodies and the most recent peer-reviewed literature.
Three-step research path
- Establish the record: confirm the title “Carasobarbus”, its source revision and the description used here.
- Expand the search: follow Carasobarbus primary sources, Carasobarbus archive and Carasobarbus research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Carasobarbus”?
- Which observation, specimen, dataset or publication supports the account?
- Is the terminology current, historical or disputed?
Search terms from this dossier
This entry incorporates text from “Carasobarbus” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.