Platygobio gracilis
Platygobio gracilis
(Flathead Chub)
Fishes
Native Transplant
Collection Info
Point Map
Species Profile
Animated Map

9 results for Platygobio gracilis (Flathead Chub)
Download Data

Specimen IDStateCountyLocalityYear HUC Number What's this? Drainage nameStatus
30273 CO San Luis Valley (Rio Grande headwaters drainage)1986 13010003 San Luisextirpated
35910 MN Red River drainage1997 09020000 Redestablished
1522361 MN Red River drainage2001 09020000 Redestablished
1697864 MTCusterFort Keogh pond1999 10100001 Lower Yellowstone-Sundayeradicated
1697717 MTLincolnLake Koocanusa1999 17010101 Middle Kootenaifailed
268203 ND Red River drainage1996 09020000 Redcollected
1541550 NEThayerLittle Blue River2007 10270206 Upper Little Blueunknown
38343 NM Gila River drainage1957 15040002 Upper Gila-Mangasfailed
1541551 WYLincolnMuddy Creek2010 16010102 Central Bearestablished

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