Explore · time zones
London to American Samoa converter
UK Time (GMT/BST) (London) → Samoa Standard Time (American Samoa) (Pago Pago)
Quick answer
The difference changes with daylight saving time. Pago Pago is 11 hours behind London from Jan 1, 2026 to Mar 29, 2026 01:00 UTC (London on GMT · UTC+0); 12 hours behind London from Mar 29, 2026 01:00 UTC to Oct 25, 2026 01:00 UTC (London on BST · UTC+1); 11 hours behind London from Oct 25, 2026 01:00 UTC to Dec 31, 2026 (London on GMT · UTC+0).
- Jan 1, 2026 to Mar 29, 2026 01:00 UTCLondon (GMT, UTC+0) → Pago Pago (SST, UTC−11)Pago Pago is 11 hours behind London
- Mar 29, 2026 01:00 UTC to Oct 25, 2026 01:00 UTCLondon (BST, UTC+1) → Pago Pago (SST, UTC−11)Pago Pago is 12 hours behind London
- Oct 25, 2026 01:00 UTC to Dec 31, 2026London (GMT, UTC+0) → Pago Pago (SST, UTC−11)Pago Pago is 11 hours behind London
9:00 AM GMT (UTC+0) in London is 10:00 PM SST (UTC−11) in Pago Pago, the previous day. Pago Pago is 11 h behind London.
| Format | Result | Copy |
|---|---|---|
| Pago Pago, American SamoaSST · UTC−11 · Tuesday, January 13, 2026 · the previous day | 10: | |
| ISO 8601UTC | 2026- | |
| Unix seconds | 1768381200 | |
| RFC 2822UTC | Wed, |
Conversions use London (Europe/London) and Pago Pago (Pacific/Pago_Pago). Other cities reached through search aliases may have different historical rules.
Current time in London and Pago Pago
Hour by hour: London (GMT, UTC+0) → Pago Pago (SST, UTC−11)
There is no time when both London and Pago Pago are inside 9:00–17:00.
| London | Pago Pago | Day |
|---|---|---|
| 12:00 AM | 1:00 PM | previous day |
| 1:00 AM | 2:00 PM | previous day |
| 2:00 AM | 3:00 PM | previous day |
| 3:00 AM | 4:00 PM | previous day |
| 4:00 AM | 5:00 PM | previous day |
| 5:00 AM | 6:00 PM | previous day |
| 6:00 AM | 7:00 PM | previous day |
| 7:00 AM | 8:00 PM | previous day |
| 8:00 AM | 9:00 PM | previous day |
| 9:00 AM | 10:00 PM | previous day |
| 10:00 AM | 11:00 PM | previous day |
| 11:00 AM | 12:00 AM | same day |
| 12:00 PM | 1:00 AM | same day |
| 1:00 PM | 2:00 AM | same day |
| 2:00 PM | 3:00 AM | same day |
| 3:00 PM | 4:00 AM | same day |
| 4:00 PM | 5:00 AM | same day |
| 5:00 PM | 6:00 AM | same day |
| 6:00 PM | 7:00 AM | same day |
| 7:00 PM | 8:00 AM | same day |
| 8:00 PM | 9:00 AM | same day |
| 9:00 PM | 10:00 AM | same day |
| 10:00 PM | 11:00 AM | same day |
| 11:00 PM | 12:00 PM | same day |
Hour by hour: London (BST, UTC+1) → Pago Pago (SST, UTC−11)
There is no time when both London and Pago Pago are inside 9:00–17:00.
| London | Pago Pago | Day |
|---|---|---|
| 12:00 AM | 12:00 PM | previous day |
| 1:00 AM | 1:00 PM | previous day |
| 2:00 AM | 2:00 PM | previous day |
| 3:00 AM | 3:00 PM | previous day |
| 4:00 AM | 4:00 PM | previous day |
| 5:00 AM | 5:00 PM | previous day |
| 6:00 AM | 6:00 PM | previous day |
| 7:00 AM | 7:00 PM | previous day |
| 8:00 AM | 8:00 PM | previous day |
| 9:00 AM | 9:00 PM | previous day |
| 10:00 AM | 10:00 PM | previous day |
| 11:00 AM | 11:00 PM | previous day |
| 12:00 PM | 12:00 AM | same day |
| 1:00 PM | 1:00 AM | same day |
| 2:00 PM | 2:00 AM | same day |
| 3:00 PM | 3:00 AM | same day |
| 4:00 PM | 4:00 AM | same day |
| 5:00 PM | 5:00 AM | same day |
| 6:00 PM | 6:00 AM | same day |
| 7:00 PM | 7:00 AM | same day |
| 8:00 PM | 8:00 AM | same day |
| 9:00 PM | 9:00 AM | same day |
| 10:00 PM | 10:00 AM | same day |
| 11:00 PM | 11:00 AM | same day |
Worked examples
| When | London | Pago Pago | ISO 8601 (UTC) | Unix |
|---|---|---|---|---|
| a winter weekday | 2:00 PM GMT (UTC+0), January 14, 2026 | 3:00 AM SST (UTC−11), January 14, 2026 | 2026-01-14T14:00:00.000Z | 1768399200 |
| a summer weekday | 3:00 PM BST (UTC+1), July 15, 2026 | 3:00 AM SST (UTC−11), July 15, 2026 | 2026-07-15T14:00:00.000Z | 1784124000 |
| New Year | 12:00 AM GMT (UTC+0), January 1, 2027 | 1:00 PM SST (UTC−11), December 31, 2026 | 2027-01-01T00:00:00.000Z | 1798761600 |
The ISO 8601 and Unix columns are the same instant written without a zone — how APIs and databases should store it. Need this for a whole column? Convert a CSV file.
London — UK Time (GMT/BST)
- IANA identifier
- Europe/London
- Standard time
- GMT · UTC+0
- Daylight time
- BST · UTC+1
- On this clock today
- London, Edinburgh, Cardiff, Belfast, Dublin
Places that share this clock as of 2026-11-13 (tzdata 2026f). Conversions for any date use Europe/London; a listed place's past or future rules may differ.
Offset changes 2026–2027
- Mar 29, 2026, 2:00 AM local (2026-03-29 01:00 UTC): clocks go forward to UTC+1 (BST)
- Oct 25, 2026, 1:00 AM local (2026-10-25 01:00 UTC): clocks go back to UTC+0 (GMT)
- Mar 28, 2027, 2:00 AM local (2027-03-28 01:00 UTC): clocks go forward to UTC+1 (BST)
- Oct 31, 2027, 1:00 AM local (2027-10-31 01:00 UTC): clocks go back to UTC+0 (GMT)
GMT (UTC+0) in winter, BST (UTC+1) from the last Sunday of March to the last Sunday of October. Ireland follows the same clock and calls summer time IST (Irish Standard Time), not to be confused with India Standard Time.
American Samoa — Samoa Standard Time (American Samoa)
- IANA identifier
- Pacific/Pago_Pago
- UTC offset
- SST · UTC−11
- Daylight saving
- Not observed
- On this clock today
- Pago Pago, American Samoa
Places that share this clock as of 2026-11-13 (tzdata 2026f). Conversions for any date use Pacific/Pago_Pago; a listed place's past or future rules may differ.
UTC−11. Independent Samoa (Apia) is on UTC+13, a full day ahead, and is not the same zone.
Related conversions
File workspace
Converting a whole column of timestamps?
The free converter handles one value at a time across 82 formats and 92 zones. The file workspace converts an entire CSV column between any two formats and zones, previews the first rows, and leaves unreadable cells exactly as they were.
Offsets and change dates on this page are computed from IANA time zone database 2026f for 2026–2027; the live tool uses the same data.