Hidden Transit Detection
A two-hour layover in Madrid is a Schengen entry. EES records it the moment your passport hits the kiosk. SchengenWeave inspects every leg of every itinerary so you see those hidden entries before you book.
The hidden-transit problem
Most flight searches present a multi-city itinerary as origin → destination. The intermediate airport — the layover — is treated as transit-only, like changing trains. But for the Schengen 90/180 day budget, a layover at a Schengen airport is a Schengen entry, full stop. The EU Entry/Exit System records it electronically just like any other border crossing.
That means a single multi-leg booking can quietly cost you 1-2 Schengen days through an intermediate stop you never planned to "visit" — particularly common on European hub routings via Amsterdam, Frankfurt, Madrid, and Vienna.
So what for nomads: You did not "go to Amsterdam" — but your passport did, and EES knows. The day count moves regardless of intent.
How SchengenWeave detects it
When you search for a flight, every leg of every result is broken into its sub-route by SchengenWeave's annotation library. Each intermediate airport's country code is checked against the country-status rules table, and any layover at a Schengen-status airport surfaces as a warning on the flight card — visible in the results list before you click through to book.
Virtual interlining (VI) layovers — where two separate tickets are connected by the booking engine, requiring you to clear immigration landside between flights — are flagged amber by default, since these always require a Schengen entry whether the airport is your destination or not.
What this gives you
Per-leg country annotation: Every flight leg surfaces the destination AND every intermediate airport country code, computed server-side from the airline response.
Layover Schengen warnings: Itineraries that route through Madrid, Frankfurt, Amsterdam, Vienna, or any other Schengen airport are flagged in the results list — not buried in fine print.
Virtual interlining flagged amber: When a booking requires you to clear immigration mid-trip and re-check baggage, the layover is automatically amber-flagged because EES records that entry.
Day count reflects all Schengen entries: The compliance flag computed for each result includes intermediate Schengen entries — not just the named destination — so the green/yellow/red colour matches what EES will record.
Try it
Open the flight planner and search a multi-city itinerary that hubs through a Schengen airport (London → Tbilisi via Madrid is a classic). The Schengen warnings surface in the results list before you click through to book. For the full EES explainer, see the Learn page.