Rivière· 34 segments
Numedalslågen
Crosses 7 administrative regions : Andebu, Flesberg, Kongsberg, Lardal, Larvik +2
Total length
103km
Max discharge
96,6m³/s
Max Strahler
4
Segments matched
34
River geography7 admin regions · 0 communes
7 administrative regions crossed (GADM L2)
- LarvikVestfold · Norway53.4 kmin this dpt
- KongsbergBuskerud · Norway36.3 kmin this dpt
- FlesbergBuskerud · Norway10.4 kmin this dpt
- Nore og UvdalBuskerud · Norway8.3 kmin this dpt
- LardalVestfold · Norway3.7 kmin this dpt
- AndebuVestfold · Norway0.0 kmin this dpt
- SandefjordVestfold · Norway0.0 kmin this dpt
7 intersecting protected areas
Korpen og Sagkollen
IUCN IaNature Reserve
Haugene
IUCN IaNature Reserve
Lunde
IUCN IaNature Reserve
Bjerke
IUCN IaNature Reserve
Kringlemyr
IUCN IaNature Reserve
Bratthagen
IUCN IIINatural Monument
Løve
IUCN Not ReportedNatural Monument
1 page = 1 named river (aggregation of 34 HydroRIVERS v10 segments). Spatial join cached after first hit.
Species present
856 distinct species · 2 123 observations
Source: GBIF Occurrence snapshot 2026-05-01.
Ecological tissue
Sample of 35 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 Numedalslågen : 22 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 66 interactions GloBI sur 6 types (connectance 9.9%, filtre Serrano α=0.2). 15 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
103km
Max discharge
96,6m³/s
Max Strahler
4
Segments matched
34
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.