Utrecht to Munich: issues with Rail Planner App

[peteb]

For anyone travelling towards Munich be aware there appears to be a glitch in Rail Planner. A journey via Mannheim to Heidelberg is suggested, followed by a 27 minute walk to a Munich suburban station, thence to Munich.

Computer has obviously got muddled up but as this is the inter-rail planner it might catch someone out?

Check out my train journey: https://eurailapp.com/share/journey...F-9AE9-51F5DFEEAC76&type=list&brand=interrail

 

[Lemmy99uk]

The Rail Planner app is notorious for errors. I always check an alternative source before adding a journey.

 

[30907]

For anyone travelling towards Munich be aware there appears to be a glitch in Rail Planner. A journey via Mannheim to Heidelberg is suggested, followed by a 27 minute walk to a Munich suburban station, thence to Munich.

Computer has obviously got muddled up but as this is the inter-rail planner it might catch someone out?

Check out my train journey: https://eurailapp.com/share/journey...F-9AE9-51F5DFEEAC76&type=list&brand=interrail

I can't replicate that, though there is an 0913 option for those not wanting to pay a (non-existent!) supplement; arrival at Munich (main part!) at 1713.

 

[nwales58]

Do you have the 'no seat reservations required' filter set on? Are the Amsterdam ICEs still reservation compulsory?
Edit: no, was DB’s 600 km/h wormhole

 

[JB_B]

Using Version 49.3.0, for 18/3/2025 09:13 departure from Utrecht Centraal...

"Muenchen Hbf" as the destination works fine.

"Munich (Germany)" as the destination works fine.

"Munchen" as the destination routes to Muenchen Hbf (Tief) with the itinerary described in post 1.

The mysterious 27 minute "public transport" leg between Heidelberg Weststadt/Südstadt and Höhenkirchen-Siegertsbrunn ( over 3.5 hour / 350 Km by road ) shows up in other queries too - presumably a data error.

 

[peteb]

Using Version 49.3.0, for 18/3/2025 09:13 departure from Utrecht Centraal...

"Muenchen Hbf" as the destination works fine.

"Munich (Germany)" as the destination works fine.

"Munchen" as the destination routes to Muenchen Hbf (Tief) with the itinerary described in post 1.

The mysterious 27 minute "public transport" leg between Heidelberg Weststadt/Südstadt and Höhenkirchen-Siegertsbrunn ( over 3.5 hour / 350 Km by road ) shows up in other queries too - presumably a data error.

Glad someone else can see the crazy 27 minutes for 350km in the itenenary!

I'd just been casually looking at the planner for indicative journey times and routes between Utrecht and Munich. Of course there are dozens of "valid" routes especially if you put in a "via" routing point.

I was a bit concerned that some inter-railer might in haste try to book that journey or upload it, before realising that from Heidelberg it requires a TARDIS more or less to complete the journey!

 

[rvdborgt]

Using Version 49.3.0, for 18/3/2025 09:13 departure from Utrecht Centraal...

Same for me. On Android with online or offline timetables.

"Munchen" as the destination routes to Muenchen Hbf (Tief) with the itinerary described in post 1.

I can't reproduce that. "Munchen" results in Muenchen Hbf and a normal 17:16 arrival.
If I use Muenchen Hbf (Tief), then I get the same result.

The mysterious 27 minute "public transport" leg between Heidelberg Weststadt/Südstadt and Höhenkirchen-Siegertsbrunn ( over 3.5 hour / 350 Km by road ) shows up in other queries too - presumably a data error.

Do you have another example where this shows up?

 

[JB_B]

...

Do you have another example where this shows up?

Heidelberg Hbf to "Muenchen Hbf" all day today most connections go via the "wormhole". ( This is on iOS )

 

[rvdborgt]

Heidelberg Hbf to "Muenchen Hbf" all day today most connections go via the "wormhole". ( This is on iOS )

Thanks, I could reproduce that, in online and offline mode, also on the Interrail website.
It's not the first wormhole that was found.
Edit: reported it to Eurail. Anybody can report such problems here:

https://eurail.zendesk.com/hc/en-001/requests/new