Faxonius virilis
Faxonius virilis
(Virile Crayfish)
Crustaceans-Crayfish
Native Transplant
Collection Info
Point Map
Species Profile
Animated Map
Impacts

8 results for Faxonius virilis (Virile Crayfish)
Download Data

Specimen IDStateCountyLocalityYear HUC Number What's this? Drainage nameStatus
1409478 MSItawamba 2014 03160101 Upper Tombigbeeunknown
1328582 WYUintaBear River2011 16010101 Upper Bearunknown
1328583 WYUintaBear River2011 16010101 Upper Bearunknown
1328584 WYUintaBear River2011 16010101 Upper Bearunknown
1632513 WYUintaBear River State Park, WY2016 16010101 Upper Bearestablished
1632514 WYUintaBear River, WY2016 16010101 Upper Bearestablished
1632512 WYUintaSulfur Creek Reservoir, WY2016 16010101 Upper Bearestablished
1632515 WYUintaWoodruff Narrows Reservoir, WY2016 16010101 Upper Bearestablished

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