Where Europe's Guests Come From

Eurostat’s guest-origin figures can help a hotel ask better questions about multilingual service. They cannot answer the most important one on their own: which language does a particular guest prefer for a particular task? A country-of-residence figure is useful context for an owner assessing a market or a group comparing destinations. Decisions about reception guidance, digital content and translation budgets still need evidence from the property and its guests.

Read the annual origin figures on their own terms

Eurostat’s release of 16 October 2026 describes 2025, when EU tourist accommodation recorded 3.1 billion guest nights, up 4.1%. Domestic and intra-EU residents together accounted for 80.9% of those nights. Residents of other European countries accounted for 10.4%; the Americas, 4.9%; Asia, 2.6%; Oceania, 0.5%; and Africa, 0.4%. The published shares are rounded, so they need not total exactly 100%.

These are shares of nights, not shares of bookings or individual travellers. A guest staying longer contributes more nights than a guest staying briefly. The figures also cover hotels and similar accommodation, holiday and other short-stay accommodation, and campsites. A hotel should therefore not label them its own guest profile or assume that the distribution holds for hotel rooms alone.

The geographic labels need care, too. “Domestic and intra-EU” combines residents travelling within their own country with residents travelling to another EU country. “Other European countries” is a separate category. Neither should be casually renamed “international guests”, and EU totals should not be presented as totals for all of Europe. For a technology director, the useful conclusion is not a prescribed language list. It is a reason to make language and content choices measurable at the property level.

Keep the first-half country update separate

A separate Eurostat release covers the first half of 2026. Its country figures below show non-resident nights as a share of all tourist accommodation nights in each country during that half-year. They do not identify the residents’ countries of origin or the languages they prefer.

The comparison shows why one EU-wide average is a poor substitute for local planning. It does not show that a hotel in Malta serves any particular language more often than a hotel in Germany. A non-resident share says nothing about which languages those visitors request, and a national share cannot describe every property in that country. A resort, airport hotel and city-centre business hotel may have different demand even when they operate under the same national figure.

Nor should the half-year country shares be read as full-year results or forecasts. Keep the annual EU origin distribution and the first-half national non-resident shares in separate views, with the period and denominator beside every figure. Combining them into a single undifferentiated “2026 guest mix” would change what the sources say.

Ask guests about language rather than inferring it

Country of residence is neither nationality nor language. A resident of a multilingual country may use any of several languages; a resident elsewhere may prefer a language unrelated to that country’s majority language. Even a recorded booking language may reflect the channel interface someone used rather than the language they want for safety information or a service request.

Hotels can invite guests to select a communication language at appropriate points, such as pre-arrival contact or check-in, and make it easy to change that choice. A brief question is more useful than an assumption based on a passport, address or surname. Where existing systems hold a preference, staff should know whether it came from an explicit selection or an inferred default. Avoid treating a missing preference as a negative answer.

For planning, compare voluntarily supplied preferences with practical signals: which translated instructions guests request, where reception regularly has to clarify a process, and which content receives correction requests. Record the period, property and method used to gather those signals. If only some guests respond, do not present their answers as a complete survey of the hotel. This approach is an editorial recommendation, not a finding measured by Eurostat or a claim about a COTT.TV deployment.

A group can compare properties using the same definitions while leaving room for different local choices. For example, “requested communication language” should mean the same thing in each property report, whereas the languages offered for a local breakfast menu can reflect that property’s guests and menu. Review whether a preference is still current before relying on it for a future stay.

Translate the actions guests need to take

Start with content where misunderstanding creates friction or risk. At arrival, check whether a guest can find reception, understand check-in instructions and identify whom to contact outside normal desk hours. For Wi-Fi, provide clear connection steps and a route to help if those steps fail. For breakfast, keep hours, location and relevant menu or allergen information aligned with what the property actually offers. For service requests, explain how to submit a request and what to do if the channel is unavailable.

Emergency directions deserve separate ownership and careful approval. They should match the property’s current procedures and be understandable without relying solely on a TV screen, mobile device or network connection. The operational priority is accurate, accessible guidance, not simply adding the longest possible list of translations. Staff also need an escalation route when a guest’s preferred language is unavailable or a translated instruction is unclear.

Make a short inventory before commissioning translations. List each guest action, the original text, where it appears, its owner and the event that should trigger an update. Then identify where guest questions or preferences indicate a genuine need. A translated breakfast time that remains on an old screen after the restaurant changes its hours can be less helpful than a smaller set of accurately maintained languages.

Give every channel an owner and an update trigger

The following matrix is a suggested operating model, not a description of functionality supplied by any platform. Adapt responsibilities to the hotel’s staffing and approval process.

An owner should be able to identify the approved source text, who authorizes a change, which translations are affected and where the old version must be removed. A technology integrator can help map publication points and test that approved material appears where intended. The hotel remains responsible for whether its local facts and procedures are correct. A useful handover records exceptions too: a channel that cannot display a needed language, or a sign that must be replaced manually, should not disappear from the workflow merely because digital content has been updated.

COTT.TV helps hotels connect in-room television, guest information and multilingual assistance. Explore the TV Marketplace for channel selection and Ellia for the guest-concierge experience. Bring your property’s preferred languages and approved local information into the project brief so the content and service workflow match the guests you actually serve.

Set a group standard without flattening local differences

A hotel group benefits from common definitions and reusable source material. It does not benefit from publishing a universal set of opening hours, contact details or local instructions that its properties cannot keep accurate. Separate centrally approved material from property-controlled facts, and specify who can change each. A central team might maintain terminology and approved templates; local teams can confirm that the instructions a guest sees still match the building and its services.

When comparing language requests across properties, retain the collection method and reporting period. A destination with a high national non-resident share may warrant closer investigation, but it does not automatically require any named language. Equally, a property in a country with a low national non-resident share should not dismiss requests from its own guests. Choose additions based on the importance of the task, evidence of demand and the ability to maintain an accurate version, not a threshold invented from regional statistics.

Practical questions

Is a non-resident share a language-preference statistic?

No. It records residence relative to the destination, not nationality or preferred language. A property needs its own preference evidence.

Can annual EU origins and half-year national shares be merged?

Keep them separate. They have different periods, categories and denominators, and neither describes every individual hotel.

Sources and methodology

The Eurostat release on 2025 EU tourist accommodation nights and origins supplies the annual total, change and residence-origin shares. The separate Eurostat first-half 2026 tourism release supplies the selected country-level non-resident shares. Evidence was reviewed on 23 October 2026; a later publication date does not imply a later source check.

Both releases concern tourist accommodation, including hotels and similar accommodation, holiday and other short-stay accommodation, and campsites. Guest nights are not room nights, occupancy, room rates, revenue or profit. Residence is not nationality or language preference. The annual EU distribution and first-half country shares have different periods and denominators; neither establishes an individual hotel’s mix, a full-year national outcome from half-year data, or the results of a multilingual-service change. The workflows and priorities above are editorial recommendations for hotels to assess against their own evidence, not measured outcomes or verified product capabilities.

Editorial visual: Inn. TRENDS.