Oncorhynchus clarkii × mykiss
Oncorhynchus clarkii × mykiss
(cutbow trout)
Fishes
Native Hybrid
Collection Info
Point Map
Species Profile
Animated Map

5 results for Oncorhynchus clarkii × mykiss (cutbow trout)
Download Data
Click here for listing in all states

Specimen IDStateCountyLocalityYear HUC Number What's this? Drainage nameStatus
38166 NM Rio Grande Gorge1995 13020101 Upper Rio Grandeestablished
38234 NM Rio Grande-Elephant Butte drainage; in native cutthroat range1997 13020200 Rio Grande-Elephant Butteestablished
38505 NM upper Pecos drainage; in native cutthroat range1997 13060000 Upper Pecosestablished
38491 NM upper Rio Grande drainage; in native cutthroat range1997 13020100 Upper Rio Grandeestablished
38501 NM upper San Juan drainage; in native cutthroat range1997 14080100 Upper San Juanestablished

Data Disclaimer: Number of records does not imply species abundance. This summary represent collection records only and may not reflect the actual distribution of established populations. These data are preliminary or provisional and are subject to revision. They are being provided to meet the need for timely best science. The data have not received final approval by the U.S. Geological Survey (USGS) and are provided on the condition that neither the USGS nor the U.S. Government shall be held liable for any damages resulting from the authorized or unauthorized use of the data.

Disclaimer:

The data represented on this site vary in accuracy, scale, completeness, extent of coverage and origin. It is the user's responsibility to use these data consistent with their intended purpose and within stated limitations. We highly recommend reviewing metadata files prior to interpreting these data.

Citation information: U.S. Geological Survey. [2024]. Nonindigenous Aquatic Species Database. Gainesville, Florida. Accessed [11/24/2024].

Contact us if you are using data from this site for a publication to make sure the data are being used appropriately and for potential co-authorship if warranted.

For general information and questions about the database, contact Wesley Daniel. For problems and technical issues, contact Matthew Neilson.