Open Source

Raileasy firmly believes that open source code and open data are central to allowing the industry to continue to innovate - without open data Raileasy wouldn't have its split ticket algorithm as it is today. While we don't expect these to necessarily be useful to other people, we prefer to follow the principle of making things open by default.

We have been proud to sponsor Open Data Camp 10 and 11 (2025 and 2026).

Public repositories

Most public repositories within our GitHub organisation are forks that we've created to fix or improve upstream projects, and are not active repositories. Our maintained repos are below:

A Google Cloud Storage based repository for ASP.NET Core's Data Protection system. Available in NuGet as Raileasy.DataProtection.Gcs.

C#MIT

A curated, although still imperfect, GIS representation of the GB rail network.

GISCC BY-SA 4.0

Python script that is capable of downloading data files for a Rail Data Marketplace product. Note: this predates RDM's support for pushing files to users automatically, and we recommend using this official functionality instead.

PythonGPLv3

A Serilog formatter that outputs to stdout in a JSON format compatible with Google Cloud's Stackdriver. Forked from an unmaintained Redbox project to run on newer .NET versions. Available in NuGet as Raileasy.Serilog.Stackdriver

C#Apache-2.0

Barcode keys

Barcode-based tickets and railcards in Great Britain use asymmetric RSA encryption, the details of which are not part of Rail Delivery Group's publicly available standards, but have been made available by a Freedom of Information request. The industry list of trusted public keys is unfortunately not published, however our public keys are listed below.

Tickets and railcards have a "unique ticket number", generally shown underneath the barcode. These are 11 or 13 characters long, and look like RDCCXTCHLCY. The first two characters, in this case RD are the issuer ID. This identifies the Ticket Issuing System which issued the ticket, and identifies which public keys should be used to try and decode the barcode payload.

Raileasy has two issuer IDs for live barcodes: RD for tickets and RF for railcards. We also have R5 which is our issuer ID in the test environment - a second list of trusted public keys for fake tickets generated by each issuing systems development environments, also used for accreditating these systems. You shouldn't come across R5 tickets in the wild as they are internal only and aren't valid for travel.

Finally, old Raileasy tickets from 2024 and before used issuer ID RE (and R1 in test). These are no longer in use, but we have included the public keys for completeness.

-----BEGIN PUBLIC KEY-----
MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDkHNLYznQHt4TaKmP//DrrUEqv
fQPYpP6BdGvEf5j3ANeO6ZizcOXzU6tbG1VXOpwjvLSmxS5/9hMAxx2d3tGFV0+s
OUCl0HwiWjLa/CmdFn2EFlAFY6hLRHC4Ej0PdfcLADnhoHOuYaXN5PCc4DwjD3iO
Arf6BGO+5Yuf7E2STQIDAQAB
-----END PUBLIC KEY-----

National Location Codes

National Location Codes (NLCs) are a widely used identifier within the industry, primarily for defining fares and accounting. NLCs associated with stations and those required for defining fares are listed in the RSPS5045 location data, however this omits various NLCs used for accounting such as those associated with retailers and Ticket Vending Machines.

All ticket sales and refunds are associated with an NLC in the rail industry's accounting system, LENNON. We've listed our NLCs below, which may be seen inside our barcode payloads or printed on Ticket on Departure tickets (printed after the collection reference, for example RC553TWK/3043).

NLCNameDescription
3043RAILEASY DOMESTICUsed for all public sales to GB-based customers
8362RAILEASY INTERNATIONALUsed for public sales that meet the industry criteria to be classed as non-GB customers
4864RAILEASY BUSINESSUsed for sales by TrainSplit for Business.