Cyprinus carpio
Cyprinus carpio
(Common Carp)

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

Specimen IDStateCountyLocalityYear HUC Number What's this? Drainage nameStatus
1674954 NVWashoe[No locality description provided]2020 16050102 Truckee 
1675768 NVWashoe[No locality description provided]2021 16050102 Truckee 
1730221 NVWashoe[No locality description provided]2023 16050102 Truckee 
1729926 NVWashoe[No locality description provided]2023 16050102 Truckee 
1729765 NVWashoe[No locality description provided]2023 16050102 Truckee 
610317 NVWashoeSteamboat Creek2004 16050102 Truckeeestablished
1635335 NVWashoeVirginia Lake, Reno, NV2020 16050102 Truckeeunknown
38982 NVWashoeWashoe Lake1960 16050102 Truckeeestablished

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