2025 - vehicles not tracking on bustimes

[Tony]

Another bus that hasn't tracked for a year is back working this morning WN 2079. WN 847 which hadn't tracked this year is also working again

[Tony]

Currently on report to the company that provides the tracking kit are:-

AG: 2174; 4495; 6106; 6115; 6124; 6128; 6148; 7511
BC: 4848; 4892; 4906; 4917; 6826; 6855; 6870; 7530
CV: 2157; E058; E072; E080; E091; E145; E154; E276
PB: 752; 1829; 1893; E168; E172; E176; E201; E215; E219; E227; E325; E329
PN: 801; 824; 828; 2094; 2098; 6919; 6923; 6933
WA: 806; 1883; 1884; 6748
WB: 1835; 4481; 4688; 4692; 4694; 4773; 4951; 6991
WN: 761; 838; 2018; 2024; 4862; 5414; 6780; 6788; 6795
YW: E248; E269

Also on the list, but are currently longer term VoR and will hopefully work when next used
4492; 5518; 6812; H1003; H1005; H1008.
5518 is being presented for MoT this week, It's location is now tracking properly, so hopefully route data will when it is used next.

[MSU2008]

2085 looks like it is suffering the same issue as 6991 whilst on the X8

[Tony]

2085 looks like it is suffering the same issue as 6991 whilst on the X8

No, It's showing the correct running board and route, just hasn't updated the journey

[a4 funcool 2022]

Pensnett heritage 2102 not tracking 
Stopped tracking since 06:59/07:00 while seen in Dudley at 13:40 on 11 11A

[PB50]

3302 currently not tracking on the 10 service. Sorry it had only just come out so it's tracking.

[Tony]

A couple more of the long term ones are now tracking, so the ones I know of not tracking today are

AG: 2174; 4495; 6115; 6124; 6128; 6148; 7506; 7511
BC: 4848; 4906; 4917; 6826; 6852; 6858
CV: 2157; E058; E080; E145; E276
PB: E168; E172; E176; E198; E201; E215; E219; E227; E325; E329
PN: 801; 824; 828; 2094; 2098; 6923; 6924; 6933
WA: 806; 1884
WB: 4481; 4688; 4692; 4694; 4773; 4951; 6991
WN: 761; 838; 2018; 2069; 4862; 6780; 6788; 6795
YW: E248; E269

57 vehicles in total, the lowest for several months and hopefully still dropping

[adambotee]

Might end up being in the wrong thread but the tracking on 2069 is very hit and miss. For example - it's on the 6 route today and the tracker is stuck in Bloxwich. Tracker commonly gets stuck with this bus

[Tony]

Might end up being in the wrong thread but the tracking on 2069 is very hit and miss. For example - it's on the 6 route today and the tracker is stuck in Bloxwich. Tracker commonly gets stuck with this bus

This is the correct thread.

Thanks for that, it's not something easily spotable, but I have reported it for fixing now

[MSU2008]

WN 2009 has the same issue, the correct board times etc. but the location does not update.

[adambotee]

2005 also has the same problem. Location tracking is hit and miss

Update: 2005 not tracking at all now

[timuk1987]

4586 not tracking on the 49

[Fred]

6961 not tracking. On 48.

I wonder why NXWM has such a big problem with this quite basic requirement when the likes of First, Go Ahead, Arriva, Stagecoach have very few issues.

[Wm2001]

6105 has stopped tracking on the 72 

[Stu]

6961 not tracking. On 48.

I wonder why NXWM has such a big problem with this quite basic requirement when the likes of First, Go Ahead, Arriva, Stagecoach have very few issues.

In the case of NX, I believe it doesn't help when they have 2 or 3 systems linked together to provide the tracking/journey data, which means it just needs one of them to fail or stop responding/transmitting that causes this problem.

Other operators do have issues with buses that don't track (I've had this before with Stagecoach's 169 service), but there is no mechanism for reporting them in this forum in order for action to be taken.

While it is a problem, it is not a 'big problem' - in the grand scheme of things, at Tony's last count there were 57 vehicles with tracking defects, which sounds a lot, but in a fleet of over 1400 buses, that's just 4% of them.