[...]
I did download Railchecker (android version) a while back, which works very well. The only issue I have is that you have to swipe up and clear to exit the app, you can't simply press back to come out of it. I would have paid for the full version, but would prefer a one off payment option instead of monthly payments. [...]
I thought I had found the perfect app - Railchecker. The app allows me to avoid the Euston Scrum as it has a good platform predictor, based on the arrival platform of the incoming service.
Even if the incoming service hasn't arrived, the app shows, "this service is formed from the 2Y72 18:00 xx service", which allows me to click that 2Y72 service to track its location, or to manually track on OpenTrainTimes map.
But there had been 2 issues recently.
1) It failed to display this altered 2324 service on 21/8/26, which even RTT (and the SWR app) is displaying correctly:
On Railchecker, it was displaying as the 2300 service, delayed by 24mins. So if you checked Railchecker at 2320, the 2300 would have already disappeared from the screen. You would have to manually click "Earlier" to view it.
2) On 24/8/26, the last northbound LNWR service of the day, the 0139 was cancelled (the corresponding first morning southbound service was also cancelled):
The SWR app showed a 0155 Rail Replacement bus. But it didn't show on Railchecker.
So now I use a combination of both SWR and the Railchecker app. SWR for the core departure info, and the Railchecker app to avoid the Euston Scrum.
