Ruisseau
Kievitsloop
Crosses 3 administrative regions : Nederweert, Someren, Weert
Total length
3km
Max discharge
0,8m³/s
Max Strahler
1
Segments matched
1
River geography3 admin regions · 0 communes
3 administrative regions crossed (GADM L2)
- NederweertLimburg · Netherlands7.6 kmin this dpt
- SomerenNoord-Brabant · Netherlands3.1 kmin this dpt
- WeertLimburg · Netherlands2.0 kmin this dpt
5 intersecting protected areas
NNN-NB
IUCN Not AssignedNature Reserves owned by professional nature management organizations
NNN-LI
IUCN Not AssignedNature Reserves owned by professional nature management organizations
Nature Conservation Act
Weerter- en Budelerbergen & Ringselven
IUCN Not ReportedSpecial Protection Area (Birds Directive)
Weerter- en Budelerbergen & Ringselven
IUCN Not ReportedSpecial Areas of Conservation (Habitats Directive)
1 page = 1 named river (aggregation of 1 HydroRIVERS v10 segment). Spatial join cached after first hit.
Species present
2 508 distinct species · 210 944 observations
Source: GBIF Occurrence snapshot 2026-05-01.
Ecological tissue
Sample of 28 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 Kievitsloop : 21 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 41 interactions GloBI sur 3 types (connectance 10.8%, filtre Serrano α=0.2). 7 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
3km
Max discharge
0,8m³/s
Max Strahler
1
Segments matched
1
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.