Specimen Information

Gambusia affinis
Gambusia affinis
(Western Mosquitofish)
Fishes
Native Transplant

Specimen ID160064
GroupFishes
GenusGambusia
Speciesaffinis
Common NameWestern Mosquitofish
StateNE
Localitystate non-specific
Mapping AccuracyCentroid
Centroid TypeState
HUC8 NameMissouri Region
HUC8 Number10000000
Map
+
Collection Month5
Collection Year2004
Year AccuracyPublication Year
Potential Pathwaystocked for biocontrol
Statusestablished
Reference 1
Ref. Number:14005
Author:Stephen, B.J.
Date:2004
Title:The mosquitofish problem.
Journal:Nebraska Land
Volume:82
Issue:4
Pages:36-37
Reference 2
Ref. Number:1411
Author:Lynch, J.D.
Date:1988
Title:Introduction, establishment, and dispersal of western mosquitofish in Nebraska (Actinopterygii:Poeciliidae).
Journal:Prarie Naturalist
Volume:20
Issue:4
Pages:203-216
Reference 3
Ref. Number:128
Author:Rees, D.M.
Date:1934
Title:Notes on mosquito fish in Utah, Gambusia affinis (Baird and Girard).
Journal:Copeia
Volume:1945
Issue:4
Pages:236
Commentswidely introduced. Lynch 1988 reports stock for original introductions of western mosquitofish, Gambusia affinis, in Nebraska were obtained from Provo, UT; which are descendent's of G. affinis from Shelby County, TN.
Record TypeLiterature
Freshwater/MarineFreshwater
Specimen ImpactAggressive fish, prey on fish eggs and smaller fish. Implicated in the decline of several fish in the American West.


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