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

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

Page:123
Specimen IDStateCountyLocalityYear HUC Number What's this? Drainage nameStatus
1523324 KSKingman[No specific locality provided in original dataset]1999 11030015 South Fork Ninnescahestablished
1523570 KSKingman[No specific locality provided in original dataset]1999 11030015 South Fork Ninnescahestablished
1523449 KSKingman[No specific locality provided in original dataset]2000 11030015 South Fork Ninnescahestablished
1523326 KSKingman[No specific locality provided in original dataset]2001 11030015 South Fork Ninnescahestablished
1523696 KSKingman[No specific locality provided in original dataset]2001 11030015 South Fork Ninnescahestablished
1523447 KSKingman[No specific locality provided in original dataset]2002 11030015 South Fork Ninnescahestablished
1523450 KSKingman[No specific locality provided in original dataset]2002 11030015 South Fork Ninnescahestablished
1523325 KSKingman[No specific locality provided in original dataset]2002 11030015 South Fork Ninnescahestablished
1523694 KSKingman[No specific locality provided in original dataset]2005 11030015 South Fork Ninnescahestablished
1523695 KSKingman[No specific locality provided in original dataset]2006 11030015 South Fork Ninnescahestablished
1523531 KSKingman[No specific locality provided in original dataset]2009 11030015 South Fork Ninnescahestablished
1523284 KSKingman[No specific locality provided in original dataset]2011 11030015 South Fork Ninnescahestablished
1523654 KSKingman[No specific locality provided in original dataset]2011 11030015 South Fork Ninnescahestablished
1421702 KSKingmanArkansas River, South Fork Ninnescah River2002 11030015 South Fork Ninnescahestablished
1421685 KSKingmanArkansas River, South Fork Ninnescah River2005 11030015 South Fork Ninnescahestablished
1421989 KSKingmanno locality provided1999 11030015 South Fork Ninnescahestablished
1421899 KSKingmanno locality provided1999 11030015 South Fork Ninnescahestablished
1421939 KSKingmanno locality provided2000 11030015 South Fork Ninnescahestablished
1421836 KSKingmanno locality provided2001 11030015 South Fork Ninnescahestablished
1421901 KSKingmanno locality provided2001 11030015 South Fork Ninnescahestablished
1421924 KSKingmanno locality provided2002 11030015 South Fork Ninnescahestablished
1421900 KSKingmanno locality provided2002 11030015 South Fork Ninnescahestablished
1421940 KSKingmanno locality provided2002 11030015 South Fork Ninnescahestablished
1421834 KSKingmanno locality provided2005 11030015 South Fork Ninnescahestablished
1421835 KSKingmanno locality provided2006 11030015 South Fork Ninnescahestablished
Page:123

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/1/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.