Faxonius juvenilis
Faxonius juvenilis
(Kentucky River crayfish)
Crustaceans-Crayfish
Native Transplant
Collection Info
Point Map
Species Profile
Animated Map

6 results for Faxonius juvenilis (Kentucky River crayfish)
Download Data
Click here for listing in all states

Specimen IDStateCountyLocalityYear HUC Number What's this? Drainage nameStatus
1754220 ALCherokeeCoosa River, 0.8 mi SE Leesburg2017 03150105 Upper Coosa 
1754219 ALCherokeeWeiss Lake, boat ramp off Hwy. 682017 03150105 Upper Coosa 
1754213 ALWinstonBrushy Creek, near river km 15.82013 03160110 Sipsey Fork 
1754216 ALWinstonBrushy Creek, river km 202013 03160110 Sipsey Fork 
1754214 ALWinstonChimney Branch, 850 m from confluence with Brushy Creek2003 03160110 Sipsey Fork 
1754215 ALWinstonMile Creek, upstream of FS Rd. 1212 crossing2013 03160110 Sipsey Fork 

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

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.



Loading...