Esox lucius
Esox lucius
(Northern Pike)
Fishes
Native Transplant

30 results for Esox lucius (Northern Pike)
Download Data

Page:12
Specimen IDStateCountyLocalityYear HUC Number What's this? Drainage nameStatus
262479 MTPhillipsBeaver Creek1981 10050012 Lower Milkestablished
262480 MTPhillipsBeaver Creek2003 10050012 Lower Milkestablished
287690 MTValleyDavenport Reservoir2009 10050012 Lower Milkestablished
1697839 MTValleyGlasgow Airforce Base Pond1999 10050012 Lower Milkestablished
287884 MTValleyGlasgow Base Pond2010 10050012 Lower Milkestablished
287885 MTValleyGlasgow Base Pond2010 10050012 Lower Milkestablished
262796 MTValleyMilk River1996 10050012 Lower Milkestablished
262797 MTValleyMilk River2003 10050012 Lower Milkestablished
290502 MTValleyMilk River River Mile: 01959 10050012 Lower Milkestablished
290473 MTValleyMilk River(River Miles: 1.8 to 2.8)[Calculated using NHD+ v2.0 GIS dataset]2003 10050012 Lower Milkestablished
290476 MTValleyMilk River(River Miles: 10 to 40)[Calculated using NHD+ v2.0 GIS dataset]1998 10050012 Lower Milkestablished
290477 MTValleyMilk River(River Miles: 11.7 to 12.7)[Calculated using NHD+ v2.0 GIS dataset]2003 10050012 Lower Milkestablished
290486 MTValleyMilk River(River Miles: 117 to 274)[Calculated using NHD+ v2.0 GIS dataset]2000 10050012 Lower Milkestablished
290487 MTValleyMilk River(River Miles: 120 to 140)[Calculated using NHD+ v2.0 GIS dataset]1998 10050012 Lower Milkestablished
290478 MTValleyMilk River(River Miles: 13.8 to 14.8)[Calculated using NHD+ v2.0 GIS dataset]2002 10050012 Lower Milkestablished
290488 MTValleyMilk River(River Miles: 132 to 139.4)[Calculated using NHD+ v2.0 GIS dataset]2002 10050012 Lower Milkestablished
290489 MTValleyMilk River(River Miles: 132 to 139.4)[Calculated using NHD+ v2.0 GIS dataset]2002 10050012 Lower Milkestablished
290479 MTValleyMilk River(River Miles: 15.3 to 16.3)[Calculated using NHD+ v2.0 GIS dataset]2002 10050012 Lower Milkestablished
290474 MTValleyMilk River(River Miles: 2.6 to 3.6)[Calculated using NHD+ v2.0 GIS dataset]2002 10050012 Lower Milkestablished
290475 MTValleyMilk River(River Miles: 3.2 to 4.2)[Calculated using NHD+ v2.0 GIS dataset]2002 10050012 Lower Milkestablished
290480 MTValleyMilk River(River Miles: 40 to 90)[Calculated using NHD+ v2.0 GIS dataset]1999 10050012 Lower Milkestablished
290481 MTValleyMilk River(River Miles: 65.6 to 66.6)[Calculated using NHD+ v2.0 GIS dataset]2002 10050012 Lower Milkestablished
290482 MTValleyMilk River(River Miles: 66.5 to 67.5)[Calculated using NHD+ v2.0 GIS dataset]2002 10050012 Lower Milkestablished
290483 MTValleyMilk River(River Miles: 67.7 to 68.7)[Calculated using NHD+ v2.0 GIS dataset]2003 10050012 Lower Milkestablished
290484 MTValleyMilk River(River Miles: 90 to 120.6)[Calculated using NHD+ v2.0 GIS dataset]1998 10050012 Lower Milkestablished
Page:12

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