siteA

The night train came back, and then it got complicated

The map is better than it has been in twenty years. Buying a ticket across it is not.

Running HB Wrapper Basic — units in the HTML How this page works ↓
  1. The wrapper loads once in the <head>, as early as practical, async.

    <script async
      src="https://hbw-cdn.hbwrapper.com/hbw.siteA.hbwrapper.com.js"></script>
  2. Every slot is a div already present in the body, carrying data-aaad and the ad unit path.

    <div data-aaad="true"
         data-aa-adunit="/19191187/hbw_siteA_mtf"></div>
  3. Nothing else runs. Slots that are in the HTML when the wrapper initialises are picked up on load, so this page never calls processAdsOnPage().

    Each link here is a full page load, so the same two steps repeat on every page of the site.

Auction console: add ?hbwConsole to this URL.

All demo patterns ↗

The night train was written off twice. First in the nineties, when the low-cost carriers arrived and a sleeper berth stopped competing on price, and again a decade later when operators retired the rolling stock rather than refurbish it. Both times the conclusion was the same: people say they want to travel overnight, and then they book the 06:20 flight.

What changed was not sentiment. It was the arithmetic of a city-centre departure against an airport an hour out, plus a procurement cycle that finally made new sleeper carriages available to order. Three operators placed orders within eighteen months of each other, and the routes followed the carriages.

In the markupThe slot below was in the document before the wrapper ran. Static pages need no API call.

The result is a network that looks, on a map, close to what existed in 1995. Vienna to Brussels runs six nights a week. Stockholm to Hamburg is daily in summer. A traveller can cross most of the continent horizontally without boarding a plane, and increasingly they do.

Then they try to buy the ticket. A journey that crosses two borders is usually sold as two or three separate contracts, because the operators' reservation systems were never built to sell each other's berths. If the first leg is late and the connection is missed, which contract covers the traveller depends on which clerk is standing in front of them.

Everyone involved knows this. A booking engineer at one of the operators described the interchange format as "a fax machine that speaks XML", and was not joking about either half. The specification predates the internet as a consumer product, and it assumes a national railway talking to another national railway once a day.

The carriages were ordered, built and delivered on something close to schedule. The ticketing layer is on its fourth attempt at a standard, and the current one is optional. Until it is not, the night train will remain the only form of transport that got its hardware right before its software.