c2c Performance

Independent performance data for c2c from Network Rail TRUST train movement records.

Based on 84 days of data (2026-02-27 to 2026-05-22) | Last updated: 22 May 2026
Reliability
80.6%
ran and arrived on time
On-time (if ran)
96.9%
within 5 minutes
Cancellation Rate
16.8%
of services
Avg Delay
0.9 min
minutes late
Compared to the previous 60 days: On-time performance has declined by 0.9% compared to the preceding period.

Performance by time of day

Period On-time % Avg Delay Services
Morning peak97.7%0.7 min58,092
Off-peak98%0.7 min114,860
Evening peak95.1%1.2 min59,728
Late/early96.2%1 min102,101

Performance by day of week

Day On-time % Avg Delay Services
Monday98.2%0.6 min49,763
Tuesday96.2%1 min53,427
Wednesday95.2%1.2 min52,987
Thursday97.9%0.7 min54,126
Friday97.8%0.7 min50,522
Saturday95.8%1 min43,560
Sunday96.8%0.8 min30,396

Monthly history

Month On-time % Avg Delay Cancellation Rate Coverage
April 202696.1%1 min18.8%100%
March 202697.6%0.7 min13.3%83.9%

Best performing routes

Route On-time % Avg Delay Services
XEM to Grays100%0.3 min114
London Liverpool Street to Barking100%0.3 min54
XEM to Leigh-on-Sea100%0.1 min51
XEM to Pitsea100%0.1 min50
Grays to Dagenham Dock100%0.1 min37

Worst performing routes

Route On-time % Avg Delay Services
London Fenchurch Street to East Tilbury63.2%5.8 min19
London Fenchurch Street to Stanford-le-Hope72.3%6.4 min65
London Liverpool Street to Stanford-le-Hope73.3%2.9 min15
Southend Central to Barking75%6.3 min16
Shoeburyness to Leigh-on-Sea81%2.5 min21
View c2c Delay Repay guide →

How we calculate these figures

These statistics come from Network Rail's TRUST system, which records the actual time every train passes through each point on the network. We receive this data in real time and calculate performance independently.

Reliability is our headline metric. It answers the question most passengers care about: "If I turn up for a scheduled train, what are the chances it runs and gets me there on time?" It's calculated as: (trains that ran and arrived within 5 minutes) divided by (total scheduled trains). A cancelled train counts against reliability, because you can't ride a train that doesn't exist.

On-time (if ran) shows how punctual trains were, but only counting trains that actually ran. This is useful for understanding whether delays are the main problem, or cancellations. If reliability is low but on-time is high, the operator's main issue is cancellations rather than lateness.

Cancellation rate is the percentage of scheduled services that were cancelled, including both full and part-cancellations.

Average delay is the mean delay across all arrivals. Trains that arrived on time count as 0 minutes delay. This tells you how late trains typically are when they don't run to time.

What we exclude: We don't count "off-route" movements — these are signals recorded when a train passes through a station that isn't on its scheduled route (for example, a Heathrow Express triggering a sensor at a Great Western station it passes through). Including these would unfairly lower an operator's on-time score.

How this differs from official figures: The Office of Rail and Road (ORR) publishes official statistics using different thresholds and reporting periods, with post-publication corrections. Our figures are independently calculated and not revised after publication. For official statistics, see the ORR Data Portal.

Full methodology details →

Data source: Network Rail TRUST train movement data. Contains public sector information licensed under the Open Government Licence v3.0. These are independent calculations and are not official statistics published by the Office of Rail and Road. On-time is defined as arriving within 5 minutes of the planned time. For official statistics, visit the ORR Data Portal.