Geographic map
Open full map ↗Relief, routes, roads, feeders and a new climate-and-terrain screening layer.
Network and regional access
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
Explore terrain, labelled stations and corridor status. S4 marks the announced Gyumri–Akhurik design and rehabilitation process. The Armenia–US Charter published 24 October 2026 refers to that rehabilitation in connection with TRIPP goals; international operation remains conditional. All three map views are available on the overview page.
Relief, routes, roads, feeders and a new climate-and-terrain screening layer.
Network architecture
Existing infrastructure, restoration, official interfaces and unselected studies have different evidence requirements. No internal mountain railway to Meghri is selected.
| Corridor / group | Geography | Planning status |
|---|---|---|
| R1 · Northern | Yerevan–Armavir–Gyumri–Vanadzor–Ayrum | Core · existing / modernisation |
| R2 · Sevan | Yerevan–Hrazdan–Sevan–Shorzha; Sotk separately gated | Core · existing / modernisation |
| R3 · Tavush | Hrazdan–Fioletovo–Dilijan–Ijevan | Core · historic / restoration after survey |
| R4 · Ararat | Yerevan–Masis–Artashat–Yeraskh | Core · existing / modernisation |
| Regional interfaces | Gyumri–Akhurik / Kars; Yeraskh–Nakhchivan; Nrnadzor–Agarak / TRIPP | Official processes · TDC formation documents are being drafted; registration, signed agreements, infrastructure rights, funding and operations remain separate gates |
| C1 | Fioletovo–Vanadzor | Previously studied connector · revalidation required |
| Access studies | Aragats / former R7; Ashotsk–Bavra / Akhalkalaki; north-eastern Tavush; Bazum crossing and Lori plateau | Mode undecided · rail, coach, feeder, road or defer |
| Earlier mountain concepts | Vardenyats / former S3; internal mountain railway to Meghri | Comparator only · no-build default; no alignment selected |
Engineering screen
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
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.
Vanadzor and Stepanavan can appear similar in endpoint elevation while the Bazum barrier between them controls alignment, gradient and tunnel demand. Every ridge and valley between two endpoints matters.
Screening only · replace with official DEM, surveyed profiles, geology and seismic investigations before route selection
New evidence cases
Neither case commits a railway. Both change the alternatives and demand that must be tested before R3 or Aragats access is selected.
The proposed road tunnel and restoration of Hrazdan–Dilijan–Ijevan solve different problems. Following the Road Department’s public consultations on 24 February 2026, Gate R3 should compare passenger demand, travel time, resilience, tourism, freight potential and lifecycle cost rather than assume one mode replaces the other.
Road Department · 25 Feb 2026 ↗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
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.