Ruisseau· 5 segments
Luchgraben
Crosses 2 administrative regions : Oder-Spree, Potsdam-Mittelmark
Total length
23km
Max discharge
0,2m³/s
Max Strahler
2
Segments matched
5
River geography2 admin regions · 0 communes
2 administrative regions crossed (GADM L2)
- Potsdam-MittelmarkBrandenburg · Germany11.8 kmin this dpt
- Oder-SpreeBrandenburg · Germany7.7 kmin this dpt
8 intersecting protected areas
Schwielochsee
IUCN VLandscape Protection Area
Landscape Protection Area
Hackenheide
IUCN Not ReportedSpecial Areas of Conservation (Habitats Directive)
Lehniner Mittelheide und Quellgebiet der Emster
IUCN Not ReportedSpecial Areas of Conservation (Habitats Directive)
Nature Reserve
Spreewiesen südlich Beeskow
IUCN IVNature Reserve
Spreewiesen südlich Beeskow
IUCN Not ReportedSpecial Areas of Conservation (Habitats Directive)
Kolpinsee und Mückenfenn
IUCN Not ReportedSpecial Areas of Conservation (Habitats Directive)
1 page = 1 named river (aggregation of 5 HydroRIVERS v10 segments). Spatial join cached after first hit.
Species present
1 318 distinct species · 6 941 observations
Source: GBIF Occurrence snapshot 2026-05-01.
Ecological tissue
Sample of 39 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 Luchgraben : 31 espèces reliées par 74 interactions GloBI sur 5 types (connectance 9.5%, filtre Serrano α=0.2). 9 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
23km
Max discharge
0,2m³/s
Max Strahler
2
Segments matched
5
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.