Is there a problem with CS and GBRf allocations at the moment? They appear to have been missing for several days.
There was an issue if a passenger vehicle was in the formation, as a result of a change to an upstream feed. This has been noted on the KYT info page for the last few weeks. A fix was made to the feed which required a bit of work on my end... I took the last fortnight off and have now finished that fix. It'll all be working from tomorrow onwards.
I’ve seen this often on RTT, correct headcode will sometimes show before the train runs, when it starts the code is scrambled. Same thing happens on Traksy. Have a look at a yard where engineering trains are due to leave. They show side by side with correct headcodes, then one will start running and the code will then scramble. Happens also when a light engine positions on the end of an engineers train.
Schedules are obfuscated using, predominantly, their two character operator code. If they're operated by ZZ, then there's a second filter that runs based on the train service code. The open data TRUST feed obfuscates using a clearlist of sector and train service codes. You can get situations, such as for Locomotive Services, where 'LS' obviously is not 'ZZ' so is clear... but they're not in the clearlist for TRUST, so they get obfuscated at that point. It's an artefact of the data feeds.
If the feeds work off TRUST/Gemini then it shouldn't be too difficult to allow a public website to use the data especially with a number of operators all working with RTT eg ScotRail, LNER etc...
Not quite as simple as that ... by a long way. A decent amount of paperwork and technical effort has to be done for each and every operator. (TRUST doesn't technically store allocations, btw, it talks to other systems...)