API expectedArrival times an hour behind current time


I’ve listed below the expectedArrival time, from a fetch, showing ‘11:03’ but the current time is 12:03.

destinationName: “Upminster Underground Station”
destinationNaptanId: “940GZZLUUPM”
direction: “outbound”
expectedArrival: “2022-10-07T11:03:23Z”

Also testing the api on tfl’s website the times being returned are an hour behind the current time.

Any ideas?

Thank you.


There’s a “Z” in the time response which means the datetime is GMT, but the current time in London is is BST.

1 Like