Rivière· 13 segments
Мерчик
Crosses 3 administrative regions : Bohodukhivs'kyi, Krasnokuts'kyi, Valkivs'kyi
Total length
37km
Max discharge
3,9m³/s
Max Strahler
4
Segments matched
13
River geography3 admin regions · 0 communes
3 administrative regions crossed (GADM L2)
- Krasnokuts'kyiKharkiv · Ukraine33.2 kmin this dpt
- Bohodukhivs'kyiKharkiv · Ukraine31.8 kmin this dpt
- Valkivs'kyiKharkiv · Ukraine4.9 kmin this dpt
10 intersecting protected areas
Slobozhanskyi
IUCN Not ReportedNational nature park
Slobozhanskyi National Nature Park
IUCN Not ReportedEmerald Network
Volodymyrivska dacha
IUCN Not ReportedZakaznyk
Murafskyi
IUCN Not ReportedZakaznyk
Sharivskyi
IUCN Not ReportedZakaznyk
Oberih
IUCN Not ReportedZakaznyk
Nataliivskyi
IUCN Not ApplicablePark-monument of landscape art
Sharivskyi
IUCN Not ApplicablePark-monument of landscape art
Murafska dacha
IUCN Not ReportedNatural monument
1 more protected areassorted by area
Murafa
IUCN Not ReportedNatural monument
1 page = 1 named river (aggregation of 13 HydroRIVERS v10 segments). Spatial join cached after first hit.
Species present
13 distinct species · 21 observations
Source: GBIF Occurrence snapshot 2026-05-01.
Ecological tissue
Sample of 7 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 Мерчик : 7 espèces reliées par 6 interactions GloBI sur 1 type (connectance 28.6%, 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
37km
Max discharge
3,9m³/s
Max Strahler
4
Segments matched
13
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.