Cryptosula pallasiana
Cryptosula pallasiana
(a bryozoan)
Bryozoans
Native Transplant
Collection Info
Point Map
Species Profile
Animated Map

7 results for Cryptosula pallasiana (a bryozoan)
Download Data
Click here for listing in all states

Specimen IDStateCountyLocalityYear HUC Number What's this? Drainage nameStatus
1727 CA San Francisco Bay1994 18050004 San Francisco Bayestablished
1726 CAAlamedaSan Francisco Bay at Berkeley Yacht Harbor [Berkeley, CA]1963 18050002 San Pablo Bayestablished
272640 CAHumboldtFields Landing Channel HB, St. 42, Humboldt Bay.2001 18010102 Mad-Redwoodestablished
272638 CAHumboldtMad River Slough Channel St. 10, Humboldt Bay.2001 18010102 Mad-Redwoodestablished
272639 CAHumboldtNorth Bay Channel HB, St. 33, Eureka Slough.2001 18010102 Mad-Redwoodestablished
1723 CAMontereyPacific Ocean, Monterey Bay1952 18060015 Monterey Bayestablished
1724 CASonomaBodega Bay1975 18050005 Tomales-Drake Baysestablished

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.

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. [2026]. Nonindigenous Aquatic Species Database. Gainesville, Florida. Accessed [1/22/2026].

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.