Specimen Information

Gambusia affinis
Gambusia affinis
(Western Mosquitofish)
Fishes
Native Transplant

Specimen ID39282
GroupFishes
GenusGambusia
Speciesaffinis
Common NameWestern Mosquitofish
StateNV
CountyWhite Pine
LocalityLund Spring, northern White River Valley, on Rt 318 just south of I-6
Mapping AccuracyAccurate
HUC8 NameWhite
HUC8 Number15010011
HUC10 NameMartins Creek-White River
HUC10 Number1501001104
HUC12 NameWilson Meadows-White River
HUC12 Number150100110406
Map
+
Collection Year1991
Year AccuracyActual
Potential Pathwaystocked for biocontrol
Statuscollected
Reference 1
Ref. Number:881
Author:U.S. Fish and Wildlife Service.
Date:1994
Title:White River spinedace, Lepidomeda albivallis, recovery plan.
Publisher:U.S. Fish and Wildlife Service, Portland, OR.
Pages:45 pp
Reference 2
Ref. Number:281
Author:Miller, R.R., and J.R. Alcorn
Date:1946
Title:The introduced fishes of Nevada, with a history of their introduction.
Journal:Transactions of the American Fisheries Society
Volume:73
Pages:173-193
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
CommentsMiller and Alcorn 1946 provide evidence that original introductions in Nevada were Gambusia affinis, the western mosquitofish (stock source: Southern California, which originally came from Mississippi (Rees 1934))
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/23/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.