Faxonius juvenilis
Faxonius juvenilis
(Kentucky River crayfish)
Native Transplant

8 results for Faxonius juvenilis (Kentucky River crayfish)
Download Data

Specimen IDStateCountyLocalityYear HUC Number What's this? Drainage nameStatus
564225 GAPutnamLittle River, (Lake Sinclair) at Twin Bridges Rd.2011 03070101 Upper Oconeeunknown
564224 GAPutnamMurder Creek, at end of FS 1108, ca. 7.5 air mi. SSW of Eatonton2011 03070101 Upper Oconeeunknown
1703911 NCSwainLittle Tennessee River, TN Drainage2010 06010202 Upper Little Tennessee 
1703907 TNCampbellElk Fork Creek, Cumberland Drainage2010 05130101 Upper Cumberland 
1703908 TNGraingerIndian Creek, Clinch TN drainage2010 06010205 Upper Clinch, Tennessee, Virginia 
1703910 TNHamblenBent Creek, Nolichucky TN drainage2010 06010108 Nolichucky 
1703909 TNHawkinsBig Creek, Holston TN drainage2010 06010104 Holston 
887547 WVMineralNew Creek, 7.4 Mile SW Of Burlington On Route 501959 02070002 North Branch Potomacunknown

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 [6/15/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.