Specimen Information

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

Specimen ID1548326
GroupCrustaceans-Crayfish
GenusFaxonius
Speciesrusticus
Common NameRusty Crayfish
StateOR
CountyGrant
LocalityJohn Day River,Clyde Holiday State Park, OR
Mapping AccuracyAccurate
HUC8 NameUpper John Day
HUC8 Number17070201
HUC10 NameLaycock Creek-John Day River
HUC10 Number1707020109
HUC12 NameLuce Creek-John Day River
HUC12 Number170702010902
Map
+
Collection Month7
Collection Year2005
Year AccuracyActual
Potential Pathwayunknown | released bait
Statusestablished
Reference 1
Ref. Number:33392
Author:Adams, J.
Date:2005
Title:Introduced Population of Orconectes (Procericambarus) neglectus neglectus (Faxon, 1885) in the Columbia Basin
Publisher:The Xerces Society for Invertebrate Conservation
Pages:5 pp.
CommentsSpecies ID updated on 11/16/2023-“Specimens collected during the surveys were originally believed to be Orconectes neglectus neglectus (Faxon, 1885), partially due to this invasive species' presence in Oregon's Rogue River drainage (Bouchard, 1977), but re-examination by the authors identified these crayfish as O. rusticus. This identification was verified by Dr. Christopher Taylor (University of Illinois) on 10 December 2008 and voucher specimens have been deposited at the Illinois Natural History Survey, Champaign, IL.” Olden et al. 2009
Record TypeLiterature
VerifierD. Christopher Rogers of EcoAnalysts Inc.
Freshwater/MarineFreshwater


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