Catostomus catostomus
Catostomus catostomus
(Longnose Sucker)
Native Transplant

8 results for Catostomus catostomus (Longnose Sucker)
Download Data

Specimen IDStateCountyLocalityYear HUC Number What's this? Drainage nameStatus
157567 COBentBent's Old Fort National Historic Site1999 11020009 Upper Arkansas-John Martin Reservoirestablished
281083 COFremontArkansas River at Parkdale.1959 11020001 Arkansas Headwatersestablished
281081 COFremontArkansas River, at Florence (near Cañon City).1959 11020002 Upper Arkansasestablished
281082 COFremontArkansas River, at Florence (near Cañon City).1960 11020002 Upper Arkansasestablished
269138 COLakeMt. Elbert Forebay Reservoir2009 11020001 Arkansas Headwatersestablished
269241 COLakeTurquoise Lake2009 11020001 Arkansas Headwatersestablished
269246 COLakeTwin Lakes Reservoir2009 11020001 Arkansas Headwatersestablished
30985 CT Housatonic River drainage, a tributary above the fall line1992 01100005 Housatonicestablished

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

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.