Ruisseau
Vekeloop
Crosses 1 administrative regions : Antwerpen
Total length
2km
Max discharge
0,2m³/s
Max Strahler
1
Segments matched
1
River geography1 admin regions · 0 communes
1 administrative regions crossed (GADM L2)
- AntwerpenVlaanderen · Belgium3.6 kmin this dpt
7 intersecting protected areas
Schelde- en Durmeëstuarium van de Nederlandse grens tot Gent
IUCN Not ReportedSpecial Areas of Conservation (Habitats Directive)
De samenvloeiing Rupel-Dijle-Nete
IUCN Not AssignedFlemish Ecological Network (Flemish Region)
Extended forest management plan (Flemish Region)
NBP-AN-20-0192 type 4
IUCN IVNature management plan type 4 (Flemish Region)
NBP-AN-18-0032 type 4
IUCN IVNature management plan type 4 (Flemish Region)
GIBP-AN-14-0033 type 4
IUCN IVNature management plan type 4 (Flemish Region)
NBP-AN-22-0257 type 2
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
3 450 distinct species · 483 557 observations
Source: GBIF Occurrence snapshot 2026-05-01.
Ecological tissue
Sample of 43 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 Vekeloop : 35 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 96 interactions GloBI sur 6 types (connectance 10.6%, 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,2m³/s
Max Strahler
1
Segments matched
1
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.