Dorosoma petenense
Dorosoma petenense
(Threadfin Shad)
Fishes
Native Transplant
Collection Info
Point Map
Species Profile
Animated Map

5 results for Dorosoma petenense (Threadfin Shad)
Download Data
Click here for listing in all states

Specimen IDStateCountyLocalityYear HUC Number What's this? Drainage nameStatus
1334305 OKTulsa(1644) At SAND SPRinGS CITY PARK1993 11110101 Polecat-Snakeestablished
1334170 OKTulsaARKANSAS RIVER At SAND SPRinGS SEC 14 TWN 19N RNG 11EU071644001992 11110101 Polecat-Snakeestablished
1334468 OKTulsaU70165520 ARKANSAS RIVER At BIXBY2002 11110101 Polecat-Snakeestablished
1334322 OKWagonerHwy 104 near Haskell; Sec 31/T16N/R16E; U071655701993 11110101 Polecat-Snakeestablished
1334434 OKWagonerHwy 104 near Haskell; Sec 31/T16N/R16E; U071655702000 11110101 Polecat-Snakeestablished

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 [4/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.