Cyprinodon eremus
Cyprinodon eremus
(Sonoyta Pupfish)
Fishes
Native Transplant
Collection Info
Point Map
Species Profile
Animated Map

6 results for Cyprinodon eremus (Sonoyta Pupfish)
Download Data
Click here for listing in all states

Specimen IDStateCountyLocalityYear HUC Number What's this? Drainage nameStatus
27849 AZPimaUniversity of Arizona, Tucson, Pima County, AZ1977 15050301 Upper Santa Cruzextirpated
27846 AZPimaUniversity of Arizona, Tucson, Pima County, AZ1993 15050301 Upper Santa Cruzextirpated
27791 AZSanta CruzBog Hole, Santa Cruz County, AZ; artificial (earthen) impoundment1977 15050301 Upper Santa Cruzstocked
27848 AZSanta CruzBog Hole, Santa Cruz County, AZ; artificial (earthen) impoundment1977 15050301 Upper Santa Cruzestablished
27853 AZSanta CruzKino Spring, Santa Cruz County, AZ1983 15050301 Upper Santa Cruzextirpated
27852 AZSanta CruzKino Spring, Santa Cruz County, AZ1993 15050301 Upper Santa Cruzextirpated

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 [11/28/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.