The data is based of a scraped/entered train schedule from 2009, and hasn't been updated since.
Essentially, the data is always playing back the regular schedule, but is offset by any delays (which can now be obtained by API, earlier by scraping the railway's mobile site). Other than that they use the average acceleration and braking performance of trains, and the max speed at route points.
The project apparently never was finished: this works but isn't up to date. A very similar site and likely by the same maker won a "Who is better than Google" prize a few years back.
It's funny this link pops up now: the Dutch Railways announced an API on March 31st.
Essentially, the data is always playing back the regular schedule, but is offset by any delays (which can now be obtained by API, earlier by scraping the railway's mobile site). Other than that they use the average acceleration and braking performance of trains, and the max speed at route points.
The project apparently never was finished: this works but isn't up to date. A very similar site and likely by the same maker won a "Who is better than Google" prize a few years back.
It's funny this link pops up now: the Dutch Railways announced an API on March 31st.