Digital Nomad Tax Residency Tracker
Period, trips & what-if details
Arrival counted · departure counted. Global example threshold 183 days · warning distance 30 · planning buffer 7. Tracking period is inclusive and fixed for this projection.
Tracking-period timeline
Each bar is a raw clipped trip segment; adjacent and overlapping segments remain visible. Country totals use the unique union. The dashed planned segment is separate and labeled.
Accessible trip list
- Portugal: Jan 10, 2026 → Feb 20, 2026 · 42 clipped raw trip days; unique country totals deduplicated.
- Portugal: Feb 21, 2026 → Apr 15, 2026 · 54 clipped raw trip days; unique country totals deduplicated.
How tracked days and projections are calculated
Apply arrival/departure exclusions to actual trip boundaries, clip to the inclusive selected period, merge same-country intervals, then sum end − start + 1. Adjacent intervals merge. A single date is never counted twice in one country.
Remaining = threshold − tracked days. Percentage = tracked days / threshold × 100, uncapped numerically. Reached is exactly zero remaining; above is negative; approaching is positive remaining at or below your warning distance.
Threshold date searches cumulative presence through each counted planned date. Buffer departure searches candidate plan end dates with the same clipped union engine, retaining every recorded trip. No dates after your entered planned departure are inferred. Rolling anchor remains fixed.
Digital Nomad Tax Residency Tracker Tracking period: 2026 calendar year; 2026-01-01 → 2026-12-31 Day convention: Arrival counted; Departure counted. Tracker assumptions only. Global example threshold 183; warning 30; planning buffer 7. 183 days is a common planning reference, not a universal tax-residency rule. Portugal (PT): 96 / 183 tracked days; 87 days remaining; BELOW THRESHOLD; 52.5%. Using global defaults; warning 30; buffer 7; buffer target 176. 2026-01-10 → 2026-02-20: 42 clipped raw trip days; country total deduplicated. 2026-02-21 → 2026-04-15: 54 clipped raw trip days; country total deduplicated. Timeline unique segments: 2026-01-10 → 2026-04-15 This tracker calculates presence days from the dates you enter. It does not determine legal tax residency or tax liability. Residency rules can depend on domestic law, personal ties, treaties, and other factors. Consult official guidance or a qualified tax professional for your circumstances. Session-only; no saved history, URL persistence, visa/Schengen, domicile or treaty calculations. Planning tool only — not a tax-residency determination.
How to use
Track unique presence days by country, compare user-selected planning thresholds and model future stays. This tracker does not determine legal tax residency.
Choose a tracking period, review the editable global planning defaults, and enter one to 200 trips using a bundled country or territory label and ISO arrival/departure dates. Review Day-count settings. Each country can explicitly override the global threshold, warning distance and buffer. Enable WHAT IF I STAY? to add a separate planned stay without changing recorded trips. Update Day Tracker moves keyboard focus to results; results also update live. Copy or print the summary. Reset restores two clearly illustrative Portugal trips in fixed 2026 and clears the what-if plan.
What this tracker measures
This tool counts unique calendar dates assigned to each country within your selected window. It reports tracked days, threshold status, projected threshold date and buffer departure date. The country list is organizational: names and ISO-style region codes carry no legal threshold, tax rule or visa limit. Totals are per country, not a global travel-day total; the same date may count in two countries if you enter overlapping ranges.
Why day count is not the same as tax residency
Presence-day arithmetic cannot establish tax residency. Relevant factors may include domestic law, permanent home, habitual abode, vital or economic interests, family ties, employment or business activity, domicile, treaties, citizenship-specific provisions and special regimes. The editable 183-day example is a planning reference, not a universal rule or evidence of a tax outcome. OECD guidance distinguishes residence permissions and citizenship from tax-residence determinations. Review applicable official guidance for your circumstances.
How travel days are counted
The engine stores date-only YYYY-MM-DD strings and converts validated dates to integer UTC calendar-day indices. It first excludes any unchecked actual arrival/departure boundary, then clips to the inclusive period. For each country it sorts and merges overlapping or adjacent intervals and sums end − start + 1. This interval approach does not enumerate every date across long trips. Invalid dates, reversed trips, exact duplicate entries and invalid active settings withhold all totals, statuses, timelines and projections.
Arrival and departure days
Both arrival and departure days are counted by default. Uncheck either under Day-count settings to exclude that actual trip boundary. These are generic assumptions, not a country-specific legal convention. A same-day trip counts exactly one day when both boundaries are included; excluding either excludes that single date. Jan 1–10 counts ten days with both included, nine with one excluded, and eight with both excluded. Clipping at a period boundary never excludes an additional day unless it is also an actual excluded trip boundary.
Overlapping trips
Same-country overlapping dates are counted once in the country total. Adjacent ranges merge naturally. Raw clipped trip days are shown individually and explicitly are not additive when trips overlap. Exact duplicate country/arrival/departure entries are rejected until edited or removed. Cross-country overlap is allowed with a visible review warning, including a shared transfer date. The tool does not infer which country should own a day or change your entries.
Calendar-year tracking
Choose an explicit year from 1900 through 2200. The tracking window is Jan 1–Dec 31, inclusive. A trip crossing a year boundary contributes only dates inside that window after actual boundary exclusions. Leap-year Feb 29 is a distinct calendar date. This calendar-year example is not a claim that a jurisdiction uses a calendar tax year.
Rolling tracking windows
Rolling days means exactly N calendar dates ending on and including your chosen anchor: start = anchor − (N − 1). Default length is 365, editable from 1 to 10,000 days, with the whole window within 1900–2200. A 365-day lookback is not necessarily twelve calendar months and is not a legal rolling test. The window remains fixed while modeling a stay; change the anchor to test another snapshot. No automatic day expiry or sliding legal-rule model is inferred.
Custom tracking periods
Custom period uses your selected start and end dates, inclusive, within 1900–2200. End must be on or after start. Every country total, percentage, status, timeline and active projection recomputes when the period changes. Trips entirely outside it contribute zero dates. No current date, browser location or server timezone chooses the window.
Setting a planning threshold
Threshold is a user-selected whole number from 1 to 10,000 days. It is never populated by selecting a country. Remaining = threshold − unique tracked days; negative remaining means days beyond the selected threshold. Percentage = tracked days / threshold × 100 and may exceed 100%; only the progress bar is visually capped. Warning distance is a user-selected whole number from zero to the threshold, default 30. Positive remaining within that distance is APPROACHING THRESHOLD; exactly zero is THRESHOLD REACHED; negative is ABOVE THRESHOLD. Color supplements the text.
Planning buffers
Your planning buffer is a personal margin, from zero to the selected threshold. Buffer target = threshold − buffer; for the illustrative 183 and 7 settings it is 176 tracked days. The buffer departure date is the latest candidate date within your entered plan whose same-country union remains at or below this target. Each candidate replaces the planned departure and honors arrival/departure settings. All recorded selected-window trips, including future ones, remain in this buffer calculation. If none qualifies, no date is shown. If the entered departure qualifies, it is shown without inventing a later departure.
Projected threshold date
The projected threshold date is the first counted date during the plan on which cumulative same-country unique presence inside the fixed window reaches your threshold. Existing future dates are not precredited. The algorithm clips presence to each candidate calendar date; the planned interval retains its entered boundary exclusions. If the threshold was already reached before arrival, this is disclosed and the first counted plan date at or above it is shown. If no counted planned date reaches it, the tracker says Threshold not reached during this planned stay. This is an arithmetic projection, not a legal deadline.
What-if travel planning
The what-if total merges recorded and planned same-country presence within the selected period. Planned additional unique days = projected total − current tracked total. A plan overlapping an existing trip adds only new dates. The result shows current days, added unique days, projected total, threshold, remaining/beyond difference, threshold date and buffer departure. Threshold timing is cumulative through the candidate date, while buffer departure retains the full recorded window for a conservative planning margin. The plan is session-only and does not modify recorded trips. A plan outside the window adds zero dates; no later date beyond entered departure is inferred.
Once you have chosen possible stay dates, compare meeting times for a planned stay using the actual meeting date and relevant time zones. Meeting scheduling does not change presence-day totals or determine legal tax residence.
Domestic-law and treaty limitations
Actual tax residence is governed by applicable domestic provisions and may involve multiple jurisdictions. Tax treaties may contain separate tie-breaker rules involving personal connections; this tracker does not apply them. It does not determine domicile or citizenship-specific tax liability. Visa permissions, immigration limits and tax residency are separate concepts. There is no Schengen 90/180 calculation, treaty-residence decision, tax return, tax amount or professional advice produced here.
Worked examples
These five examples use illustrative Country A labels and the same date engine as the form. No country rule is inferred from an example threshold.
1. Two adjacent trips
Country A: Jan 10–Feb 20 and Feb 21–Apr 15, 2026, both boundaries included. Unique tracked total: 96 days.
2. Same-country overlap
Jan 1–10 and Jan 5–15, 2026, both boundaries included: 15 unique tracked days. Overlap is counted once.
3. Calendar-year clipping
Dec 20, 2025–Jan 10, 2026 clipped to calendar year 2026: 10 tracked days.
4. What if the stay continues?
Existing Jan 1–Jun 19, 2026: 170 unique days. Planned Oct 1–31, both boundaries included, adds 31 days, giving 201. With an entered 183-day threshold, the projected threshold date is Oct 13, 2026.
5. A personal planning buffer
The same existing 170 days with threshold 183 and buffer 7 gives target 176. The latest modeled departure within this plan preserving that target is Oct 6, 2026.
This is based only on your entered travel dates and selected day-count settings. It is not a legal tax-residency deadline.
Assumptions and limitations
This tracker calculates presence days from the dates you enter. It does not determine legal tax residency or tax liability. Residency rules can depend on domestic law, personal ties, treaties, and other factors. Consult official guidance or a qualified tax professional for your circumstances.
183 days is a common planning reference, not a universal tax-residency rule.
All country labels organize user-entered dates only. No country-specific threshold database or automatic tax rule is shipped. Tracking assumptions may differ from domestic law. Boundary-day exclusions apply to actual trip endpoints, not newly clipped endpoints. Raw trip contributions may overlap; unique country totals are the comparison measure. Cross-country totals should not be summed as unique global dates. Projection threshold timing does not precredit later recorded dates; buffer tests keep those recorded commitments. No sliding window, background monitoring, imports, saved travel history, accounts, notifications, network calculations or geolocation. Data disappears when the session/page state is reset or closed. Dates are UTC calendar-day indices, unaffected by DST; no current-time default is used.
FAQ
How do I track days spent in each country?
Enter each trip country, arrival and departure, choose a tracking window and boundary assumptions. The tracker clips ranges and counts each calendar date once per country.
Does spending 183 days in a country automatically make me tax resident?
The 183-day value here is an editable example threshold. This tool cannot determine residency from it; review applicable domestic law and personal circumstances.
Does staying fewer than 183 days guarantee I am not tax resident?
No. Day count alone does not establish your status. Other domestic rules, personal ties and treaty considerations may be relevant.
Should arrival and departure days both count?
Both are included by default as a generic tracker assumption. You can exclude either. Determine the applicable legal convention separately from official guidance.
How does the tracker handle overlapping trips?
Same-country intervals are merged without double-counting. Different countries keep their entered dates and produce a review warning. Exact duplicate trips must be corrected.
What is the difference between a calendar-year and rolling tracking period?
Calendar year covers Jan 1–Dec 31 of your chosen year. Rolling days covers exactly the selected length ending on its inclusive anchor. It does not automatically model calendar months or a legal rule.
What does the planning threshold mean?
It is your own comparison point for tracked presence days. Global defaults can be explicitly overridden per country; country labels do not supply tax rules.
What is the projected threshold date?
It is the first counted date in a planned stay at which cumulative unique same-country dates in the selected window reach your threshold. It is not a legal tax-residency deadline.
What does the planning buffer do?
It lowers your personal planning target by the selected cushion. Candidate departure dates are tested against that target while retaining all recorded selected-window trips.
Can this calculator determine my legal tax residency?
No. It calculates presence dates and planning comparisons only. Use official guidance or a qualified tax professional for your circumstances.
Sources
Official sources provide general tax-residence and treaty context, not an automatic threshold or endorsement of this tracker. No national rule is encoded or stated for any worked-example country.
- OECD — tax residency guidance and jurisdiction information ↗ (opens in a new tab)
- OECD — model convention concepts, Article 4 residence and treaty tie-breakers ↗ (opens in a new tab)
Sources reviewed October 7, 2026 for general caveats only. No legal thresholds, national day-count conventions or individual advice supplied.