Skip to content

Roadmap

anonymous44401 edited this page Jul 27, 2026 · 2 revisions

anonymous44401 Project Roadmap

You can suggest features by creating an issue and adding the enhancement tag.

Coming in the next few months:

New watch_service feature

This feature will be similar to get_live, except it'll show you the live information for any service.

Preview:

03:23 Peterborough to London King's Cross
  │ 
  ├─ 03:23 Peterborough (P1)
  │ 
  ├─ 03:38 Huntingdon (P2)
  │
  ├─ 03:45 St Neots (P4)
  │ 
  ├─ 03:53 Sandy (P1)
  │ 
  ├─ 03:57 Biggleswade (P1)
  │ 
  ├─ 04:02 Arlesey (P1)
  │ 
  ├─ 04:11 Hitchin (P1)
  │ 
  ▼  04:17 Stevenage (P1) 
  │
  ├─ 04:45 Finsbury Park (P1)
  │ 
  ╰─ 04:51 London King's Cross (P1)

             
Operated by Thameslink
Formed of 8 coaches

04:16:17

Not final product - will feature colours

This feature is currently in development and is expected to be released in Autumn 2026.


Coming further down the line

realtime-trains-rs

A new package, based on realtime-trains-py, for Rust is currently in development. Built from the ground up, once released, realtime-trains-rs will be baseline for all of my Realtime Trains API Wrapper projects, so will normally get new features before they're introduced to realtime-trains-py.

Both projects will remain separate, but will share functionality and styles.

Expected to be released at some point in 2027...


Other bits on the roadmap:

  • Async for get_live and watch_service
  • Automated tests
  • Better file management for complex mode
  • CLI support
  • Complexity per method
  • More API features (such as Network Rail specific endpoints)
  • Reimplementation of get_arrivals and get_station
  • Station lookup to find CRS and vice versa

A few of the above features will come once realtime-trains-rs releases.

Clone this wiki locally