Esox lucius
Esox lucius
(Northern Pike)
Native Transplant

9 results for Esox lucius (Northern Pike)
Download Data
Click here for listing in all states

Specimen IDStateCountyLocalityYear HUC Number What's this? Drainage nameStatus
287666 MTPhillipsCole Pond NE2010 10050011 Whitewaterestablished
287675 MTPhillipsCole Pond, NNW1969 10050011 Whitewaterestablished
287674 MTPhillipsCole Pond, NNW1970 10050011 Whitewaterestablished
287673 MTPhillipsCole Pond, NNW1971 10050011 Whitewaterestablished
287670 MTPhillipsCole Pond, NNW1986 10050011 Whitewaterestablished
287672 MTPhillipsCole Pond, NNW2005 10050011 Whitewaterestablished
287671 MTPhillipsCole Pond, NNW2009 10050011 Whitewaterestablished
287685 MTPhillipsCompton Reservoir1995 10050011 Whitewaterestablished
262993 MTPhillipsWhitewater Creek2000 10050011 Whitewaterestablished

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. [2023]. Nonindigenous Aquatic Species Database. Gainesville, Florida. Accessed [12/10/2023].

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.