Ontologia

Rivière· 2 segments

Leybeek

Crosses 3 administrative regions : Antwerpen, Bruxelles, Vlaams Brabant

rivière

Total length

8km

Max discharge

9,5m³/s

Max Strahler

4

Segments matched

2

River geography3 admin regions · 0 communes

Parent watershed

hybas-2080403000372 km²

3 administrative regions crossed (GADM L2)

  • Antwerpen
    Vlaanderen · Belgium
    5.0 km
    in this dpt
  • Bruxelles
    Bruxelles · Belgium
    0.9 km
    in this dpt
  • Vlaams Brabant
    Vlaanderen · Belgium
    0.4 km
    in this dpt

7 intersecting protected areas

1 page = 1 named river (aggregation of 2 HydroRIVERS v10 segments). Spatial join cached after first hit.

Species present

2 536 distinct species · 59 519 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 38 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).

RègnesAnimalPlanteChampignonBacterie
RelationsPredationParasitismeSymbiosePollinisation
StatutEn dangerVulnérableProtégéeEndémique

Indicateurs du tissu écologique

Tissu écologique de Leybeek : 28 espèces dont 2 patrimoniales (LR IUCN CR/EN/VU) reliées par 133 interactions GloBI sur 5 types (connectance 18.9%, filtre Serrano α=0.2). 10 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
38
Interactions affichées
133
Connectance
0.189
Patrimoniales
2
Plus dense que (national)0 %(top 100%)

Comparaison sur la connectance du réseau local complet vs distribution nationale (toutes les communes françaises).

Hydrology (HydroRIVERS v10)

Total length

8km

Max discharge

9,5m³/s

Max Strahler

4

Segments matched

2

HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.