Network and regional access

One network,
Different ways to reach it

Rail is assigned to the strongest corridors. Timed feeders complete access where a new mountain railway would be disproportionate. Every coloured line is a concept until its route, demand and impacts are verified.

Interactive system

Geography and passenger logic

Explore terrain, labelled stations and corridor status. S4 marks the official Gyumri–Akhurik project; international operation remains conditional. Both map formats remain available on the overview page.

Map layers
Core infrastructure corridorsR1 NorthernR2 SevanR3 TavushR4 Ararat
Station symbolsLocal stopPrincipalInterchangeBorder interfaceStudy point
DebedAghstevHrazdanArpaVorotanAraksYerevanZvartnotsVagharshapatArmavirGyumriVanadzorAlaverdiAyrumHrazdanGagarinSevanSotkDilijanIjevanArtashatYeraskhGavarMartuniJermukSisianShinuhayr / Tatev HubGorisKapanMeghriAgarakYeghegnadzorAshtarakAparanAshotskStepanavanTashirAkhuryan / AkhurikNrnadzor
Drag to move · wheel or pinch to zoom · select a station or line
Concept map — routes are not surveyed alignments

Geographic map

Open full map ↗

Relief, routes, roads, feeders and a new climate-and-terrain screening layer.

Network architecture

Four core corridors and conditional access

Existing infrastructure, restoration, official interfaces and unselected studies have different evidence requirements. No internal mountain railway to Meghri is selected.

Corridor / groupGeographyPlanning status
R1 · NorthernYerevan–Armavir–Gyumri–Vanadzor–AyrumCore · existing / modernisation
R2 · SevanYerevan–Hrazdan–Sevan–Shorzha; Sotk separately gatedCore · existing / modernisation
R3 · TavushHrazdan–Fioletovo–Dilijan–IjevanCore · historic / restoration after survey
R4 · AraratYerevan–Masis–Artashat–YeraskhCore · existing / modernisation
Regional interfacesGyumri–Akhurik / Kars; Yeraskh–Nakhchivan; Nrnadzor–Agarak / TRIPPOfficial processes · design, agreements, funding and operations remain separate gates
C1Fioletovo–VanadzorPreviously studied connector · revalidation required
Access studiesAragats / former R7; Ashotsk–Bavra / Akhalkalaki; north-eastern Tavush; Bazum crossing and Lori plateauMode undecided · rail, coach, feeder, road or defer
Earlier mountain conceptsVardenyats / former S3; internal mountain railway to MeghriComparator only · no-build default; no alignment selected

Engineering screen

Topography before a route

The relief view marks broad constraint zones, not alignments. Vardenyats, Bazum, Vayk–Jermuk, Sisian–Kajaran and Kajaran–Meghri each need surveyed profiles, geology and an emergency-access concept before a rail option can be compared fairly.

03 · Topographic feasibility

Terrain before alignment

A terrain screening layer, not a railway alignment. Broad zones show where relief is likely to drive gradients, curves, tunnels, viaducts, winter operations and emergency-access requirements.

Aragats plateauBazum crossingVardenyatsVayk–JermukSisian–KajaranKajaran–MeghriMylerAragats resort study area
Moderate constraintHigh constraintVery high / tunnel-intensiveTourism demand points · not stations
Why endpoint height is not enough

Similar endpoint elevations do not make a corridor level. The railway must cross every ridge and valley between them; the controlling gradient and tunnel requirement are set by the intervening terrain.

Screening only · replace with official DEM, surveyed profiles, geology and seismic investigations before route selection

New evidence cases

Road and tourism projects change the demand test

Neither case commits a railway. Both change the alternatives and demand that must be tested before R3 or Aragats access is selected.

R3 · TAVUSH

Dilijan access · road tunnel and restored rail are not substitutes by default

The Road Department reported public consultations on 24 February 2026 for the new Dilijan road-tunnel design. R3 must therefore be compared with the road project on capacity, door-to-door time, capital and lifecycle cost, winter reliability, tourism demand and network resilience.

Road Department · 25 Feb 2026
ARAGATS ACCESS

Aragats tourism growth case

Test Myler, the separate Government-approved Aragats resort project, Aparan growth and winter peak traffic together. Compare rail, express coach, park-and-ride and seasonal shuttle capacity before selecting the mode. Myler and the resort are demand points, not stations.

Regional passports

What changes for every marz

Each passport states what is direct, what needs a timed feeder and what remains conditional. Journey times and station sites still require a national demand model and official GIS.

National access does not mean rails in every valley. A region counts as served only if the railway and its guaranteed feeder operate as one timetable, one ticket and one protected connection. A study corridor does not count as committed access.

Yerevan

Direct rail
Rail hubs
Yerevan Central; Masis
Coverage
R1, R2 and R4; airport rail access remains a separate option
Key destinations
City centre, airport, national interchange
Programme
2030–2038 · subject to renewal gates

Aragatsotn

Conditional
Rail hubs
Access hubs to be selected
Coverage
Myler, the approved Aragats resort project, Aparan growth and winter peaks form one demand case; no mode selected
Key destinations
Myler and Aragats resort as demand points; Byurakan and Amberd by timed feeder
Programme
Rail / express coach / park-and-ride / seasonal shuttle study

Ararat

Direct rail
Rail hubs
Artashat, Ararat, Yeraskh
Coverage
R4 renewal; Yeraskh–Nakhchivan is a separate conditional regional interface
Key destinations
Khor Virap and Areni corridor connections
Programme
Renewal / regional agreements

Armavir

Direct rail
Rail hubs
Armavir; existing corridor access
Coverage
R1 renewal; Etchmiadzin and airport access by feeder or separately justified rail
Key destinations
Etchmiadzin, Zvartnots Cathedral and airport
Programme
2030–2038 · renewal gate

Gegharkunik

Conditional
Rail hubs
Sevan / Shorzha; Sotk separately gated
Coverage
R2 renewal; Gavar and Martuni are access objectives served by coach or feeders
Key destinations
Lake Sevan, shore settlements and eastern industry
Programme
Renewal / separate Sotk gate

Kotayk

Rail + feeder
Rail hubs
Abovyan, Charentsavan, Hrazdan, Gagarin
Coverage
R2 services; through Tavush trains only after R3 restoration
Key destinations
Tsaghkadzor, Garni and Geghard by feeder
Programme
Renewal / R3 validation

Lori

Rail + feeder
Rail hubs
Spitak, Vanadzor, Alaverdi, Ayrum
Coverage
R1 renewal; C1 revalidation; Bazum engineering and plateau mode studies remain separate
Key destinations
Sanahin, Haghpat, Debed valley
Programme
Renewal / conditional studies

Shirak

Rail + feeder
Rail hubs
Gyumri; Akhuryan conditional
Coverage
Hourly-target R1; Ashotsk and Bavra by protected feeder and study corridor
Key destinations
Gyumri, Marmashen and northern plateau
Programme
Stage 1 / reserve studies

Syunik

Conditional
Rail hubs
Sisian, Goris, Kapan, Meghri: access objectives, not promised rail stations
Coverage
Road, direct coach and feeders; regional rail via Nakhchivan only when agreements and infrastructure permit
Key destinations
Tatev, Goris and Khndzoresk by coordinated road transport
Programme
Gate S · no fixed railway date

Tavush

Rail + feeder
Rail hubs
Dilijan and Ijevan
Coverage
R3 rehabilitation compared with the new Dilijan road-tunnel project; Noyemberyan remains conditional
Key destinations
Haghartsin, Goshavank and forest destinations by feeder
Programme
R3 engineering + road / rail comparison

Vayots Dzor

Conditional
Rail hubs
Areni, Yeghegnadzor, Vayk, Jermuk: access objectives
Coverage
Road, direct coach and feeders; Vardenyats railway has no-build default
Key destinations
Noravank, Areni wine region and Jermuk
Programme
Gate S · mode undecided