Wellington is 13 hours ahead UTC in winter and 12 hours ahead UTC in summer — 13 hours ahead of UTC in winter. Its standard offset is UTC+12:00, moving to UTC+13:00 when daylight saving is in effect. This page explains the difference, shows it month by month, and gives the conversion tables in both directions.
Try the tool: UTC Converter — convert any time between UTC and Wellington, with the offset for the date you pick.
How far is Wellington from UTC?
The difference between Wellington and UTC is the offset: UTC+12:00 in standard time and UTC+13:00 in daylight saving time. When it is noon in Wellington, it is still morning in London — the day in Wellington is 13 hours ahead the day at Greenwich. The sign matters: a positive offset means ahead of UTC (east of Greenwich), a negative offset means behind it (west of Greenwich).
In practical terms, the difference means that the working day in Wellington (09:00–17:00 local) is 20:00–04:00 UTC in January and 21:00–05:00 UTC in July. A team that schedules in UTC needs to know both numbers, because a meeting set for 15:00 UTC is 04:00 in Wellington in January and 03:00 in July — and one of those may be outside the working day even when the other is inside it.
Wellington vs UTC through the year
The offset on the 15th of each month in 2026. If the table shows one value all year, Wellington does not observe daylight saving. If it shows two values, the change between them is the clock change.
| Month | Offset from UTC |
|---|---|
| January | UTC+13:00 |
| February | UTC+13:00 |
| March | UTC+13:00 |
| April | UTC+12:00 |
| May | UTC+12:00 |
| June | UTC+12:00 |
| July | UTC+12:00 |
| August | UTC+12:00 |
| September | UTC+12:00 |
| October | UTC+13:00 |
| November | UTC+13:00 |
| December | UTC+13:00 |
The clock changes are: in 2026, Sunday, 5 April 2026, Sunday, 27 September 2026; in 2027, Sunday, 4 April 2027, Sunday, 26 September 2027. For the full story, see the Wellington DST 2026 page and the daylight saving checker.
Conversion tables
UTC to Wellington, for eight hours of the day:
| UTC | Wellington (January) | Wellington (July) |
|---|---|---|
| 00:00 | 13:00 | 12:00 |
| 03:00 | 16:00 | 15:00 |
| 06:00 | 19:00 | 18:00 |
| 09:00 | 22:00 | 21:00 |
| 12:00 | 01:00 | 00:00 |
| 15:00 | 04:00 | 03:00 |
| 18:00 | 07:00 | 06:00 |
| 21:00 | 10:00 | 09:00 |
Wellington to UTC, for the same eight hours:
| Wellington local | UTC (January) | UTC (July) |
|---|---|---|
| 00:00 | 11:00 | 12:00 |
| 03:00 | 14:00 | 15:00 |
| 06:00 | 17:00 | 18:00 |
| 09:00 | 20:00 | 21:00 |
| 12:00 | 23:00 | 00:00 |
| 15:00 | 02:00 | 03:00 |
| 18:00 | 05:00 | 06:00 |
| 21:00 | 08:00 | 09:00 |
Two things to watch in these tables. First, the date: a UTC time in the evening is the next day in Wellington when the offset is positive — 21:00 UTC is 10:00 the next day in Wellington in January — and a Wellington time early in the morning is the previous day in UTC when the offset is positive. Second, the season: the January and July columns differ by an hour, which is daylight saving. The UTC to Wellington page has the full 24-hour table.
Daylight saving and the difference
Wellington observes daylight saving, so the difference from UTC is not constant. In 2026 the clocks go back on Sunday, 5 April 2026 and forward again on Sunday, 27 September 2026; in 2027 the clocks go back on Sunday, 4 April 2027 and forward again on Sunday, 26 September 2027. Between those dates the difference is 13 hours ahead UTC; outside them it is 12 hours ahead UTC. The change happens at 2am local time in most places, so the hour from 02:00 to 03:00 does not exist on the spring change day and happens twice on the autumn change day.
What the difference means for scheduling
For a team that works in UTC — software, aviation, science — the difference is the number you add to every UTC time to get Wellington time, and the number you subtract from every Wellington time to get UTC. The mistake is to use one number all year when there are two. The safe habit is to put the UTC time in every invitation as well as the local time, and to let the calendar do the conversion: a calendar event set in UTC moves correctly when daylight saving changes, and an event set in local time does not always.
For comparison, two other major cities: London is the same time UTC in January and 1 hour ahead UTC in July, and Tokyo is 9 hours ahead UTC all year. Wellington's difference of 13 hours ahead (January) sits between them in the sense that matters for scheduling: a meeting at 14:00 UTC is 03:00 in Wellington, 14:00 in London and 23:00 in Tokyo in January. The time in Wellington page has the working-hours tables, and the meeting planner finds the overlap for any pair of cities.
Wellington vs UTC: the numbers at a glance
| Fact | Value |
|---|---|
| Standard offset | UTC+12:00 |
| Daylight saving offset | UTC+13:00 |
| Offset in January 2026 | UTC+13:00 |
| Offset in July 2026 | UTC+12:00 |
| Difference from UTC in January | 13 hours ahead |
| Difference from UTC in July | 12 hours ahead |
| IANA time zone | Pacific/Auckland |
| Country | New Zealand |
Adjusting to the difference — travel and jet lag
Travelling to Wellington from London means setting your watch forward by 13 hours in January — you lose time going east, and the first day feels short. Travelling the other way, from Wellington to London, you gain the hours back. The rule of thumb for jet lag is that it takes about a day to adjust for each hour of difference when travelling east, and a little less when travelling west — so a trip from London to Wellington in January takes most travellers about 13 days to fully adjust to, while the return trip is usually easier. The practical advice is the same in both directions: get sunlight in the morning at your destination, avoid naps longer than 20 minutes, and do not schedule important meetings for the first morning after you arrive.
The same arithmetic applies to remote work. If you are in Wellington and your team works in UTC, your working day of 09:00–17:00 local time is 20:00–04:00 UTC in January — so a stand-up at 09:00 UTC is 22:00 for you, and a stand-up at 16:00 UTC is 05:00. If those times are outside your working day, the meeting is in the wrong place in the day, and the fix is to move the UTC time, not to ask one person to work at midnight. The meeting time finder finds the hours that work for a whole team, and the time in Wellington page has the working-hours tables.
Frequently asked questions
How many hours is Wellington ahead of UTC?
Wellington is 13 hours ahead UTC in January and 12 hours ahead UTC in July. The difference changes with daylight saving.
Is Wellington ahead of or behind UTC?
Wellington is ahead of UTC — its offset is positive (UTC+13:00 in January), so local time is later than UTC.
Does the time difference between Wellington and UTC change?
Yes — it is 12 hours ahead in standard time and 13 hours ahead in daylight saving time. In 2026 the clocks go back on Sunday, 5 April 2026 and forward again on Sunday, 27 September 2026.
What is Wellington's UTC offset?
Wellington's standard offset is UTC+12:00, and its daylight saving offset is UTC+13:00. Its IANA time zone is Pacific/Auckland.
When it is midnight UTC, what time is it in Wellington?
It is 13:00 in January and 12:00 in July — the same day, because the offset is positive.
Sources
- IANA Time Zone Database, via Node.js Intl (
Intl.DateTimeFormatwithtimeZone) — offsets, daylight saving dates and local times in this article were worked out from the IANA database, not typed from memory. - TimeFlow's own time-zone data (
data/cities.ts,data/dst.ts), computed from the IANA database. - TimeFlow's UTC converter and world clock — the live tools behind the numbers on this page.
- Time-zone and daylight saving rules are set by governments and can change. For flights, deadlines and meetings that cannot move, confirm the time with an official source.