Salvelinus fontinalis
Salvelinus fontinalis
(Brook Trout)
Native Transplant

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

Specimen IDStateCountyLocalityYear HUC Number What's this? Drainage nameStatus
34574 KY Cumberland River, upper, above falls1986 05130101 Upper Cumberlandestablished
262935 KYBellShillalah Creek and Martins Fork1980 05130101 Upper Cumberlandestablished
34570 KYBellShillalah Creek and Martins Fork1986 05130101 Upper Cumberlandestablished
34572 KYBellShillalah Creek and Martins Fork1986 05130101 Upper Cumberlandestablished
34400 KYHarlanMartin's Fork. Bell County1975 05130101 Upper Cumberlandstocked
1702494 KYLetcherBad Branch1980 05130101 Upper Cumberland 
1702495 KYLetcherBad Branch1981 05130101 Upper Cumberland 
1702496 KYLetcherBad Branch1982 05130101 Upper Cumberland 
34571 KYLetcherBad Branch (Ohio drainage)1986 05130101 Upper Cumberlandestablished

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