Converting Between Perth and UK Time Is Simpler Than Most People Make It
The core issue most people run into is that both locations shift daylight saving at different times of year. Perth operates on Australian Western Standard Time (AWST), which is UTC+8 and does not observe DST at all. The UK uses Greenwich Mean Time (UTC+0) in winter and British Summer Time (UTC+1) in summer. That means the offset between them is either 8 hours or 7 hours depending on where we are in the calendar year. Most mistakes happen in the six-week window when one place has switched but the other hasn't. Here's the straightforward method. Take the UK time and add 8 hours for the standard offset. If it's British Summer Time, subtract 1 hour from that result, giving you a 7-hour difference instead. So 9am London during summer equals 4pm Perth. 9am London in winter equals 5pm Perth. That's it. The entire conversion is just figuring out which seasonal regime is active right now and applying the correct number. I spent years scheduling engineering standups between our Perth office and a client in London. The first couple of years I messed this up more often than I'd like to admit. The real headache hits in late March and late October, because the UK shifts first while Perth stays locked on UTC+8 year-round. There's a rough three-week period each season where the offset is wrong if you're just memorizing a single number. I ended up writing a small script that pulls both timezones from IANA's database and flags the transition weeks in my calendar so I wouldn't accidentally book a meeting at the wrong hour. That script has saved me probably fifty wrong-time-zone invites over the years.
The edge case nobody warns you about is the asymmetric DST window. Australia doesn't change clocks, so during the UK's BS period the gap shrinks to 7 hours. But in early April, before Australia would have started its own DST (if it ever did), and especially around late October when the UK falls back, you briefly get a 8-hour gap again while Perth has already been sitting at UTC+8 the whole time. I once scheduled a handoff call assuming a consistent 8-hour gap and showed up to an empty Zoom room at 5pm Perth time when it was actually only 10am in London. The call had been moved to 4pm Perth by the client without much warning. After that, I stopped trusting my memory for anything in those transition months. For most everyday use, you don't need anything fancy. Open a browser, go to a site like timeanddate.com, type in both cities, and compare. If you're doing this repeatedly throughout the year, the IANA timezone database is your friend. The two identifiers you need are Australia/Perth and Europe/London. Any modern programming language or scheduling tool that respects IANA zones will handle the transitions automatically. If you're using something that only accepts fixed UTC offsets like UTC+8 and UTC+0, you're going to hit problems twice a year and you won't know why until you've already caused a missed meeting. There are a few practical things to keep in mind. First, Perth doesn't just lack DST, it lacks any seasonal variation at all. The clock is identical on January 1st and July 1st. The UK, on the other hand, flips between GMT and BST on set dates that align with EU-style scheduling even though the UK has left the bloc. Those dates are the last Sunday in March and the last Sunday in October. Second, if you're coordinating with someone in Edinburgh rather than London, the timezone is the same but you'll occasionally see people confuse the two cities as if they're in different zones. They're not. Third, Perth is significantly ahead of London, not behind. A common beginner error is subtracting instead of adding, which puts you in the previous day entirely.
The biggest limitation of any manual approach is that it breaks down the moment someone in your chain is also shifting or working across multiple zones. If your London contact travels to Frankfurt for a few weeks and forgets to update their timezone, a fixed-offset mental model won't catch that. The only reliable workaround is to always confirm the actual local time in a message before locking in a call, rather than assuming the conversion is still correct. It takes five seconds and prevents most of the friction. If you want a quick reference without looking anything up, remember this: during UK winter the gap is 8 hours, during UK summer the gap is 7 hours. Perth is always ahead. Anything after 5pm Perth time is already early morning in London and probably not a good time for a live conversation unless both sides are used to it. I tend to aim for 10am to 3pm Perth, which lands at 2am to 7am London, and then flip it for the London-friendly slot of 8am to 3pm London, which is 4pm to 11pm Perth. It's not ideal, but it's workable and at least keeps both sides within reasonable waking hours. Australia/Perth and Europe/London are the identifiers to use if you're setting this up in any calendar, spreadsheet, or automation tool. Anything else is just asking for a mismatch during the transition windows.
Get the Full Details
