9am in Jakarta is 12pm in Melbourne

Melbourne is 3 hours ahead of Jakarta. Jakarta runs on Asia/Jakarta (UTC+7); Melbourne runs on Australia/Sydney (UTC+10). The difference is measured right now; it can shift by one hour during daylight-saving-time transitions.

Melbourne observes daylight saving time — shifting between AEST (UTC+10) and AEDT (UTC+11) — while Jakarta stays on WIB (UTC+7) year-round. The difference is 3 hours in Melbourne’s winter and 4 hours in Melbourne’s summer. Transitions happen in late March and late October for most Northern-Hemisphere DST zones, and late September/early April for Southern-Hemisphere ones — check the current date against the city’s DST schedule before anchoring a meeting at the edge of those windows.

Standard 9-to-5 business hours in Jakarta and Melbourne overlap for roughly 5 hours a day. That window lands at 09:00–14:00 in Jakarta and 12:00–17:00 in Melbourne. Teams with real-time coordination needs anchor cross-city calls inside it: long enough to cover handovers, short enough that it forces crisp agendas. Outside that window, async is the default — shared docs, recorded updates, and scheduled follow-ups rather than live meetings.

When planning recurring meetings across Jakarta and Melbourne, pin them to one city’s local time rather than UTC or the other city’s clock. That way, the meeting time stays stable for the person anchoring the schedule, and the other side absorbs the one-hour drift during DST transitions. The alternative — a meeting pinned to the non-DST city — means the DST city sees the meeting time “move” twice a year, which is how recurring calendar invites end up at 7am on someone’s calendar in October.