ThanksIt's the journey planner behind some ticketing websites (including the forum's) and TVMs.

You forgot to mention that it is absolutely brilliant. My biggest pro is that it will suggest the fastest route even if it is quite indirect. Ipswich to Ely at 07:00 is an example, with the Greater Anglia app suggesting the 07:58 direct train (arrives at 08:59), and FastJP suggesting the 07:07 to Norwich, followed by the 07:55 to Ely (arrives at (08:49).It's the journey planner behind some ticketing websites (including the forum's) and TVMs.
Not sure if I'm missing something, but the 'via Norwich' you quoted takes almost twiceIpswich to Ely at 07:00 is an example, with the Greater Anglia app suggesting the 07:58 direct train (arrives at 08:59), and FastJP suggesting the 07:07 to Norwich, followed by the 07:55 to Ely (arrives at (08:49).
It's clearly "fastest" in the meaning of "reaching the destination the soonest".Not sure if I'm missing something, but the 'via Norwich' you quoted takes almost twice
as long as the direct train, rather than being the "fastest route"?
MARK
Although if you're willing to start just before 7:00 and take a risk with the connection at Cambridge, you could take 2W04 (06:56 Ipswich-Cambridge, arrives at Cambridge P5 08:15) and have a stroll to the adjacent platform 6 to catch 2K60 (08:19 Cambridge-Norwich, arriving at Ely at 08:37).You forgot to mention that it is absolutely brilliant. My biggest pro is that it will suggest the fastest route even if it is quite indirect. Ipswich to Ely at 07:00 is an example, with the Greater Anglia app suggesting the 07:58 direct train (arrives at 08:59), and FastJP suggesting the 07:07 to Norwich, followed by the 07:55 to Ely (arrives at (08:49).
Which the Greater Anglia app won't suggest because Norwich is not on a permitted route for a Ipswich-Ely ticket. TrainSplit will offer this quicker journey but at a significant premium due to the combination of tickets to make it valid, something the GA app can't do.You forgot to mention that it is absolutely brilliant. My biggest pro is that it will suggest the fastest route even if it is quite indirect. Ipswich to Ely at 07:00 is an example, with the Greater Anglia app suggesting the 07:58 direct train (arrives at 08:59), and FastJP suggesting the 07:07 to Norwich, followed by the 07:55 to Ely (arrives at (08:49).
Depends on the ticket held. The route is certainly valid on an Anglia Plus Day RangerWhich the Greater Anglia app won't suggest because Norwich is not on a permitted route for a Ipswich-Ely ticket. TrainSplit will offer this quicker journey but at a significant premium due to the combination of tickets to make it valid, something the GA app can't do.
Good point!Depends on the ticket held. The route is certainly valid on an Anglia Plus Day Ranger![]()
Sure, but it also offers a second itinerary with the same arrival and departure times with only one change at Reading.Just had a play on FastJP to see what it offers. I tried Basingstoke to Bristol Temple Meads. This was one it came up with. A mildly bonkers (but harmless) extra change of trains.
This is a screenshot of the output, showing a change at Reading West, before the expected change at Reading.

Google Maps also takes the latter approach of the 0707, changing at Norwich.You forgot to mention that it is absolutely brilliant. My biggest pro is that it will suggest the fastest route even if it is quite indirect. Ipswich to Ely at 07:00 is an example, with the Greater Anglia app suggesting the 07:58 direct train (arrives at 08:59), and FastJP suggesting the 07:07 to Norwich, followed by the 07:55 to Ely (arrives at (08:49).
Depends on the ticket held. The route is certainly valid on an Anglia Plus Day Ranger![]()
However, in the context being discussed of a departure around 0700, it is not valid due to the morning peak restriction.Good point!
Whoops. I use a staff card so the first ticket that came to my mind was the day ranger. Forgot that there's a morning restriction there!However, in the context being discussed of a departure around 0700, it is not valid due to the morning peak restriction.
Your point still stands - it is a valid routeWhoops. I use a staff card so the first ticket that came to my mind was the day ranger. Forgot that there's a morning restriction there!

It only works for "Must change here" mode.Although I've used it successfully in the past, I just can't get the "Extra Time" at change/via stations to have any effect, either with negative or positive times. I've tried clearing site data, I've tried both Chrome and Firefox and I've tried all sorts of options and variations. But it seems to have no effect whatsoever.
Is this feature currently broken or (maybe more likely) am I just doing something stupid?
Thanks, but that was what I was using, "Must Change Here". However, I've just realised what the problem was when adding extra change time. It doesn't work if you specify e.g. "+10", you need to just specify "10".It only works for "Must change here" mode.
The site is poorly designed and offers the input regardless as to the selection, but it is doomed not to work unless you have picked "Must change here".
Accredited journey planners like FastJP are required to use official minimum connection times as specified by RDG. These are excessive for most London termini but a journey planner would not get accredited if it made up its own values.I've never found a journey planner that will plan a realistic cross London journey. Fastjp is great for finding what a valid connection is but since the minimum connection time between Euston and Liverpool Street is 45 mins and it actually takes 20 this is not hugely useful for actually travelling.
Unfortunately there is an incentive to have these ridiculous MCTs: it means a delay to the first leg of your journey won't result in a missed connection and hence delay repay.Frankly, a better solution would be if minimum connection times were reduced to a more sensible level
That's good news!Raileasy have indeed asked FastJP about commissioning support for such a thing.