Darwin pushport problem about P00460-20251020-COVNTRY

69 views
Skip to first unread message

Dean Zhong

unread,
Oct 20, 2025, 11:23:32 PM (13 days ago) Oct 20
to A gathering place for the Open Rail Data community
Hi All,

Our team found that there was train number P00460 without COVNTRY in the train schedule (https://www.brtimes.com/!train?uid=P00460&date=20251020) on October 20, 2025.
 And there is no such site on the website (https://www.realtimetrains.co.uk/service/gb-nr:P00460/2025-10-20#allox_id=0) that displays real-time information of train times.

Please ask if this is an error in Darwin pushport information, the following is the original information of Darwin:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<Pport xmlns="http://www.thalesgroup.com/rtti/PushPort/v16" xmlns:ns2="http://www.thalesgroup.com/rtti/PushPort/Schedules/v3" xmlns:ns3="http://www.thalesgroup.com/rtti/PushPort/Schedules/v2" xmlns:ns4="http://www.thalesgroup.com/rtti/PushPort/Formations/v2" xmlns:ns5="http://www.thalesgroup.com/rtti/PushPort/Forecasts/v3" xmlns:ns6="http://www.thalesgroup.com/rtti/PushPort/Formations/v1" xmlns:ns7="http://www.thalesgroup.com/rtti/PushPort/StationMessages/v1" xmlns:ns8="http://www.thalesgroup.com/rtti/PushPort/TrainAlerts/v1" xmlns:ns9="http://www.thalesgroup.com/rtti/PushPort/TrainOrder/v1" xmlns:ns10="http://www.thalesgroup.com/rtti/PushPort/TDData/v1" xmlns:ns11="http://www.thalesgroup.com/rtti/PushPort/Alarms/v1" xmlns:ns12="http://thalesgroup.com/RTTI/PushPortStatus/root_1"ts="2025-10-20T19:31:44.1266881+01:00"version="16.0">
<uR updateOrigin="CIS"requestSource="NA01"requestID="1309976163-1">
<schedule rid="202510208709699"uid="W09699"trainId="1H39"ssd="2025-10-20"toc="VT"trainCat="XX">
<ns2:OR wtd="19:13" tpl="EUSTON" act="TB" ptd="19:13"/>
<ns2:PP wtp="19:15:30" tpl="CMDNSTH"/>
<ns2:PP wtp="19:16" tpl="CMDNJN"/>
<ns2:PP wtp="19:19" tpl="WLSDWLJ"/>
<ns2:PP wtp="19:20:30" tpl="WMBY"/>
<ns2:PP wtp="19:22:30" tpl="HROW"/>
<ns2:PP wtp="19:25:30" tpl="WATFDJ"/>
<ns2:PP wtp="19:29:30" tpl="BONENDJ"/>
<ns2:PP wtp="19:32:30" tpl="TRING"/>
<ns2:PP wtp="19:35:30" tpl="LEDBRNJ"/>
<ns2:PP wtp="19:40" tpl="BLTCHLY"/>
<ns2:PP wtp="19:41:30" tpl="MKNSCEN"/>
<ns2:PP wtp="19:43" tpl="WLVR"/>
<ns2:PP wtp="19:45:30" tpl="HANSLPJ"/>
<ns2:PP wtp="19:52" tpl="WEEDON"/>
<ns2:PP wtp="19:59:30" tpl="HMTNJ"/>
<ns2:PP wtp="20:00" tpl="RUGBY"/>
<ns2:PP wtp="20:00:30" tpl="RUGBTVJ"/>
<ns2:PP wtp="20:03" tpl="BRINKLW"/>
<ns2:PP wtp="20:06:30" tpl="ATLBRJN"/>
<ns2:IP wta="20:08:30" wtd="20:10" tpl="NNTN" act="T " pta="20:09" ptd="20:10"/>
<ns2:PP wtp="20:13" tpl="ATHRSTN"/>
<ns2:PP wtp="20:15" tpl="PWTH"/>
<ns2:PP wtp="20:17:30" tpl="AMNGTNJ"/>
<ns2:PP wtp="20:18" tpl="TMWTHLL"/>
<ns2:PP wtp="20:21" tpl="LCHTTVL"/>
<ns2:PP wtp="20:21:30" tpl="LCHTNJ"/>
<ns2:PP wtp="20:24" tpl="RUGL"/>
<ns2:PP wtp="20:25" tpl="RUGLYNJ"/>
<ns2:PP wtp="20:28" tpl="COLWICH"/>
<ns2:PP wtp="20:35:30" tpl="STONE"/>
<ns2:PP wtp="20:41" tpl="STOKOTJ"/>
<ns2:IP wta="20:42:30" wtd="20:44:30" tpl="STOKEOT" act="T " pta="20:43" ptd="20:44"/>
<ns2:PP wtp="20:47" tpl="LNGP"/>
<ns2:PP wtp="20:50" tpl="KIDSGRV"/>
<ns2:PP wtp="20:53" tpl="CONGLTN"/>
<ns2:PP wtp="20:57:30" tpl="MACLSFD"/>
<ns2:PP wtp="20:59" tpl="PSBY"/>
<ns2:PP wtp="21:01" tpl="ADLC"/>
<ns2:PP wtp="21:03" tpl="POYNTON"/>
<ns2:PP wtp="21:04" tpl="BMHL"/>
<ns2:PP wtp="21:05:30" tpl="CHDH"/>
<ns2:PP wtp="21:06:30" tpl="ADSWDRD"/>
<ns2:PP wtp="21:07:30" tpl="STKPE1"/>
<ns2:PP wtp="21:08" tpl="STKPE2"/>
<ns2:IP wta="21:09" wtd="21:10:30" tpl="STKP" act="T " pta="21:09" ptd="21:10"/>
<ns2:PP wtp="21:12" tpl="HTNOJN"/>
<ns2:PP wtp="21:12:30" tpl="HTCP"/>
<ns2:PP wtp="21:13" tpl="LVHM"/>
<ns2:PP wtp="21:14" tpl="SLDLJN"/>
<ns2:PP wtp="21:15:30" tpl="ARDWCKJ"/>
<ns2:DT wta="21:19" pta="21:19" tpl="MNCRPIC" act="TF"/>
</schedule>
<schedule rid="202510208000460"uid="P00460"trainId="1A84"rsid="VT775000"ssd="2025-10-20"toc="VT"trainCat="XX">
<ns2:OR wtd="22:15" tpl="MNCRPIC" act="TB" ptd="22:15"/>
<ns2:PP wtp="22:17" tpl="ARDWCKJ"/>
<ns2:PP wtp="22:19" tpl="SLDLJN"/>
<ns2:PP wtp="22:19:30" tpl="LVHM"/>
<ns2:PP wtp="22:20" tpl="HTCP"/>
<ns2:PP wtp="22:21" tpl="HTNOJN"/>
<ns2:IP wta="22:22:30" wtd="22:24" tpl="STKP" act="T " pta="22:23" ptd="22:24"/>
<ns2:PP wtp="22:24:30" tpl="STKPE2"/>
<ns2:PP wtp="22:25" tpl="STKPE1"/>
<ns2:PP wtp="22:26:30" tpl="ADSWDRD"/>
<ns2:PP wtp="22:27:30" tpl="CHDH"/>
<ns2:PP wtp="22:28" tpl="BMHL"/>
<ns2:PP wtp="22:29" tpl="POYNTON"/>
<ns2:PP wtp="22:31" tpl="ADLC"/>
<ns2:PP wtp="22:32" tpl="PSBY"/>
<ns2:IP wta="22:35" wtd="22:36:30" tpl="MACLSFD" act="T " pta="22:35" ptd="22:36"/>
<ns2:PP wtp="22:42" tpl="CONGLTN"/>
<ns2:PP wtp="22:45" tpl="KIDSGRV"/>
<ns2:PP wtp="22:48" tpl="LNGP"/>
<ns2:IP wta="22:51" wtd="22:53" tpl="STOKEOT" act="T " pta="22:51" ptd="22:53"/>
<ns2:PP wtp="22:54" rdelay="1" tpl="STOKOTJ"/>
<ns2:PP wtp="22:58:30" rdelay="1" tpl="STONE"/>
<ns2:PP wtp="23:07:30" tpl="COLWICH" can="true"/>
<ns2:PP wtp="23:09:30" tpl="RUGLYNJ" can="true"/>
<ns2:PP wtp="23:10" tpl="RUGL" can="true"/>
<ns2:PP wtp="23:13:30" tpl="LCHTNJ" can="true"/>
<ns2:PP wtp="23:14" tpl="LCHTTVL" can="true"/>
<ns2:PP wtp="23:16" tpl="TMWTHLL" can="true"/>
<ns2:PP wtp="23:17" tpl="AMNGTNJ" can="true"/>
<ns2:PP wtp="23:18" tpl="PWTH" can="true"/>
<ns2:PP wtp="23:20" tpl="ATHRSTN" can="true"/>
<ns2:IP wta="23:24" wtd="23:26" tpl="NNTN" act="T " can="true" pta="23:24" ptd="23:26"/>
<ns2:IP wta="00:18" wtd="00:18" tpl="COVNTRY" act="T " pta="00:18" ptd="00:18"/>
<ns2:PP wtp="23:36" rdelay="51" tpl="RUGBTVJ"/>
<ns2:IP wta="23:37:30" wtd="23:39:30" rdelay="51" tpl="RUGBY" act="T " pta="23:38" ptd="23:39"/>
<ns2:PP wtp="23:41:30" rdelay="50" tpl="HMTNJ"/>
<ns2:PP wtp="23:47:30" rdelay="48" tpl="WEEDON"/>
<ns2:PP wtp="00:03" rdelay="48" tpl="HANSLPJ"/>
<ns2:PP wtp="00:07" rdelay="48" tpl="WLVR"/>
<ns2:IP wta="00:10" wtd="00:16" rdelay="48" tpl="MKNSCEN" act="T " pta="00:10" ptd="00:16"/>
<ns2:PP wtp="00:19:30" rdelay="48" tpl="DNBGHSJ"/>
<ns2:PP wtp="00:20" rdelay="48" tpl="BLTCHLY"/>
<ns2:PP wtp="00:30:30" rdelay="48" tpl="LEDBRNJ"/>
<ns2:PP wtp="00:34:30" rdelay="48" tpl="TRING"/>
<ns2:PP wtp="00:40" rdelay="48" tpl="BONENDJ"/>
<ns2:IP wta="00:49:30" wtd="00:51" rdelay="48" tpl="WATFDJ" act="D " pta="00:50"/>
<ns2:PP wtp="00:55:30" rdelay="48" tpl="HROW"/>
<ns2:PP wtp="01:00:30" rdelay="48" tpl="WMBY"/>
<ns2:PP wtp="01:05" rdelay="48" tpl="WLSDWLJ"/>
<ns2:PP wtp="01:10:30" rdelay="48" tpl="CMDNJN"/>
<ns2:PP wtp="01:11" rdelay="48" tpl="CMDNSTH"/>
<ns2:DT wta="01:14" rdelay="48" pta="01:14" tpl="EUSTON" act="TF"/>
<ns2:cancelReason>811</ns2:cancelReason>
</schedule>
</uR>
</Pport>

Regards,
Dean

David Wheatley

unread,
Oct 21, 2025, 4:18:53 AM (13 days ago) Oct 21
to openrail...@googlegroups.com
Hi Dean,

It looks like this train was diverted via Coventry. You'll see that every location from COLWICH to NNTN was cancelled, and then COVNTRY was inserted as a new calling point in the schedule. The train was then due to return back to its planned path from RUGBTVJ.

COVNTRY won't show on sites such as Realtime Trains or BRTimes since they show the information from the planned schedules (CIF). But you will see the service had no reports between COLWICH and RUGBTVJ, which confirms the diversion.

On Tue, 21 Oct 2025, 04:23 Dean Zhong, <dean...@gmail.com> wrote:
Hi All,

Our team found that there was train number P00460 without COVNTRY in the train schedule (https://www.brtimes.com/!train?uid=P00460&date=20251020) on October 20, 2025.
 And there is no such site on the website (https://www.realtimetrains.co.uk/service/gb-nr:P00460/2025-10-20#allox_id=0) that displays real-time information of train times.

Please ask if this is an error in Darwin pushport information, the following is the original information of Darwin:

Regards,
Dean

--
You received this message because you are subscribed to the Google Groups "A gathering place for the Open Rail Data community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openraildata-t...@googlegroups.com.
To view this discussion, visit https://groups.google.com/d/msgid/openraildata-talk/d422d988-0d04-4bf5-8241-bdd7cfe4aecfn%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages