Rivière· 4 segments
Łaźna Struga
Crosses 3 administrative regions : Ełk, Giżycko, Olecko
Total length
25km
Max discharge
3,9m³/s
Max Strahler
4
Segments matched
4
River geography3 admin regions · 0 communes
3 administrative regions crossed (GADM L2)
- OleckoWarmińsko-Mazurskie · Poland22.1 kmin this dpt
- EłkWarmińsko-Mazurskie · Poland4.3 kmin this dpt
- GiżyckoWarmińsko-Mazurskie · Poland0.2 kmin this dpt
5 intersecting protected areas
Obszar Chronionego Krajobrazu Pojezierza Ełckiego
IUCN Not AssignedProtected Landscape Area
Obszar Chronionego Krajobrazu Pojezierza Iławskiego - część A i B
IUCN Not AssignedProtected Landscape Area
Ostoja Borecka
IUCN Not ReportedSite of Community Importance (Habitats Directive)
Puszczy Boreckiej
IUCN Not AssignedProtected Landscape Area
Puszcza Borecka
IUCN Not ReportedSpecial Protection Area (Birds Directive)
1 page = 1 named river (aggregation of 4 HydroRIVERS v10 segments). Spatial join cached after first hit.
Species present
66 distinct species · 95 observations
Source: GBIF Occurrence snapshot 2026-05-01.
Ecological tissue
Sample of 27 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 Łaźna Struga : 23 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 33 interactions GloBI sur 4 types (connectance 9.4%, filtre Serrano α=0.2). 4 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
25km
Max discharge
3,9m³/s
Max Strahler
4
Segments matched
4
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.