Intro:
Stems:
Leaves:
Inforescence:
Flowers:
Fruits:
Comments:
Height:
plant sale text:
bloom table text:
description:
stems:
leaves:
inflorescence:
flowers:
fruits:
comments:
cultural notes:
germination code:
native range:
https://fsus.ncbg.unc.edu/main.php?pg=show-taxon-detail.php&lsid=urn:lsid:ncbg.unc.edu:taxon:{503F950A-5263-4B13-9B14-6B9EDCF8C5F0}
*Dipsacus sativus (Linnaeus) Honckeny. Fuller's Teasel. Phen: Jul-Sep; Sep-Oct. Hab: Disturbed areas. Dist: Native of Europe.
Origin/Endemic status: Europe
Taxonomy Comments: We here follow Ferguson (1965), Ferguson & Brizicky (1965), and Stace (2021) in their determination that D. sativus is the correct name to apply to this plant.
Other Comments: The dried inflorescences were used in the past for fulling cloth (raising the nap).
Synonymy ⓘ: = GBI4, K1, K4, NY, Pa, Ferguson (1965), Stace (2021); = Dipsacus fullonum L. – C, F, G, misapplied; = Dipsacus fullonum L. ssp. sativus (L.) Thell.; < Dipsacus fullonum L. – GrPl
Wetland Indicator Status:
- Atlantic and Gulf Coastal Plain: FACU (taxonomic split from wetland indicator species)
- Eastern Mountains and Piedmont: FACU (taxonomic split from wetland indicator species)
- Great Plains: FACU (taxonomic split from wetland indicator species)
- Midwest: FACU (taxonomic split from wetland indicator species)
- Northcentral & Northeast: FACU (taxonomic split from wetland indicator species)
Heliophily ⓘ: 9
Hover over a shape, letter, icon, or arrow on the map for definition or see the legend.
© Dan Killam, some rights reserved (CC BY), uploaded by Dan Killam source CC-BY | Original Image ⭷
© Cricket Raspet, some rights reserved (CC BY), uploaded by Cricket Raspet source CC-BY | Original Image ⭷
© Avilez, some rights reserved (CC BY), uploaded by Avilez source CC-BY | Original Image ⭷
© Dutza K., some rights reserved (CC BY), uploaded by Dutza K. source CC-BY | Original Image ⭷Feedback
See something wrong or missing on about Dipsacus sativus? Let us know here: (Please include your name and email if at all complicated so we can clarify if needed.) We greatly appreciate feedback, and will include updates from you in our next webapp update, which can take a few months.