Perca flavescens
Perca flavescens
(Yellow Perch)
Native Transplant

8 results for Perca flavescens (Yellow Perch)
Download Data
Click here for listing in all states

Specimen IDStateCountyLocalityYear HUC Number What's this? Drainage nameStatus
1697603 MTFlatheadHubbart Reservoir1999 17010212 Lower Flatheaderadicated
1697644 MTFlatheadRogers Lake1993 17010212 Lower Flatheaderadicated
613885 MTLakeFlathead River. Township - 20n. Range - 21w. Section - 17. Maps: 250k-Wallace, 24k-Sloan, 100k-Plains.2000 17010212 Lower Flatheadestablished
290216 MTLakeNinepipe Reservoir1931 17010212 Lower Flatheadestablished
289981 MTSandersDry Fork Reservoir1949 17010212 Lower Flatheadestablished
292626 MTSandersFlathead River(River Miles: 43.8 to 43.9)2000 17010212 Lower Flatheadestablished
290258 MTSandersRainbow Lake1952 17010212 Lower Flatheadestablished
290256 MTSandersRainbow Lake1957 17010212 Lower Flatheadestablished

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/12/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.