Colossoma or Piaractus sp.
Colossoma or Piaractus sp.
(unidentified pacu)

7 results for Colossoma or Piaractus sp. (unidentified pacu)
Download Data

Specimen IDStateCountyLocalityYear HUC Number What's this? Drainage nameStatus
269192 AKAnchorageCampbell Creek, Anchorage2002 19020401 Anchoragefailed
159931 IAJaspera small pond in the Jacob Krumm Nature Preserve2002 07080106 North Skunkfailed
269224 INSt. JosephSt. Joseph River2002 04050001 St. Josephfailed
269219 INWhiteLake Shafer [just N of Monticello, IN]2002 05120106 Tippecanoefailed
565073 NCWakeSmall impoundment, tributary to Beaver Creek, S of Haddon Hall Road, 0.85 air miles SE junction US 64 & NC 55, 1.2 air miles NW center of Apex2002 03030002 Hawfailed
156930 WAThurstonLong Lake2002 17110019 Puget Soundfailed
166823 WIWalworthPickerel Lake2002 07120006 Upper Foxfailed

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 [6/29/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.