What is the time difference between Lima and Sydney?

Sydney is 15 hours ahead of Lima. That figure is current — it changes by an hour when either city starts or ends daylight saving, and the exact dates are listed above.

When is the best time to call Sydney from Lima?

There is no time inside normal working hours in both cities, so someone has to take the call outside them. The nearest workable windows are listed above — pick one and alternate who gets the awkward slot.

Does Lima observe daylight saving time?

No. Lima stays on UTC-5 all year, so its clocks never move.

Does Sydney observe daylight saving time?

Yes. Sydney runs on UTC+10 in winter and UTC+11 in summer. The next change is on 2026-10-04, when clocks go forward by 60 minutes.

If it is midday in Lima, what time is it in Sydney?

It is 03:00 in Sydney, and already the following day. That holds for the current offsets; it shifts by an hour around the daylight saving dates listed above.

Which time zones do Lima and Sydney use?

Lima uses America/Lima, currently UTC-5, and Sydney uses Australia/Sydney, currently UTC+10 (AEST). Those identifiers are the ones to use in code — abbreviations are ambiguous and offsets change.

Convert Lima time to Sydney time

Right now Sydney runs 15 hours ahead of Lima. That gap is not fixed: it moves when either city changes its clocks.

Convert a time

From

Date

Time

Converted time

—

The converter needs JavaScript to run. Everything below — offsets, daylight saving dates and the hour-by-hour table — is part of the page and works without it.

Hour by hour

The whole day mapped across: read down the left for Lima, across for Sydney.

Lima	Sydney
00:00	15:00
01:00	16:00
02:00	17:00
03:00	18:00
04:00	19:00
05:00	20:00
06:00	21:00
07:00	22:00
08:00	23:00
09:00	00:00next day
10:00	01:00next day
11:00	02:00next day
12:00	03:00next day
13:00	04:00next day
14:00	05:00next day
15:00	06:00next day
16:00	07:00next day
17:00	08:00next day
18:00	09:00next day
19:00	10:00next day
20:00	11:00next day
21:00	12:00next day
22:00	13:00next day
23:00	14:00next day

Daylight saving time

Lima keeps one offset all year while Sydney moves twice. That is the whole reason this difference is seasonal.

Lima

Does not observe daylight saving time

Standard: UTC-5

Sydney

Observes daylight saving time

Standard: UTC+10
Daylight: UTC+11
Next change: 2026-10-04 +60m

When you can actually talk

A standard working day in Lima and one in Sydney do not overlap at all. Any call between them is early for one side or late for the other.

Lima 19:00–03:00Sydney 10:00–18:00
Lima 09:00–19:00Sydney 00:00–10:00

Reference

The underlying data, in case you need to put it in a calendar invitation or a configuration file.

	Lima	Sydney
IANA zone	America/Lima	Australia/Sydney
Abbreviation	UTC-5	AEST
Standard offset	UTC-5	UTC+10
Daylight offset	—	UTC+11
Clock changes this year	0	2
Country	Peru	Australia

Example, not the current time. Live times appear once the page loads.

Common questions

What is the time difference between Lima and Sydney?: Sydney is 15 hours ahead of Lima. That figure is current — it changes by an hour when either city starts or ends daylight saving, and the exact dates are listed above.
When is the best time to call Sydney from Lima?: There is no time inside normal working hours in both cities, so someone has to take the call outside them. The nearest workable windows are listed above — pick one and alternate who gets the awkward slot.
Does Lima observe daylight saving time?: No. Lima stays on UTC-5 all year, so its clocks never move.
Does Sydney observe daylight saving time?: Yes. Sydney runs on UTC+10 in winter and UTC+11 in summer. The next change is on 2026-10-04, when clocks go forward by 60 minutes.
If it is midday in Lima, what time is it in Sydney?: It is 03:00 in Sydney, and already the following day. That holds for the current offsets; it shifts by an hour around the daylight saving dates listed above.
Which time zones do Lima and Sydney use?: Lima uses America/Lima, currently UTC-5, and Sydney uses Australia/Sydney, currently UTC+10 (AEST). Those identifiers are the ones to use in code — abbreviations are ambiguous and offsets change.