Moxostoma erythrurum
Moxostoma erythrurum
(Golden Redhorse)
Native Transplant

7 results for Moxostoma erythrurum (Golden Redhorse)
Download Data

Specimen IDStateCountyLocalityYear HUC Number What's this? Drainage nameStatus
745282 MDAlleganySideling Hill Creek1998 02070003 Cacapon-Townunknown
745277 MDAlleganySideling Hill Creek, Near Cumberland, Md1998 02070003 Cacapon-Townunknown
745280 MDFrederickMonocacy River, Thurmont, Md.1998 02070009 Monocacyunknown
745272 MDFrederickPotomac River. Frederick, Md.1998 02070008 Middle Potomac-Catoctinunknown
745281 MDWashingtonHagerstown, Md1998 02070004 Conococheague-Opequonunknown
745279 MDWashingtonLicking Creek1998 02070004 Conococheague-Opequonunknown
745283 VAFauquierCarter Run1998 02080103 Rapidan-Upper Rappahannockunknown

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. [2022]. Nonindigenous Aquatic Species Database. Gainesville, Florida. Accessed [12/5/2022].

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.