Specimen Information

Astyanax mexicanus
Astyanax mexicanus
(Mexican Tetra)
Fishes
Native Transplant

Specimen ID261199
GroupFishes
GenusAstyanax
Speciesmexicanus
Common NameMexican Tetra
StateTX
CountyBexar
LocalitySan Antonio River near Brackenridge Park and the San Antonio Zoo
Mapping AccuracyAccurate
HUC8 NameUpper San Antonio
HUC8 Number12100301
HUC10 NameHeadwaters San Antonio River
HUC10 Number1210030102
HUC12 NameOlmos Creek-San Antonio River
HUC12 Number121003010201
Map
+
Collection Year1990
Year AccuracyActual
Potential Pathwayunknown
Statusestablished
Reference 1
Ref. Number:13013
Author:Edwards, R.J.
Date:2001
Title:New additions and persistence of the introduced fishes of the Upper San Antonio River, Bexar County, Texas.
Journal:Texas Journal of Science
Volume:53
Issue:1
Pages:3-12
Reference 2
Ref. Number:10256
Author:Howells, R.G.
Date:1992
Title:Annotated List of Introduced Non-native Fishes, Mollusks, Crustaceans and Aquatic Plants in Texas Waters.
Publisher:Texas Parks and Wildlife Department, Fisheries and Wildlife Division, Inland Fisheries Branch
Pages:19 p.
Reference 3
Ref. Number:360
Author:Howells, R.G.
Date:1992
Title:Annotated list of non-native fishes, mollusks, crustaceans, and aquatic plants, in Texas waters. Management Data Series No. 78.
Publisher:Texas Parks and Wildlife Department
Pages:19 p.
Comments1985-1990
Record TypeLiterature
Freshwater/MarineFreshwater


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/21/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.