Ruisseau
Pisselet
Crosses 2 administrative regions : Brabant Wallon, Vlaams Brabant
Total length
2km
Max discharge
0,3m³/s
Max Strahler
1
Segments matched
1
River geography2 admin regions · 0 communes
2 administrative regions crossed (GADM L2)
- Brabant WallonWallonie · Belgium6.2 kmin this dpt
- Vlaams BrabantVlaanderen · Belgium0.0 kmin this dpt
6 intersecting protected areas
Special Areas of Conservation (Habitats Directive)
De Dijlevallei
IUCN Not AssignedFlemish Ecological Network (Flemish Region)
De Dijlevallei
IUCN Not ReportedSpecial Protection Area (Birds Directive)
Vallée de la Dyle de Wavre à Archennes
IUCN Not ReportedSpecial Protection Area (Birds Directive)
Vallée de la Dyle de Wavre à Archennes
IUCN Not ReportedSpecial Areas of Conservation (Habitats Directive)
NBP-VB-18-0038
IUCN VINature management plan type 2 (Flemish Region)
1 page = 1 named river (aggregation of 1 HydroRIVERS v10 segment). Spatial join cached after first hit.
Species present
1 554 distinct species · 14 065 observations
Source: GBIF Occurrence snapshot 2026-05-01.
Ecological tissue
Sample of 46 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 Pisselet : 38 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 111 interactions GloBI sur 5 types (connectance 10.7%, filtre Serrano α=0.2). 8 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
2km
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.