Ctenopharyngodon idella
Ctenopharyngodon idella
(Grass Carp)

6 results for Ctenopharyngodon idella (Grass Carp)
Download Data
Click here for listing in all states

Specimen IDCommon NameStateCountyLocalityYear HUC Number What's this? Drainage nameStatus
1685113 Grass CarpMNDakota[no locality description provided] Coordinates may be off.2013 07010206 Twin Citiesunknown
1685114 Grass CarpMNDakotaunnamed ponds1995 07010206 Twin Citiesunknown
849974 Grass Carp (diploid)MNWashingtonMississippi River, adjacent to Lower Grey Cloud Island2015 07010206 Twin Citiesunknown
1398226 Grass Carp (diploid)MNWashingtonMississippi River, at Lower Grey Cloud Slough [just above Hastings]2017 07010206 Twin Citiesunknown
558193 Grass Carp (diploid)MNWashingtonMississippi River, Pool 22013 07010206 Twin Citiesunknown
166597 Grass CarpMNWashingtonSt. Croix River, near Douglas Point Beach2006 07010206 Twin Citiesestablished

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/28/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.