Oncorhynchus clarkii × mykiss
Oncorhynchus clarkii × mykiss
(cutbow trout)
Fishes
Native Hybrid

12 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
660939 IDCaribouBECHLER CREEK1968 17040105 Saltstocked
660930 IDCaribouBOULDER CREEK1968 17040105 Saltstocked
660938 IDCaribouBOULDER CREEK1968 17040105 Saltstocked
660936 IDCaribouBRUSH CREEK1968 17040105 Saltstocked
660937 IDCaribouBRUSH CREEK1968 17040105 Saltstocked
660935 IDCaribouCROOKED CREEK1968 17040105 Saltstocked
661032 IDCaribouHYDE CREEK1968 17040105 Saltstocked
661037 IDCaribouHYDE CREEK1968 17040105 Saltstocked
661038 IDCaribouHYDE CREEK1968 17040105 Saltstocked
660941 IDCaribouN F STUMP CREEK1968 17040105 Saltstocked
660933 IDCaribouS F TINCUP CREEK1968 17040105 Saltstocked
660934 IDCaribouS F TINCUP CREEK1968 17040105 Saltstocked

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/21/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.