Morone chrysops
Morone chrysops
(White Bass)
Fishes
Native Transplant
Collection Info
Point Map
Species Profile
Animated Map

10 results for Morone chrysops (White Bass)
Download Data
Click here for listing in all states

Specimen IDStateCountyLocalityYear HUC Number What's this? Drainage nameStatus
1675323 UTUtah[No locality description provided]2020 16020201 Utah Lake 
263311 UTUtahJordan River, at Lehi2000 16020201 Utah Lakeestablished
44546 UTUtahUtah Lake1955 16020201 Utah Lakeestablished
1468008 UTUtahUtah Lake1956 16020201 Utah Lakeestablished
1467962 UTUtahUtah Lake1958 16020201 Utah Lakeestablished
1467963 UTUtahUtah Lake1970 16020201 Utah Lakeestablished
273733 UTUtahUtah Lake1970 16020201 Utah Lakeestablished
1468009 UTUtahUtah Lake1974 16020201 Utah Lakeestablished
44714 UTUtahUtah Lake1987 16020201 Utah Lakeestablished
265736 UTUtahUtah Lake near the mouth of the Provo River2000 16020201 Utah Lakeestablished

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.

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.