Ruisseau
Ophasseltbeek
Crosses 1 administrative regions : Oost-Vlaanderen
Total length
10km
Max discharge
0,3m³/s
Max Strahler
1
Segments matched
1
River geography1 admin regions · 0 communes
1 administrative regions crossed (GADM L2)
- Oost-VlaanderenVlaanderen · Belgium4.2 kmin this dpt
6 intersecting protected areas
Bossen van de Vlaamse Ardennen en andere Zuidvlaamse bossen
IUCN Not ReportedSpecial Areas of Conservation (Habitats Directive)
Het Hasselt-, Parkbos en Uilenbroek
IUCN Not AssignedFlemish Ecological Network (Flemish Region)
Moenebroek
IUCN IVNature management plan type 4 (Flemish Region)
De Vallei van de Moenebroekbeek
IUCN Not AssignedFlemish Ecological Network (Flemish Region)
NBP-OV-22-0302 type 4
IUCN IVNature management plan type 4 (Flemish Region)
NBP-OV-23-0106 type 3
IUCN IVNature management plan type 3 (Flemish Region)
1 page = 1 named river (aggregation of 1 HydroRIVERS v10 segment). Spatial join cached after first hit.
Species present
2 224 distinct species · 42 858 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 Ophasseltbeek : 29 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 101 interactions GloBI sur 6 types (connectance 13.6%, 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
10km
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.