Ambloplites rupestris
Ambloplites rupestris
(Rock Bass)
Fishes
Native Transplant

8 results for Ambloplites rupestris (Rock Bass)
Download Data

Specimen IDStateCountyLocalityYear HUC Number What's this? Drainage nameStatus
1677603 CTHartford[No locality description provided]2016 01080205 Outlet Connecticut River 
1671800 DENew Castle[No locality description provided]2016 02040205 Brandywine-Christina 
1331596 NCSurryMitchell River, at SR 13302016 03040101 Upper Yadkinestablished
1331597 NCWataugaLaurel Creek, at SR 15082016 03040101 Upper Yadkinestablished
1331598 NCWilkesMiddle Prong Roaring River, at SR 10022016 03040101 Upper Yadkinestablished
1321790 SDPenningtonDeerfield Lake, Black Hills National Forest2016 10120110 Rapidestablished
1320646 WAKingLake Washington2016 17110012 Lake Washingtonestablished
1320647 WAKingLake Washington Ship Canal2016 17110012 Lake Washingtonestablished

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. [2026]. Nonindigenous Aquatic Species Database. Gainesville, Florida. Accessed [2/22/2026].

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.