Pylodictis olivaris
Pylodictis olivaris
(Flathead Catfish)
Fishes
Native Transplant
Collection Info
Point Map
Species Profile
Animated Map

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

Page:12
Specimen IDStateCountyLocalityYear HUC Number What's this? Drainage nameStatus
1523328 KSReno[No specific locality provided in original dataset]1999 11030014 North Fork Ninnescahestablished
1523451 KSReno[No specific locality provided in original dataset]2002 11030014 North Fork Ninnescahestablished
1523574 KSReno[No specific locality provided in original dataset]2002 11030014 North Fork Ninnescahestablished
1523575 KSReno[No specific locality provided in original dataset]2002 11030014 North Fork Ninnescahestablished
1523697 KSReno[No specific locality provided in original dataset]2002 11030014 North Fork Ninnescahestablished
1523698 KSReno[No specific locality provided in original dataset]2002 11030014 North Fork Ninnescahestablished
1523327 KSReno[No specific locality provided in original dataset]2003 11030014 North Fork Ninnescahestablished
1523427 KSReno[No specific locality provided in original dataset]2008 11030014 North Fork Ninnescahestablished
1421748 KSRenoArkansas River, North Fork Ninnescah River2002 11030014 North Fork Ninnescahestablished
1421622 KSRenoArkansas River, North Fork Ninnescah River2002 11030014 North Fork Ninnescahestablished
1421903 KSRenono locality provided1999 11030014 North Fork Ninnescahestablished
1421941 KSRenono locality provided2002 11030014 North Fork Ninnescahestablished
1421837 KSRenono locality provided2002 11030014 North Fork Ninnescahestablished
1421838 KSRenono locality provided2002 11030014 North Fork Ninnescahestablished
1421993 KSRenono locality provided2002 11030014 North Fork Ninnescahestablished
1421994 KSRenono locality provided2002 11030014 North Fork Ninnescahestablished
1421902 KSRenono locality provided2003 11030014 North Fork Ninnescahestablished
1421868 KSRenono locality provided2008 11030014 North Fork Ninnescahestablished
1523329 KSSedgwick[No specific locality provided in original dataset]2001 11030014 North Fork Ninnescahestablished
1523452 KSSedgwick[No specific locality provided in original dataset]2002 11030014 North Fork Ninnescahestablished
1523589 KSSedgwick[No specific locality provided in original dataset]2007 11030014 North Fork Ninnescahestablished
1523712 KSSedgwick[No specific locality provided in original dataset]2007 11030014 North Fork Ninnescahestablished
1523426 KSSedgwick[No specific locality provided in original dataset]2009 11030014 North Fork Ninnescahestablished
1421759 KSSedgwickArkansas River, North Fork Ninnescah River2002 11030014 North Fork Ninnescahestablished
1421717 KSSedgwickArkansas River, North Fork Ninnescah River2002 11030014 North Fork Ninnescahestablished
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 [4/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.