Empetrichthys latos latos
(Pahrump Poolfish)
Fishes
Native Transplant

6 results for Empetrichthys latos latos (Pahrump Poolfish)
Download Data
Click here for listing in all states

Specimen IDStateCountyLocalityYear HUC Number What's this? Drainage nameStatus
39296 NVClarkCorn Creek Springs Pond, approximatly 25 miles nw of Las Vegas1972 15010015 Las Vegas Washestablished
39292 NVClarkisolated spring in southern Nevada1970  unknown
39294 NVClarkLatos pools west of Lake Mohave1972 15030101 Havasu-Mohave Lakesestablished
39295 NVClarkLatos pools west of Lake Mohave1976 15030101 Havasu-Mohave Lakesestablished
39293 NVClarkSpring Valley, Clark County, in nonnative springs1972 15010015 Las Vegas Washestablished
39297 NVWhite PineShoshone Ponds, near Ely, Spring Valley1972 16060008 Spring-Steptoe Valleysestablished

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.