Hassocks delay claim denied

[Amorerob]

Travelled from Brighton to London Bridge on Monday 28th October 2024. 12.28 departure on time. Calling all stops en route. Driver had a bit of a turn and failed to stop at Hassocks. Train taken out of service at Three Bridges. Had to wait to get 14.10 to London Bridge. 1 hour+ delay. However claim declined because the 12.28 train apparently arrived at London Bridge just 5 minutes late. No record of train being taken out of service at Three Bridges. I did mange to speak on phone to some customer services person to explain. I was advises to 'resubmit claim'. I did. Declined again for exact same reason. I have submitted a complaint.
I don't suppose there's anybody on this forum who happened to be on that 12.28 train from Brighton?
Does anyone know how to speak to the stationmaster at Three Bridges? Do station masters still exist? Any advice gratefully received.

 

[SuspectUsual]

This train?

Realtime Trains | 9T28 1228 Brighton to Bedford | 28/10/2024

Real-time train running information for 9T28 1228 departure from Brighton to Bedford on 28/10/2024. From Realtime Trains, an independent source of train running info for Great Britain.

www.realtimetrains.co.uk

 

[Amorerob]

Yes. I tried Realtime Trains and didn't really understand what it was displaying.

 

[Haywain]

Travelled from Brighton to London Bridge on Monday 28th October 2024. 12.28 departure on time.

You mean 13:28, don't you?

 

[AlterEgo]

Sounds like you claimed for the wrong train. The 1328 is the one which terminated at Three Bridges.

Realtime Trains | 9T32 1328 Brighton to Three Bridges | 28/10/2024

Real-time train running information for 9T32 1328 departure from Brighton to Three Bridges on 28/10/2024. From Realtime Trains, an independent source of train running info for Great Britain.

www.realtimetrains.co.uk

 

[Haywain]

Had to wait to get 14.10 to London Bridge. 1 hour+ delay.

It's difficult to see how the 13:28 being cancelled at Three Bridges would have led to a delay of over an hour. After it arrived at Three Bridges at 14:03 there were several trains to London Bridge that would have got you there, including the 14:10 which got to London Bridge at 14:44, just 9 minutes later than the scheduled arrival of the 13:28 from Brighton.

 

[Mcr Warrior]

Any advice gratefully received.

Welcome to the forum. Reckon that you may possibly have made an invalid 'Delay Repay' claim / unnecessary complaint, given that you seem not to have been delayed by 15 minutes or more, as @Haywain has pointed out.

I'm guessing that the 1 hour mix up has nothing to do with the clocks having changed from GMT to BST the day previously?!

 

[Amorerob]

You mean 13:28, don't you?

No, I travelled on the 12.28.

 

[SuspectUsual]

No, I travelled on the 12.28.

Look at the links upthread. The 1238 ran throughout, the 1328 was canned at Three Bridges.

 

[Amorerob]

It's difficult to see how the 13:28 being cancelled at Three Bridges would have led to a delay of over an hour. After it arrived at Three Bridges at 14:03 there were several trains to London Bridge that would have got you there, including the 14:10 which got to London Bridge at 14:44, just 9 minutes later than the scheduled arrival of the 13:28 from Brighton.

The wait at Three Bridges was long and wet. Definitely much longer than 9 minutes. Trains had to come in at different platforms because the one from Brighton was stationary at the platform it arrived at. It was quite chaotic. I know the clocks changed. The departure boards kept changing as trains were being redirected (well I assumed that was the reason) and the first departure showing to London Bridge was 14.10.

== Doublepost prevention - post automatically merged: 1 Nov 2024 ==

Sounds like you claimed for the wrong train. The 1328 is the one which terminated at Three Bridges.

Realtime Trains | 9T32 1328 Brighton to Three Bridges | 28/10/2024

Real-time train running information for 9T32 1328 departure from Brighton to Three Bridges on 28/10/2024. From Realtime Trains, an independent source of train running info for Great Britain.

www.realtimetrains.co.uk

Sounds like you claimed for the wrong train. The 1328 is the one which terminated at Three Bridges.

Realtime Trains | 9T32 1328 Brighton to Three Bridges | 28/10/2024

Real-time train running information for 9T32 1328 departure from Brighton to Three Bridges on 28/10/2024. From Realtime Trains, an independent source of train running info for Great Britain.

www.realtimetrains.co.uk

Looks like it but that was a very long 9 minutes if it's true!

 

[Trainguy34]

The 13.28 train was definitely cancelled from Three Bridges onwards, aswell as being shown to pass Hassocks. This arrived at Three Bridges at 14.03. The next departure to London Bridge was from across the platform on platform 3 at 14.11 (9S34). This arrived into London Bridge at 14.44, compared to 14.34 on the 13.28. This delay of 10 minutes is not within the delay repay thresholds, and therefore no money is claimable.

The 12.28 train was not cancelled at all, running flawlessly and arriving into London Bridge at 13.40, a delay of 5 minutes. This delay is also not within the thresholds for delay repay, and therefore no money is due.

== Doublepost prevention - post automatically merged: 1 Nov 2024 ==

The wait at Three Bridges was long and wet. Definitely much longer than 9 minutes. Trains had to come in at different platforms because the one from Brighton was stationary at the platform it arrived at. It was quite chaotic. I know the clocks changed. The departure boards kept changing as trains were being redirected (well I assumed that was the reason) and the first departure showing to London Bridge was 14.10.

== Doublepost prevention - post automatically merged: 1 Nov 2024 ==

If you did get that 14.10 you mentioned, you would have had a 9 minute wait and a 9 minute delay, with no money due.

 

[Amorerob]

The wait at Three Bridges was long and wet. Definitely much longer than 9 minutes. Trains had to come in at different platforms because the one from Brighton was stationary at the platform it arrived at. It was quite chaotic. I know the clocks changed. The departure boards kept changing as trains were being redirected (well I assumed that was the reason) and the first departure showing to London Bridge was 14.10.

== Doublepost prevention - post automatically merged: 1 Nov 2024 ==

== Doublepost prevention - post automatically merged: 1 Nov 2024 ==

OK have to accept I "misremembered" time of train from Brighton! Feel suitably stupid.

 

[30907]

I have to accept I "misremembered" time of train from Brighton! Feel suitably stupid.

You should be careful not to misremember too often

Train companies do check out dubious delay repay claims (not that I am suggesting your claim was such!).

 

[LordCreed]

The next departure to London Bridge was from across the platform on platform 3 at 14.11 (9S34). This arrived into London Bridge at 14.44, compared to 14.34 on the 13.28. This delay of 10 minutes is not within the delay repay thresholds, and therefore no money is claimable.

I suspect that by the time the 13:28 stopped, the driver spoke to control, and it was announced to be terminating, the 14:11 would have long gone.

 

[Haywain]

I suspect that by the time the 13:28 stopped, the driver spoke to control, and it was announced to be terminating, the 14:11 would have long gone.

I don't. Based on what's shown in RTT, I think the driver had already had a discussion while at Burgess Hill and would have known the train was coming out of service at Three Bridges. Even if he didn't the discussion would have taken place after the doors had been released at Three Bridges.