Ruisseau· 2 segments
Kromme Rijn
Crosses 4 administrative regions : Bunnik, Houten, Wijk bij Duurstede, Zeist
Total length
28km
Max discharge
0,3m³/s
Max Strahler
1
Segments matched
2
River geography4 admin regions · 0 communes
4 administrative regions crossed (GADM L2)
- Wijk bij DuurstedeUtrecht · Netherlands5.1 kmin this dpt
- BunnikUtrecht · Netherlands3.5 kmin this dpt
- ZeistUtrecht · Netherlands0.3 kmin this dpt
- HoutenUtrecht · Netherlands0.0 kmin this dpt
5 intersecting protected areas
NNN-UT
IUCN Not AssignedNature Reserves owned by professional nature management organizations
Rijntakken
IUCN IVNature Conservation Act
Rijntakken
IUCN Not ReportedSpecial Protection Area (Birds Directive)
Kolland & Overlangbroek
IUCN IVNature Conservation Act
Kolland & Overlangbroek
IUCN Not ReportedSpecial Areas of Conservation (Habitats Directive)
1 page = 1 named river (aggregation of 2 HydroRIVERS v10 segments). Spatial join cached after first hit.
Species present
4 132 distinct species · 95 817 observations
Source: GBIF Occurrence snapshot 2026-05-01.
Ecological tissue
Sample of 37 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 Kromme Rijn : 28 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 123 interactions GloBI sur 5 types (connectance 17.5%, 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
28km
Max discharge
0,3m³/s
Max Strahler
1
Segments matched
2
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.