Pyeongtaek to Daegu by bus
Daegu lies 184 km (114 mi) south-east of Pyeongtaek, in the same time zone. What the numbers say about getting there.
A coach takes about 3 h 33 min including stops, over roughly 224 km (139 mi) of road.
| Pyeongtaek | Daegu | |
|---|---|---|
| Country | South Korea | South Korea |
| Population | 364,694 | 2.4 million |
| Elevation | 14 m (46 ft) | 45 m (148 ft) |
| Time now | UTC+9 (Asia/Seoul) | UTC+9 (Asia/Seoul) |
Where to book buses from Pyeongtaek 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 Pyeongtaek?
184 km (114 mi) in a straight line, south-east of Pyeongtaek; by road roughly 224 km (139 mi).
How long does it take to get from Pyeongtaek to Daegu by bus?
About 3 h 33 min, estimated from distance and typical speeds. Timetables and traffic decide the real figure.
Is there a time difference between Pyeongtaek 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 13 September 2026. Hotel 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.