Esox niger
Esox niger
(Chain Pickerel)
Fishes
Native Transplant
Collection Info
Point Map
Species Profile
Animated Map

9 results for Esox niger (Chain Pickerel)
Download Data
Click here for listing in all states

Specimen IDStateCountyLocalityYear HUC Number What's this? Drainage nameStatus
859924 OH Great Miami River1970 05080002 Lower Great Miami, Indiana, Ohiofailed
268857 OH Muskingum River drainage1986 05040004 Muskingumestablished
39897 OH state non-specific1981  established
40037 OHSummitLong Lake [in south Akron]1935 05040001 Tuscarawasestablished
40038 OHSummitLong Lake [in south Akron]1935 05040001 Tuscarawasestablished
785889 OHSummitLong Lake [in south Akron]1959 05040001 Tuscarawasestablished
39896 OHSummitLong Lake [in south Akron]1981 05040001 Tuscarawasestablished
269012 OHSummitLong Lake, Summit County, OH1935 05040001 Tuscarawasestablished
269013 OHSummitNesmith Lake, Ohio1957 05040001 Tuscarawasestablished

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 [11/24/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.