Tours, tickets and day trips in Pingxiang
The sights with published visitor numbers, the heritage listings, and the towns close enough for a day out.
No attraction in Pingxiang has a published visitor count in Wikidata yet, which usually means the draw is the city itself rather than one ticketed sight.
Day trips from Pingxiang
| Route | Country | Distance | Estimated time |
|---|---|---|---|
| Pingxiang to Chongzuo | China | 70 km (44 mi) | about 1 h 9 min |
| Pingxiang to Dongxing | China | 139 km (86 mi) | about 2 h 16 min |
| Pingxiang to Fangchenggang | China | 169 km (105 mi) | about 2 h 45 min |
| Pingxiang to Nanning | China | 179 km (111 mi) | about 2 h 55 min |
| Pingxiang to Qinzhou | China | 196 km (122 mi) | about 3 h 11 min |
| Pingxiang to Baise | China | 200 km (124 mi) | about 3 h 15 min |
| Pingxiang to Beihai | China | 253 km (157 mi) | about 4 h 7 min |
| Pingxiang to Hepu | China | 257 km (160 mi) | about 4 h 11 min |
| Pingxiang to Wenshan City | China | 293 km (182 mi) | about 4 h 46 min |
Distances are straight-line; road and rail routes run about 15–25% longer. Times are estimates from distance and typical speeds, not timetables.
Where to book tours and tickets
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.
Common questions
How are the journey times on this page worked out?
From straight-line distance and typical speeds for each mode, so they are estimates for planning, not timetables. Road and rail routes run 15–25% longer than the straight line.
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.