ForHosting KIT · Travel & geography

Time difference between cities calculator

At 15:00 in New York (UTC−5) it is 05:00 the next day in Tokyo (UTC+9), a 14-hour difference. Type both cities, their UTC offsets and the local time to plan a call or a trip. Free in your browser.

  • Free
  • Runs in your browser
  • No sign-up
  • Your data stays on your device
Use it from WebAPIEmailTelegramApp soon
If you enter
City a
New York
Utc a
-5
City b
Tokyo
Utc b
9
Hour
15
Minute
0
You get
Utc a label
UTC-5
Utc b label
UTC+9
Time a
15:00
Time b
05:00

A time difference between cities calculator answers the everyday travel and calling question: if it is a given local hour in one city, what time is it in the other, and how many hours sit between those two clocks? You name both cities and supply each city's fixed UTC offset in hours—minus five for New York on standard time, plus nine for Tokyo, plus twelve for Auckland, minus ten for Honolulu—plus the local hour and optional minute in the first city. The solver returns the signed hour difference, both local clocks as HH:MM, the calendar-day shift after midnight wrap, a shortest-path wrap into a plus-or-minus twelve hour window, and a flag that marks when the two offsets sit more than half a day apart, which is the civil-offset signature of a date-line crossing. Offsets outside plus or minus fourteen hours are rejected.

How the hour gap and both local clocks are computed

Every civil city clock can be written as a fixed offset from Coordinated Universal Time once you already know the seasonal schedule you care about. New York on Eastern Standard Time is UTC minus five; Tokyo is UTC plus nine; Delhi is UTC plus five and a half; Adelaide is UTC plus nine and a half; Kathmandu is UTC plus five and three quarters.

This calculator never looks up those numbers for you: you type the city names as labels and the two offsets as hours, then you give the local hour—and optionally the minute—already showing on the first city's clock. The signed hour difference is always offset of city B minus offset of city A. That single subtraction is the number of hours you add to the first city's local time to obtain the second city's local time at the same instant.

Work proceeds in whole minutes so half-hour and quarter-hour zones stay exact: the difference is multiplied by sixty and rounded to the nearest minute, then added to hour times sixty plus minute. The resulting minute total is folded back into a twenty-four-hour clock. Whatever remains after removing complete days is the HH:MM in city B; the number of complete days removed is the calendar-day offset, which can be minus two through plus two at the real extremes of UTC minus fourteen and UTC plus fourteen.

When the two cities share an offset the clocks match and the day offset is zero. When they do not, the response names which city is ahead, prints both clocks, and lists the substitution steps so you can check the arithmetic by hand before you book a call or a meeting.

Day rollover across the International Date Line

The International Date Line is the civil seam near one hundred eighty degrees longitude where the calendar date jumps. Cities on the far-east side of that seam use large positive offsets such as UTC plus twelve in Auckland, UTC plus thirteen in Samoa, or UTC plus fourteen on the Line Islands. Cities on the far-west side use large negative offsets such as UTC minus ten in Honolulu, UTC minus eleven in American Samoa, or UTC minus twelve on Baker Island.

Subtracting those offsets can produce a gap larger than twelve hours and, at the extremes, larger than twenty-four hours, so adding the gap to a local clock can land not only on the previous or next calendar day but two days away. Classic pairs illustrate the contract. Fifteen hundred in New York at UTC minus five is zero five hundred the next calendar day in Tokyo at UTC plus nine, a plus fourteen hour gap that flags the date line and wraps to minus ten hours the other way.

Noon in Auckland at UTC plus twelve is fourteen hundred the previous calendar day in Honolulu at UTC minus ten, a minus twenty-two hour gap that wraps to plus two hours. Nine in the morning in Samoa at UTC plus thirteen is nine in the morning the previous day in American Samoa at UTC minus eleven: same clock face, twenty-four hours and one calendar day apart.

Use those fields when you need to tell a traveler whether to write Tuesday or Wednesday on a boarding pass, not only what the wall clock will read.

Schedule a call across an ocean

Pick a local hour in your city, enter the other city's UTC offset, and read both clocks plus the calendar-day note before you send a meeting invite.

Check a date-line travel day

Compare Auckland with Honolulu or Samoa with American Samoa and see whether the destination calendar is yesterday, today, or two days off.

Write city clocks into a trip brief

Label two cities, pin their published UTC± offsets, and drop the HH:MM pair and hour gap into an itinerary without opening a timezone database.

How do I find the time difference between two cities?

Enter both city names, each city's fixed UTC offset in hours, and the local hour in the first city.

Why can the calendar day differ when the clocks look close?

Across the date line the raw gap can be 22 or 24 hours. Clock faces may look only two hours apart, or even identical, while city B is on the previous or next calendar day.

Does this look up time zones from the city name?

No. City names are display labels only. You supply the fixed UTC offsets. The solver does not call a timezone database, apply DST, or read the host clock.

How do I handle daylight saving time?

Choose the offsets for the season you care about before you enter them. The calculator uses the fixed offsets you type, so New York is minus five on standard time; in summer you would enter its summer offset instead.

Does it work with half-hour and quarter-hour time zones?

Yes. Offsets can be fractional, such as plus five and a half for Delhi, plus nine and a half for Adelaide or plus five and three quarters for Kathmandu. The arithmetic runs in whole minutes, so these zones stay exact.

Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.

POSThttps://api.kit.forhosting.com/travel/time-difference-cities

Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.

curl -X POST https://api.kit.forhosting.com/travel/time-difference-cities \
  -H "Authorization: Bearer $KIT_KEY" \
  -H "Content-Type: application/json" \
  -d '{"city_a":"New York","utc_a":-5,"city_b":"Tokyo","utc_b":9,"hour":15}'
{
  "city_a": "New York",
  "utc_a": -5,
  "city_b": "Tokyo",
  "utc_b": 9,
  "hour": 15
}
{
  "task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
  "type": "travel.time_difference_cities",
  "status": "queued",
  "_links": {
    "result": "/tasks/tsk_…/result"
  }
}

The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.

Per request$0.002

Published price — no tokens, no invented credits. A failed task is never charged.

max_abs_offset_hours14
max_city_len80
HTTPCodeMeaning
401unauthorizedMissing or invalid API key.
402insufficient_balanceYour balance doesn't cover the task price.
404unknown_typeThat task type doesn't exist.
429rate_limitedToo many requests. Use the webhook instead of polling.

Day rollover across the International Date Line

This endpoint treats that situation as first-class data rather than an afterthought. The field hour_diff is the raw signed gap. The field hour_diff_wrapped maps that gap onto the unique representative in the open-closed interval from minus twelve through plus twelve, which is the shorter way around the twenty-four-hour clock. The boolean crosses_date_line is true precisely when the absolute raw gap is strictly greater than twelve hours—the civil-offset test that the two clocks sit more than half a day apart.

Input contract, errors, and when this landing is the right tool

Search intent here is the consumer query time difference between cities, not a raw timezone-offset identity and not a flight-duration arrival clock. Resolve daylight-saving yourself before you pick the offsets, or use a named-zone converter when you only have IANA identifiers. POST a JSON body with five required fields and one optional field. city_a and city_b are non-empty names of at most eighty characters after trim; they are labels for the result, not keys into a timezone database. utc_a and utc_b are finite UTC offsets in hours, inclusive of minus fourteen through plus fourteen, and they may be fractional so that India, Nepal, and the Australian half-hour zones stay honest. hour is the integer local hour in city A on a twenty-four-hour clock from zero through twenty-three. minute is optional, defaults to zero, and must be an integer from zero through fifty-nine when present. Aliases are accepted in transport: from_city, city, or a_name for city_a; to_city or b_name for city_b; offset_a, from_offset, or utc_from for utc_a; offset_b, to_offset, or utc_to for utc_b; hour_a, h, or local_hour for hour; minute_a, m, or local_minute for minute. Missing names, empty strings, non-finite offsets, hours or minutes outside their ranges, non-integer hour or minute, and any offset whose absolute value exceeds fourteen hours all fail with invalid_input naming the field; those failures are not billed. On success the body echoes the cities, rounded offsets, UTC± labels, the input clock, both HH:MM strings, the signed and absolute and wrapped hour gaps, day_offset and day_label, the date-line flag, ahead_city and behind_city, a one-line message, and the ordered steps. Successful API calls cost $0.002 per request; invalid input does not consume prepaid balance.

What does crosses_date_line mean?

It is true when the absolute hour difference is greater than 12. That civil-offset test marks clocks more than half a day apart, the usual signature of a Pacific / date-line pair.

What does the time difference between cities calculator cost?

The browser tool is free. API requests use prepaid KIT balance at $0.002 per successful call; invalid input is not billed.

Read the full KIT documentation →