How to Turn Your Flighty Flight History Into a Visa and Residency Day Count
Flighty is built to track your flights. Visa limits and residency tests are about days in a country. Here is how to bridge the two without losing accuracy.
Last verified: June 2026
In short: Flighty keeps an excellent log of the flights you have taken, but it does not total how many days you have spent in each country or check that against a visa or residency limit. To get a day count, you treat each flight as an arrival in a country and add up the days between arrivals and departures – work a day-counting app can do for you straight from a Flighty export.
Why your flight history is a strong starting point
Flighty logs the flights you take, follows live status and delays, and turns your history into stats like airports visited, miles flown, and time in the air. For remembering exactly where and when you flew, it is hard to beat. What it is not built to do is answer the questions visa and residency rules ask: how many days you have spent in the Schengen area in the last 180 days, whether you have been in a country more than 183 days this year, or whether your next trip crosses a stay limit. Those are about presence measured in days per country, not about flights. Your flight history is the raw material; the day count is a separate calculation built on top of it.
It is good raw material. Each international flight is a dated border crossing: the destination airport tells you which country you entered, and your next departure tells you roughly when you left by air. A reasonably complete flight history is close to a skeleton of your movements, already dated and far more reliable than counting from memory. It is one of the better sources when you are rebuilding a travel history from passport stamps, emails, and photos. The gap is everything between the flights: how long you actually stayed, whether a connection should count, and any travel you did on the ground.
What has to happen to get from flights to days
- Airport to country. Each airport code maps to a country, so an arrival into CDG is an arrival in France and an arrival into NRT is an arrival in Japan.
- Chaining legs into trips. A journey is usually several flights. Out-and-back legs need to become the trips they represent, not a separate row for every flight.
- Connections versus stays. A same-day connection through a third country is normally transit and should not add days there. An overnight layover is a judgement call. See Does a Layover Count as Visiting a Country?
- Counting against a window. Once you have dated stays per country, the count is measured against the relevant rule – a rolling 180-day window for Schengen 90/180, which is a lookback across the whole Schengen area rather than per country, or a calendar or fiscal year for many 183-day residency tests, each with their own exceptions.
There are two realistic routes. Manually: export your flights from Flighty as a CSV, then work out country stays and tally days in a spreadsheet. It is doable, but it has to be redone every time plans change, and that is where spreadsheets tend to fail. Faster: bring the same export into an app that infers trips and counts days for you. AtlasDays reads a Flighty CSV, maps airports to countries, chains the legs into trips, flags same-day connections as transit, and counts those days against whatever limit you are tracking. The step-by-step is in Help Center: Flighty Import.
Either way, review before you trust it. An automated pass turns hundreds of flights into trips in seconds, but a connection misread as a stay, or a missing leg, changes the count. Treat the first result as a strong draft and check the trips that feed a limit you care about.
Tracking this yourself? AtlasDays keeps a private, dated travel record on your iPhone and counts the days that matter: visa limits, residency thresholds, and country totals. Get the app →
Where flight history alone is not enough
Visa and residency questions are high-stakes, so it is worth being honest about what a flight log cannot tell you:
- Ground crossings are invisible. A train from France to Spain or a drive across a land border never appears in a flight history, so a stay that ended on the ground may need its dates adjusted.
- Flights show movement, not where you slept. A connection is not a visit, and a long layover is a grey area. What actually counts as a "day" depends on the rule – see What Counts as a 'Day' for Visa Purposes?
- It is evidence, not proof. A flight history is strong supporting evidence of your movements, but official decisions still rest on stamps, permits, and authority records. If you are assembling a record for an application, see How to Prepare Travel History for a Visa Application.
The point of starting from Flighty is that you build the record once, then check the same clean set of dated trips against whichever limit applies.
FAQ
Does Flighty count your days in a country?
No. Flighty logs the flights you take and builds flight stats, but it does not total how many days you have spent in each country or measure that against a visa or residency limit. Day counting is a separate calculation that uses your flight history as its source.
Can Flighty track the Schengen 90/180 rule?
Not directly. Flighty is a flight tracker, not a visa-limit calculator, so it does not keep a rolling 90/180 Schengen total. You can use your flight history as the source data and count it against the rule in a day-tracking app.
How do I export my travel history from Flighty?
Flighty can export your flight history to a CSV file, which you can save or share to your device. From there you can open it in a spreadsheet or import it into a day-counting app to turn the flights into dated trips.
From flight log to day count
AtlasDays imports your Flighty history once, turns it into dated trips you review, and recalculates rolling windows and residency thresholds from that single record – private, on your iPhone. For the broader case for keeping one trusted record, see How to Track Your Travel Days.
Get AtlasDays on the App Store