Ruisseau· 3 segments
Duwenbeek
Crosses 1 administrative regions : Vorpommern-Rügen
Total length
19km
Max discharge
0,8m³/s
Max Strahler
2
Segments matched
3
River geography1 admin regions · 0 communes
1 administrative regions crossed (GADM L2)
- Vorpommern-RügenMecklenburg-Vorpommern · Germany21.3 kmin this dpt
8 intersecting protected areas
Vorpommersche Boddenlandschaft und nördlicher Strelasund
IUCN Not ReportedSpecial Protection Area (Birds Directive)
Vorpommersche Boddenlandshaft National Park (West-Pommeranian Lagoon National Park)
IUCN Not ReportedBaltic Sea Protected Area (HELCOM)
National Park
Ostrügen
IUCN VLandscape Protection Area
Wetland of International Importance (Ramsar Site)
Westrügensche Boddenlandschaft mit Hiddensee
IUCN Not ReportedSpecial Areas of Conservation (Habitats Directive)
Binnenbodden von Rügen
IUCN Not ReportedSpecial Protection Area (Birds Directive)
West-Rügen
IUCN VLandscape Protection Area
1 page = 1 named river (aggregation of 3 HydroRIVERS v10 segments). Spatial join cached after first hit.
Species present
856 distinct species · 4 400 observations
Source: GBIF Occurrence snapshot 2026-05-01.
Ecological tissue
Sample of 22 species (selected proportionally per kingdom among those with at least one documented interaction here) to keep the graph readable. Hover for details, click to explore the full ecosystem of a species.
ℹ️ The territory contains many more species than displayed and all their documented interactions: the graph is intentionally the structural skeleton (top-N species by composite local score, edges filtered by Serrano 2009 disparity filter α=0.2).
Indicateurs du tissu écologique
Tissu écologique de Duwenbeek : 16 espèces reliées par 52 interactions GloBI sur 4 types (connectance 22.5%, filtre Serrano α=0.2). 6 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).
Comparaison sur la connectance du réseau local complet vs distribution nationale (toutes les communes françaises).
Hydrology (HydroRIVERS v10)
Total length
19km
Max discharge
0,8m³/s
Max Strahler
2
Segments matched
3
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.