ClockCC clockcc.com

Hora mundial · Conversor de fusos · Tempo · Feriados · Cotações · Guias de cidades

📖 Evergreen explainer2026-11-14

How to convert a time between cities without getting it wrong

The four mistakes that wreck most cross-time-zone plans — forgetting the date line inside the result, ignoring a clock change near your date, trusting a fixed offset table, and reading an ambiguous autumn hour as unique — and the checks that prevent each one.

Mistake 1: converting the clock and forgetting the date

A converted time is a date plus a clock reading, never a clock reading alone. When it is 09:00 in Beijing it is 20:00 the previous evening in New York; a flight that 'lands at 13:05' after a 12-hour westbound flight lands on a calendar that has barely moved. Always carry the date through the conversion and state it in the message you send: '20:00 on Tuesday in New York' cannot be misread, '20:00 in New York' can.

Mistake 2: using today's offset for next month's meeting

Offsets are rules with dates, not constants. The United States and Europe change their clocks on different Sundays, so for a few weeks each spring and autumn the transatlantic difference is one hour smaller than usual; the southern hemisphere changes on yet other dates. A conversion done with today's offset can be an hour wrong for a meeting three weeks away. Convert the actual date of the event, every time — that is the whole point of a converter that works from IANA rules rather than a printed table.

Mistake 3: treating an autumn hour as one moment

On the night clocks go back, one wall-clock hour happens twice — 01:30 occurs once in daylight time and once in standard time. A serious converter flags this instead of silently picking one reading. If your invitation lands in that overlap, ask which of the two was meant; for anything automated, record the UTC instant alongside the local reading so the ambiguity cannot resurrect itself later.

Mistake 4: assuming a spring hour exists

The mirror image is the spring-forward gap: when clocks jump from 02:00 to 03:00, the hour in between never occurs. Alarms, cron jobs and departures set inside the gap are a classic source of 'it just didn't happen' bugs and missed connections. If a tool accepts a nonexistent time without comment, do not trust its other answers either.

The two-minute checklist

Convert the real date, not today's offset. State the date with the time when you share it. Check whether either city changes its clocks near the date. If the time is in the autumn overlap, pin down which reading was meant. Our converter applies all four checks as part of the conversion itself — the flags are in the result, not in a footnote.

Compartilhar esta página

XFacebookWhatsAppTelegramWeibo

Deste site

🎉 Contagens regressivas ao vivo para os festivais do mundo

Festa da Primavera, Natal, Páscoa, Diwali, a próxima mudança de horário e mais — cada um com sua página e cartão compartilhável.

Ver as contagens →

Deste site

🧰 Ferramentas de tempo gratuitas em uma só caixa

Hora exata com milissegundos, conversor Unix, cronômetro, temporizador, calculadora de duração e de semana/idade.

Abrir a caixa de ferramentas →

Fontes de dados: Open-Meteo (tempo) · ExchangeRate API (cotações, atualização por hora/dia) · Nager.Date (feriados) · Wikipédia (neste dia) · GeoNames (dados básicos das cidades, CC BY 4.0)