Trachemys scripta elegans
Trachemys scripta elegans
(Red-eared Slider)
Reptiles-Turtles
Native Transplant
Collection Info
Point Map
Species Profile
Animated Map
Impacts

4 results for Trachemys scripta elegans (Red-eared Slider)

Impact ID Scientific Name Impact Type Study Type Study Location Impact Description Reference
4107 Trachemys scripta elegans Genetic Observational N/A Red-eared Sliders have been shown to hybridize with the Chinese stripe-necked turtle, Mauremys... 35785
4364 Trachemys scripta elegans Genetic Observational Field T. s. elegans hybridizes with T. s. scripta and T. gaigeae in the... 36306
4366 Trachemys scripta elegans Genetic Anecdotal N/A Intergeneric hybridization is known to occur, but it is unknown whether the red-eared slider would... 36307
4382 Trachemys scripta elegans Genetic Anecdotal N/A The hybridization of freshwater turtles with introduced T. s. elegans have been reported... 36308

View all impact types for Trachemys scripta elegans
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. [2024]. Nonindigenous Aquatic Species Database. Gainesville, Florida. Accessed [11/28/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.