The UK Pakistan time difference is five hours while the UK is on Greenwich Mean Time and four hours while it is on British Summer Time. Pakistan Standard Time (PKT) sits at UTC+5 all year and never moves its clocks, so every change in the gap comes from the UK side. On the last Sunday in March the gap shrinks to four hours; on the last Sunday in October it widens back to five. In 2026 the UK clocks go back on 25 October. In 2027 they go forward on 28 March and back on 31 October.
For a London corporate travel desk booking airport pickups, intercity cars and driver days in Pakistan, that one-hour swing does more damage than the arithmetic suggests. It moves the window when both offices are awake, it changes which UK shift owns an arrival that lands in the small hours, and it sits behind a steady trickle of cars booked for the wrong day. What follows turns the clock maths into a working routine: the overlap hours, a travel desk handover note you can copy, an on-call rule for overnight arrivals, and the date checks that catch after-midnight landings before anyone dispatches a driver.
The UK Pakistan time difference, season by season
The UK pattern never varies, and the government publishes it: clocks go forward one hour at 01:00 on the last Sunday in March and back one hour at 02:00 on the last Sunday in October (GOV.UK, When do the clocks change). Pakistan tried daylight saving in 2002 and again in 2008 and 2009, dropped it each time after public resistance, and has stayed on UTC+5 ever since (Pakistan Standard Time).
| Period | UK clock | Pakistan clock | Gap | 09:00 in London is |
|---|---|---|---|---|
| 29 Mar 2026 to 25 Oct 2026 | BST (UTC+1) | PKT (UTC+5) | 4 hours | 13:00 in Pakistan |
| 25 Oct 2026 to 28 Mar 2027 | GMT (UTC+0) | PKT (UTC+5) | 5 hours | 14:00 in Pakistan |
| 28 Mar 2027 to 31 Oct 2027 | BST (UTC+1) | PKT (UTC+5) | 4 hours | 13:00 in Pakistan |
So the short version for anyone asking about Pakistan time vs BST: add four hours to a London summer time to get Pakistan, add five in winter. Going the other way, subtract. Nobody on the Pakistan side will warn you that the gap has changed, because from their side nothing has.
What the changeover weekend does to bookings already on file
A booking stored in Pakistan local time is untouched by the UK change. A booking where someone on the desk worked out “that’s 06:00 our time” and wrote that down is now wrong by an hour, and nothing in the system will flag it. The same goes for reminder calls, check-in messages to travellers and supplier chasers that were set as London times.
The fix is a single rule: every Pakistan pickup lives in the record in PKT, on the 24-hour clock, and the UK equivalent is never stored. UK time belongs only on the desk’s own rota. Then, in the week before each change, run through this:
- List every Pakistan job in the seven days after the change and check nothing was keyed in London time.
- Check calendar entries that were typed as London times for a Pakistan event. An entry created with the event’s own time zone will move correctly; one typed as “06:00 London” will not.
- Re-send the on-call rota with the new PKT coverage hours, since the same London shift now covers a different slice of the Pakistan day.
- Tell frequent travellers that the gap has changed, in one line, with the new figure.
Overlapping working hours and how to spend them
Take a London desk working 09:00 to 17:30 and a Pakistan-side contact (a supplier, a site office, a local coordinator) working 09:00 to 18:00 PKT. These are example hours; swap in your own, but the pattern holds.
| Season | London desk in PKT | Pakistan office in UK time | Shared window (UK time) |
|---|---|---|---|
| BST, gap 4 hours | 13:00 to 21:30 | 05:00 to 14:00 | 09:00 to 14:00, five hours |
| GMT, gap 5 hours | 14:00 to 22:30 | 04:00 to 13:00 | 09:00 to 13:00, four hours |
Two things fall out of that. First, the shared window is a London morning, and it is an hour shorter in winter. Second, the Pakistan morning, when a lot of pickups, hotel departures and site visits actually happen, runs while London is asleep or on the commute. The desk is never live when a 07:00 PKT hotel pickup rolls; in summer that is 03:00 in London, in winter 02:00.
Spend the overlap on anything that needs a human on both ends:
- Confirm every Pakistan job in the next 48 hours, not just tomorrow’s, so a problem found on Tuesday morning still has a Wednesday overlap to be fixed in.
- Push through changes that need the Pakistan side to act: vehicle swaps, added passengers, new pickup addresses, extra stops.
- Collect driver name and contact number for early-morning PKT jobs before the window closes, and get them to the traveller the same day.
- Settle anything commercial, such as a revised quote or an extra hour of waiting, while both parties can still reply.
A daily rhythm that works in both seasons
- 09:00 London (13:00 or 14:00 PKT). Read the overnight log first. Anything that happened in Pakistan during the UK night gets triaged before new work starts.
- 09:30 to 12:30 London. Confirmations, changes and supplier questions for the next 48 hours. This is the only reliable two-way window in winter.
- 12:30 London. Last call for anything that needs the Pakistan office today. After 13:00 GMT it is 18:00 PKT and you are relying on goodwill.
- Afternoon London (Pakistan evening). New requests, quotes, traveller communications, and building tomorrow’s handover.
- 17:00 London. Write the handover note and pass the on-call phone. That hand-off happens at 21:00 PKT in summer and 22:00 PKT in winter, which is often just before a run of late arrivals.
The travel desk handover note
A handover that says “all fine, see system” fails at 02:00 when the on-call person opens a record with no context. The note should let someone who has never seen the trip make a decision without phoning anyone. Keep it to one screen per job and use the same fields every time.
- Job reference and traveller. Booking reference, traveller name as on the passport, company, cost centre if the traveller may be asked about it.
- Event time in PKT, with the weekday. “Tue 27 Oct 2026, 02:40 PKT”. Add the UK equivalent in brackets only here, for the on-call person’s benefit: “(Mon 26 Oct, 21:40 GMT)”.
- Flight or trigger. Flight number and the final-leg arrival airport, or the hotel and the event that sets the pickup time.
- Pickup point and destination. Terminal or hotel entrance, destination address, and any stop on the way.
- Driver and vehicle status. Confirmed, pending, or requested only. If confirmed, the driver’s name and number and when they were shared with the traveller.
- Traveller contact. Mobile that will work on landing, plus WhatsApp if it differs, and a second contact where one exists.
- What can go wrong and the pre-agreed answer. For example: flight delayed more than two hours, traveller not at the meeting point after 45 minutes, or a change of hotel.
- Authority. What the on-call person may approve without waking anyone, such as extra waiting time or a replacement car up to an agreed amount, and who to escalate to above that.
- Open questions. Anything unresolved, with who owns it and by when.
Two formatting habits prevent most errors. Write dates as weekday, day, month name and year, never “10/27” or “27/10”, because a traveller from the US and a supplier in Lahore will read those differently. And use the 24-hour clock throughout: “12:30 am” is the quickest way to have a car turn up twelve hours early or late.
Overnight arrivals and who is on call
Work out the London dark window in PKT and the scale of the problem becomes obvious. With the desk closing at 17:30 and reopening at 09:00 London time, nobody is at a desk from 21:30 to 13:00 PKT in summer, or 22:30 to 14:00 PKT in winter. That is not just the Pakistan night. It is the Pakistan night plus the whole Pakistan morning: late-evening landings, the small-hours arrivals, early hotel checkouts and the 08:00 drive to a factory or client office.
| Event (PKT) | London time, BST | London time, GMT | Who owns it |
|---|---|---|---|
| 18:00 evening landing | 14:00 | 13:00 | Day desk |
| 23:30 late landing | 19:30 | 18:30 | On-call (evening) |
| 03:00 small-hours landing | 23:00 the previous day | 22:00 the previous day | On-call (night) |
| 07:00 hotel pickup | 03:00 | 02:00 | On-call, or a Pakistan-side coordinator |
| 11:00 site visit | 07:00 | 06:00 | Early on-call, or the Pakistan side |
Notice the 03:00 PKT row. The traveller lands in Pakistan on the morning of one date while London is still on the evening of the previous date. That single fact accounts for many of the date errors covered below.
Three ways to cover out of hours travel support
| Model | How it works | Suits | Weak spot |
|---|---|---|---|
| London on-call phone | One named person holds a mobile after 17:30 London, with the handover notes and approval limits. | Low volume, a handful of Pakistan trips a month | The Pakistan morning lands in the on-call person’s night; fatigue builds fast in busy weeks |
| Split ownership | London owns the booking; a Pakistan-based coordinator owns execution from 21:00 PKT to the London opening. | Regular traffic, project teams, repeat site visits | Needs a clean handover twice a day and a shared log both sides actually read |
| Provider operations as first line | The ground transport provider handles driver issues directly with the traveller; the desk is the escalation point. | Travellers who are comfortable dealing locally | Only as good as the provider’s own monitoring hours, which you should ask about in writing |
Whichever model you pick, the traveller needs the same three things before they fly: one number to call if the car is not there, the driver’s details or a clear statement that they will arrive later, and a plain rule for what happens if the flight is badly delayed. Our sister service Pakistan Taxi, which runs on the same iDrive network, has a traveller-side contact plan for arriving in Pakistan late at night that you can pass on to the people you book for.
Duty of care is not suspended at night
Check the FCDO travel advice for Pakistan before the trip is booked, not when the on-call phone rings. At the time of writing its regional risks page advises against all travel to Balochistan, to a long list of Khyber Pakhtunkhwa districts including Peshawar city, to Sindh north of and including Nawabshah, and to within 10 miles of the Line of Control. It advises against all but essential travel to further areas, including Azad Jammu and Kashmir, Dera Ghazi Khan and the strips near the Afghanistan, China and India borders. It also warns that during protests major roads in and around cities may be shut or blocked, and mobile data can be cut without warning, which matters when the on-call person is relying on WhatsApp to reach a driver. The advice changes, so the desk should re-check it for each trip and record the date checked in the handover note. Your company’s travel risk policy and insurer’s terms sit on top of that.
Date errors on flights that land after midnight
The most expensive mistake a desk makes on Pakistan work is not the hour. It is the day. A traveller who “gets in Monday night” may well land at 02:00 on Tuesday, and a car booked for Monday 02:00 will be at the terminal a full day early, then absent when it matters.
Here is a worked example with a hypothetical flight. A traveller leaves London at 13:00 GMT on Monday 2 November 2026, on a flight scheduled at eight hours. They land at 21:00 GMT Monday, which is 02:00 PKT on Tuesday 3 November. Everyone in London will think of this as a Monday evening arrival. The ticket, the airline and the driver all work in Pakistan time, so the job is Tuesday. Put Monday in the booking and the error is locked in.
The same trap runs in reverse on departures. For a hypothetical 03:15 PKT flight out of Islamabad on Thursday 5 November, the car probably needs to leave the hotel before midnight, which makes the pickup a Wednesday job. The flight date and the pickup date are different, and the handover note must show both.
Checks that catch after-midnight errors
- Take the arrival date and time from the arrival field of the airline e-ticket, which is shown in local time at the arrival airport. Never calculate it from departure time plus flight length.
- Restate every job between 00:00 and 05:00 PKT in full in the confirmation to the traveller: “Your driver meets you at 02:00 on Tuesday 3 November, Pakistan time, after flight XX123”. Ask them to reply to confirm.
- Anchor the booking to the flight number, so a delay that pushes an arrival past midnight moves the job with it rather than leaving it on the old date.
- For connecting itineraries, use the final leg only. The London departure date is irrelevant to the driver.
- Flag any job whose PKT date differs from its London date with a visible marker in your system, and read those rows aloud at handover.
Airport specifics that change the rota
The airport shapes the timing, and the timing shapes who is on call. A few points worth building into the plan:
- Islamabad (ISB). The current airport opened in May 2018 near Fateh Jang, about 25 km southwest of central Islamabad, and connects directly to the motorways towards Lahore and Peshawar (Islamabad International Airport). Hotel-to-airport timings for early departures need that distance built in; the old habit of treating the airport as being in town does not apply.
- Lahore (LHE). Allama Iqbal International sits about 15 km from the city centre, and PIA resumed London to Lahore flights in March 2026 (Allama Iqbal International Airport).
- Karachi (KHI). At the time of writing Jinnah International has no direct scheduled UK service, so UK travellers usually connect through a Gulf or Istanbul hub. The arrival time is then set by the connection, and a missed connection can move a Karachi pickup by many hours. Track the final-leg flight number, not the London flight.
Direct UK services are listed on the airports’ pages as operated by PIA and British Airways, but schedules and routes change each season. Check the airline’s own timetable for the specific date rather than relying on last year’s pattern. For airport-by-airport pickup detail, see our Pakistan airport transfers page.
Running Pakistan trips through iDrive
iDrive is built for bookers outside Pakistan. You send the job details, including the pickup time in Pakistan time, the flight number and the traveller’s contact, and the request is quoted for that specific journey, then confirmed only once a suitable vehicle is secured. A submitted request is not a confirmed car until you receive the confirmation, and the handover note should show which of the two you hold. Vehicle availability varies by city, date and time, which is one more reason to clear next-day jobs inside the morning overlap rather than at 17:00.
For company bookers, the business travel car service in Pakistan page sets out the options for meetings, site visits and multi-day driver hire. If you are booking from London for the first time, how to book a taxi in Pakistan from the UK walks through the details to prepare, and booking Pakistan transport before you fly covers timing the request against the flight. When the job is ready, start a booking request with the flight number and the PKT pickup time filled in.
Questions people ask
Is Pakistan four or five hours ahead of the UK?
Both, depending on the season. Pakistan is four hours ahead while the UK is on British Summer Time (late March to late October) and five hours ahead while the UK is on GMT (late October to late March).
Does Pakistan change its clocks?
No. Pakistan stays on UTC+5 all year. It tried daylight saving in 2002 and in 2008 and 2009, then dropped it, so any change in the gap comes from the UK clocks.
What time is 09:00 in London in Pakistan?
13:00 in Pakistan during British Summer Time and 14:00 during GMT. A London morning is a Pakistan early afternoon, which is why the useful overlap is short.
Which date goes on a booking for a flight landing just after midnight?
The Pakistan local arrival date shown on the e-ticket. A flight that lands at 01:30 on Wednesday is a Wednesday job, even if London still thinks of it as Tuesday night.