Ontologia

Ruisseau· 8 segments

Åmose Å

Crosses 4 administrative regions : Holbæk, Kalundborg, Ringsted, Sorø

ruisseau

Total length

41km

Max discharge

3,1m³/s

Max Strahler

3

Segments matched

8

River geography4 admin regions · 0 communes

Parent watershed

hybas-2080056320584 km²

4 administrative regions crossed (GADM L2)

  • Holbæk
    Sjælland · Denmark
    22.1 km
    in this dpt
  • Kalundborg
    Sjælland · Denmark
    7.4 km
    in this dpt
  • Sorø
    Sjælland · Denmark
    5.6 km
    in this dpt
  • Ringsted
    Sjælland · Denmark
    4.2 km
    in this dpt

14 intersecting protected areas

5 more protected areas

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

Species present

1 780 distinct species · 14 269 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 34 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 Åmose Å : 23 espèces reliées par 98 interactions GloBI sur 6 types (connectance 13.9%, filtre Serrano α=0.2). 15 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
38
Interactions affichées
98
Connectance
0.139
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

41km

Max discharge

3,1m³/s

Max Strahler

3

Segments matched

8

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