Rivière
Rathenower Stremme
⚠ Partial coverage : only 1 named segment matched so far. The real rivière extends much further (Strahler order 5 indicates a major river). Cross-source ingest in progress — values below reflect only the matched segment.
Crosses 1 administrative regions : Havelland
Max discharge
71,7m³/s
Max Strahler
5
Segments matched
1
River geography1 admin regions · 0 communes
1 administrative regions crossed (GADM L2)
- HavellandBrandenburg · Germany3.9 kmin this dpt
5 intersecting protected areas
Westhavelland
IUCN VLandscape Protection Area
Niederung der Unteren Havel
IUCN Not ReportedSpecial Protection Area (Birds Directive)
Wetland of International Importance (Ramsar Site)
Niederung der Unteren Havel/Gülper See
IUCN Not ReportedSpecial Areas of Conservation (Habitats Directive)
Untere Havel Nord
IUCN IVNature Reserve
1 page = 1 named river (aggregation of 1 HydroRIVERS v10 segment). Spatial join cached after first hit.
Species present
779 distinct species · 3 390 observations
Source: GBIF Occurrence snapshot 2026-05-01.
Ecological tissue
Sample of 38 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 Rathenower Stremme : 32 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 102 interactions GloBI sur 4 types (connectance 14.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)
Matched len.
4,3km
Max discharge
71,7m³/s
Max Strahler
5
Segments matched
1
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.