JST is 9 hours ahead of Zulu. Live clocks, the full hour chart and the daylight saving rule that catches people out.
Zulu time is UTC — the clock every flight plan, order and server log is written in, precisely because it never moves. Japan Standard Time (JST) sits UTC+9, which makes it 9 hours ahead of Zulu. Converting one to the other is a single addition, and the only two things that go wrong are the date and daylight saving.
The converter above tracks the current time until you type into it. Enter any Zulu time — 1730Z, 17:30Z or NOW — and it renders the same instant in JST in 24-hour, 12-hour and dated form. The chart below is the same conversion for every hour of the day, so it can be read without typing anything at all.
Every hour from 0000Z to 2300Z. One column is enough — JST keeps the same offset all year. Where the sum crosses midnight the date moves with it, marked in the cell.
| Zulu | JSTUTC+9 |
|---|---|
| 0000Z | 09:00 |
| 0100Z | 10:00 |
| 0200Z | 11:00 |
| 0300Z | 12:00 |
| 0400Z | 13:00 |
| 0500Z | 14:00 |
| 0600Z | 15:00 |
| 0700Z | 16:00 |
| 0800Z | 17:00 |
| 0900Z | 18:00 |
| 1000Z | 19:00 |
| 1100Z | 20:00 |
| 1200Z | 21:00 |
| 1300Z | 22:00 |
| 1400Z | 23:00 |
| 1500Z | 00:00 +1 day |
| 1600Z | 01:00 +1 day |
| 1700Z | 02:00 +1 day |
| 1800Z | 03:00 +1 day |
| 1900Z | 04:00 +1 day |
| 2000Z | 05:00 +1 day |
| 2100Z | 06:00 +1 day |
| 2200Z | 07:00 +1 day |
| 2300Z | 08:00 +1 day |
Take the four digits, add 9 hours, and roll the date if the result falls outside 00:00–23:59. 1730Z becomes 02:30 JST the next day; 0200Z becomes 11:00 JST.
Do the arithmetic in Zulu and convert once, at the end, for whoever needs a local time. Adding en-route time to a departure slot in local time and converting afterwards is how the day boundary gets lost. The Zulu time converter does both halves in one box.
Japan does not observe daylight saving, so JST is UTC+9 every day of the year. The catch is the date, not the hour: any Zulu time from 1500Z onward is already tomorrow in Tokyo.
Because neither clock shifts, a conversion written down today is still right in six months. That is unusual — most of the abbreviations on the sibling pages have a second offset for half the year.
All of Japan on one zone. Yokota, Kadena and Misawa run their local schedules on JST while every order and flight plan is written in Zulu, which makes this the pair where the day shift bites hardest.
Flight plans, METARs, TAFs, NOTAMs and ATC clearances are all in Zulu, and so are military orders, satellite passes and incident timelines. The conversion to JST is the last step, for the people who have to be somewhere at a local hour — a briefing time, a crew report, a maintenance window. Written the aviation way it carries the day of the month too: 141730Z is the 17:30 Zulu of the 14th, which removes the last ambiguity a date shift can create. See military time for the four-digit notation itself.
JST is 9 hours ahead of Zulu (UTC+9). To convert, take the Zulu time and add 9 hours: 1200Z is 21:00 JST.
No. JST stays on UTC+9 all year, so a single conversion works in every season. Zulu does not change either.
0000Z is 09:00 JST.
Yes, for every practical purpose. Zulu is how UTC is written and spoken in aviation and military use — the Z suffix is the phonetic letter for the zero-offset zone. GMT is the older name for the same clock reading, though the UK itself moves to BST in summer.
Reverse the arithmetic: subtract 9 hours and add the Z suffix. Do the maths in Zulu first and convert once at the end — converting first and adding afterwards is where the date boundary gets lost.