Ontologia

Ruisseau

Lutterbeek

Crosses 2 administrative regions : Grafschaft Bentheim, Losser

ruisseau

Total length

5km

Max discharge

0,1m³/s

Max Strahler

1

Segments matched

1

River geography2 admin regions · 0 communes

Parent watershed

hybas-20803614601606 km²

2 administrative regions crossed (GADM L2)

3 intersecting protected areas

  • NNN-OV

    IUCN Not Assigned

    Nature Reserves owned by professional nature management organizations

  • Dinkelland

    IUCN IV

    Nature Conservation Act

  • Dinkelland

    IUCN Not Reported

    Special Areas of Conservation (Habitats Directive)

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

Species present

4 290 distinct species · 95 539 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 30 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 Lutterbeek : 20 espèces reliées par 103 interactions GloBI sur 6 types (connectance 22.2%, filtre Serrano α=0.2). 11 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
31
Interactions affichées
103
Connectance
0.222
Patrimoniales
0
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

5km

Max discharge

0,1m³/s

Max Strahler

1

Segments matched

1

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