Sander vitreus
Sander vitreus
Native Transplant

10 results for Sander vitreus (Walleye)
Download Data
Click here for listing in all states

Specimen IDStateCountyLocalityYear HUC Number What's this? Drainage nameStatus
36823 MTPetroleumPetrolia Lake (?), lower Flatwillow Creek1990 10040203 Flatwillowestablished
289776 MTPetroleumPetrolia Reservoir1985 10040203 Flatwillowestablished
289775 MTPetroleumPetrolia Reservoir1991 10040203 Flatwillowestablished
289774 MTPetroleumPetrolia Reservoir1995 10040203 Flatwillowestablished
289770 MTPetroleumPetrolia Reservoir1997 10040203 Flatwillowestablished
289773 MTPetroleumPetrolia Reservoir2000 10040203 Flatwillowestablished
289769 MTPetroleumPetrolia Reservoir2002 10040203 Flatwillowestablished
289772 MTPetroleumPetrolia Reservoir2005 10040203 Flatwillowestablished
289771 MTPetroleumPetrolia Reservoir2010 10040203 Flatwillowestablished
289768 MTPetroleumPetrolia Reservoir2011 10040203 Flatwillowestablished

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