Hi John, I am sorry to hear that. I've not heard of such issue before. Can you go the '’more'’ menu in the app → settings. There you can enable error logging and sent it to us. We will then be able to look into your specific case.  If you are just planning your trip (instead of finding journeys to add to your pass) you can also search for trains via our timetable here. 

I enabled the error logging in the settings.

After further investigation I located the problem to the part of Norway that is served by Go Ahead. Other parts, served by VY, like Oslo - Drammen and Oslo - Trondheim served by Nord works. Take a look at the screenshots I provided :)

Another thing I have asked about before, you need to include scandinavian name compatibility, so that stations like Ål, Ålen, Åndalsnes can be located both by typing Å and AA or Øyeflaten can be located both by typing Øyeflaten and Oeyeflaten.

By the way the search function on the website works, it’s just the app. I’ve tried it on at least four seperate installations, several Android versions and several phones.

That's a data problem. Go Ahead probably had not yet delivered their data when the monthly update for the rail planner app was prepared. Maybe they'll be in the next update.

But the Interrail planner app can't be relied on anyway, one of the reasons being exactly that it only has monthly updates. It's better to use the operator's planners/websites and for international planning, use the DB or ÖBB websites ot apps.

The problem has persisted for between 4-6 months, so this really needs to be fixed.

Regarding the planning part, you are dead wrong in your assumption. As a train conductor this is the best tool I can use. It’s offline, shows train numbers, can show crossing train numbers, departures and arrivals from stations, and it shows the length of stay on stations.

Why is this problem marked as “solved”?

As to the planning: I meant the reliability of the timetable data, not of the internet connection. The planner only has monthly updates, but weekly updates would be needed to have reasonably reliable data.

If data have been missing for several months now, then there may be a problem indeed. The Go Ahead data are included in the DB planner, so presumably the European Timetable Centre also has the data. @Nanja, doesn't that mean that the planner app should also contain the data?

Hi John, thanks for enabling the error logging and providing the additional information. I've created a ticket so the relevant department will be looking into the issue as soon as possible. We will also take along the request regarding Scandinavian names. As soon as I know more, you'll be the first one to know. Apologies for the inconvenience once again and I hope to get back to you soon. 

@rvdborgt Good question! I hope to find out why it is included in the DB planner and not in the Rail Planner App. Will get back to you on that. 

@rvdborgt can you perhaps provide a screenshot of the Go Ahead data showing in the DB planner? Thaniks

Lines in Norway operated by Go Ahead:
https://go-aheadnordic.no/trafikk-ruter-linjer/rutetabeller
(3 PDF files)

Example of trains that are in the DB planner but not in the planner app:
 

You can do more checks by comparing the above PDFs, the DB planner and the app.

Good evening,

@John34, there was an app update today and guess what… the planner app now finds trans for the examples you showed. Are there still any trains missing?

This shows it was really a data problem.

Amazing Back on track. Now just waiting for scandinavian signs.

Thanks @rvdborgt for the screenshot. To come back to your question regarding timetable data, DB is using their own database so data is not 100% from the database of the European Timetable center according to our reservation specialist. Therefore, timetable information can differ if the carrier did provide it differently or incomplete in the database of the European Timetable Centre that we are using for our timetable. With such a regional carrier it can be that data in the database of the European Timetable Centre is not always updated. 

Thanks for checking rvdborgt! Happy to hear it has been resolved by the app update!