Conflicting archive train times

[williamn]

I took the 22.46 London Victoria to Lewes on 1 August, which was delayed. Southern seem to think it should have arrived at 00.02, whereas realtime trains have it down for a 23.55 arrival. Which is correct? It seems that the delay was annoyingly only 14 minutes in any case, but I'm still curious as to the discrepancy.

 

[Mcr Warrior]

I took the 23.36 London Victoria to Lewes on 1 August, which was delayed. Southern seem to think it should have arrived at 00.02, whereas realtime trains have it down for a 23.55 arrival. Which is correct? It seems that the delay was annoyingly only 14 minutes in any case, but I'm still curious as to the discrepancy.

Do you mean the 22.46 departure from London Victoria?

 

[williamn]

Yes sorry, will correct that!

 

[MikeWh]

I don't know where Southern get that time of 0002 from, but the realtimetrains detailed version has the arrival at Lewes at 0010 and departure at 0010.5. That's 15 minutes late arriving and 14.5 minutes late departing. I'd contest their decision if I were in your shoes.

 

[SargeNpton]

Is RealTime Trains quoting the working times, whilst Southern is showing the advertised times?

 

[30907]

Is RealTime Trains quoting the working times, whilst Southern is showing the advertised times?

The advertised stop was 2355-2356

 

[Vexed]

As the delay made it cross midnight Southern might have got their dates mixed up. The service the next day (2nd August) has an arrival time at Lewes of 0003 in both TRUST and Darwin which is very close to what Southern claims the service you were on was delayed by.

0010 is definitely the correct time for the service with a start date of 1st August - 1F86 stepped into the Lewes platform 1 berth at 00:08:53 with an offset of 73 seconds would make the arrival time approximately 00:10:06, which then gets truncated to 0010.

This is worth appealing.

 

[williamn]

thanks all, happily they have accepted the claim and I stall try not to spend the £2 all at once!