Ontologia

Ruisseau

Eidarengbekken

Crosses 2 administrative regions : Askim, Eidsberg

ruisseau

Total length

4km

Max discharge

0,4m³/s

Max Strahler

1

Segments matched

1

River geography2 admin regions · 0 communes

Parent watershed

hybas-2080240520239 km²

2 administrative regions crossed (GADM L2)

  • Eidsberg
    Ãstfold · Norway
    5.0 km
    in this dpt
  • Askim
    Ãstfold · Norway
    1.0 km
    in this dpt

4 intersecting protected areas

  • Berg

    IUCN Ia

    Nature Reserve

  • Berg

    IUCN Not Reported

    Emerald Network

  • Sletner

    IUCN Ia

    Nature Reserve

  • Slitu

    IUCN Ia

    Nature Reserve

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

Species present

1 661 distinct species · 9 015 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 31 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 Eidarengbekken : 20 espèces reliées par 108 interactions GloBI sur 5 types (connectance 21.8%, filtre Serrano α=0.2). 12 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
32
Interactions affichées
108
Connectance
0.218
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

4km

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.