Cyprinus carpio
Cyprinus carpio
(Common Carp)

5 results for Cyprinus carpio (Common Carp)

Impact ID Scientific Name Impact Type Study Type Study Location Impact Description Reference
3297 Cyprinus carpio Predation/Herbivory Observational Field Cyprinus carpio eradication and exclusion from reservoir tributaries allowed for increased... 27700
3299 Cyprinus carpio Predation/Herbivory Observational Field Through the consumption of eggs, Cyprinus carpio may be responsible for the decline of... 10
3300 Cyprinus carpio Predation/Herbivory Observational Field White Sturgeon (Acipenser transmontanus) eggs have been found in the stomachs of... 1399
3846 Cyprinus carpio Predation/Herbivory Anecdotal N/A Cyprinus carpio consume other Great Lakes invasive species, including Dreissena... 13595
5838 Cyprinus carpio Predation/Herbivory Observational Field Cyprinus carpio is harvested from Groenvlei Lake to feed underprivileged communities in... 39779

View all impact types for Cyprinus carpio
Data Disclaimer: 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 [3/31/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.