Oncorhynchus clarkii
Oncorhynchus clarkii
(Cutthroat Trout)
Native Transplant

10 results for Oncorhynchus clarkii (Cutthroat Trout)
Download Data

Specimen IDStateCountyLocalityYear HUC Number What's this? Drainage nameStatus
653176 IDBear LakeBEAVER CREEK1969 16010102 Central Bearstocked
651622 IDBear LakeBEAVER CREEK1970 16010102 Central Bearstocked
651094 IDBear LakeBEAVER CREEK1971 16010102 Central Bearstocked
649619 IDBear LakeBEAVER CREEK1972 16010102 Central Bearstocked
652318 WYLincolnGIRAFFE CREEK1969 16010102 Central Bearstocked
651625 WYLincolnGIRAFFE CREEK1970 16010102 Central Bearstocked
651096 WYLincolnGIRAFFE CREEK1971 16010102 Central Bearstocked
649621 WYLincolnGIRAFFE CREEK1972 16010102 Central Bearstocked
649052 WYLincolnGIRAFFE CREEK1975 16010102 Central Bearstocked
651989 WYLincolnGIRAFFE CREEK1976 16010102 Central Bearstocked

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.


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 [6/18/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.