Faxonius rusticus
Faxonius rusticus
(Rusty Crayfish)
Native Transplant

7 results for Faxonius rusticus (Rusty Crayfish)
Download Data
Click here for listing in all states

Specimen IDStateCountyLocalityYear HUC Number What's this? Drainage nameStatus
4463 NJ state non-specific1989 02000000 Mid-Atlantic Regioncollected
1632844 NJPassaicPassaic River above the Paterson Great Falls2019 02030103 Hackensack-Passaicunknown
1420742 NJPassaicRingwood Creek wetland2017 02030103 Hackensack-Passaicestablished
1736248 NJSussexDelaware river watershed, Sussex, NJ2013 02040105 Middle Delaware-Musconetcong 
153949 NJSussexWallkill River, 1 mi W of Owens1968 02020007 Rondoutcollected
1321951 NJWarrenDelaware Water Gap, Sussex Co., NJ.2015 02040104 Middle Delaware-Mongaup-Brodheadunknown
1463659 NJWarrenVanCampens Brook, downstream of crossing Old Mine Road in Delaware Water Gap National Recreation Area.2016 02040104 Middle Delaware-Mongaup-Brodheadestablished

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/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.