©2024 Phil Wieland
|
Train Service Performance at Huyton - May 2013
| Date | Scheduled | Trains Run | On Time | Within 5 min. | Comments |
|---|
| 1 | 156 | 156 | (100.0%) | 137 | (87.8%) | 149 | (95.5%) | |
| 2 | 156 | 156 | (100.0%) | 132 | (84.6%) | 152 | (97.4%) | |
| 3 | 163 | 162 | (99.4%) | 144 | (88.3%) | 157 | (96.3%) | |
| 4 | 164 | 164 | (100.0%) | 126 | (76.8%) | 154 | (93.9%) | |
| 5 | 56 | 56 | (100.0%) | 39 | (69.6%) | 45 | (80.4%) | |
| 6 | 156 | 155 | (99.4%) | 120 | (76.9%) | 136 | (87.2%) |
A signalling problem caused disruption at Liverpool Lime Street 11:00 to 17:00.
|
| 7 | 156 | 156 | (100.0%) | 122 | (78.2%) | 149 | (95.5%) | |
| 8 | 156 | 156 | (100.0%) | 128 | (82.1%) | 150 | (96.2%) | |
| 9 | 156 | 156 | (100.0%) | 119 | (76.3%) | 140 | (89.7%) | |
| 10 | 164 | 164 | (100.0%) | 136 | (82.9%) | 158 | (96.3%) | |
| 11 | 164 | 154 | (93.9%) | 98 | (59.8%) | 114 | (69.5%) |
A signalling problem near Huyton caused severe disruption 13:00 to 15:30.
A signalling problem at St Helens caused delays 18:00 to 22:00.
|
| 12 | 56 | 56 | (100.0%) | 52 | (92.9%) | 54 | (96.4%) | |
| 13 | 157 | 156 | (99.4%) | 112 | (71.3%) | 139 | (88.5%) | |
| 14 | 157 | 157 | (100.0%) | 130 | (82.8%) | 142 | (90.4%) | |
| 15 | 158 | 147 | (93.0%) | 117 | (74.1%) | 135 | (85.4%) |
A person hit by a train near Wavertree Technology Park caused major disruption from 07:15 to 10:00.
|
| 16 | 157 | 156 | (99.4%) | 139 | (88.5%) | 151 | (96.2%) | |
| 17 | 164 | 164 | (100.0%) | 112 | (68.3%) | 149 | (90.9%) | |
| 18 | 164 | 164 | (100.0%) | 155 | (94.5%) | 163 | (99.4%) | |
| 19 | 39 | 39 | (100.0%) | 35 | (89.7%) | 39 | (100.0%) | |
| 20 | 157 | 157 | (100.0%) | 132 | (84.1%) | 147 | (93.6%) | |
| 21 | 157 | 157 | (100.0%) | 132 | (84.1%) | 152 | (96.8%) | |
| 22 | 157 | 157 | (100.0%) | 126 | (80.3%) | 147 | (93.6%) | |
| 23 | 157 | 156 | (99.4%) | 131 | (83.4%) | 144 | (91.7%) | |
| 24 | 165 | 158 | (95.8%) | 106 | (64.2%) | 131 | (79.4%) |
A trespass incident at Lime Street plus a signalling problem at Earlestown caused disruption from 11:00 to 15:00.
|
| 25 | 164 | 163 | (99.4%) | 116 | (70.7%) | 147 | (89.6%) |
A signalling problem at St Helens Junction caused some disruption in the afternoon.
|
| 26 | 64 | 63 | (98.4%) | 33 | (51.6%) | 43 | (67.2%) |
Overrunning engineering works severely delayed the first few trains.
|
| 27 | 157 | 156 | (99.4%) | 142 | (90.4%) | 152 | (96.8%) | |
| 28 | 161 | 160 | (99.4%) | 133 | (82.6%) | 153 | (95.0%) |
Overrunning engineering works at Eccles. No trains between Earlestown and Manchester until about 08:15.
|
| 29 | 157 | 157 | (100.0%) | 135 | (86.0%) | 153 | (97.5%) | |
| 30 | 157 | 157 | (100.0%) | 128 | (81.5%) | 146 | (93.0%) | |
| 31 | 164 | 164 | (100.0%) | 126 | (76.8%) | 155 | (94.5%) | |
| May | 4516 | 4479 | (99.2%) | 3593 | (79.6%) | 4146 | (91.8%) | |
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.
|