Oncorhynchus clarkii
Oncorhynchus clarkii
(Cutthroat Trout)
Fishes
Native Transplant
Collection Info
Point Map
Species Profile
Animated Map

6 results for Oncorhynchus clarkii (Cutthroat Trout)
Download Data

Specimen IDCommon NameStateCountyLocalityYear HUC Number What's this? Drainage nameStatus
30538 Cutthroat TroutCO upper White drainage1982 14050005 Upper Whiteestablished
30539 Cutthroat TroutCO upper Yampa drainage1982 14050001 Upper Yampaestablished
283328 Yellowstone cutthroat troutCOGarfieldTrappers Lake1943 14050005 Upper Whiteunknown
261096 Cutthroat TroutCOMoffatYampa River at Yampa Canyon1987 14050002 Lower Yampaestablished
262539 Cutthroat TroutCOMoffatYampa River, lower, at river mile 24 in Dinosaur National Monument1969 14050002 Lower Yampastocked
267605 Snake River Finespotted Cutthroat TroutCORio BlancoLake Avery [aka Big Beaver Reservoir]2000 14050005 Upper Whiteestablished

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. [2026]. Nonindigenous Aquatic Species Database. Gainesville, Florida. Accessed [3/14/2026].

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.