Potamogeton crispus
Potamogeton crispus
(curly-leaf pondweed)

7 results for Potamogeton crispus (curly-leaf pondweed)
Download Data
Click here for listing in all states

Specimen IDStateCountyLocalityYear HUC Number What's this? Drainage nameStatus
272759 WI Lake Superior, nearshore2010 04180000 Lake Superiorestablished
1425454 WIAshlandChequamegon Bay2011 04180000 Lake Superiorestablished
625244 WIAshlandLake Superior, Chequamegon Bay at Ashland2011 04180000 Lake Superiorestablished
625245 WIAshlandLake Superior, Chequamegon Bay at Ashland2012 04180000 Lake Superiorestablished
1337396 WIBayfieldWashburn Harbor, Chequamegon Bay, Lake Superior1996 04180000 Lake Superiorestablished
253039 WIDouglasSaint Louis River2008 04180000 Lake Superiorestablished
253040 WIDouglasSuperior Bay, Lake Superior2006 04180000 Lake Superiorestablished

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. [2023]. Nonindigenous Aquatic Species Database. Gainesville, Florida. Accessed [3/26/2023].

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.