Specimen Information

Faxonius rusticus
Faxonius rusticus
(Rusty Crayfish)
Crustaceans-Crayfish
Native Transplant

Specimen ID154722
GroupCrustaceans-Crayfish
GenusFaxonius
Speciesrusticus
Common NameRusty Crayfish
StateNC
CountyRutherford
LocalityBroad River, Hwy 64/74A, ~1.5 mi W of Rock Springs Road bridge and ~ 3 mi E of Lake Lure dam
Mapping AccuracyAccurate
HUC8 NameUpper Broad
HUC8 Number03050105
HUC10 NameHeadwaters Broad River
HUC10 Number0305010503
HUC12 NameKnob Creek-Broad River
HUC12 Number030501050308
Map
+
Collection Day7
Collection Month7
Collection Year2002
Year AccuracyActual
Potential Pathwayreleased bait
Statuscollected
Reference 1
Ref. Number:16109
Author:Cooper, J.E., and S.A. Armstrong
Date:2007
Title:Locality records and other data for invasive crayfishes (Decapoda: Cambaridae) in North Carolina.
Journal:Journal of the North Carolina Academy of Science
Volume:123
Issue:1
Pages:1-13
Reference 2
Ref. Number:13155
Author:Richerson, Myriah.
Date:2002
Title:Nonindigenous Species Data Base Voluntary Reporting Form: Orconectes rusticus.
CommentsTotal Carapace Length= 40 mm; Body Length=75 mm; Postorbital Carapace Length=28 mm
Record TypeSpecimen
DisposalNorth Carolina Museum of Natural Sciences
Museum Cat NumberNCSM 23751
VerifierJohn Cooper
Freshwater/MarineFreshwater
Number Collected1
Number Preserved1
Number of Breeding Males1
Specimen ImpactForm-1 male
Photo
Faxonius rusticus


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 [11/21/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.