Driving from Punāsa to Surat
Surat lies 386 km (240 mi) west of Punāsa, in the same time zone. What the numbers say about getting there.
Driving takes about 5 h 53 min without stops, over roughly 471 km (292 mi) of road; add breaks, fuel and any border.
| Punāsa | Surat | |
|---|---|---|
| Country | India | India |
| Population | 350,000 | 4.6 million |
| Elevation | 278 m (912 ft) | 20 m (66 ft) |
| Time now | UTC+5:30 (Asia/Kolkata) | UTC+5:30 (Asia/Kolkata) |
Where to book car hire from Punāsa to Surat
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 Surat
Our booking partner lists 346 places to stay in Surat. Of the 295 with a star rating, the largest group is 3-star (194), and 8 are five-star. Across 30 properties with at least 50 reviews, the average guest score is 7.7 out of 10. Guests have left 8,016 reviews in total.
Book a hotel in Surat
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 Surat from Punāsa?
386 km (240 mi) in a straight line, west of Punāsa; by road roughly 471 km (292 mi).
How long does it take to get from Punāsa to Surat by car?
About 5 h 53 min, estimated from distance and typical speeds. Timetables and traffic decide the real figure.
Is there a time difference between Punāsa and Surat?
No, both are on Asia/Kolkata at the moment.
Where can I stay in Surat?
Our booking partner lists 346 places to stay in Surat, 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.