Long-Distance Transport 2026

Can we apply if we only have references from another industry (e.g., aviation IRROPS, logistics)? 
Yes. References from other industries are sufficient to apply. Railway-specific references are not required. 

Is DB looking for a software orchestration platform only, or also for a partner that operationally manages mobility providers and service delivery?
DB is primarily looking for a partner, that delivers the technical solution. Existing relationships with mobility providers can be an advantage but are not required. 

What is the current taxi volume handled by DB Fernverkehr (annually and during major disruption events)? 
The taxi volume in 2025 for DB Fernverkehr amounted to roughly €5.5 million, corresponding to approximately 5 million kilometres and around 32,000 taxi trips. It is difficult to determine how much volume is typically generated during disruption events, as every incident differs in scale and impact. However, on 29–30 May 2026, operations were significantly affected, resulting in a taxi volume of almost 100,000 kilometres within two days across Germany.

What are the most important success criteria for DB Fernverkehr?
Key success criteria include reducing costs and passenger waiting times, lowering customer dissatisfaction in situations of disruption, maximizing automation, and achieving a high pooling rate wherever possible. 

Will the PoC run with real stranded passengers in live operation or in a test environment? 
This will depend on the maturity and progress of the solution during the 100-day program. If feasible, a live test in a real operational setting may be explored. Alternatively, the solution may be evaluated through a realistic simulation of disruption scenarios. 

What data and APIs will be available to participating startups? 
Data provided (Excel files): 

• Taxi trips dataset as needed
• Pooling results: simulation outputs for ride-sharing with 4 and 8 passengers per vehicle
• Selected train operation datasets as needed: connections including delays, disruptions, and cancellations
• Booking data as needed

Potentially more data and APIs available as required. 

Is it required to have direct contracts with taxi operators, or will DB Fernverkehr take over this part? 
No. Direct contracts with taxi operators are not required for participation. Existing partnerships may be beneficial but are not a prerequisite. 

Does the solution have to be fully browser-based? 
Yes. The use case explicitly calls for a simple browser-based self-service experience that can be accessed without installing a dedicated application. 

Is passenger pooling a mandatory requirement? 
Yes. The solution should be able to identify passengers with compatible routes and assign them to shared rides whenever possible. 

Do startups need to verify passengers’ individual claims against taxi providers or handle billing directly? 
No. The startup's role is to orchestrate the mobility process. Claim verification, reimbursement, and billing remain the responsibility of DB. 

Which analyses should be possible with the solution? 
The proposed solution should provide occupancy data in an aggregated, privacy-compliant manner. Of particular interest are analyses by building, floor, room type, and temporal patterns, such as weekdays or times of day. In addition, it would be valuable to determine whether different user groups, such as employees with assigned workstations and visitors, can be analyzed separately without allowing conclusions to be drawn about individual persons.