Salvelinus fontinalis
Salvelinus fontinalis
(Brook Trout)
Native Transplant

8 results for Salvelinus fontinalis (Brook Trout)
Download Data
Click here for listing in all states

Specimen IDStateCountyLocalityYear HUC Number What's this? Drainage nameStatus
266080 NVElkoAngel Creek2001 16060007 Long-Ruby Valleysestablished
266159 NVElkoFranklin River2001 16060007 Long-Ruby Valleysestablished
1419890 NVElkoNA2000 16060007 Long-Ruby Valleysestablished
265601 NVElkoOverland Lake2001 16060007 Long-Ruby Valleysestablished
265603 NVElkoRobinson Lake2001 16060007 Long-Ruby Valleysestablished
265604 NVElkoRuby Lake National Wildlife Refuge2001 16060007 Long-Ruby Valleysestablished
164083 NVElkoRuby Lake National Wildlife Refuge2005 16060007 Long-Ruby Valleysestablished
265605 NVElkoSteele Lake2001 16060007 Long-Ruby Valleysestablished

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 [4/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.