Service history for N474
| Date | Service | Consist |
|---|---|---|
| 15 December 2020 17:20 | 8630 up Albury | N474 PCJ493 SN15 |
| 15 December 2020 12:05 | 8615 down Albury | N474 SN15 PCJ493 |
| 14 December 2020 06:35 | 8610 up Albury | PCJ493 SN15 N474 |
| 13 December 2020 18:02 | 8625 down Albury | SN15 N474 PCJ493 |
| 13 December 2020 12:45 | 8620 up Albury | PCJ493 SN15 N474 |
| 12 December 2020 12:05 | 8615 down Albury | N474 SN15 PCJ493 |
| 11 December 2020 18:02 | 8625 down Albury | N474 SN15 PCJ493 |
| 11 December 2020 12:45 | 8620 up Albury | N474 PCJ493 SN15 |
| 11 December 2020 07:05 | 8605 down Albury | N474 SN15 PCJ493 |
| 10 December 2020 06:35 | 8610 up Albury | N474 PZ260 SN8 |
| 9 December 2020 18:02 | 8625 down Albury | N474 SN8 PZ260 |
| 9 December 2020 12:45 | 8620 up Albury | N474 PZ260 SN8 |
| 9 December 2020 07:05 | 8605 down Albury | N474 SN8 PZ260 |
| 2 December 2020 06:35 | 8610 up Albury | N474 PZ260 SN8 |
| 1 December 2020 18:02 | 8625 down Albury | N474 SN8 PZ260 |
| 1 December 2020 12:45 | 8620 up Albury | N474 PZ260 SN8 |
| 1 December 2020 07:05 | 8605 down Albury | N474 SN8 PZ260 |
| 6 July 2020 17:20 | 8630 up Albury | N474 PCJ491 SN1 |
| 6 July 2020 12:05 | 8615 down Albury | N474 PCJ491 SN1 |
| 4 July 2020 17:20 | 8630 up Albury | N474 PCJ491 SN1 |
| 4 July 2020 12:05 | 8615 down Albury | N474 PCJ491 SN1 |
| 3 July 2020 06:35 | 8610 up Albury | N474 PCJ493 SN15 |
| 2 July 2020 18:02 | 8625 down Albury | N474 PCJ493 SN15 |
| 2 July 2020 12:45 | 8620 up Albury | N474 PCJ493 SN15 |
| 2 July 2020 07:05 | 8605 down Albury | N474 PCJ493 SN15 |
| 30 June 2020 17:20 | 8630 up Albury | N474 PCJ491 SN1 |
| 30 June 2020 12:05 | 8615 down Albury | N474 PCJ491 SN1 |
| 30 June 2020 06:35 | 8610 up Albury | N474 PCJ491 SN1 |
| 29 June 2020 18:02 | 8625 down Albury | N474 PCJ491 SN1 |
| 29 June 2020 12:45 | 8620 up Albury | N474 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.