Prosopium williamsoni
Prosopium williamsoni
(Mountain Whitefish)
Fishes
Native Transplant

6 results for Prosopium williamsoni (Mountain Whitefish)
Download Data
Click here for listing in all states

Specimen IDStateCountyLocalityYear HUC Number What's this? Drainage nameStatus
30367 CO upper Colorado River in CO1960 14010001 Colorado Headwatersestablished
30368 CO upper Colorado River in CO1960 14010001 Colorado Headwatersestablished
1428200 COEagleColorado River2009 14010001 Colorado Headwatersunknown
282664 COEagleColorado River [upstream of Burns, CO].2002 14010001 Colorado Headwatersestablished
282665 COEagleColorado River [upstream of Colorado River Rd., between McCoy and Burns, CO].2002 14010001 Colorado Headwatersestablished
1428202 COGrandColorado River near Sheephorn Creek2009 14010001 Colorado Headwatersunknown

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 [5/10/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.