Time in Cocos Islands — regions, cities and time zones

Current time in West Island

The Cocos (Keeling) Islands keep UTC+6:30 throughout the year. West Island, where the airport and most administration sit, uses that offset, as does Home Island. There is no daylight saving on the territory.

The half-hour offset explained

UTC+6:30 is one of the rarer offsets in use anywhere. Most of the world settles on whole hours; a handful of places keep a thirty-minute step, and a very few use forty-five minutes. The Cocos Islands are firmly in the half-hour club, which means that converting to almost anywhere else leaves you with a :30 hanging off the end of the answer.

It is not an error and not a legacy quirk waiting to be tidied up. It is the territory's actual civil time, and flight schedules, opening hours and everything else are published against it. If your time conversion for the Cocos Islands comes out on a round hour, you have made a mistake somewhere.

Two inhabited islands, one clock

The territory is a pair of atolls with a very small population spread across two inhabited islands: West Island — the administrative centre, with the airstrip and most services. Home Island — the other inhabited island, connected by a short ferry crossing.

The ferry between them does not cross a time boundary, and neither does anything else in the territory. Whatever the clock says on one island, it says on the other.

Neighbours and near neighbours

The Cocos Islands sit in the Indian Ocean, geographically closer to Indonesia than to Australia despite being an Australian external territory. That produces some offsets worth knowing: The islands are half an hour behind Christmas Island, the other Australian territory in the region, which keeps UTC+7.

They are well behind mainland Australian capitals — a call to Sydney or Perth needs real arithmetic, and the Sydney gap changes seasonally when daylight saving applies there. Against UTC the offset is fixed, so the islands are always the stable half of any pairing.

Planning around a rare offset

The main risk with an unusual offset is software that handles it badly, or a person who rounds it. Both produce the same failure: someone arrives thirty minutes early or thirty minutes late, and each blames the other's calendar. The fix is to write the offset out in full when it matters, and to use a named time zone rather than a typed-in number for anything recurring. Booking a flight is the case where this bites hardest — departure times are local, the half hour is real, and the airport is not large enough to absorb a mistake gracefully.