Mawlamyine to Nay Pyi Taw by bus
Nay Pyi Taw lies 395 km (245 mi) north-west of Mawlamyine, in the same time zone. What the numbers say about getting there.
A coach takes about 7 h 20 min including stops, over roughly 482 km (299 mi) of road.
Open Nay Pyi Taw in Google Maps
| Mawlamyine | Nay Pyi Taw | |
|---|---|---|
| Country | Myanmar | Myanmar |
| Population | 438,861 | 925,000 |
| Elevation | 52 m (171 ft) | 122 m (400 ft) |
| Time now | UTC+6:30 (Asia/Yangon) | UTC+6:30 (Asia/Yangon) |
Where to book buses from Mawlamyine to Nay Pyi Taw
We take no bookings for these providers and hold no reservation with them. The provider you choose handles payment, confirmation, changes and refunds. How that works.
Staying in Nay Pyi Taw
Our booking partner lists 4 places to stay in Nay Pyi Taw. Of the 4 with a star rating, the largest group is 5-star (2), and 2 are five-star. Guests have left 101 reviews in total.
Book a hotel in Nay Pyi Taw
Live rooms and prices from our booking partner, booked and paid for here. Free cancellation is marked where it applies.
Common questions
How far is Nay Pyi Taw from Mawlamyine?
395 km (245 mi) in a straight line, north-west of Mawlamyine; by road roughly 482 km (299 mi).
How long does it take to get from Mawlamyine to Nay Pyi Taw by bus?
About 7 h 20 min, estimated from distance and typical speeds. Timetables and traffic decide the real figure.
Is there a time difference between Mawlamyine and Nay Pyi Taw?
No, both are on Asia/Yangon at the moment.
Where can I stay in Nay Pyi Taw?
Our booking partner lists 4 places to stay in Nay Pyi Taw, bookable on this site.
Where these facts come from
- GeoNames (CC BY 4.0): population, elevation, time zone, postal codes
- Wikidata (CC0): area, sister cities, visitor numbers, heritage listings, stations and ports
- OurAirports (public domain): airports, runways
- Natural Earth (public domain): map outlines
Data compiled 14 September 2026. Hotel and hostel figures are from our booking partner’s catalogue on that date. Journey times on this page are estimates from distance, not timetables; check the operator before you rely on one.