DateServiceConsist
6 July 2020 17:208630 up AlburyN474 PCJ491 SN1
6 July 2020 12:058615 down AlburyN474 PCJ491 SN1
4 July 2020 17:208630 up AlburyN474 PCJ491 SN1
4 July 2020 12:058615 down AlburyN474 PCJ491 SN1
4 July 2020 06:358610 up AlburyN457 PCJ491 SN1
3 July 2020 18:028625 down AlburyN457 PCJ491 SN1
3 July 2020 12:458620 up AlburyN457 PCJ491 SN1
3 July 2020 07:058605 down AlburyN457 PCJ491 SN1
2 July 2020 17:208630 up AlburyN457 PCJ491 SN1
2 July 2020 12:058615 down AlburyN457 PCJ491 SN1
2 July 2020 06:358610 up AlburyN457 PCJ491 SN1
1 July 2020 18:028625 down AlburyN457 PCJ491 SN1
1 July 2020 12:458620 up AlburyN457 PCJ491 SN1
1 July 2020 07:058605 down AlburyN457 PCJ491 SN1
30 June 2020 17:208630 up AlburyN474 PCJ491 SN1
30 June 2020 12:058615 down AlburyN474 PCJ491 SN1
30 June 2020 06:358610 up AlburyN474 PCJ491 SN1
29 June 2020 18:028625 down AlburyN474 PCJ491 SN1
29 June 2020 12:458620 up AlburyN474 PCJ491 SN1

Notes on the data

The information in the V/LineCars Tracker was collated from public facing V/Line service data. Data collection continued from July 2020 until December 2020, when consist information was removed.

Unfortunately the data was not 100% accurate - things to keep in mind include:

  • The consist for a given service might be changed before departure time, but the data might not get updated, resulting in inaccurate data being logged by the V/LineCars Tracker.
  • Data entry errors sometimes result in non-existent carriages being included in a given consist.
  • Non-revenue movements are not included in the data, so 'last seen' dates reflect revenue services.
  • 'First seen' date reflects the first appearance in revenue service, blank values mean that a service appeared before the tracker was switched on.
  • 'SH' and 'SH' carriage sets are not tracked as 3-car sets, but as a six car long 'SSH' or 'SLH' carriage set.
  • 'N', 'FN' and 'VN' codes do not appear to reflect the code actually applied to the carriage set.