Rivière· 14 segments
釧路川
Crosses 5 administrative regions : Kushiro, Kushiro City, Shibecha, Teshikaga, Tsurui
Total length
105km
Max discharge
37,9m³/s
Max Strahler
4
Segments matched
14
River geography5 admin regions · 0 communes
5 administrative regions crossed (GADM L2)
- ShibechaHokkaido · Japan24.4 kmin this dpt
- TeshikagaHokkaido · Japan19.1 kmin this dpt
- KushiroHokkaido · Japan5.2 kmin this dpt
- Kushiro CityHokkaido · Japan0.0 kmin this dpt
- TsuruiHokkaido · Japan0.0 kmin this dpt
7 intersecting protected areas
Akanmashu
IUCN IINational Park
Kushiroshitsugen
IUCN IINational Park
Kushiro shitsugen
IUCN IVNational Wildlife Protection Area
Kussharoko
IUCN IVPrefectural Wildlife Protection Area
Kushiro-shitsugen
IUCN Not ReportedWetland of International Importance (Ramsar Site)
Toubetsu
IUCN IVPrefectural Wildlife Protection Area
Toritoushi
IUCN IVAcademic Nature Protection Area(Hokkaido)
1 page = 1 named river (aggregation of 14 HydroRIVERS v10 segments). Spatial join cached after first hit.
Species present
98 distinct species · 160 observations
Source: GBIF Occurrence snapshot 2026-05-01.
Ecological tissue
Sample of 4 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 釧路川 : 3 espèces reliées par 3 interactions GloBI sur 1 type (connectance 30.0%, filtre Serrano α=0.2). 2 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
105km
Max discharge
37,9m³/s
Max Strahler
4
Segments matched
14
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.