Ruisseau
Tversted Å
Crosses 1 administrative regions : Hjørring
Total length
8km
Max discharge
0,6m³/s
Max Strahler
1
Segments matched
1
River geography1 admin regions · 0 communes
1 administrative regions crossed (GADM L2)
- HjørringNordjylland · Denmark8.4 kmin this dpt
6 intersecting protected areas
Skagens Gren og Skagerak
IUCN Not ReportedSpecial Areas of Conservation (Habitats Directive)
Skagens Gren og Skagerrak
IUCN Not ReportedMarine Protected Area (OSPAR)
Hjørring Kommune private
IUCN Not Assigned§3 protected habitats (all lakes, bogs, streams, heaths and meadows etc.)
Hjørring Kommune public
IUCN IV§3 protected habitats (all lakes, bogs, streams, heaths and meadows etc.)
Uggerby Klitplantage og Uggerby Å's udløb
IUCN Not ReportedSpecial Areas of Conservation (Habitats Directive)
Tversteds Grønne Front
IUCN VProtected by conservation order, excl. Church surroundings
1 page = 1 named river (aggregation of 1 HydroRIVERS v10 segment). Spatial join cached after first hit.
Species present
1 581 distinct species · 48 203 observations
Source: GBIF Occurrence snapshot 2026-05-01.
Ecological tissue
Sample of 21 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 Tversted Å : 11 espèces reliées par 69 interactions GloBI sur 4 types (connectance 27.3%, 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
8km
Max discharge
0,6m³/s
Max Strahler
1
Segments matched
1
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.