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

7 results for Faxonius virilis (Virile Crayfish)
Download Data

Specimen IDStateCountyLocalityYear HUC Number What's this? Drainage nameStatus
1420828 OKNowataMiddle Fork Double Creek, 1.5 mi E Double Creek Cove1993 11070103 Middle Verdigrisunknown
1328495 OKOsageBartlesville1996 11070106 Caneyunknown
1328497 OKOsageBartlesville1996 11070106 Caneyunknown
1328498 OKOsageBartlesville1996 11070106 Caneyunknown
1420911 OKRogersBird Creek, 2.4 mi NE Catoosa, just W confl. Verdigris River1996 11070107 Birdunknown
1420878 OKRogersVerdigris River, 2.4 mi NE Catoosa1996 11070105 Lower Verdigrisunknown
1328487 OKWagonerVerdigris River1997 11070105 Lower Verdigrisunknown

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.