Rhinogobius brunneus
Rhinogobius brunneus
(Amur goby)
Fishes
Exotic
Collection Info
Point Map
Species Profile
Animated Map

5 results for Rhinogobius brunneus (Amur goby)
Download Data

Specimen IDStateCountyLocalityYear HUC Number What's this? Drainage nameStatus
785921 ORMultnomahColumbia Slough2014 17090012 Lower Willametteestablished
238456 ORMultnomahRamsey Wetland [=Ramsey Lake] in Portland [near the mouth of the Willamette River]2007 17090012 Lower Willametteestablished
785920 ORMultnomahWillamette River, along east bank just upstream from the Ross Island Sand and Gravel Co. boat ramp2015 17090012 Lower Willametteestablished
886066 ORMultnomahWillamette River, east bank downstream of Ross Island2015 17090012 Lower Willametteestablished
886065 ORMultnomahWillamette River, near Riverdale2015 17090012 Lower Willametteestablished

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.