-
Our booking engine at tickets.railforums.co.uk (powered by TrainSplit) helps support the running of the forum with every ticket purchase! Find out more and ask any questions/give us feedback in this thread!
Train breaks down other TOC's get compo?
- Thread starter zaax
- Start date
- Status
Sponsor Post - registered members do not see these adverts; click here to register, or click here to log in
R
RailUK Forums
Yes indeed.
In layman’s terms; yes. The reality is far, far more complex.
pdeaves
Established Member
but reclaimed from the TOC at fault.
It doesn’t work like that.
The simple version:
TOC A’s train fails, delaying TOC B.
TOC A pays NR for the delay minutes it causes, at the TOC A to NR delay minute rate.
NR pays TOC B at the NR to TOC B delay minute rate.
With a few exceptions, the NR to TOC rate is always higher than the TOC to NR rate. Therefore NR usually loses out on an individual failure.
hybrid.pigeon
Member
Which TOC pays delay replay to pax?
TOC A as their train breaked down
Or TOC B as their train was delayed, or both to their respective pax?
TOC A as their train breaked down
Or TOC B as their train was delayed, or both to their respective pax?
bb21
Emeritus Moderator
- Joined
- 4 Feb 2010
- Messages
- 24,151
The operator of the delayed service pays Delay Repay to their own customers.
The cause of the delay is irrelevant.
I saw a good one the other day.
I'm sure it was something like Train A was delayed departing a London station.
This then delayed Train B somewhere on the route, which then delayed Train C on it's journey. But the locations were somewhere like Horsham, Birmingham and Peterborough - really far off ones.
Don't know how to read the delay reasons in TSID (scroll to the delayed train and then choose what to view full NR text?).
If someone points me in the right direction, I can see what the full NR text says.
Platform staff at Station A said they pushed the TRTS, Signalbox says they didn't.
I'm sure it was something like Train A was delayed departing a London station.
This then delayed Train B somewhere on the route, which then delayed Train C on it's journey. But the locations were somewhere like Horsham, Birmingham and Peterborough - really far off ones.
Don't know how to read the delay reasons in TSID (scroll to the delayed train and then choose what to view full NR text?).
If someone points me in the right direction, I can see what the full NR text says.
Platform staff at Station A said they pushed the TRTS, Signalbox says they didn't.
So TSID will give you a lineup for given location.
S to select the train; which will bring up the schedule.
G in the command line to switch from schedule mode to train running.
F9 to scroll to last page.
A to select the delay incident you want to read.
High Dyke
Established Member
Ah the old it's not my fault excuse. Train delay is usually a blame game, and yes i've played it too... If a TOC can get away with accepting the blame they will; equally so will NR. However as someone mentioned the actual payment recovery system is somewhat complex.
One favourite trick with a TOC is to hold onto a delay until late in the week, i believe they have a certain amount of time to accept/dispute a delay. They then dispute that delay on the penultimate day, which means it can be difficult for the NR to challenge.
tsr
Established Member
These are more common (and more bizarre) than many people think!
The best I encountered was an incident involving cows on the line at Nailsea and Backwell. By the time the delays had finished spooling across the network, several issues had been caused around Kent and Sussex, including a train from somewhere around Portsmouth to Victoria missing at least one or two stops... basically on the other side of England!
Somebody tried to see if there was any link to a delay shunting something at Bedford, which I don't seem to recall there was, but a good try nonetheless!
In fact, the Coastway routes are particularly notorious for doing this sort of stuff but the other way round; trains from Victoria to the South Coast regularly have to run "fast" to avoid making stops at smaller stations whilst delayed. This is so the sporadic GWR services between Brighton and the random selection of West Country shacks are not delayed.
Some controllers have a bit of a mantra... "Southern must not delay the Pasty Train... Southern must not delay the Pasty Train..."
pdeaves
Established Member
OK, I was just trying to keep it simple. 'Reclaimed' intended only as showing a money flow.
Highlandspring
Established Member
- Joined
- 14 Oct 2017
- Messages
- 2,777
Or more directly..
On TSID type T then <enter>
<return> to move cursor to train of interest then type S <enter>
Then page down or <F9> to the bottom of the page
Then <return> to move the cursor to the dot next to the TDA number
Then type I <enter> against the delay you want to view
On the incident screen either press <F5> to scroll through the NR text/affected trains/dispute details or type 1 <enter> to go to the NR text (as long as there are less than 50 trains affected)
...or you could start with a TRJC or TRJE, or do TRJF if you know the responsible manager code or straight in from a TRJG if you know the TDA number. As always with TRUST there are many, many ways of getting to the same bit of information!
theironroad
Established Member
I reckon at the end of the financial year, NR and all the tocs and focs sit around a table and give each other a £1 coin as it all probably balances out.*
* No doubt someone will come along shortly with audited accounts to show I'm wrong lol
* No doubt someone will come along shortly with audited accounts to show I'm wrong lol
- Status