Rivière· 35 segments
Орчик
Crosses 6 administrative regions : Chutivs'kyi, Karlivs'kyi, Krasnohrads'kyi, Novovodolaz'kyi, Valkivs'kyi +1
Total length
125km
Max discharge
4,3m³/s
Max Strahler
4
Segments matched
35
River geography6 admin regions · 0 communes
6 administrative regions crossed (GADM L2)
- Karlivs'kyiPoltava · Ukraine61.0 kmin this dpt
- Valkivs'kyiKharkiv · Ukraine25.3 kmin this dpt
- Zachepylivs'kyiKharkiv · Ukraine22.2 kmin this dpt
- Chutivs'kyiPoltava · Ukraine21.1 kmin this dpt
- Krasnohrads'kyiKharkiv · Ukraine3.2 kmin this dpt
- Novovodolaz'kyiKharkiv · Ukraine1.9 kmin this dpt
9 intersecting protected areas
Pryorilskyi
IUCN Not ReportedEmerald Network
Pryorilskyi
IUCN Not ReportedZakaznyk
Klymivskyi
IUCN Not ReportedZakaznyk
Kapusnyk
IUCN Not ReportedZakaznyk
Krasnoperivka
IUCN Not ReportedZakaznyk
Orilskyi
IUCN Not ReportedZakaznyk
Klymivskyi
IUCN Not ReportedZakaznyk
Hirchakivskyi
IUCN Not ReportedZakaznyk
Mokrianskyi
IUCN Not ReportedZakaznyk
1 page = 1 named river (aggregation of 35 HydroRIVERS v10 segments). Spatial join cached after first hit.
Species present
11 distinct species · 15 observations
Source: GBIF Occurrence snapshot 2026-05-01.
Ecological tissue
Sample of 2 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 Орчик : 2 espèces reliées par 1 interaction GloBI sur 1 type (connectance 100.0%, filtre Serrano α=0.2).
Comparaison sur la connectance du réseau local complet vs distribution nationale (toutes les communes françaises).
Hydrology (HydroRIVERS v10)
Total length
125km
Max discharge
4,3m³/s
Max Strahler
4
Segments matched
35
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.