# Overview

If you’re doing this, you’re doing it wrong…:

2016-05-31 10:19:45.493314 Client 92.x.x.192 hamburg, germany/hamburg/hamburg
2016-05-31 10:19:48.443380 Client 74.x.x.189 greensboro, united_states/north_carolina/greensboro
2016-05-31 10:19:56.733260 Client 50.x.x.50 beaverton, united_states/oregon/beaverton
2016-05-31 10:19:56.745653 Client 50.x.x.50 beaverton, united_states/oregon/beaverton
2016-05-31 10:19:56.759656 Client 50.x.x.50 beaverton, united_states/oregon/beaverton
2016-05-31 10:19:56.819283 Client 50.x.x.50 beaverton, united_states/oregon/beaverton
2016-05-31 10:20:16.287744 Client 5.x.x.13 kaiserslautern, germany/rhineland-palatinate/kaiserslautern
2016-05-31 10:20:35.182942 Client 85.x.x.140 katowice, poland/silesia/katowice
2016-05-31 10:20:47.029550 Client 193.x.x.226 oslo, norway/oslo/oslo/oslo

Lots of people use the finger service @graph.no in an automated way. That’s quite alright, it’s what it’s there for. As an example:

# Overview

By request, a quick how-to on setting up your own realtime monitor for ruter.no, Oslos public transit.

# As simple as possible

• Get an old laptop
• Set it to start a web browser at boot
• Make the browser start to i.e. http://mon.ruter.no/monitor/3010314/Adamstuen/2190090

Done!

# Background

Ruter has an API, so you can go crazy and implement your own client easily, like I’ve done with rutercli. But there’s a much simpler solution. They’ve got a website in the same style as their public monitors, mon.ruter.no. You can start with the link above, and find the numbers and names you need from a normal ruter.no search. You’ll also find NSB stuff there. See ruter.no/reiseplanlegger/sanntid/egen-sanntidsskjerm for more info.