What Trainline actually does
Trainline was founded in 1997 in Edinburgh and is headquartered in London, operating as the UK's dominant third-party rail ticket distributor. The company is listed on the London Stock Exchange (LSE: TRN) with a market cap of approximately $1.16B as of December 2025 per PitchBook. In FY2026 (year ending February 2026), Trainline processed £6.3B in net ticket sales (+7% YoY) generating £453M in revenue (+2% YoY). The company acquired Trenes.com in April 2025 for European expansion and launched an AI assistant in June 2025. B2B distribution (Trainline Solutions) grew net ticket sales +36% YoY in H1 FY2026 with international B2B up +55%.
Trainline's revenue model is primarily booking fees charged on UK consumer journeys: typically 59p to £2.79 per journey, varying by ticket price and journey complexity. The UK commission rate from rail operators (TOCs) was actually reduced in 2025 per Trainline's H1 FY2026 release — reflecting increased competitive pressure from TOC-owned apps. UK train operating companies launched their own booking apps charging zero booking fees in 2023, creating a direct competing channel that explicitly eliminates Trainline's primary fee justification.
The infrastructure runs on AWS with a stack including .NET, Node.js, React/React Native, Kafka, and Aurora/Postgres. Trainline's core technical challenge is fare calculation: UK rail fares are governed by National Rail's complex fare rules including Railcard discounts, zonal logic, time-of-day restrictions, and hundreds of operator-specific rule sets. Split-ticketing optimization — finding combinations of shorter journey fares that total less than the through-fare — is a significant value-add feature that default users cannot easily access.
Multi-modal transit search and booking
Journey search across rail, bus, coach, and ferry options in UK and European markets, with real-time schedule data from GTFS/GTFS-RT feeds and TOC API connections.
UK fare calculation engine
Complex UK rail fare calculation covering hundreds of fare rules, Railcard discounts (16-25, 26-30, Senior, Family & Friends, Two Together), time-of-day restrictions (off-peak, super off-peak), and zonal logic — the highest-complexity component of UK rail ticketing.
E-ticket generation with Aztec barcode
UK rail e-tickets use Aztec barcode format (not QR codes) per Rail Delivery Group standards. Trainline generates compliant e-tickets for gate and manual inspection across all UK operators.
Seat reservation with real-time seat maps
For advance purchase and first-class tickets, seat reservation is mandatory or optional depending on the service. Real-time seat map display showing occupied/available seats per carriage per service.
Split-ticketing optimization
Buying separate tickets for intermediate stations can cost less than the through-fare — Trainline does not surface this by default, but specialist tools (SplitTicketing.com, TrainSplit) do. Building split-ticketing surfacing into the default booking flow is a significant customer value-add.
B2B distribution platform (Trainline Solutions)
Trainline Solutions provides rail ticket distribution infrastructure to corporate travel managers and travel agents, contributing +36% YoY B2B net ticket sales growth in H1 FY2026.
Trainlinepricing & limits
Based on a regular commuter making 2–4 journeys/week at 59p–£2.79 fee per booking
Where Trainline falls short
59p–£2.79 booking fees while TOC apps charge zero
A Threads user in 2025 summarized: 'Trainline always add a booking fee too which many other apps don't. I ditched them many years ago for that reason alone.' UK train operating companies launched their own booking apps in 2023 with zero booking fees, creating a direct competing channel that explicitly eliminates Trainline's primary fee model. Regular commuters making 10 journeys per month at £2.79/booking pay £334/year for a convenience layer they could access free.
Duplicate charges with no resolution for three weeks
A PissedConsumer report documented: 'An error on Trainline's website caused a duplicate charge of £159. After three weeks of phone calls and emails, Trainline has still not refunded the money.' A £159 duplicate charge is a significant consumer harm, and a three-week resolution timeline for a documented billing error reflects inadequate consumer protection in the refund process.
Often cheaper to book directly with train operating companies
For many UK journeys, booking directly with the train operator's app or website eliminates Trainline's booking fee entirely — offering the identical ticket at lower total cost. Informed travelers consistently find direct booking cheaper. Trainline's value is convenience and multi-operator coverage, but the fee transparency problem means even convenience-seeking consumers may check alternatives.
Split-ticketing not surfaced for default users
Split-ticketing — buying separate tickets for intermediate stations at a combined cost below the through-fare — can save £10–£50+ per journey on many UK routes. Specialist platforms like TrainSplit and SplitTicketing.com expose this. Trainline does not surface split-ticketing by default, leaving significant consumer savings on the table that a competing platform could provide transparently.
App push-notification spam
App store reviews for Trainline consistently cite excessive push notifications for promotional offers and travel reminders as a major annoyance. For an app that users primarily install for infrequent travel booking, aggressive notification patterns create churn and negative reviews that erode brand trust.
Key features to replicate
The core feature set any Trainline alternative needs — plus what you can improve on.
GTFS/GTFS-RT integration for rail schedules
GTFS (General Transit Feed Specification) provides static schedule data; GTFS-RT provides real-time departure/arrival updates and service alerts. National Rail's Darwin data feed provides UK rail real-time data (separate from GTFS). OpenTripPlanner handles GTFS-based routing for journey planning. National Rail Data API provides the authoritative UK rail data including live departures, platform information, and service disruptions.
UK fare calculation engine
UK rail fare calculation is notoriously complex: hundreds of operator-specific fare rules, time-of-day restrictions (off-peak/super off-peak vary by TOC), Railcard discounts (16-25 Railcard: 1/3 off most fares), zonal logic for London and urban areas, and fare restriction flags. The National Rail ATOC fare data file (FFL format) is the source of truth for fare rules. Building a custom fare engine requires parsing FFL files and implementing the complete restriction and discount logic — typically 8–12 weeks of specialized engineering.
TOC API integration for booking
Actually selling train tickets requires integration with each TOC's booking system or the National Rail Distribution (NRD) API. NRD provides a single integration point covering most UK operators, but requires business agreement with Rail Delivery Group (RDG) and formal accreditation as a Retail Service Provider (RSP). This accreditation process takes 3–6 months and is the single highest barrier to entry for UK rail ticketing.
E-ticket generation with Aztec barcode (UK rail standard)
UK rail e-tickets use Aztec barcode format specified by Rail Delivery Group's Ticket on Departure (ToD) standard. Aztec barcode libraries are available for most platforms. The barcode must encode specific RDG-format data fields in the correct byte order. Tickets must also include NLC (National Location Code) station codes and NRS (National Reservation System) booking reference format.
Seat reservation with real-time seat map
For Advance ticket types and First Class, seat reservation may be mandatory (Eurostar, Avanti West Coast) or optional (LNER, CrossCountry). Real-time seat availability by carriage and seat number requires integration with each operator's seat reservation system — typically accessed via the NRD API. Building an interactive seat map requires SVG carriage diagrams with seat state overlaid from the real-time API.
Split-ticketing optimization engine
Split-ticketing finds combinations of shorter-journey tickets with total cost below the through-fare. The algorithm requires testing fare combinations at intermediate stations along the route. For a 3-station journey (A→B→C), test A→B + B→C versus A→C. For longer routes, the combination space grows — use graph algorithms (Dijkstra's on a fare graph) to find the minimum-cost ticket combination efficiently. TrainSplit's open-source implementation is a useful reference.
Technical architecture
A Trainline alternative is a two-sided rail ticketing platform requiring TOC API accreditation (RDG Retail Service Provider status), complex UK fare calculation, Aztec barcode e-ticket generation, and real-time schedule data from Darwin/GTFS-RT feeds. The regulatory accreditation and fare complexity are the primary barriers — not the web application engineering.
Frontend
Next.js App Router, React Native (mobile), React SPA
Recommended: Next.js App Router for web — SSR for route and journey pages improves SEO for 'train from X to Y' queries. React Native for mobile with Expo, sharing API clients and booking flows between iOS and Android.
Journey planning and routing
OpenTripPlanner, custom GTFS parser, National Rail Darwin API
Recommended: OpenTripPlanner for journey planning using GTFS feeds for initial scheduling. National Rail Darwin real-time feed provides live departure/arrival updates and platform information for UK journeys. OTP handles multi-modal routing; Darwin handles live UK rail data.
Fare calculation
Custom FFL parser, ATOC fare data integration, third-party fare API
Recommended: Custom FFL (ATOC fare data) parser for UK fare calculation — there is no off-the-shelf open-source UK rail fare engine. Budget 8–12 weeks for a fare engine covering the most common journey types, with ongoing maintenance as National Rail updates fare data quarterly.
TOC booking integration
National Rail Distribution (NRD) API, individual TOC APIs, Evolvi/Trainline wholesale
Recommended: NRD API via Rail Delivery Group accreditation provides the single integration point covering most UK operators. RDG Retail Service Provider accreditation takes 3–6 months. Evolvi (KAD) provides a commercial wholesale API as an alternative that transfers some regulatory burden.
Payments
Stripe, Braintree, Worldpay
Recommended: Stripe for consumer payments — UK rail ticketing is straightforward single-transaction e-commerce. Stripe Radar for fraud detection on high-value advance tickets. PCI compliance is handled by Stripe's hosted payment fields.
E-ticket generation
Custom Aztec barcode library, React-PDF, server-side PDF
Recommended: Custom Aztec barcode generation (aztec-js or bwip-js for Node.js) encoded with RDG-standard ticket data fields. React-PDF for ticket PDF layout with barcode embedded. Server-side generation ensures barcode fidelity without client-side rendering differences.
Background jobs
BullMQ + Redis, Temporal, AWS SQS
Recommended: BullMQ for GTFS feed refresh jobs, schedule change notifications, seat map cache refresh, and booking confirmation delivery. Darwin subscription management for real-time service alerts.
Complexity estimate
Complexity 9/10 for UK-only; 10/10 for multi-country. RDG accreditation and fare calculation are the hardest components — both are specialized domain problems requiring deep UK rail industry knowledge. Plan for 6–9 months with a team of 3–4 engineers.
Trainline vs building your own
Open-source Trainline alternatives
Existing projects you can self-host or use as a starting point. Each has trade-offs.
OpenTripPlanner
2.6KOpenTripPlanner is an open-source multi-modal trip planning engine in Java with LGPL-3.0 license. It uses GTFS and GTFS-RT feeds with OpenStreetMap data for routing. v2.9.0 released March 2026. Production-used by transit agencies globally.
transitland-lib
50transitland-lib is a Go library for reading, writing, and validating GTFS data, underpinning Interline's Transitland data hub. v1.3.2 released February 24, 2025.
MOTIS
unverifiedMOTIS is an open-source intermodal mobility platform providing transit routing with real-time updates. It supports GTFS and other European transit formats, and has been used in German transport research contexts.
Build vs buy: the real math
6–9 months
Custom build time
£200,000–£400,000 (agency)
One-time investment
Not applicable vs. Trainline's SaaS model — compare against TOC direct booking (zero fee) and B2B distribution revenue
Breakeven vs Trainline
The build case for a Trainline alternative is unusual because the consumer-facing comparison is not against Trainline's fees (59p–£2.79 per booking) but against TOC apps that already charge zero. Building a Trainline consumer alternative to save booking fees is not a viable business — the fees are already eliminable by booking direct. The viable build cases are: (1) a B2B corporate rail booking platform targeting the £2.8B+ UK corporate travel market where Trainline Solutions charges platform fees and where a custom build offers industry-specific compliance; (2) a split-ticketing-first consumer app that monetizes through transparent savings discovery rather than fees — the consumer value proposition is '£30 saved on every London to Edinburgh booking'; or (3) a multi-modal trip planner for a specific region or market (UK-to-Europe rail, London transport integration) where the booking experience is differentiated from Trainline's generic interface. RDG accreditation (3–6 months) is the gating constraint that must start before writing code.
DIY roadmap: build it yourself
This roadmap covers a split-ticketing-enabled UK rail booking platform as the strongest consumer differentiation against Trainline. Team of 3–4 engineers. RDG Retail Service Provider accreditation must begin in parallel with — ideally before — development.
Journey planning and schedule data
5–6 weeks- Bootstrap Next.js + Supabase project with station, route, and journey data models
- Integrate National Rail Darwin real-time data feed for UK live departures and platform information
- Deploy OpenTripPlanner with UK GTFS feeds for multi-modal journey planning
- Build journey search UI: origin, destination, date, time, passenger count, Railcard selection
- Integrate station autocomplete with National Location Code (NLC) station data from National Rail open data
Fare calculation and split-ticketing
8–10 weeks- Parse ATOC FFL (Fare File Library) data: fare records, restriction codes, Railcard discounts, time-of-day rules
- Build fare calculation engine: apply fare rules per journey type, class, and Railcard
- Implement split-ticketing optimizer: Dijkstra's algorithm on fare graph to find minimum-cost combination
- Build fare comparison display: through-fare vs. split-ticket with savings highlighted
- Validate fare calculations against National Rail sample journeys for accuracy
TOC booking integration and e-tickets
8–12 weeks (overlaps with RDG accreditation)- Complete RDG Retail Service Provider accreditation process (start in month 1)
- Integrate NRD API for ticket booking: reserve, payment, confirm, retrieve
- Implement Aztec barcode generation with RDG-format ticket data encoding
- Build e-ticket PDF generation with React-PDF including Aztec barcode, journey details, and RDG compliance fields
- Build seat reservation flow for mandatory and optional reservation services
Payments, refunds, and operations
4–5 weeks- Implement Stripe payment flow with PCI-compliant card input via Stripe Elements
- Build refund processing: structured ticket refund request to TOC via NRD, consumer Stripe refund
- Implement booking history and e-ticket retrieval in subscriber account
- Build Trainline-competing zero-booking-fee pricing model with transparent cost display
- Set up Datadog APM for journey search latency and booking pipeline success rate monitoring
The fare calculation phase (8–10 weeks) requires deep UK rail industry knowledge — ATOC FFL data format documentation is dense and not publicly accessible without a formal relationship with Rail Delivery Group. Budget for specialist UK rail consultancy time (1–2 weeks) to accelerate the fare engine build. RDG RSP accreditation is the hardest part: it involves legal agreements, technical compliance testing, and operational capability assessment that no amount of engineering skill can shortcut.
Features you can't get from Trainline
This is where a custom build pulls ahead — features impossible or impractical on a shared platform.
Split-ticketing as a default feature with savings display
Trainline does not surface split-ticketing to default users despite potential savings of £10–£50+ per journey on many UK routes. A custom platform that makes split-ticketing the default — displaying 'You could save £28 on this journey with split tickets' on every applicable search result — provides the single most compelling consumer value proposition in UK rail booking and directly addresses Trainline's most criticized omission.
Zero booking fee with transparent monetization
Trainline's 59p–£2.79 booking fees are eliminable by booking direct with TOC apps. A custom platform can charge zero booking fees and monetize through a corporate subscription (£5/month for business travelers with enhanced features), affiliate commissions from hotel and car rental upsells alongside rail tickets, and a premium split-ticketing premium tier for complex journeys.
Railcard optimization and savings calculator
UK rail has 7 types of Railcard offering 1/3 discount on most fares. Most consumers do not know which Railcard provides the best value for their journey patterns. A custom platform can analyze a user's journey history and recommend the optimal Railcard purchase — a feature Trainline does not offer but that directly drives platform loyalty by creating measurable savings.
Corporate rail travel with policy enforcement
Trainline Solutions serves the B2B corporate market, but a custom corporate rail booking tool can implement industry-specific policies: government per diem limits, class restrictions by seniority, preferred operator agreements, and integration with expense management systems (SAP Concur, Expensify) for automatic expense filing from every booking.
Real-time disruption alerts with alternative routing
When a service is cancelled or delayed, Trainline sends a notification — but it doesn't proactively suggest and book alternatives. A custom platform can implement disruption-aware rebooking: detecting delays above 30 minutes, finding the next available alternatives, and offering one-tap rebooking with automatic refund of the affected ticket.
UK-to-Europe multi-modal booking
Trainline covers UK and some European rail after the Trenes.com acquisition, but seamlessly combining UK rail, Eurostar, and European rail (DB, SNCF, Renfe) into a single booking flow remains fragmented. A custom platform specializing in London-to-Europe multi-modal journeys — rail to St Pancras + Eurostar + onward European rail — creates a vertical niche that Trainline's generic interface serves poorly.
Who should build a custom Trainline
Corporate travel managers building UK rail booking tools
The UK corporate travel market processes £2.8B+ in annual rail spend. A corporate-first rail booking platform with policy enforcement, automatic expense filing, and preferred operator rates captures a high-value B2B segment that Trainline's consumer-first interface addresses inadequately. Corporate accounts provide predictable revenue versus per-transaction booking fees.
Travel tech startups with the split-ticketing value proposition
The UK rail market has a documented consumer pain point — opaque fare pricing and unadvertised split-ticketing savings — that a technically sophisticated booking platform can address directly. Monetizing through premium split-ticketing features and corporate subscriptions rather than per-booking fees creates a consumer-aligned business model.
Tourism platforms building UK rail + accommodation packages
UK city breaks and countryside tourism are frequently planned around rail journeys. A platform combining rail booking with hotel reservations, activity tickets, and day-trip itineraries creates a package tourism product that Trainline's pure rail focus cannot offer.
European rail and multi-modal operators expanding into UK
European operators (Deutsche Bahn, Eurail Group, FlixBus) entering the UK market need UK rail integration without starting from scratch on NRD integration and RDG accreditation. A UK rail API wrapper with pre-existing accreditation could serve as a white-label backend for European operators expanding cross-channel.
Skip the DIY — let RapidDev build it
Everything above is doable — but it takes months of full-time work. We build custom Trainline alternatives using AI-accelerated development, delivering in weeks what used to take quarters.
Discovery call (free)
30 minWe map your exact requirements: which Trainline features you need, what custom features to add, your users, integrations, and compliance needs. You get a detailed scope document and fixed-price quote within 48 hours.
AI-accelerated build
6–9 monthsOur engineers use Claude Code, Lovable, and custom AI tooling to build 3–5x faster than traditional development. You see progress in a staging environment every week — not a black box for months.
Launch + handoff
1 weekWe deploy to your infrastructure, transfer the GitHub repo, set up CI/CD, and walk your team through the codebase. You own 100% of the source code — no vendor lock-in, no recurring platform fees.
What you get
Timeline
6–9 months
Investment
£200,000–£400,000 (agency)
vs Trainline
ROI in Not applicable vs. Trainline's SaaS model — compare against TOC direct booking (zero fee) and B2B distribution revenue
30-min call. Fixed-price quote within 48 hours. No commitment.
Frequently asked questions
How much does it cost to build a Trainline alternative?
£200,000–£400,000 agency cost for a UK-only consumer rail booking platform. The cost breakdown is roughly: journey planning and schedule integration (£30K–£50K), fare calculation engine (£50K–£80K), TOC booking integration via NRD (£60K–£100K), e-ticket generation (£20K–£30K), payments and UI (£40K–£70K). RDG accreditation legal costs add £20K–£50K and 3–6 months before ticketing is possible.
How long does it take to build a rail booking platform?
6–9 months with a team of 3–4 engineers for UK-only consumer rail booking. The critical path is RDG Retail Service Provider accreditation (3–6 months) and fare calculation engine development (8–10 weeks) — both must start as early as possible. Multi-country expansion adds 4–6 months per additional market.
Are there open-source Trainline alternatives?
OpenTripPlanner (2.6K stars, LGPL-3.0, Java) is the best open-source routing engine for GTFS-based transit planning. transitland-lib (50 stars, GPL-3.0, Go) handles GTFS parsing. Neither provides booking, fare calculation, or e-ticket generation. No open-source UK rail ticketing stack exists — the fare calculation and NRD integration require proprietary data access.
What is RDG accreditation and why does it matter?
Rail Delivery Group (RDG) Retail Service Provider (RSP) accreditation is the formal certification required to sell UK rail tickets commercially via the National Rail Distribution API. The process involves legal agreements with RDG, technical compliance testing against NRD API specifications, and operational capability assessment. It takes 3–6 months and costs £20K–£50K in legal and compliance fees. Without it, you cannot issue valid UK rail tickets — it is not optional.
How does UK rail fare calculation work?
UK rail fares are governed by ATOC's Fare File Library (FFL) — a complex data format encoding hundreds of operator-specific fare rules, time-of-day restrictions, station groupings, Railcard discount eligibility, and fare validity windows. The FFL file is updated quarterly by National Rail. Building a fare engine requires parsing FFL data and implementing the complete restriction and discount logic. This is specialized domain work — budget 8–10 weeks for a fare engine covering the most common fare types.
What is split-ticketing and should I implement it?
Split-ticketing means buying separate tickets for intermediate stations at a combined cost below the through-fare. For example, London to Edinburgh might cost £120, but London to York (£45) + York to Edinburgh (£55) = £100. Implementing split-ticketing as a default feature using a graph algorithm on the fare database creates the strongest consumer differentiation against Trainline, which does not surface this by default.
Can RapidDev build a custom rail booking platform?
Yes — RapidDev has built 600+ apps including booking systems with complex inventory management and payment processing. We recommend starting the RDG accreditation process in parallel with scoping discussions. Contact us at rapidevelopers.com/contact to discuss the specific UK rail integration requirements.
Is building a Trainline competitor worth it given TOC apps are now free?
Generic consumer competition is hard to justify — TOC apps charge zero booking fees and already capture direct bookings. The viable builds are: (1) split-ticketing-first with a transparent savings model, (2) corporate travel management with policy compliance, or (3) a multi-modal package builder combining rail, hotel, and experiences. All three have clear differentiation from Trainline's generic booking model.
We'll build your Trainline
- Delivered in 6–9 months
- You own 100% of the code
- No per-seat fees, ever
30-min call. No commitment.