===============
= ptrcnull.me =
===============

rtd.banenor.no

Real Norwegian departure boards, from the comfort of your own home!

⚠️ This is not a full blog post!
Instead, it's a Gist-like dump of random information that I couldn't find elsewhere.
If you've got something to add to the topic, feel free to reach out to me ^^

So, the screens on Bane NOR stations are actually just web browsers, and by having one crash near me, I managed to get this:

https://rtd.banenor.no/web_client/std?station=OSL

And wouldn't you know it, it's just a public web app, available from anywhere!

Departure screen, showing a "Not in service" warning

Annoyingly, I wasn't able to find anything like a GitHub repo — of which Bane NOR and Entur have plenty — or even a more detailed documentation of the parameters besides what's on their website, so... here goes:

Those parameters then get rendered by some script server-side, and passed to an iframe pointing at /rtd/{layout}.html, so for example:

https://rtd.banenor.no/rtd/landscape.html?id=TND-RTD%2FArrival&hideNotice=false&noPassengerDisplay=false&header=true&station=Trondheim S

That goes through a few more iframes (for some reason), but the parameters are not being transformed further, so let's look at these as well.

Starting with the last one, as far as I can tell, the station parameter is used only for the header, and otherwise doesn't affect anything. The id param is kinda interesting though, because it allows for more options that I wasn't able to achieve with just the /web_client/std ones, such as TND-RTD/Departure-Freight showing freight departures from Trondheim S. Once in a while, pageCount also shows up, but no matter the value, it didn't affect the actual display.

Besides rtd.banenor.no, the same app is also hosted on http://rtd.opm.jbv.no:8080jbv.no seems to be owned by Bane NOR as well, and the hostname is pointing to the same server, so not much surprise there.