Morone chrysops
Morone chrysops
(White Bass)
Native Transplant

7 results for Morone chrysops (White Bass)
Download Data

Specimen IDStateCountyLocalityYear HUC Number What's this? Drainage nameStatus
1403062 NC upper French Broad drainage1993 06010105 Upper French Broadlocally established
264825 SCOconeeHartwell Lake, west of Pendleton2009 03060101 Senecaestablished
264826 SCPickensLake Keowee, southwest of Nine Times2009 03060101 Senecaestablished
1403059 TN Watauga, North Carolina, Tennessee drainage1993 06010103 Watauga, North Carolina, Tennesseelocally established
1469497 TXBaylorMillers Creek Reservoir2012 12060101 Middle Brazos-Millersunknown
1403067 VA North Fork Holston drainage1994 06010101 North Fork Holstonlocally established
1403069 VA South Fork Holston drainage1994 06010102 South Fork Holstonlocally established

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 [6/13/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.