Oncorhynchus tshawytscha
Oncorhynchus tshawytscha
(Chinook Salmon)
Fishes
Native Transplant

8 results for Oncorhynchus tshawytscha (Chinook Salmon)
Download Data
Click here for listing in all states

Specimen IDStateCountyLocalityYear HUC Number What's this? Drainage nameStatus
38990 NV Lahontan Basin, lakes and major rivers1879 16050203 Carson Desertcollected
38991 NV Lahontan Basin, lakes and major rivers1908 16050203 Carson Desertcollected
38992 NV Lahontan Basin, lakes and major rivers1909 16050203 Carson Desertcollected
38993 NV Lahontan Basin, lakes and major rivers1910 16050203 Carson Desertcollected
38994 NV Lake Tallac1911 16050101 Lake Tahoecollected
38845 NV state non-specific1878  collected
38585 NV state non-specific1896  collected
159624 NVDoug/Lyon/WahsoeLake Tahoe2001 16050101 Lake Tahoefailed

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.