Fatehpur to Lucknow by bus
Lucknow lies 102 km (63 mi) north of Fatehpur, in the same time zone. What the numbers say about getting there.
A coach takes about 2 h 5 min including stops, over roughly 124 km (77 mi) of road.
| Fatehpur | Lucknow | |
|---|---|---|
| Country | India | India |
| Population | 166,480 | 2.5 million |
| Elevation | 121 m (397 ft) | 126 m (413 ft) |
| Time now | UTC+5:30 (Asia/Kolkata) | UTC+5:30 (Asia/Kolkata) |
Where to book buses from Fatehpur to Lucknow
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 Lucknow
Our booking partner lists 944 places to stay in Lucknow. Of the 724 with a star rating, the largest group is 3-star (462), and 21 are five-star. Across 91 properties with at least 50 reviews, the average guest score is 7.2 out of 10. Guests have left 23,575 reviews in total.
Book a hotel in Lucknow
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 Lucknow from Fatehpur?
102 km (63 mi) in a straight line, north of Fatehpur; by road roughly 124 km (77 mi).
How long does it take to get from Fatehpur to Lucknow by bus?
About 2 h 5 min, estimated from distance and typical speeds. Timetables and traffic decide the real figure.
Is there a time difference between Fatehpur and Lucknow?
No, both are on Asia/Kolkata at the moment.
Where can I stay in Lucknow?
Our booking partner lists 944 places to stay in Lucknow, 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.