Registration-free Schengen 90/180 rolling-window stay calculator: enter entry/exit dates and check day by day whether the total stay inside any 180-day window exceeds 90 days — all computed inside your own browser.
Any single day starts a rolling 180-day window looking backwards, and the total stay inside that window must not exceed 90 days. Both the entry day and the exit day count as stay days, and the same day is never counted twice.
No, it never resets. The rolling window always looks back 180 days from "today" as its endpoint, and older stay days simply age out of the window naturally — there is no concept of "clearing every six months".
It starts 180 days back from the reference day you query, including that day. In other words, every single day has a window of its own, and the rule must hold for "each day" individually — it is not checked only once on the entry day.
Yes, both count. Stays are computed as a closed interval: the entry day and the exit day each count as one day, and a single-day stay is still one day. A same-day return trip occupies 1 day, not 2.
Yes. The cap is 90 days, so exactly 90 days is still within the limit; one more day (91 days) is a violation. This is the rule commonly known as 90+1.
Overlapping or back-to-back trips are first merged into one continuous stay and deduplicated, so overlapping dates are counted only once. Each 180-day window is then checked day by day after the merge.
It depends on how many stay days you have already used in the past 180 days. The earliest entry day is the first day on which every window is back within the 90-day limit; the deeper the overage, the longer you must wait.
Enter the planned entry and exit dates into the calculator together. The engine checks every 180-day window covered by that stay and highlights the specific dates that would violate the rule.
Dates are always computed as dates themselves, independent of your device timezone. Internally the engine converts dates to UTC day numbers before subtracting, avoiding one-day drift across timezones.
No. This is a purely front-end tool: trips are saved only in your browser's local storage, and the page performs no server-side data upload at all.