Esox lucius
Esox lucius
(Northern Pike)
Fishes
Native Transplant
Collection Info
Point Map
Species Profile
Animated Map

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

Specimen IDStateCountyLocalityYear HUC Number What's this? Drainage nameStatus
27020 ARBaxterNorfork Lake1988 11010006 North Fork Whiteestablished
27019 ARBentonBeaver [Lake] Reservoir [White River][just W of Rogers, AR]1988 11010001 Beaver Reservoirestablished
27021 ARFultonBig Creek1988 11010006 North Fork Whiteestablished
27024 ARHempsteadMillwood Reservoir1988 11140109 Lower Little Arkansas, Oklahomastocked
27023 ARHot SpringDe Gray Reservoir1988 08040102 Upper Ouachitastocked
27025 ARScottJones Creek1988 11110206 Fourche La Faveunknown
27022 ARWashingtonIllinois drainage1988 11110103 Illinoisunknown

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