If you are looking for the best meeting time between London and Singapore, here it is: 9 to 11 AM in London, which is 4 to 6 PM in Singapore. That is the October 2026 answer, while London is still on British Summer Time. After October 25 the same London slot lands at 5 to 7 PM Singapore time, because London falls back an hour and Singapore does not move at all. This is one of the kinder Europe-to-Asia pairings. Nobody has to get up at 6 AM or stay past dinner. The whole guide below is the month-by-month version of that sentence, plus the one trap that catches every team once.
The window, month by month
The gap is 7 hours while London is on BST (UTC+1) and 8 hours on GMT (UTC+0). Singapore is UTC+8 all year.
| Period | London | Singapore | Best two-hour slot |
|---|---|---|---|
| Early Oct (Oct 1 – 24) | BST, UTC+1 | SGT, UTC+8 | 9–11 AM London / 4–6 PM Singapore |
| Late Oct (Oct 25 – 31) | GMT, UTC+0 | SGT, UTC+8 | 9–11 AM London / 5–7 PM Singapore |
| Nov – Mar | GMT, UTC+0 | SGT, UTC+8 | 9–11 AM London / 5–7 PM Singapore |
| Late Mar (from last Sunday) | BST, UTC+1 | SGT, UTC+8 | 9–11 AM London / 4–6 PM Singapore |
| Apr – Sep | BST, UTC+1 | SGT, UTC+8 | 9–11 AM London / 4–6 PM Singapore |
London moves to GMT on the last Sunday of October and back to BST on the last Sunday of March. Singapore never changes.
The October trap, since you are probably reading this because of it
Here is the thing that actually brings people to this page. You set a recurring call in September at 4 PM Singapore time. It worked for weeks. Then one Monday it shows up at 5 PM, or your London colleague joins an hour late, and everyone assumes someone edited the invite. Nobody did. London left BST on the last Sunday of October, the gap went from 7 hours to 8, and every recurring meeting anchored to one city's local time slid an hour for the other city.
The fix is boring and it works: schedule the recurring meeting in the city that does not observe daylight saving, and put the other city's time in the invite title. "Weekly sync, 4 PM SGT / 9 AM London (8 AM in winter)" survives both transitions because Singapore is the anchor that never moves. Calendar apps handle this correctly if the event carries a real time zone, but only if someone set it. The trap is not a software bug. It is a September decision meeting an October clock.
Why this pairing is easier than it looks
Compare it to the alternatives and London–Singapore starts to look generous. Tokyo to London has essentially no shared working hours at all. Berlin to Sydney demands an 8 AM start against a 6 PM finish as the only option. New York to Singapore forces somebody into the night. London to Singapore asks London for mid-morning and Singapore for late afternoon, and both of those are inside the working day without anyone stretching. A 9 AM London call is nobody's heroic early start. A 5 PM Singapore call is nobody's ruined evening.
That is why my recommendation for this corridor is simpler than for most: book the slot and keep it. The harder pairings need rotation rules, regional sessions, and async defaults to stay humane. This one mostly needs the October note in the invite and a written record for anyone who misses the call. Save the structural machinery for the pairings that actually hurt.
Check the overlap for your own two cities, including the DST shifts.
Find Your Time Zone OverlapFrequently asked questions
What is the best meeting time between London and Singapore?
9 to 11 AM in London, which is 4 to 6 PM in Singapore during London's summer (BST) and 5 to 7 PM in winter (GMT). Both sides stay inside reasonable working hours.
How many hours apart are London and Singapore?
7 hours when London is on British Summer Time (UTC+1, late March to late October) and 8 hours when London is on GMT (UTC+0). Singapore is UTC+8 year-round and does not observe daylight saving.
Why did my London-Singapore recurring call move an hour in October?
London leaves British Summer Time on the last Sunday of October, moving from UTC+1 to UTC+0. Singapore stays on UTC+8, so the gap widens from 7 to 8 hours. A call fixed in Singapore time shifts an hour for London, and vice versa.
Is there a shared 9-to-5 overlap between London and Singapore?
Barely: one hour at the edges. 9 to 10 AM in London overlaps 4 to 5 PM in Singapore during BST, or 5 to 6 PM during GMT. Widening the day slightly, London from 8:30 AM or Singapore to 6:30 PM, buys a comfortable two-hour window.
How do London-Singapore remote teams handle the gap?
Most book the morning-London slot and keep it. Because the window sits inside both working days, this pairing needs less structural machinery than harder corridors: a fixed slot, a written record for anyone who misses it, and async updates for the rest.
Related guides: London to Sydney Meeting Times · Best Meeting Time Between New York and Singapore · Daylight Saving Time and Recurring International Meetings · Best Meeting Time for Teams Across the US, Europe, and Asia
Remote-work scheduling notes, roughly monthly: subscribe to the newsletter.