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

7 results for Alosa sapidissima (American Shad)
Download Data

Specimen IDStateCountyLocalityYear HUC Number What's this? Drainage nameStatus
30327 CODenverPlatte River at Denver1872 10190003 Middle South Platte-Cherry Creekfailed
30738 CODenverPlatte River at Denver1872 10190002 Upper South Plattefailed
34088 IN White River, Indianapolis1872 05120201 Upper Whitefailed
35897 MNRamseyMississippi River a few km above St. Paul1872 07010206 Twin Citiesfailed
35903 MNRamseyMississippi River at St. Paul1872 07010206 Twin Citiesfailed
39721 NYCattaraugusAllegheny River at Salamanca1872 05010001 Upper Alleghenyfailed
40121 OHPortageCuyahoga River at Kent1872 04110002 Cuyahogafailed

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.