Oncorhynchus tshawytscha
Oncorhynchus tshawytscha
(Chinook Salmon)
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
1403611 NYOswegoBeaverdam Brook2016 04140102 Salmon-Sandyestablished
1403612 NYOswegoBeaverdam Brook2016 04140102 Salmon-Sandyestablished
1403613 NYOswegoBeaverdam Brook2016 04140102 Salmon-Sandyestablished
1524031 NYOswegoLittle Sandy Creek1997 04140102 Salmon-Sandystocked
1524040 NYOswegoLittle Sandy Creek1997 04140102 Salmon-Sandystocked
1524049 NYOswegoSalmon River1997 04140102 Salmon-Sandystocked
1524059 NYOswegoSalmon River1997 04140102 Salmon-Sandystocked
39509 NYOswegoSalmon River, Pulaski, and its tributaries1985 04140102 Salmon-Sandyestablished

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

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.