Oncorhynchus nerka
Oncorhynchus nerka
(Sockeye Salmon)
Fishes
Native Transplant
Collection Info
Point Map
Species Profile
Animated Map

7 results for Oncorhynchus nerka (Sockeye Salmon)
Download Data
Click here for listing in all states

Specimen IDStateCountyLocalityYear HUC Number What's this? Drainage nameStatus
268628 CT Connecticut River drainage1986 01080205 Outlet Connecticut Riverestablished
268627 CT Housatonic River drainage1986 01100005 Housatonicestablished
268629 CT Thames drainage1986 01100003 Thamesestablished
30968 CT state non-specific1880 01000000 New England Regioncollected
30926 CT state non-specific1992 01000000 New England Regionestablished
30969 CTLitchfieldEast Twin Lakes, Salibury1935 01100005 Housatonicfailed
30876 CTLitchfieldEast Twin Lakes, Salibury1936 01100005 Housatonicestablished

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.