Planning dates run from Thu, Jan 1, 2026 through Mon, Dec 31, 2035. Future rules can be revised; review the data version when a distant schedule matters.
More context and planning advice
A stable sampled offset is not a universal shortcut
Buenos Aires uses UTC−03:00 on the displayed 2026 dates. At 09:00 there on 27 October, New York reads 08:00; on 3 November New York reads 07:00. Even with no change in the Buenos Aires row, a colleague’s clock change can move their local meeting time.
A dated view of the local clock
Four examples at 13:00 UTC, calculated with IANA 2026f. These are selected dates, not a live clock.
UTC date
UTC offset
Abbreviation
Local date and time
2026-01-15
UTC−03:00
-03
Thu, 15 Jan 2026 · 10:00
2026-07-15
UTC−03:00
-03
Wed, 15 Jul 2026 · 10:00
2026-10-27
UTC−03:00
-03
Tue, 27 Oct 2026 · 10:00
2026-11-03
UTC−03:00
-03
Tue, 3 Nov 2026 · 10:00
Name the location in an Americas handoff
America/Argentina/Buenos_Aires identifies this city’s rules. A broad label such as “Argentina time” or an offset copied into a note is less useful when another participant needs to reproduce the plan. Add São Paulo or New York as a separate row, then export the same resolved instant for everyone.
Build a plan for this city
Select Buenos Aires, add the other participants, and enter the actual meeting date. The planner uses America/Argentina/Buenos_Aires; the abbreviation in the table is a display label. Adjust working days, hours, and meeting length before choosing a shared window. The supported planning range is 2026–2035.