Rail in DACH (Germany · Austria · Switzerland)
2 rail providers across DACH (Germany · Austria · Switzerland), publishing 2 APIs.
Rail across DACH (Germany · Austria · Switzerland) — 2 providers on the APIs.io network sit in both cohorts, and between them they publish 2 indexed APIs.
This cell is below the 5-provider floor, so it carries no generated statistics. A distribution over 2 providers is not a small characterisation of rail across DACH (Germany · Austria · Switzerland), it is a wrong one. What follows is the roster and nothing more. The gap is a statement about catalog coverage rather than about the market: DACH (Germany · Austria · Switzerland) holds 425 providers in total and Rail holds 29, so the intersection being this small is worth reading as a queue of organisations not yet profiled.
Region membership is derived from three explicit signals — a provider tag, a provider-name pattern, or a stated headquarters in the provider’s own description. This is a map of stated headquarters, not of markets served.
Providers (2)
| Provider | Description | APIs | Rating |
|---|---|---|---|
| FlixBus | FlixBus is the long-distance coach brand of Flix SE (formerly FlixMobility), a Munich-headquartered mobility provider that also operates FlixTrain in Europe and Greyhound in Nor... | 2 | emerging |
| Selectron | Selectron Systems AG is a Swiss rail-vehicle automation and safety supplier founded in 1956 in Lyss, Switzerland, and part of the Knorr-Bremse Group since 2015. Its core busines... | 0 | emerging |
Indexed API documents (2)
Two numbers, both real: these providers publish 2 APIs as their own documents, which the catalog indexes split one-per-resource into 2 documents.
Flix API
Flix GTFS Schedule Feeds
Other industries in DACH (Germany · Austria · Switzerland)
Rail elsewhere
This page is the intersection of two independently computed cohorts:
DACH (Germany · Austria · Switzerland) and
Rail. A provider appears here only when it is
already a member of both. DACH (Germany · Austria · Switzerland) membership is matched on tag, name pattern, stated HQ,
so this is a floor rather than a census — coverage gaps show up here as small numbers, not as absent pages.
Work with this as data
Every region here is available over the APIs.io API and to AI agents over MCP.