Trachemys scripta troostii
Trachemys scripta troostii
(Cumberland Slider)
Native Transplant

7 results for Trachemys scripta troostii (Cumberland Slider)
Download Data

Specimen IDStateCountyLocalityYear HUC Number What's this? Drainage nameStatus
1660339 ILMonroe[No locality information provided]1906 07140101 Cahokia-Joachimunknown
115878 NEAdamsBlue River (Little Blue River?)1926 10270206 Upper Little Bluecollected
1668680 TNPickettObey River, Dale Hollow Lake2005 05130105 Obeyunknown
1661465 TXReevesBalmorhea, Toyah Creek, or-a-tributary1929 13070003 Toyahunknown
1661464 TXReevesToyahvale1929 13070003 Toyahunknown
1667979 VASmythNorth Fork Holston River, State Road 91 & Kent Street, 0.24 mi SW2016 06010101 North Fork Holstonunknown
1668229 VAWashingtonNorth Fork Holston River, 0.05 mi W Smyth County line2016 06010101 North Fork Holstonunknown

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. [2023]. Nonindigenous Aquatic Species Database. Gainesville, Florida. Accessed [3/25/2023].

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.