Cyprinus carpio
Cyprinus carpio
(Common Carp)
Fishes
Exotic
Collection Info
Point Map
Species Profile
Animated Map
Impacts

5 results for Cyprinus carpio (Common Carp)
Download Data
Click here for listing in all states

Specimen IDStateCountyLocalityYear HUC Number What's this? Drainage nameStatus
283994 SD Vermillion drainage1980 10170102 Vermillionestablished
42699 SD Vermillion drainage, throughout1959 10170102 Vermillionestablished
42661 SDClayVermillion River, Vermillion (#35)1934 10170102 Vermillionestablished
609672 SDTurnerTurkey Ridge Creek. Township:96n, Range:52w, Section:17. Maps:250k-Sioux Falls, 24k-Viborg, 100k-Freeman.2001 10170102 Vermillionestablished
609671 SDTurnerTurkey Ridge Creek. Township:96n, Range:52w, Section:17. Maps:250k-Sioux Falls, 24k-Viborg, 100k-Freeman.2001 10170102 Vermillionestablished

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