Where we can take you, and from where
A route page answers a different question from a destination page. “Lisbon” is somewhere you might go; “Luxembourg to Lisbon” is a trip you have already half decided on — and the useful part is what sits at both ends.
From Luxembourg
Why only from Luxembourg so far
Because a route page is only worth having if both ends of it are real. Every city on this site has coordinates somebody checked by hand, an airport catchment mapped to 200 km and a twelve-month climate table entered row by row — and a route needs all of that at the origin as well as the destination. Generating “flights from X to Y” for every pair of city names is a couple of hours of work and produces a great many pages with nothing in them.
Luxembourg first because it is where LetzGo is built, because it is the market whose airport problem the whole product came out of, and because “every route we cover from here” is a coherent thing to have published in a way that a scattering of popular pairs is not. More origins follow once these have earned it.
What is on each one
The straight-line distance and a rough non-stop flying time for that specific pair. Every airport within 200 km of both ends, with how far out each sits — ordered by distance, and saying so, because the airport dataset behind it cannot rank hubs against each other and pretending otherwise is how the big airport an hour down the motorway gets buried under a regional field nobody uses.
And the seasonal contrast between the two cities: how much warmer or wetter it is there than here in January and in July. That is the section a route page on a larger site structurally cannot write, because it needs both endpoints and most of them only have one.
Why there is no price on any of them
Because there is no such thing as the price of a route. A fare is a fare on a date, for a number of people, and it moves. Every “flights from €39” badge you have ever seen on a page like this is a number that was true for one seat on one day, cached and left there because it makes the page look useful. Chasing it and finding nothing at that price is the normal outcome, not the unlucky one.
There is a second reason, and it is more practical. Pricing a route means asking a provider, and these pages exist to be fetched by robots — a crawler walking twelve route pages would be running twelve real searches, and a search engine does not book trips. Keeping the pages free to crawl is what lets them be built from data we actually stand behind rather than from whatever the search happened to return that morning.
So the numbers here are the ones that hold still: distances, airport positions, and typical seasonal averages. The ones that move — fares, room rates, what is left — come from the search, where a flight price is held with a live countdown so you can see exactly how long the figure in front of you is good for.