Lythrum salicaria
Lythrum salicaria
(purple loosestrife)

10 results for Lythrum salicaria (purple loosestrife)
Download Data
Click here for listing in all states

Specimen IDStateCountyLocalityYear HUC Number What's this? Drainage nameStatus
1683113 MNBecker[no locality description provided]2016 09020106 Buffalounknown
1683114 MNBecker[no locality description provided]2016 09020106 Buffalounknown
1686768 MNBeckerBoardson Lake1988 09020106 Buffalounknown
1686762 MNBeckerCallaway1988 09020106 Buffalounknown
1686764 MNBeckerCallaway1997 09020106 Buffalounknown
1686781 MNBeckerLabelle Lake1988 09020106 Buffalounknown
1684313 MNBeckerLake Park1987 09020106 Buffalounknown
1686780 MNBeckerLake Park1988 09020106 Buffalounknown
1686760 MNBeckerRichwood Twp1987 09020106 Buffalounknown
1686503 MNClayGlyndon1988 09020106 Buffalounknown

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.


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. [2022]. Nonindigenous Aquatic Species Database. Gainesville, Florida. Accessed [5/19/2022].

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.