A time in Manila, and what it is everywhere that matters — or the other way round, since any zone on the list can be the source.
Every offset is looked up in your browser's copy of the IANA time zone database, for the exact moment you asked about. None is written down. A table of offsets is wrong twice over: wrong for eight months of the year in any zone that keeps daylight saving, and stale as soon as a country changes its rules, which happens somewhere most years. Manila never moves, so the gap changing is always the far end doing it.
Two answers most converters get quietly wrong. On the night clocks go back, a local time happens twice — there really are two instants with that name. On the night they go forward, an hour never happens at all. This page detects both and says so, rather than handing you one of two possible answers with nothing to indicate there was a choice.
No. The country has kept none since 1978, so Manila is UTC+8 all year round. That is why the gap to somewhere like New York or London changes twice a year even though nothing changes here — it is the other end that moves.
Because most of the United States puts its clocks forward in March and back in November. Manila is thirteen hours ahead of New York for part of the year and twelve for the rest. Any converter that quotes a fixed number of hours is wrong for several months of every year.
That the moment falls on a different calendar date there. 8am Monday in Manila is 5pm Sunday in Los Angeles — the same instant, a different day. It is given as much weight as the time itself because getting it wrong misses a call by twenty-four hours rather than by one.
You picked a local time on the night the clocks went back, so it ran once, the clocks turned back, and it ran again. There are genuinely two instants with that local time. This page uses the first — before the change — and tells you rather than choosing silently.
You picked a local time inside the hour that was skipped when the clocks went forward. Nobody in that zone ever saw 2:30am that night. The conversion is worked out from the instant the clock jumped to, so you still get a usable answer alongside the warning.
Your browser’s copy of the IANA time zone database, the same one your operating system uses, looked up for the exact moment you asked about. Nothing is hard-coded here — a table of offsets would be wrong for every zone on daylight saving and would go stale whenever a country changed its rules.
The full database holds over four hundred entries, most of which are duplicates or historical. This list is the places Filipinos actually work and call: the Gulf, East and Southeast Asia, North America, Europe, Australasia, and the islands in between.
Manila is UTC+8 in both. It is New York that moves.
There is no way to ask a browser what instant a local time refers to, so this one guesses from a nearby offset and then checks by converting back. A guess that does not read back is a time that never existed; two that both read back is a time that existed twice.
8am Monday in Manila is 5pm Sunday in Los Angeles. Reading the time and missing the day is how a call gets missed by a whole day rather than an hour, so the day difference is printed beside every result rather than under it.
Offsets come from your browser's IANA time zone database, looked up for the exact moment asked about. Nothing you type here is sent to our servers — the calculation runs entirely in your browser.
