Skip to main content

About TrainsTracking

We built TrainsTracking because every country had its own railway website — often in a local language, poorly designed, and impossible to find from abroad. There was no single, trusted place covering trains worldwide. We're fixing that.

Our Mission

TrainsTracking exists to give anyone in the world — from a tourist planning a journey in Pakistan to a daily commuter in Finland — instant, free access to their train's schedule, live position, fare, and route information, all in one clean, fast, and trustworthy platform.

Rail travel is one of the most sustainable, affordable, and rewarding ways to move between cities and countries. Yet for most of the world, finding accurate, up-to-date train information means navigating a maze of disconnected national websites, often in unfamiliar languages. We believe that information barrier shouldn't exist. Train timetables are public data — every passenger deserves to access them easily.

Since launch, we have grown to cover 76 countries, integrating live railway APIs where operators publish one and maintaining verified timetable data for dozens of operators worldwide.

How Our Data Works

We source data exclusively from official railway operators, government transport agencies, and open data programmes. We do not scrape unofficial sources or accept user-submitted timetable data without verification. Our three-tier system reflects the state of open data availability across the global rail industry.

Tier 1 — Live GPS

We connect directly to official GTFS-RT feeds and REST APIs — including Digitraffic (Finland), iRail (Belgium), DB Open Data (Germany), and Amtrak — refreshing positions every 30 seconds.

Tier 2 — Schedule APIs

For countries without live GPS, we pull timetable data from official schedule APIs and update automatically whenever operators publish new timetables. Data is verified against multiple sources.

Tier 3 — Verified Static Schedules

For countries with no public API, our local data team manually curates schedules directly from official operator websites, printed timetables, and government PDFs — verified and date-stamped on every page.

All data sources are documented publicly on our Data Sources page.

How Our Pages Are Made

TrainsTracking combines a structured railway database with human editorial work, and we believe in being transparent about which is which. Schedule, station, route, and fare pages are generated from our database of official operator timetables — that is the only way to keep tens of thousands of timetable pages current. Every dataset behind those pages is imported from the official sources listed on our Data Sources page, checked by our editorial team for completeness and duplicates before publication, and re-verified when operators publish timetable changes.

Our travel guides, country introductions, reviews, and blog articles are researched and written by the TrainsTracking team, drawing on official timetables, fare tables, and published operator information rather than AI-generated text. Every guide carries a last-reviewed date.

If you find an error on any page — a wrong departure time, an outdated fare, a station that has closed — email [email protected] with the page URL. Verified corrections are applied within 48 hours.

Technology

TrainsTracking is built as a high-performance web application using modern open-source technologies. Every page is server-rendered for speed and SEO, and schedule pages are regenerated automatically whenever new data arrives — so you always see the most current information without a full page reload.

Next.js & React

Server-rendered pages with ISR for near-instant load times and fresh schedule data.

Supabase

PostgreSQL database powering our train, station, and route index with full-text search.

19 Live APIs

Direct integrations with official railway data sources across four continents.

Our Team

TrainsTracking is built and maintained by a small team of two engineers who are passionate about rail travel and open data.

Muhammad Adeel
Full-Stack Engineer

Full-stack developer and systems architect behind the TrainsTracking platform's core infrastructure. Adeel built the Next.js application, API integrations, and the real-time data processing layer that keeps schedule information updated around the clock. He brings extensive experience in building high-performance, SEO-optimised web products.

adeelahmad.com
Muhammad Zeeshan
Backend & API Engineer

Backend engineer specialising in API design, database architecture, and scalable data systems. Zeeshan architected the Supabase-powered database layer and the train indexing pipeline that powers TrainsTracking's search and retrieval across 19 live railway data sources. He ensures the platform remains fast, reliable, and secure.

zeeshansoft.com

Data Accuracy Commitment

For real-time data (Tier 1), accuracy depends on official operator APIs and is typically within 30 seconds of ground truth. For schedule data (Tier 2 and 3), we source directly from official timetables and mark the last verification date on every page.

If you spot an incorrect departure time, station name, or fare, please contact us at [email protected] — we verify and correct confirmed errors within 24 hours.

Contact

General enquiries, data corrections, and press:

Or use the contact formand we'll respond within one business day.