Alosa sapidissima
Alosa sapidissima
(American Shad)
Fishes
Native Transplant
Collection Info
Point Map
Species Profile
Animated Map

8 results for Alosa sapidissima (American Shad)
Download Data

Specimen IDStateCountyLocalityYear HUC Number What's this? Drainage nameStatus
27687 AZMohaveColorado River at The Needles1885 15030101 Havasu-Mohave Lakesfailed
28249 CA Sacramento-San Joaquin Delta1885 18040003 San Joaquin Deltaestablished
34309 KS state non-specific1885  failed
40443 OR Columbia River1885 17080003 Lower Columbia-Clatskanieestablished
40414 ORMultnomahWillamette River at Portland1885 17090012 Lower Willametteestablished
45832 WA Columbia River1885 17020010 Upper Columbia-Entiatestablished
45752 WA Columbia River1885 17020010 Upper Columbia-Entiatestablished
45750 WAWalla WallaSnake River, near the junction with the Columbia at Ainsworth1885 17060110 Lower Snakecollected

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

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.