©2026 Phil Wieland
|
Train Service Performance at Huyton - June 2012
| Date | Scheduled | Trains Run | On Time | Within 5 min. | Comments |
| 1 | 164 | 164 | (100.0%) | 112 | (68.3%) | 146 | (89.0%) | |
| 2 | 96 | 94 | (97.9%) | 67 | (69.8%) | 82 | (85.4%) |
Person hit by train at Leyland at about 09:00
Monitoring system down 10:30 to 17:40, no trains logged between these times.
|
| 3 | 65 | 65 | (100.0%) | 47 | (72.3%) | 57 | (87.7%) | |
| 4 | 157 | 155 | (98.7%) | 126 | (80.3%) | 143 | (91.1%) |
Signalling problem at Lime Street from start of service until 06:30.
|
| 5 | 157 | 157 | (100.0%) | 137 | (87.3%) | 149 | (94.9%) | |
| 6 | 157 | 156 | (99.4%) | 136 | (86.6%) | 153 | (97.5%) | |
| 7 | 157 | 149 | (94.9%) | 121 | (77.1%) | 138 | (87.9%) |
Signalling problem between Wavertree and Broad Green from start of service until 07:40
|
| 8 | 164 | 164 | (100.0%) | 115 | (70.1%) | 139 | (84.8%) | |
| 9 | 164 | 164 | (100.0%) | 150 | (91.5%) | 160 | (97.6%) | |
| 10 | 57 | 57 | (100.0%) | 48 | (84.2%) | 53 | (93.0%) | |
| 11 | 157 | 154 | (98.1%) | 136 | (86.6%) | 149 | (94.9%) | |
| 12 | 47 | 47 | (100.0%) | 43 | (91.5%) | 46 | (97.9%) |
Data feed down 08:06 to 19:24, no train information logged between these times.
|
| 13 | 157 | 156 | (99.4%) | 134 | (85.4%) | 150 | (95.5%) | |
| 14 | 157 | 157 | (100.0%) | 134 | (85.4%) | 150 | (95.5%) | |
| 15 | 164 | 164 | (100.0%) | 131 | (79.9%) | 155 | (94.5%) | |
| 16 | 164 | 164 | (100.0%) | 141 | (86.0%) | 159 | (97.0%) | |
| 17 | 56 | 56 | (100.0%) | 52 | (92.9%) | 55 | (98.2%) | |
| 18 | 157 | 155 | (98.7%) | 104 | (66.2%) | 131 | (83.4%) | |
| 19 | 157 | 154 | (98.1%) | 115 | (73.2%) | 144 | (91.7%) | |
| 20 | 157 | 157 | (100.0%) | 102 | (65.0%) | 135 | (86.0%) |
No notification received, but personal observation at 18:45 revealed a signal failure at Huyton, with the Inner Home on the Down St Helens being passed at danger. Trains were mostly late 17:30 - 20:00 although I cannot say whether these were all for the same reason.
|
| 21 | 157 | 157 | (100.0%) | 130 | (82.8%) | 149 | (94.9%) | |
| 22 | 164 | 162 | (98.8%) | 133 | (81.1%) | 155 | (94.5%) | |
| 23 | 164 | 164 | (100.0%) | 142 | (86.6%) | 158 | (96.3%) | |
| 24 | 56 | 56 | (100.0%) | 44 | (78.6%) | 52 | (92.9%) | |
| 25 | 157 | 156 | (99.4%) | 134 | (85.4%) | 153 | (97.5%) | |
| 26 | 157 | 157 | (100.0%) | 127 | (80.9%) | 152 | (96.8%) | |
| 27 | 157 | 157 | (100.0%) | 147 | (93.6%) | 157 | (100.0%) | |
| 28 | 157 | 156 | (99.4%) | 134 | (85.4%) | 154 | (98.1%) | |
| 29 | 164 | 164 | (100.0%) | 112 | (68.3%) | 150 | (91.5%) | |
| 30 | 164 | 162 | (98.8%) | 138 | (84.1%) | 158 | (96.3%) | |
| June | 4208 | 4180 | (99.3%) | 3392 | (80.6%) | 3932 | (93.4%) | |
Notes
- The figures are derived from the public live departure board systems. These do not always correspond precisely to actual train running.
- Trains cancelled by planned engineering works are not counted as a cancellation. (As long as they are removed from the departure board system.)
- Rail replacement buses are not counted, since running information is not available.
- Trains running within two minutes of correct time are deemed to be on time. I also show trains within five minutes, the railway's standard.
|