Driving from Yangsan to Daegu
Daegu lies 71 km (44 mi) north-west of Yangsan, in the same time zone. What the numbers say about getting there.
Driving takes about 1 h 5 min without stops, over roughly 87 km (54 mi) of road; add breaks, fuel and any border.
| Yangsan | Daegu | |
|---|---|---|
| Country | South Korea | South Korea |
| Population | 358,074 | 2.4 million |
| Elevation | 6 m (20 ft) | 45 m (148 ft) |
| Time now | UTC+9 (Asia/Seoul) | UTC+9 (Asia/Seoul) |
Where to book car hire from Yangsan to Daegu
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 Daegu
Our booking partner lists 367 places to stay in Daegu. Of the 295 with a star rating, the largest group is 3-star (197), and 4 are five-star. Across 60 properties with at least 50 reviews, the average guest score is 8.5 out of 10. Guests have left 9,081 reviews in total.
Book a hotel in Daegu
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 Daegu from Yangsan?
71 km (44 mi) in a straight line, north-west of Yangsan; by road roughly 87 km (54 mi).
How long does it take to get from Yangsan to Daegu by car?
About 1 h 5 min, estimated from distance and typical speeds. Timetables and traffic decide the real figure.
Is there a time difference between Yangsan and Daegu?
No, both are on Asia/Seoul at the moment.
Where can I stay in Daegu?
Our booking partner lists 367 places to stay in Daegu, 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.