nachtzug.net valid
nachtzug.net
Independent reference for night trains: which train runs where, when it
For agents: Independent reference for European night trains: routes, city pairs, countries, timetables, classes and a network map showing reachable cities.
night-trainstrain-timetablesrail-traveleuropean-railroute-map
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-25T20:11:54.341Z. Cached copy · Source on nachtzug.net
# nachtzug.net
> Independent reference for night trains: which train runs where, when it
> departs and arrives, where it stops, which sleeping-car classes it
> carries and where to book. Editorially maintained and checked against
> the operators. Published by Railworld AB, Älmhult, Sweden — not a
> railway company and not a ticket vendor.
Coverage: 265 night train routes, 328 city-pair journeys, 1,299 cities with a night train stop in 29 countries.
Languages (21): de, en, fr, it, ja, nl, pl, sv, uk, cs, es, hu, ro, tr, da, no, fi, sk, hr, bg, ko. Every page exists under a language
prefix, and the path segments are translated as well — the German train
page `/de/nachtzug/muenchen-rom/` is `/en/night-train/munich-rome/` in
English and `/it/treno-notte/monaco-di-baviera-roma/` in Italian. All
versions cross-reference each other with `hreflang`; `x-default` is
English.
Structured data, if you would rather read facts than prose:
- Train pages carry schema.org `TrainTrip` — departure and arrival time,
every stop in order with coordinates, operator, train name and number —
plus `FAQPage`.
- Journey pages (city pairs) carry `TrainTrip` for that section only, with
`partOfTrip` pointing at the train it runs on. A journey is a part of a
train, never a second page about the same train.
- Every page carries `BreadcrumbList`; the start page and the about page
carry `WebSite` and `Organization`.
Two distinctions worth keeping straight, because they are the two mistakes
outsiders make most often with this data:
- A **train** is a service with a timetable (NJ295, Munich–Rome). A
**journey** is a city pair lying on that train (Munich–Bologna). Both
have their own pages.
- Whether a train **runs** is `service_status`, not whether its page is
published. A page can be live for a service that is suspended for the
season, and the page says so.
## Terms
Search indexing and citation are welcome: quote a passage, name
nachtzug.net and link to the page you took it from. Corrections are
welcome too — see "Report an issue" below.
Using this content to train or fine-tune a model is **not** permitted.
The editorial texts exist in nine languages and the timetable database is
maintained by hand against the operators; both represent substantial
investment by Railworld AB. This is a reservation of rights under
Article 4(3) of Directive (EU) 2019/790, stated here and in
machine-readable form in [robots.txt](https://nachtzug.net/robots.txt) as
`Content-signal: search=yes, ai-train=no, use=reference`.
Interested in a licence for training or bulk use? partner@nachtzug.net
## Start here
- [All night trains](https://nachtzug.net/en/night-train/): every route, with timetable and classes. German: https://nachtzug.net/de/nachtzug/
- [All journeys](https://nachtzug.net/en/journey/): city pairs. German: https://nachtzug.net/de/verbindung/
- [Cities](https://nachtzug.net/en/city/): every city with a night train stop. German: https://nachtzug.net/de/stadt/
- [Cou
…
Related sites
Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.
| Domain | Title | Category | Country | Authority | llms.txt | llms-full.txt | Save |
|---|---|---|---|---|---|---|---|
| chronotrains.com | Chronotrains | interface Travel | — | 54 | ✓ | ||
| livetraintimes.org | Live Train Times | interface Travel | — | 49 | ✓ | ✓ | |
| trainfyi.com | TrainFYI.com | documentation Travel | — | 46 | ✓ | ✓ | |
| zug-ticket-kaufen.de | zug-ticket-kaufen.de | documentation Travel | DE | 45 | ✓ | ✓ | |
| worldtrainmap.com | World Train Map | documentation Travel | — | 47 | ✓ | ||
| bahndampf.de | Bahndampf: Das Zug\-Portal | transactional Travel | DE | 47 | ✓ | ||
| bodo.de | bodo | documentation Travel | DE | 53 | ✓ | ✓ | |
| goedkoop-treinkaartje.nl | Goedkoop\-treinkaartje\.nl: Boek goedkope treinkaartjes en treinreizen | transactional Travel | NL | 50 | ✓ |
Machine-readable: GET /v1/resolve?q=nachtzug.net · GET /v1/domain/nachtzug.net · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage nachtzug.net, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for nachtzug.net:
1. POST https://agentwebmap.com/v1/sites/nachtzug.net/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://nachtzug.net/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/nachtzug.net/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/nachtzug.net).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.