Ruisseau· 3 segments
Zuunbeek
Crosses 2 administrative regions : Bruxelles, Vlaams Brabant
Total length
21km
Max discharge
1,3m³/s
Max Strahler
2
Segments matched
3
River geography2 admin regions · 0 communes
2 administrative regions crossed (GADM L2)
- Vlaams BrabantVlaanderen · Belgium12.8 kmin this dpt
- BruxellesBruxelles · Belgium1.1 kmin this dpt
6 intersecting protected areas
Hallerbos en nabije boscomplexen met brongebieden en heiden
IUCN Not ReportedSpecial Areas of Conservation (Habitats Directive)
De Vallei van de Zuunbeek en zijlopen
IUCN Not AssignedFlemish Ecological Network (Flemish Region)
Nature management plan type 4 (Flemish Region)
Vogelzangbeek
IUCN Not AssignedCertified Nature Reserve (Brussels Capital Region)
NBP-VB-19-0012 type 2
IUCN VINature management plan type 2 (Flemish Region)
V-083 type 4
IUCN IVNature management plan type 4 (Flemish Region)
1 page = 1 named river (aggregation of 3 HydroRIVERS v10 segments). Spatial join cached after first hit.
Species present
3 027 distinct species · 35 659 observations
Source: GBIF Occurrence snapshot 2026-05-01.
Ecological tissue
Sample of 37 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 Zuunbeek : 23 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 125 interactions GloBI sur 5 types (connectance 17.8%, filtre Serrano α=0.2). 15 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
21km
Max discharge
1,3m³/s
Max Strahler
2
Segments matched
3
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.