UTC+13:45 — the time, and everywhere that is on it
Nowhere is at UTC+13:45 at this moment. It is a seasonal offset: 1 zone reaches it for one half of the year, when their clocks change, and leave it for the other half. The panel below still reads it against your own day, because a timestamp stamped +13:45 out of season is exactly the case that needs explaining.
Reading your clock…
Zones that visit UTC+13:45
Read from the IANA database at build time. A zone appears here because it is at this offset now, not because it always is.
An offset is not a time zone
This is the one thing worth taking away from a page like this. UTC+13:45 describes a clock at a single instant: it is 13.75 hours ahead of UTC, right now. It says nothing about what that clock will read in March, because it carries no rules. A time zone does. Pacific/Chatham is a promise about the whole year, including the mornings when the clocks move.
That is why the list above is dated rather than fixed. Between January and July, 1 zone join or leave this offset without anything about them changing except the season. If you store +13:45 in a database and someone books a recurring meeting against it, half that series will be wrong after the next changeover, and it will be wrong quietly.
UTC+13:45 is one of the offsets that is not a whole number of hours, and a quarter-hour one at that — the rarest kind on Earth. It is worth testing software against: code that assumes an offset divides evenly into hours works perfectly until someone here opens it, at which point meetings land 45 minutes out and nobody can reproduce it.
This is one of the ends of the world. The inhabited planet spans 26 hours of offsets rather than 24, so at any moment there are at least two calendar dates in use and, for about two hours either side of midnight in London, three. An offset this far out is on the far side of that seam: it shares working hours with almost nowhere, and its calendar date is frequently not the same as yours.
The practical reading of the band above: the top row is the day at UTC+13:45, the bottom row the same hours on your own clock, aligned by instant rather than by number. Tap any hour and it is read out as a sentence. The green block is a conventional nine-to-five, which is the part most people are really trying to line up.
How to use this
- The clock is live and computed as arithmetic on UTC, so it is right regardless of what your own device thinks the rules are.
- The band puts your day under theirs, aligned by instant. Tap an hour to read the pair out.
- The zone list is generated at build time from the IANA database — the same source your operating system uses.
Worth knowing: Membership of an offset changes with the seasons. If you need a time to survive a daylight-saving change, use the IANA zone name rather than the number.
FAQ
What time is it at UTC+13:45?
The clock above is live and reads it directly, along with what that hour is on your own clock. It runs 13.75 hours ahead of UTC, so take the UTC time and add 13.75 hours.
Which countries are at UTC+13:45?
None all year. The zones that reach it do so only when their clocks change: Chatham.
Is UTC+13:45 a time zone?
No, and the difference matters. An offset says how far a clock is from UTC at one instant. A time zone — America/New_York, Europe/Oslo — carries the rules as well, including when the clocks change and by how much. Two places can share an offset today and be an hour apart next month. Store the zone, never the offset.
Why is UTC+13:45 not a whole hour?
Because time zones follow politics and solar noon rather than arithmetic. Quarter-hour offsets like this one are the rarest kind — a handful of places chose 45 minutes to sit closer to their own sun than any whole-hour zone would allow. They are also the offsets that break naive software, which tends to assume an offset divides evenly into hours.