Echinogammarus ischnus
Echinogammarus ischnus

10 results for Echinogammarus ischnus (scud)
Download Data
Click here for listing in all states

Specimen IDStateCountyLocalityYear HUC Number What's this? Drainage nameStatus
1463887 KYBrackenOhio River2006 05090201 Ohio Brush-Whiteoakunknown
1463899 KYBreckinridgeOhio River2006 05140104 Blue-Sinkingunknown
1463967 KYBreckinridgeOhio River2006 05140104 Blue-Sinkingunknown
1463991 KYBreckinridgeOhio River2006 05140201 Lower Ohio-Little Pigeonunknown
1463876 KYLivingstonOhio River2006 05140203 Lower Ohio-Bayunknown
860154 KYLivingstonOhio River2006 05140203 Lower Ohio-Bayestablished
887471 KYLivingstonOhio River, at GRE-1509/400539; 397 miles from mouth of Ohio River2006 05140203 Lower Ohio-Bayestablished
1464002 KYMasonOhio River2006 05090201 Ohio Brush-Whiteoakunknown
1463911 KYMeadeOhio River2006 05140104 Blue-Sinkingunknown
1463912 KYOldhamOhio River2006 05140101 Silver-Little Kentuckyunknown

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