Taphromysis louisianae
(Possum shrimp)
Native Transplant

5 results for Taphromysis louisianae (Possum shrimp)
Download Data
Click here for listing in all states

Specimen IDStateCountyLocalityYear HUC Number What's this? Drainage nameStatus
541965 INSwitzerlandOhio River at RM 511.9, ORSANCO survey site OH511.9RDB2009 05090203 Middle Ohio-Laugheryunknown
541967 INSwitzerlandOhio River at RM 520, ORSANCO survey site OH520.0RDB2009 05090203 Middle Ohio-Laugheryunknown
541984 INSwitzerlandOhio River at RM 528.3, ORSANCO survey site OH528.3RDB2005 05090203 Middle Ohio-Laugheryunknown
541985 INSwitzerlandOhio River at RM 530.2, ORSANCO survey site OH530.2RDB2005 05090203 Middle Ohio-Laugheryunknown
542000 INSwitzerlandOhio River at RM 531, ORSANCO survey site OH531.0RDB2009 05090203 Middle Ohio-Laugheryunknown

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