DRS Move seemingly ran by LSL?

[Rail Quest]

Just come across a bizarre move - there is currently a VSTP 0Z37 move in progress, 1630 Carlisle Kingmoor Sdg(Drs) to Crewe Gresty Bridge (Drs) and despite being something normally hauled by DRS - its got the TSC of an LSL move. Even weirder is that the allocation for this move can be viewed on RTT as 88010 with 66427.

Realtime Trains | 0Z37 1630 Carlisle Kingmoor Sdg(Drs) to Crewe Gresty Bridge (Drs) | 24/01/2024

Real-time train running information for 0Z37 1630 departure from Carlisle Kingmoor Sdg(Drs) to Crewe Gresty Bridge (Drs) on 24/01/2024. From Realtime Trains, an independent source of train running info for Great Britain.

www.realtimetrains.co.uk

So either - the move is ran by LSL for whatever reason or the move has incorrectly been raised as an LSL move which raises the question of how the DRS loco allocations then displayed on the working (albeit this last question probably comes from my lack of familiarity with the inner workings of RTT and wider systems).

Posting screenshot of the move to show what is currently shown in case the move gets edited in some way.

Does anyone have any possible explanations for this?

 

[tiptoptaff]

Possibly an ex-DRS 37 being moved by LSL now they've all been sold/withdrawn?

 

[800001]

Just come across a bizarre move - there is currently a VSTP 0Z37 move in progress, 1630 Carlisle Kingmoor Sdg(Drs) to Crewe Gresty Bridge (Drs) and despite being something normally hauled by DRS - its got the TSC of an LSL move. Even weirder is that the allocation for this move can be viewed on RTT as 88010 with 66427.

Realtime Trains | 0Z37 1630 Carlisle Kingmoor Sdg(Drs) to Crewe Gresty Bridge (Drs) | 24/01/2024

Real-time train running information for 0Z37 1630 departure from Carlisle Kingmoor Sdg(Drs) to Crewe Gresty Bridge (Drs) on 24/01/2024. From Realtime Trains, an independent source of train running info for Great Britain.

www.realtimetrains.co.uk

So either - the move is ran by LSL for whatever reason or the move has incorrectly been raised as an LSL move which raises the question of how the DRS loco allocations then displayed on the working (albeit this last question probably comes from my lack of familiarity with the inner workings of RTT and wider systems).

Posting screenshot of the move to show what is currently shown in case the move gets edited in some way.
View attachment 151045
Does anyone have any possible explanations for this?

Simple mistake by who ever had planned the path, put wrong FOC in.Nothing more to it than that.
Happens frequently with passenger/ECS workings.

 

[Rail Quest]

Simple mistake by who ever had planned the path, put wrong FOC in.Nothing more to it than that.
Happens frequently with passenger/ECS workings.

Fair fair, I think I remember seeing a couple of occurrences recently, more so than previously such as a colas light loco appearing as an EMR service.

What I find particularly interesting is this leading to the DRS loco allocations for the move showing up. Less so from a technical perspective of how it could happen, but more of a potential data security thing if its DRS's wish for loco allocations to not appear on sites like RTT

 

[Whistler40145]

Is it the movement of 37422 and 37425 following their use on snow plough duties?

 

[Rail Quest]

Is it the movement of 37422 and 37425 following their use on snow plough duties?

The allocation showing on RTT (probably inadvertently) was 88010 with 66427 so seemingly not if its anything to go by.

 

[Spartacus]

It's a VSTP so whoever created it probably copied from an LSL schedule and forgot to change the sector & service codes before publishing. As such the consist won't have been suppressed from downstream systems.