---
title: "Best time to meet: London and Singapore (2026)"
url: https://meet.barq.dev/meeting-planner/london-and-singapore
updated: 2026-11-21
author: "Hammad Ali"
---

# Best time to meet: London and Singapore (2026)

**Short answer:** Singapore is 8 hours ahead relative to London as of 2026-11-21. Their 09:00–17:00 workdays share 0 hours in that period. The tables below cover 2026-11-21 through 2027-11-21.


## Time difference and clock changes

On 2026-11-21, London uses UTC+0 and Singapore uses UTC+8.


| City changing | Local date and time after change | UTC instant | Offset before → after | Singapore relative to London after change |
| --- | --- | --- | --- | --- |
| London | 2027-03-28 02:00 | 2027-03-28 01:00 | UTC+0 → UTC+1 | 7 hours ahead |
| London | 2027-10-31 01:00 | 2027-10-31 01:00 | UTC+1 → UTC+0 | 8 hours ahead |

## Shared working hours by period

Monday–Friday in both cities; public holidays and individual calendars are excluded. Each period uses a representative shared weekday after its boundary. The 10:00–18:00 profile shifts the workday later; 07:00–21:00 is a flexible comparison, not a recommended daily schedule.


| Period (UTC, end exclusive) | Singapore relative to London | 09:00–17:00 | 08:00–18:00 | 10:00–18:00 | 07:00–21:00 |
| --- | --- | --- | --- | --- | --- |
| 2026-11-21 00:00 to 2027-03-28 01:00 | 8 hours ahead | 0 h | 2 h | 0 h | 6 h |
| 2027-03-28 01:00 to 2027-10-31 01:00 | 7 hours ahead | 1 h | 3 h | 1 h | 7 h |
| 2027-10-31 01:00 to 2027-11-21 00:00 | 8 hours ahead | 0 h | 2 h | 0 h | 6 h |

## Meeting windows from 2026-11-21 00:00 UTC

Representative date: 2026-11-23. No shared 09:00–17:00 working hours.



**London and Singapore: shared working hours**

2026-11-23 in Europe/London; axis in UTC. Overlap: no shared working hours.

| Zone | IANA | Working hours (local) | Working intervals (UTC, 2026-11-23) | Shared hours (local) |
| --- | --- | --- | --- | --- |
| London | Europe/London | 09:00–17:00 | 09:00–17:00 | None |
| Singapore | Asia/Singapore | 09:00–17:00 | 01:00–09:00 | None |


### Ranked one-hour options

Outside the standard workday, using 07:00–21:00. Ranked by the smallest worst distance from 12:30 in either city, then the combined distance; ties use the earlier UTC time.


| Rank | London | Singapore | Day boundary |
| --- | --- | --- | --- |
| 1 | Mon 08:00–09:00 | Mon 16:00–17:00 | Same local date |
| 2 | Mon 07:30–08:30 | Mon 15:30–16:30 | Same local date |
| 3 | Mon 08:30–09:30 | Mon 16:30–17:30 | Same local date |

For recurring calls, rotate the burden: week 1 uses London's morning and Singapore's evening; week 2 reverses the preference. Agree the exception together and recheck both dates before sending invitations.


### If it is morning or afternoon in London

| London | Singapore | Date check |
| --- | --- | --- |
| Mon 09:00 | Mon 17:00 | Same local date |
| Mon 10:00 | Mon 18:00 | Same local date |
| Mon 11:00 | Mon 19:00 | Same local date |
| Mon 12:00 | Mon 20:00 | Same local date |
| Mon 13:00 | Mon 21:00 | Same local date |
| Mon 14:00 | Mon 22:00 | Same local date |
| Mon 15:00 | Mon 23:00 | Same local date |
| Mon 16:00 | Tue 00:00 | Different local date |

## Meeting windows from 2027-03-28 01:00 UTC

Representative date: 2027-03-29. Mon 09:00–10:00 in London / Mon 16:00–17:00 in Singapore



**London and Singapore: shared working hours**

2027-03-29 in Europe/London; axis in UTC. Overlap: 09:00–10:00 London / 16:00–17:00 Singapore

| Zone | IANA | Working hours (local) | Working intervals (UTC, 2027-03-29) | Shared hours (local) |
| --- | --- | --- | --- | --- |
| London | Europe/London | 09:00–17:00 | 08:00–16:00 | 09:00–10:00 |
| Singapore | Asia/Singapore | 09:00–17:00 | 01:00–09:00 | 16:00–17:00 |


### Ranked one-hour options

Within 09:00–17:00. Ranked by the smallest worst distance from 12:30 in either city, then the combined distance; ties use the earlier UTC time.


| Rank | London | Singapore | Day boundary |
| --- | --- | --- | --- |
| 1 | Mon 09:00–10:00 | Mon 16:00–17:00 | Same local date |

### If it is morning or afternoon in London

| London | Singapore | Date check |
| --- | --- | --- |
| Mon 09:00 | Mon 16:00 | Same local date |
| Mon 10:00 | Mon 17:00 | Same local date |
| Mon 11:00 | Mon 18:00 | Same local date |
| Mon 12:00 | Mon 19:00 | Same local date |
| Mon 13:00 | Mon 20:00 | Same local date |
| Mon 14:00 | Mon 21:00 | Same local date |
| Mon 15:00 | Mon 22:00 | Same local date |
| Mon 16:00 | Mon 23:00 | Same local date |

## Meeting windows from 2027-10-31 01:00 UTC

Representative date: 2027-11-01. No shared 09:00–17:00 working hours.



**London and Singapore: shared working hours**

2027-11-01 in Europe/London; axis in UTC. Overlap: no shared working hours.

| Zone | IANA | Working hours (local) | Working intervals (UTC, 2027-11-01) | Shared hours (local) |
| --- | --- | --- | --- | --- |
| London | Europe/London | 09:00–17:00 | 09:00–17:00 | None |
| Singapore | Asia/Singapore | 09:00–17:00 | 01:00–09:00 | None |


### Ranked one-hour options

Outside the standard workday, using 07:00–21:00. Ranked by the smallest worst distance from 12:30 in either city, then the combined distance; ties use the earlier UTC time.


| Rank | London | Singapore | Day boundary |
| --- | --- | --- | --- |
| 1 | Mon 08:00–09:00 | Mon 16:00–17:00 | Same local date |
| 2 | Mon 07:30–08:30 | Mon 15:30–16:30 | Same local date |
| 3 | Mon 08:30–09:30 | Mon 16:30–17:30 | Same local date |

For recurring calls, rotate the burden: week 1 uses London's morning and Singapore's evening; week 2 reverses the preference. Agree the exception together and recheck both dates before sending invitations.


### If it is morning or afternoon in London

| London | Singapore | Date check |
| --- | --- | --- |
| Mon 09:00 | Mon 17:00 | Same local date |
| Mon 10:00 | Mon 18:00 | Same local date |
| Mon 11:00 | Mon 19:00 | Same local date |
| Mon 12:00 | Mon 20:00 | Same local date |
| Mon 13:00 | Mon 21:00 | Same local date |
| Mon 14:00 | Mon 22:00 | Same local date |
| Mon 15:00 | Mon 23:00 | Same local date |
| Mon 16:00 | Tue 00:00 | Different local date |

## Working between London and Singapore

London finance teams and Singapore regional offices have a narrow handover near London's opening and Singapore's closing. Use the first part of London's day, with questions circulated beforehand so Singapore can answer them before the call. A later London meeting needs the Singapore participant's agreement to work into the evening. Make that choice explicit. Singapore has no daylight saving. London's March clock advance makes the ordinary office-hours handover more accessible, while the October return can remove a full shared hour from a standard-day arrangement. Check the dated window before repeating a summer offer in winter. Create a separate early London schedule for the booking link, with starts ending before the Singapore team's agreed finish. Preview the link in Asia/Singapore and use [one-off times](https://meet.barq.dev/guides/one-off-meeting-links) for a board or regional planning session that needs a longer exception.


## Other cities on these rules

London: Dublin, Lisbon (same offsets). Singapore: Manila, Kuala Lumpur, Hong Kong, Shanghai, Taipei, Perth. Choose each participant’s city or time zone when booking.


## Set up a booking schedule

Set the schedule time zone to `Europe/London`. There is no shared 09:00–17:00 slot in the period starting 2026-11-21. Agree an early or late exception before adding availability. Review the dated periods before repeating these hours across a clock change. Barq Meet converts a booking link to each guest's zone and checks connected calendars.


## Explore this corridor

[Meeting times between Europe and Asia](https://meet.barq.dev/meeting-planner/europe-and-asia) · [Time-zone overlap atlas](https://meet.barq.dev/meeting-planner/time-zone-overlap-atlas) · [Time-zone scheduling guide](https://meet.barq.dev/guides/scheduling-across-time-zones).


- [London and Karachi](https://meet.barq.dev/meeting-planner/london-and-karachi)
- [London and India](https://meet.barq.dev/meeting-planner/london-and-india)
- [London and Tokyo](https://meet.barq.dev/meeting-planner/london-and-tokyo)
- [London and Sydney](https://meet.barq.dev/meeting-planner/london-and-sydney)
- [Berlin and India](https://meet.barq.dev/meeting-planner/berlin-and-india)
- [Berlin and Singapore](https://meet.barq.dev/meeting-planner/berlin-and-singapore)


Time-zone source: [IANA time-zone database](https://www.iana.org/time-zones). Local time-zone rules can change.

## Frequently asked questions

### How do I convert London time to Singapore time?

For 2026-11-21, Singapore runs at 8 hours ahead versus London. The hourly rows show the conversion in both cities.

### Should I recheck London–Singapore calls after a clock change?

Recheck recurring calls at the listed transitions. Singapore moves between 8 hours ahead and 7 hours ahead relative to London during this window.

### Can both London and Singapore keep a 09:00–17:00 day?

The current overlap is 0 hours, too short for an hour-long call. Alternate early and late meetings instead of asking one city to absorb every change.

## Related pages

- [Meeting times between Europe and Asia](https://meet.barq.dev/meeting-planner/europe-and-asia)
- [Working-hours overlap between business hubs](https://meet.barq.dev/meeting-planner/time-zone-overlap-atlas)
- [How to schedule meetings across time zones](https://meet.barq.dev/guides/scheduling-across-time-zones)
- [Best time to meet: London and Karachi (2026)](https://meet.barq.dev/meeting-planner/london-and-karachi)
- [Best time to meet: London and India (2026)](https://meet.barq.dev/meeting-planner/london-and-india)
- [Best time to meet: London and Tokyo (2026)](https://meet.barq.dev/meeting-planner/london-and-tokyo)
- [Best time to meet: London and Sydney (2026)](https://meet.barq.dev/meeting-planner/london-and-sydney)
- [Best time to meet: Berlin and India (2026)](https://meet.barq.dev/meeting-planner/berlin-and-india)
- [Best time to meet: Berlin and Singapore (2026)](https://meet.barq.dev/meeting-planner/berlin-and-singapore)

[Create your free booking link](https://meet.barq.dev/app/sign-in)
