Vehicles seen in service, but not showing on bus times

[Jack]

6896 not tacking on 50

[BlackCountryBusSpotter]

859 which I caught earlier was strange it was displayed on the 29 route map but said it was on the 70A didn't see if it was on the 70A Route map as well

[frostjay974]

For some reason E212 was tracking as the AG 1 at 06:35 this morning 

[cardew]

For some reason E212 was tracking as the AG 1 at 06:35 this morning

Someone's clearly added E212 to bustimes and because it is not in service, and probably not even taxed, it looks to have  defaulted to the first journey/route/garage numerically and alphabetically, Journey 1 Route 1 AG

[Stu]

For some reason E212 was tracking as the AG 1 at 06:35 this morning

You didn't see it in service though.

The purpose of this thread is "Vehicles seen in service, but not showing on bus times"

[frostjay974]

You didn't see it in service though.

The purpose of this thread is "Vehicles seen in service, but not showing on bus times"

I'm sorry, I didn't know where else to put it. 

[frostjay974]

Someone's clearly added E212 to bustimes and because it is not in service, and probably not even taxed, it looks to have  defaulted to the first journey/route/garage numerically and alphabetically, Journey 1 Route 1 AG

That makes a lot more sense now thank you. 

[Wba_lad]

I'm not sure if these have been reported, but 1854, 1882 and 1884 aren't tracking. 1884 has not been tracking for a while now. Sorry if these have already been reported. 

[Stu]

I'm not sure if these have been reported, but 1854, 1882 and 1884 aren't tracking. 1884 has not been tracking for a while now. Sorry if these have already been reported.

Which routes did you see them on? (Please refer to the opening post for the rules of this topic)

[Wba_lad]

Which routes did you see them on? (Please refer to the opening post for the rules of this topic)

Oh sorry they was on the 4s today. 

[Rachvince53]

2080 and 2081 not tracking on WN 15 today. Seems like 2080 hasn't tracked since October. 

[Tony]

Bad spell again at the moment, Here's the full list I have on report to save a few repeat reports.

AG - nil
BC: 4466; 4843; 4896; 4899; 4903; 4907; 4908; 5518; 6830; 6855; 6861; 7520
CV: E058; E070; E091; E115; E127; E129; E143; E155; E157
PB: 1826; 1866; 1971; 1973; 1974; 1903; 1914; 4778; 4800; 4803; 4806; 4807; 4809; 4811; 4849; 4853; 6961
PN: 2093; 6933
WA: 804; 1846; 1854; 1878; 1881; 1882; 1884; 2126; 2129; 2134; 6711; 6717; 6727; 6741
WB: 817; 1796; 1937; 4480; 4525; 4687; 4692; 4694; 4768; 6980; 6985
WN: 835; 2022; 2025; 2076; 2080; 2081; 4839; 4990; 4992; 5401; 5411; 5420; 5429; 6762; 6788; 6789
YW: 4729; 4730; 6896; 6904; E010

[Wba_lad]

1835 not tracking on the 4M

[Secondary trigger 28]

2168 is showing the route but no location tracking 

[BlackCountryBusSpotter]

I notice any veichle on the WA39 doesn't track even if it tracked on the 34 in 37 before, some will show as going on to the 39 later on the bustimes veichle data but won't then display is this a timetable issue, as I know the 39 wouldn't have been running when the issue was fixed but the 70A and the 69 track as well as the 10A. Maybe it's the veichles but 860 was on it but not Tracking it had tracked as a 34 earlier in the morning