Kathmandu's Connectivity at a Glance

Kathmandu's 25 tracked connections lean toward the medium-haul band rather than short-hops: just one, Bangkok, qualifies as short-haul, eight sit in the medium-haul range, and sixteen are long-haul city pairs reaching Europe, Africa, Oceania and the Americas. The verified count, 9 of 25, clusters almost entirely in that medium-haul Asian band — Hong Kong, Dubai, Abu Dhabi, Kuala Lumpur, Doha, Singapore and Seoul all carry a confirmed historical operating record alongside Bangkok — while only a single long-haul pair, Istanbul, does.

This is a hub whose real, historically-flown reach is regional: Nepal's national carrier and the major Gulf and Asian airlines built Kathmandu's short and medium-haul network into Southeast Asia, East Asia and the Gulf, but nothing in this dataset shows Kathmandu flying nonstop to Europe, Australia or North America except via Turkish Airlines' long Istanbul route. An agent can quote the eight verified regional connections with confidence; every other long-haul entry here, from Frankfurt to Los Angeles, is a real routing reference that will need at least one connection, commonly through Doha, Istanbul or Delhi.

International Connections from Kathmandu

All 25 of Kathmandu's tracked destinations are international, split into one short Gulf-region hop (Bangkok), eight medium-haul regional pairs, and sixteen long-haul city pairs. The verified record sits almost entirely below the long-haul line — Istanbul is the sole exception — leaving the rest of long-haul Europe, Africa, Oceania and North America as distance and time references only.

Notable Verified Routes

Nine of Kathmandu's 25 tracked routes carry a verified historical operating record, and eight of those nine sit in the short-to-medium band toward the Gulf, Southeast Asia and East Asia; Istanbul is the lone long-haul exception.

Looking Up Kathmandu Routes Across GDS Systems

Every route out of Kathmandu here runs under the KTM origin code in a standard GDS availability check, whether you're pricing the 2.6-hour hop to Bangkok or a long-haul reference fare toward Los Angeles — only the destination and date change.

Amadeus:  AN15JULKTMxxx
Sabre:    A15JUNKTMxxx
Galileo:  A/15JUNKTMxxx

Replace xxx with the destination's own 3-letter IATA code from the tables above — the availability-check syntax itself doesn't change by destination, only the city pair does.

Frequently Asked Questions