Peculiar London Overground service

[Skimpot flyer]

While looking for whether any mainline trains call at Queens Park station (i.e. stopping at the non-Bakerloo/LO platforms) I found this service from Woodgrange Park (near Barking) to Willesden Junction, which appears to pass through Willesden Junction (without calling), then go on a convoluted trip only to arrive back at Willesden Junction a full 17 minutes after departing Kensal Rise station.

Is this correct ?

http://www.realtimetrains.co.uk/train/L71686/2015/08/11/advanced

 

[louis97]

This isn't correct. If you look at the train in the future (here) without the estimated passing locations (RTT adds these in but for this unusual train it is incorrect) you can see its direct Kensal Green to Willesden Junction low level as there is a direct route (this is the only passenger train over it I think). RTT however does not have the line from Kensal Green to the Low Level platforms in its database - although in the next release it will.

 

[causton]

No that is an error in the automatic route calculation by Railmiles. There is a direct line from Kensal Green to the low level "DC" platforms in Willesden Junction where the train terminates. (Hence why there are no reports on that long way round!)

 

[Skimpot flyer]

Any guesses as to why the train's origin is Woodgrange Park, and not the more logical / usual origin, of Barking ?

 

[causton]

It comes empty through Barking on the main c2c platforms, so possibly:

a) to not hold up any c2c trains going towards Fenchurch Street
b) to avoid people being confused ("they always go from platform 1 where is it?")
c) to give people from other stations a chance at getting on, so it doesn't get too busy from just the Barking passengers!

 

[Skimpot flyer]

all three, I suspect. Thanks!

 

[AM9]

RTT lists it pathed as 'Class 150/153/155/156 (Sprinter) DMU'. I suppose that it hasn't been changed since the silverlink 150s did the run. When i was passing through WIJ last week, I noticed a 172 parked in the sidings just south of the low level station so I suppose that was it.

 

[cactustwirly]

this video covers it https://youtu.be/RxcH9M4moks?t=46s

 

[yorkie]

While looking for whether any mainline trains call at Queens Park station (i.e. stopping at the non-Bakerloo/LO platforms) I found this service from Woodgrange Park (near Barking) to Willesden Junction, which appears to pass through Willesden Junction (without calling), then go on a convoluted trip only to arrive back at Willesden Junction a full 17 minutes after departing Kensal Rise station.

Is this correct ?

http://www.realtimetrains.co.uk/train/L71686/2015/08/11/advanced

No that's not correct.

The open data itself is correct, but Realtimetrains is adding phantom intermediate stations to it.

Open Train Times shows the train correctly: http://www.opentraintimes.com/schedule/L71686/2015-08-12
--- old post above --- --- new post below ---

RTT lists it pathed as 'Class 150/153/155/156 (Sprinter) DMU'. I suppose that it hasn't been changed since the silverlink 150s did the run. When i was passing through WIJ last week, I noticed a 172 parked in the sidings just south of the low level station so I suppose that was it.

That's just a timing load. The open data doesn't have any allocations information, so yes that was it.

 

[swt_passenger]

It comes empty through Barking on the main c2c platforms, so possibly:

a) to not hold up any c2c trains going towards Fenchurch Street
b) to avoid people being confused ("they always go from platform 1 where is it?")
c) to give people from other stations a chance at getting on, so it doesn't get too busy from just the Barking passengers!

I think option c) is the main one. It was added as a peak extra service outside the standard pattern a couple of years back, using an otherwise spare unit. (Note that the 0751 and 0806 are 15 mins apart and either side of this one.)

Initially it only ran in passenger service as far as one of the Hampstead stations on its way back to Willesden depot, but this led to platform congestion when it tipped out, so a further application a couple of timetables later had it remaining in service all the way to Willesden. There are also a couple of other 'off pattern' evening peak extras that run over part of the route that were also added as PIXC busters.

 

[AndrewB]

(RTT adds these in but for this unusual train it is incorrect) .

I assume this is a rare case and usually RTT gets it right. Is there any way of telling that it is an added passing place.

 

[87015]

LO have provided another one to be shown when the examples of why RTT doesn't show the allocated traction...
http://www.realtimetrains.co.uk/train/F25874/2015/08/17/advanced

Obviously want some proper trains to play with!

 

[yorkie]

I assume this is a rare case and usually RTT gets it right. Is there any way of telling that it is an added passing place.

All the other sites showing open train time data e.g. Open Train Times and Raildar do not add their own passing places; only Realtimetrains does. So simply use one of the other sites instead.

 

[headshot119]

I assume this is a rare case and usually RTT gets it right. Is there any way of telling that it is an added passing place.

Compare the schedule with the same one about two weeks ahead on Real Time Trains, the extra places don't get added in till nearer the time it runs.

All the other sites showing open train time data e.g. Open Train Times and Raildar do not add their own passing places; only Realtimetrains does. So simply use one of the other sites instead.

OpenTrainTimes isn't as good as RealTimeTrains I find, though I do use both.

For example I'm looking at a service between Margam and Dee Marsh.

On RTT I can see all the actual times for it passing various places between Margam and Llanwern.

On OTT the same train just has "On Time" at Newport, and no reports for anywhere else.

 

[Tom]

RTT adds interpolated locations at 3pm the day before operation of the service.

In a future version, the locations that are interpolated will be shown in italics. At the moment IiRC you can roll over, before the service passes it, the expected time and I believe the tooltip will say estimate.

 

[louis97]

This service is fixed now: http://realtimetrains.co.uk/train/L71686/2015/08/17/advanced

 

[Esker-pades]

This service is fixed now: http://realtimetrains.co.uk/train/L71686/2015/08/17/advanced

From 3 late to 6 early? How much extra time has this service got built into it? (Doing the maths, it's 9 minutes.) But why?

 

[IanD]

From 3 late to 6 early? How much extra time has this service got built into it? (Doing the maths, it's 9 minutes.) But why?

I've used it loads and it has mostly arrived early. Once or twice it has arrived close to right time but we've sat outside Willesden J station for about 10 minutes after branching off the high level line. Presumably there's some conflicting movement on the southbound Bakerloo/dcc lines which you have to cross. If you know it's going to wait, it's quicker to jump off at Kensall Rise and get the one behind which arrives in the high level platforms 8 mins earlier - but that defeats the object!

 

[The Planner]

LO have provided another one to be shown when the examples of why RTT doesn't show the allocated traction...
http://www.realtimetrains.co.uk/train/F25874/2015/08/17/advanced

Obviously want some proper trains to play with!

Ha Ha! superb, that is an 86 or 87 with load 11.
--- old post above --- --- new post below ---

From 3 late to 6 early? How much extra time has this service got built into it? (Doing the maths, it's 9 minutes.) But why?

Its 12, the schedule shows it in the pathing column, it is there as it is timed to sit and wait at the junction.