Southeastern rail passengers were left furious after their train didn't stop at Sidcup - leaving them stranded in Dartford.

Chaos erupted on the 5.04pm train from Victoria to Dartford on October 16 when passengers hoping to alight at Sidcup ended up in Dartford.

Southeastern have said that the train did not call at the station as the 'stop was missed due to an error.'

Many users took to Twitter to voice their anger over the situation.

Karly Jones tweeted: "Didn't fancy stopping at Sidcup today @Se_Railway ? No announcement and goes straight to Dartford from new Eltham."

Lucy Freeman added: "Stranded at Dartford because the train driver didn't stop at Sidcup! Absolute joke!!!"

It was reported over Twitter that angry passengers confronted the driver to find out why he hadn't stopped at Sidcup.

Marilisa Lanave said: "People challenged the driver - asked him to bring everyone back to Sidcup! SE staff didn't know what to do."

A spokesman for Southeastern said: "This service failed to call at Sidcup last night due to an error on the train schedule.

"This train is timetabled to call at Sidcup but due to this error this stop was missed last night.

"We have investigated the cause of the error and this has been rectified and the service will continue to call at Sidcup station.

"We are very sorry to all our passengers who were inconvenienced by this. If passengers were delayed by 30 minutes or more as a result, we encourage them to claim compensation."

Were you affected by this error? Call Fiona Simpson on 01689 885734 or email: fiona.simpson@london.newsquest.co.uk