Cyprinella lutrensis
Cyprinella lutrensis
(Red Shiner)
Fishes
Native Transplant

4 results for Cyprinella lutrensis (Red Shiner)

Impact ID Scientific Name Impact Type Study Type Study Location Impact Description Reference
2101 Cyprinella lutrensis Disease/Parasites/Toxicity Observational Field The introduction of Red Shiner into Utah was probably how the Asian tapeworm entered the Virgin... 1104
2102 Cyprinella lutrensis Disease/Parasites/Toxicity Observational Field Red Shiner is one of the species that potentially introduced the Asian fish tapeworm... 15579
3956 Cyprinella lutrensis Disease/Parasites/Toxicity Observational Field The introduction of Red Shiner to the Great Lakes may further the spread of Bothriocephalus... 30704
3957 Cyprinella lutrensis Disease/Parasites/Toxicity Observational Field Red Shiner are host to Pseudocapillaria tomentosa, a parasitic nematode that can cause inflammation... 35522

View all impact types for Cyprinella lutrensis
Data Disclaimer: 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. [2022]. Nonindigenous Aquatic Species Database. Gainesville, Florida. Accessed [5/25/2022].

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.