Esox lucius
Esox lucius
(Northern Pike)
Fishes
Native Transplant

8 results for Esox lucius (Northern Pike)
Download Data

Specimen IDStateCountyLocalityYear HUC Number What's this? Drainage nameStatus
1674712 CTNew Haven[No locality description provided]2020 01100005 Housatonic 
1675876 IDBonner[No locality description provided]2020 17010214 Pend Oreille Lake 
1674884 MEKennebec[No locality description provided]2020 01030003 Lower Kennebec River 
1655286 NHCoosConnecticut River, oxbow adjacent to Route 1022020 01080101 Headwaters Connecticut Riverestablished
1679001 NHGrafton[No locality description provided]2020 01080104 Waits River-Connecticut River 
1655196 NHGraftonPerch Pond2020 01080103 Ammonoosuc River-Connecticut Riverestablished
1679030 VTCaledonia[No locality description provided]2020 01080102 Passumpsic River 
1673384 VTChittenden[No locality description provided]2020 04300103 Winooski River 

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 [12/26/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.