Scheduled freight workings across the GB network — what runs, between where, and on which days.
How to read this
What am I looking at?
Each row is one scheduled freight path from the network timetable.
Headcode
The 4-character train reporting number, e.g. 4A01. Every working on the network has one.
Class
The first digit tells you the type: 4 / 6 / 7 / 8 are freight (by speed), 0 is a light engine, 1 / 2 passenger, 5 empty stock. All rows here are freight or light-engine paths.
From / To
Origin and destination, shown as short network location codes (e.g. FELIXSTOW). Open a working to see the full place names, a map and the return workings.
Type
The commodity the path is booked to carry (intermodal, aggregates, steel…).
Days
Which days it runs — Mon–Fri, Daily, or named days such as Wed.
CSV export is a member feature.7,634 workings shown (narrow with the filters below)
Source: Multiple rail data feeds — including the Network Rail NRDP working timetable — via the LopoRail data hub · Updated: 2026-11-20 00:27:29 · Licence: Network Rail Open Data (OGL) — attribution required Live coverage: headcodes, routes and running days are real network data. Commodity type and operator are not yet carried by the live feed, so many rows read “Other / not yet classified”.
Help keep this accurate.
An observation or a correction takes a minute and helps the next person.
Contains information related to marketing campaigns of the user. These are shared with Google AdWords / Google Ads when the Google Ads and Google Analytics accounts are linked together.
90 days
__utma
ID used to identify users and sessions
2 years after last activity
__utmt
Used to monitor number of Google Analytics server requests
10 minutes
__utmb
Used to distinguish new sessions and visits. This cookie is set when the GA.js javascript library is loaded and there is no existing __utmb cookie. The cookie is updated every time data is sent to the Google Analytics server.
30 minutes after last activity
__utmc
Used only with old Urchin versions of Google Analytics and not with GA.js. Was used to distinguish between new sessions and visits at the end of a session.
End of session (browser)
__utmz
Contains information about the traffic source or campaign that directed user to the website. The cookie is set when the GA.js javascript is loaded and updated when data is sent to the Google Anaytics server
6 months after last activity
__utmv
Contains custom information set by the web developer via the _setCustomVar method in Google Analytics. This cookie is updated every time new data is sent to the Google Analytics server.
2 years after last activity
__utmx
Used to determine whether a user is included in an A / B or Multivariate test.
18 months
_ga
ID used to identify users
2 years
_gali
Used by Google Analytics to determine which links on a page are being clicked
30 seconds
_ga_
ID used to identify users
2 years
_gid
ID used to identify users for 24 hours after last activity
24 hours
_gat
Used to monitor number of Google Analytics server requests when using Google Tag Manager
1 minute
SourceBuster is used by WooCommerce for order attribution based on user source.
Name
Description
Duration
sbjs_session
The number of page views in this session and the current page path
30 minutes
sbjs_udata
Information about the visitor’s user agent, such as IP, the browser, and the device type
session
sbjs_first
Traffic origin information for the visitor’s first visit to your store (only applicable if the visitor returns before the session expires)
session
sbjs_current
Traffic origin information for the visitor’s current visit to your store
session
sbjs_first_add
Timestamp, referring URL, and entry page for your visitor’s first visit to your store (only applicable if the visitor returns before the session expires)
session
sbjs_current_add
Timestamp, referring URL, and entry page for your visitor’s current visit to your store
session
sbjs_migrations
Technical data to help with migrations between different versions of the tracking feature