Pimephales notatus
Pimephales notatus
(Bluntnose Minnow)
Fishes
Native Transplant

5 results for Pimephales notatus (Bluntnose Minnow)
Download Data

Specimen IDStateCountyLocalityYear HUC Number What's this? Drainage nameStatus
749831 VAShenandoahPassage Creek [Duncan et al. 2011 sampling site FM3]2007 02070006 North Fork Shenandoahestablished
749832 VAShenandoahPassage Creek [Duncan et al. 2011 sampling site FM5]2007 02070006 North Fork Shenandoahestablished
749833 VAShenandoahPassage Creek [Duncan et al. 2011 sampling site FM6]2007 02070006 North Fork Shenandoahestablished
749834 VAShenandoahPassage Creek [Duncan et al. 2011 sampling site FM7]2007 02070006 North Fork Shenandoahestablished
749830 VAWarrenPassage Creek near mouth [Duncan et al. 2011 sampling site FM1]2007 02070006 North Fork Shenandoahestablished

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