Salvelinus alpinus oquassa
(blueback trout, Sunapee trout)
Fishes
Native Transplant

7 results for Salvelinus alpinus oquassa (blueback trout, Sunapee trout)
Download Data

Specimen IDStateCountyLocalityYear HUC Number What's this? Drainage nameStatus
773671 MECumberlandCoffee Pond southeast of Casco in Cumberland County1973 01060001 Presumpscotstocked
773715 MEHancockFloods Pond near Otis in Hancock County1973 01050002 Maine Coastalstocked
773675 MEPiscataquisLower South Branch Pond near T5 R9 Wels in Piscataquis County1973 01020002 East Branch Penobscot Riverstocked
773672 MEPiscataquisUpper South Branch Pond near T5 R9 Wels in Piscataquis County1973 01020002 East Branch Penobscot Riverstocked
37794 NH state non-specific1973 01000000 New Englandfailed
37869 NHCarrollConner Pond, Ossipee1973 01060002 Saco Riverfailed
37796 NHGraftonTewksbury Pond, Grafton Township1973 01070001 Pemigewasset Riverfailed

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. [2025]. Nonindigenous Aquatic Species Database. Gainesville, Florida. Accessed [1/15/2025].

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.