Estimate jet lag adjustment days
Six time zones eastward means about six days to adjust, while the same six zones westward take about four, because advancing your body clock is harder than delaying it. A planning estimate, not a diagnosis. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Time zones crossed
- 6
- Direction
- Eastward
- Days per zone
- 1
- Adjustment days
- 6
- Rule
- About 1 adjustment day per time zone crossed eastward.
Estimate the typical number of days needed to adjust after crossing time zones with a simple, transparent jet lag rule of thumb. Enter how many time zones the trip crosses and whether the journey is eastward or westward. The calculator treats eastward travel as harder because advancing the body clock is generally more difficult than delaying it. It returns a practical whole-day planning estimate, not a diagnosis or personalized sleep schedule.
Understand the direction-aware estimate
Jet lag appears when the local clock at a destination no longer matches the timing expected by a traveler's circadian system. Crossing more time zones usually creates a larger mismatch, but direction matters too. This calculator uses a familiar planning heuristic: allow about one adjustment day for every time zone crossed eastward, and about two adjustment days for every three time zones crossed westward.
The eastward estimate is longer because traveling east asks the body to advance its normal sleep and wake timing. Many people find that shift more difficult than the phase delay associated with westward travel. The result is rounded upward to a whole day so it can be used as a cautious calendar allowance.
For example, six zones eastward produces an estimate of six days, while six zones westward produces four days. This is deliberately a rule of thumb rather than a clinical prediction. Sleep history, age, light exposure, flight timing, stopovers, and personal circadian tendencies can all change the actual experience.
Use the number as a straightforward buffer for plans, then adapt it to what you already know about your own response to long-distance travel.
Enter time zones and travel direction correctly
Provide the positive number of time zones crossed, not the flight duration, distance, or destination's clock reading. A route that changes the local clock by seven hours normally crosses seven time zones for this estimate, even if the aircraft spends more or fewer than seven hours in the air. Fractional values are accepted for itineraries involving half-hour offsets, and the final estimate is still rounded up to a whole planning day.
The supported range ends at twenty-four zones to catch accidental or nonsensical entries. You must also identify the direction as eastward or westward; the shorter forms east and west are accepted and normalized in the result. Zero zones produces an error because there is no time-zone adjustment to estimate, and the capability is specifically designed for trips that cross at least one zone.
Negative values, missing fields, infinite numbers, and unknown direction labels are rejected rather than silently corrected. This strict validation keeps automated results dependable. When a trip has several legs, compare the origin and final destination for a broad estimate.
If long stopovers effectively create separate adjustment periods, calculate each meaningful segment separately and treat the figures as planning signals rather than values to add mechanically.
Use adjustment days as a practical travel buffer
The estimate is most useful before a trip, when you can still protect important events from the roughest adjustment period. A traveler crossing eight zones eastward might avoid scheduling a high-stakes presentation on the first morning and preserve several evenings for regular local sleep. A westward traveler can apply the shorter estimate while remembering that early waking may still disrupt plans.
Travel coordinators can place the result beside itinerary details to communicate why two routes with the same time-zone count receive different buffers. The result should not be used to prescribe melatonin, light therapy, medication, or medical treatment. Those choices depend on health context and precise timing that this simple heuristic does not collect.
What you can do with it
Protect important events
Estimate a sensible arrival buffer before a conference, wedding, examination, or performance after long-distance travel.
Compare travel directions
Show why eastward and westward trips across the same number of zones may need different adjustment allowances.
Add estimates to travel software
Return deterministic whole-day adjustment estimates inside booking, itinerary, and corporate travel workflows.
FAQ
How are jet lag adjustment days estimated?
Eastward travel uses about one day per time zone. Westward travel uses about two days per three time zones, with the result rounded up to a whole day.
Why does eastward travel take longer?
Eastward travel requires the body clock to advance. That shift is commonly considered harder than the phase delay required by westward travel.
Can I enter a fractional time-zone count?
Yes. Positive fractional counts are accepted for places with partial-hour offsets, and the estimated adjustment period is rounded up to a whole day.
How long does it take to adjust after flying west across six time zones?
About four days. Westward travel allows roughly two days for every three zones, so six zones give four days, compared with six days for the same trip eastward.
Should I enter the flight time or the time difference?
Enter the number of time zones crossed, not the hours in the air or the distance. A route that moves the local clock by seven hours counts as seven zones, whatever the flight duration.
Related tools
For developers — API access
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.
API endpoint
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.
Call it from your stack
curl -X POST https://api.kit.forhosting.com/travel2/jet-lag-adjustment-days \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"time_zones_crossed":6,"direction":"eastward"}'const res = await fetch("https://api.kit.forhosting.com/travel2/jet-lag-adjustment-days", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"time_zones_crossed": 6,
"direction": "eastward"
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/travel2/jet-lag-adjustment-days",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"time_zones_crossed": 6,
"direction": "eastward"
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/travel2/jet-lag-adjustment-days", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"time_zones_crossed":6,"direction":"eastward"}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"time_zones_crossed":6,"direction":"eastward"}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/travel2/jet-lag-adjustment-days", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"time_zones_crossed": 6,
"direction": "eastward"
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "travel2.jet_lag_adjustment_days",
"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.
Pricing
Published price — no tokens, no invented credits. A failed task is never charged.
Limits
max_time_zones | 24 |
Errors
| HTTP | Code | Meaning |
|---|---|---|
401 | unauthorized | Missing or invalid API key. |
402 | insufficient_balance | Your balance doesn't cover the task price. |
404 | unknown_type | That task type doesn't exist. |
429 | rate_limited | Too many requests. Use the webhook instead of polling. |
Technical notes
The browser tool is free to use, while automated API requests cost $0.002 each.
Use adjustment days as a practical travel buffer
Software teams can call the API to create consistent estimates in booking tools, employee travel forms, event planners, or educational demonstrations. Each successful API request costs $0.002, and the deterministic calculation returns the same output for the same input without using live data, randomness, network services, or the current date. Think of adjustment_days as a useful calendar estimate: it helps set expectations, compare eastward and westward travel, and reduce avoidable scheduling pressure without pretending to predict one person's biology exactly.
Technical questions
What happens if I enter zero time zones?
The request returns invalid_input because at least one time zone must be crossed for this adjustment estimate.
How much does the API cost?
Each successful API request costs $0.002. The same deterministic calculation can be used free in the browser.