Ruisseau
Kraaiwinkelbeek
Crosses 1 administrative regions : Vlaams Brabant
Total length
1km
Max discharge
0,3m³/s
Max Strahler
1
Segments matched
1
River geography1 admin regions · 0 communes
1 administrative regions crossed (GADM L2)
- Vlaams BrabantVlaanderen · Belgium2.3 kmin this dpt
7 intersecting protected areas
Valleien van de Winge en de Motte met valleihellingen
IUCN Not ReportedSpecial Areas of Conservation (Habitats Directive)
De Wingevallei
IUCN Not AssignedFlemish Ecological Network (Flemish Region)
NBP-VB-21-0022 type 4
IUCN IVNature management plan type 4 (Flemish Region)
NBP-VB-21-0210 type 2
IUCN VINature management plan type 2 (Flemish Region)
NBP-VB-22-0178 type 2
IUCN VINature management plan type 2 (Flemish Region)
De Spicht
IUCN IVNature management plan type 4 (Flemish Region)
NBP-VB-21-0323 type 4
IUCN IVNature management plan type 4 (Flemish Region)
1 page = 1 named river (aggregation of 1 HydroRIVERS v10 segment). Spatial join cached after first hit.
Species present
2 337 distinct species · 84 615 observations
Source: GBIF Occurrence snapshot 2026-05-01.
Ecological tissue
Sample of 44 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 Kraaiwinkelbeek : 34 espèces reliées par 117 interactions GloBI sur 4 types (connectance 12.4%, filtre Serrano α=0.2). 10 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
1km
Max discharge
0,3m³/s
Max Strahler
1
Segments matched
1
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.