Driving from Lengshuijiang to Xiangtan
Xiangtan lies 146 km (91 mi) east of Lengshuijiang, in the same time zone. What the numbers say about getting there.
Driving takes about 2 h 13 min without stops, over roughly 178 km (111 mi) of road; add breaks, fuel and any border.
| Lengshuijiang | Xiangtan | |
|---|---|---|
| Country | China | China |
| Population | 198,299 | 959,303 |
| Elevation | 194 m (636 ft) | 31 m (102 ft) |
| Time now | UTC+8 (Asia/Shanghai) | UTC+8 (Asia/Shanghai) |
| Postal codes | 417200–417500 | 411100 |
Where to book car hire from Lengshuijiang to Xiangtan
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 Xiangtan
Our booking partner lists 10 places to stay in Xiangtan. Of the 8 with a star rating, the largest group is 4-star (3). Guests have left 2 reviews in total.
Book a hotel in Xiangtan
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 Xiangtan from Lengshuijiang?
146 km (91 mi) in a straight line, east of Lengshuijiang; by road roughly 178 km (111 mi).
How long does it take to get from Lengshuijiang to Xiangtan by car?
About 2 h 13 min, estimated from distance and typical speeds. Timetables and traffic decide the real figure.
Is there a time difference between Lengshuijiang and Xiangtan?
No, both are on Asia/Shanghai at the moment.
Where can I stay in Xiangtan?
Our booking partner lists 10 places to stay in Xiangtan, 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.