Pylodictis olivaris
Pylodictis olivaris
(Flathead Catfish)
Native Transplant

6 results for Pylodictis olivaris (Flathead Catfish)
Download Data
Click here for listing in all states

Specimen IDStateCountyLocalityYear HUC Number What's this? Drainage nameStatus
1523558 KSButler[No specific locality provided in original dataset]2000 11030017 Upper Walnut Riverestablished
1523550 KSButler[No specific locality provided in original dataset]2009 11030017 Upper Walnut Riverestablished
1421728 KSButlerBig Sandy Creek2003 11030017 Upper Walnut Riverestablished
1421821 KSButlerno locality provided2000 11030017 Upper Walnut Riverestablished
1421893 KSButlerno locality provided2009 11030017 Upper Walnut Riverestablished
1421619 KSButlerWalnut R., Walnut River at US 54, near [E] edge of El Dorado2002 11030017 Upper Walnut Riverestablished

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