Oncorhynchus clarkii
Oncorhynchus clarkii
(Cutthroat Trout)
Native Transplant

8 results for Oncorhynchus clarkii (Cutthroat Trout)
Download Data

Specimen IDCommon NameStateCountyLocalityYear HUC Number What's this? Drainage nameStatus
29320 Cutthroat TroutCANevadaIndependence Lake1955 16050102 Truckeeestablished
167822 Cutthroat TroutCANevadaWarren Lake2000 16050102 Truckeeestablished
29340 Cutthroat TroutCASierraWebber Lake, 48 airkm due west of Reno1962 16050102 Truckeeunknown
265958 Cutthroat TroutNVDouglasSpooner Lake near Lake Tahoe2001 16050101 Lake Tahoeestablished
266068 Cutthroat TroutNVStoreyTruckee River2001 16050102 Truckeeestablished
265957 Cutthroat TroutNVWashoeHobart Creek Reservoir2001 16050102 Truckeeestablished
38961 Cutthroat TroutNVWashoePyramid Lake1977 16050103 Pyramid-Winnemucca Lakesunknown
39079 Lahontan cutthroat troutNVWashoePyramid Lake1953 16050103 Pyramid-Winnemucca Lakesestablished

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. [2022]. Nonindigenous Aquatic Species Database. Gainesville, Florida. Accessed [8/9/2022].

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.