Service history for SSH23
Date | Service | Consist |
---|---|---|
17 July 2020 07:31 | 8220 up Melton | N458 SSH23 |
16 July 2020 17:59 | 8253 down Bacchus Marsh | N458 SSH23 |
16 July 2020 07:31 | 8220 up Melton | N470 SSH23 |
15 July 2020 17:59 | 8253 down Bacchus Marsh | N455 SSH23 |
15 July 2020 08:03 | 8738 up South Geelong | N459 SSH23 |
14 July 2020 18:18 | 8797 down Geelong | N459 SSH23 |
14 July 2020 08:03 | 8738 up South Geelong | N456 SSH23 |
13 July 2020 18:18 | 8797 down Geelong | N472 SSH23 |
13 July 2020 08:03 | 8738 up South Geelong | N468 SSH23 |
10 July 2020 18:18 | 8797 down Geelong | N473 SSH23 |
10 July 2020 16:09 | 8237 down Bacchus Marsh | N473 SSH23 |
10 July 2020 06:55 | 8306 up Seymour | N469 SSH23 |
9 July 2020 17:11 | 8327 down Seymour | N469 SSH23 |
9 July 2020 05:10 | 8360 up Shepparton | N469 SSH23 |
8 July 2020 19:08 | 8369 down Shepparton | N469 SSH23 |
8 July 2020 06:55 | 8306 up Seymour | N452 SSH23 |
7 July 2020 17:11 | 8327 down Seymour | N452 SSH23 |
7 July 2020 05:10 | 8360 up Shepparton | N452 SSH23 |
6 July 2020 19:08 | 8369 down Shepparton | N452 SSH23 |
6 July 2020 19:08 | 8369 down Shepparton | N473 SSH23 |
6 July 2020 05:10 | 8360 up Shepparton | N454 SSH23 |
5 July 2020 18:32 | 8369 down Shepparton | N454 SSH23 |
4 July 2020 16:02 | 8368 up Shepparton | N454 SSH23 |
4 July 2020 12:52 | 8365 down Shepparton | N454 SSH23 |
4 July 2020 07:13 | 8362 up Shepparton | N466 SSH23 |
3 July 2020 19:08 | 8369 down Shepparton | N466 SSH23 |
3 July 2020 16:09 | 8237 down Bacchus Marsh | N466 SSH23 |
3 July 2020 06:55 | 8306 up Seymour | N470 SSH23 |
2 July 2020 17:11 | 8327 down Seymour | N470 SSH23 |
2 July 2020 05:10 | 8360 up Shepparton | N471 SSH23 |
1 July 2020 19:08 | 8369 down Shepparton | N471 SSH23 |
1 July 2020 08:03 | 8738 up South Geelong | N471 SSH23 |
30 June 2020 18:18 | 8797 down Geelong | N471 SSH23 |
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.