Rivière· 78 segments
Медведица
Crosses 9 administrative regions : Berezniki gorsovet, Kashinskiy rayon, Kimrskiy rayon, Likhoslavl'skiy rayon, Oleninskiy rayon +4
Total length
1 772km
Max discharge
37,6m³/s
Max Strahler
5
Segments matched
78
River geography9 admin regions · 0 communes
9 administrative regions crossed (GADM L2)
- Rameshkovskiy rayonTver' · Russia104.3 kmin this dpt
- Likhoslavl'skiy rayonTver' · Russia74.1 kmin this dpt
- Spirovskiy rayonTver' · Russia62.6 kmin this dpt
- Kashinskiy rayonTver' · Russia54.8 kmin this dpt
- Kimrskiy rayonTver' · Russia47.8 kmin this dpt
- Berezniki gorsovetPerm' · Russia9.9 kmin this dpt
- Pavinskiy rayonKostroma · Russia6.3 kmin this dpt
- Sychevskiy rayonSmolensk · Russia5.5 kmin this dpt
- Oleninskiy rayonTver' · Russia4.1 kmin this dpt
14 intersecting protected areas
Rameshkovskij
IUCN IVState Natural Zakaznik
State Natural Zakaznik
Boloto YArvin SHuo
IUCN IVState Natural Zakaznik
Boloto CHistyj Moh
IUCN IVState Natural Zakaznik
Boloto Ustinovskoe
IUCN IVState Natural Zakaznik
Boloto Medvedickaya nizina
IUCN IVState Natural Zakaznik
Boloto Laptevskoe
IUCN IVState Natural Zakaznik
Boloto Spasoklinskoe
IUCN IVState Natural Zakaznik
Boloto Tureckoe
IUCN IVState Natural Zakaznik
5 more protected areassorted by area
Boloto Krasnyj gorodok
IUCN IVState Natural Zakaznik
Reliktovyj sosnovyj bor
IUCN IIINatural Monument
Boloto Novostanskoe
IUCN IVState Natural Zakaznik
Bor SHirkun
IUCN IIINatural Monument
Lesopark bol`nicy im.Kalinina
IUCN IIINatural Monument
1 page = 1 named river (aggregation of 78 HydroRIVERS v10 segments). Spatial join cached after first hit.
Species present
0 distinct species · 0 observations
Source: GBIF Occurrence snapshot 2026-05-01.
Ecological tissue
Graphe en cours d’indexation
Calcul du tissu écologique de cette entité.
Le graphe apparaîtra automatiquement dès que le calcul est terminé (rafraîchissement toutes les 2s).
Hydrology (HydroRIVERS v10)
Total length
1 772km
Max discharge
37,6m³/s
Max Strahler
5
Segments matched
78
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.