Nocomis leptocephalus
Nocomis leptocephalus
(Bluehead Chub)
Fishes
Native Transplant

7 results for Nocomis leptocephalus (Bluehead Chub)
Download Data

Specimen IDStateCountyLocalityYear HUC Number What's this? Drainage nameStatus
1331634 NCHendersonBat Fork, at SR 17791997 06010105 Upper French Broadestablished
1331635 NCHendersonBat Fork, at SR 17792002 06010105 Upper French Broadestablished
1331638 NCHendersonClear Creek, at SR 15132001 06010105 Upper French Broadestablished
1331639 NCHendersonClear Creek, at SR 15862001 06010105 Upper French Broadestablished
1331640 NCHendersonClear Creek, at SR 15872001 06010105 Upper French Broadestablished
1331642 NCHendersonMud Creek, at SR 16471997 06010105 Upper French Broadestablished
1331643 NCHendersonMud Creek, at SR 16472002 06010105 Upper French Broadestablished

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 [4/23/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.