Hypophthalmichthys nobilis
Hypophthalmichthys nobilis
(Bighead Carp)

8 results for Hypophthalmichthys nobilis (Bighead Carp)
Download Data
Click here for listing in all states

Specimen IDStateCountyLocalityYear HUC Number What's this? Drainage nameStatus
158507 KY Ohio River1999 05140206 Lower Ohioestablished
1524516 KYBallardGar Creek [Ohio River tributary]2018 05140206 Lower Ohioestablished
775352 KYLivingstonOhio River2009 05140206 Lower Ohioestablished
280448 KYLivingstonOhio River (R.M. 928.0) [in Ledbetter]2009 05140206 Lower Ohiounknown
775353 KYMcCrackenOhio River2005 05140206 Lower Ohioestablished
775319 KYMcCrackenOhio River2006 05140206 Lower Ohioestablished
775297 KYMcCrackenOhio River2009 05140206 Lower Ohioestablished
280449 KYMcCrackenOhio River (R.M. 950.2) [across from Joppa, IL]2009 05140206 Lower Ohiounknown

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 [5/18/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.