Ruisseau
Rethse Loop
Crosses 4 administrative regions : Alphen-Chaam, Antwerpen, Baarle-Nassau, Goirle
Total length
5km
Max discharge
0,4m³/s
Max Strahler
1
Segments matched
1
River geography4 admin regions · 0 communes
4 administrative regions crossed (GADM L2)
- Baarle-NassauNoord-Brabant · Netherlands3.5 kmin this dpt
- AntwerpenVlaanderen · Belgium2.6 kmin this dpt
- Alphen-ChaamNoord-Brabant · Netherlands1.0 kmin this dpt
- GoirleNoord-Brabant · Netherlands0.0 kmin this dpt
4 intersecting protected areas
NNN-NB
IUCN Not AssignedNature Reserves owned by professional nature management organizations
Arendonk, Merksplas, Oud-Turnhout, Ravels en Turnhout
IUCN Not ReportedSpecial Protection Area (Birds Directive)
NBP-AN-19-0143 type 2
IUCN VINature management plan type 2 (Flemish Region)
NBP-AN-21-0001 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
2 878 distinct species · 48 708 observations
Source: GBIF Occurrence snapshot 2026-05-01.
Ecological tissue
Sample of 36 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 Rethse Loop : 26 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 77 interactions GloBI sur 5 types (connectance 11.0%, filtre Serrano α=0.2). 12 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
5km
Max discharge
0,4m³/s
Max Strahler
1
Segments matched
1
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.