Messages

@Simon Dunn

I would like to bring to your attention to the fact I was waiting in Halesowen Bus Station earlier this afternoon (04/08) for the 14:37 4H to Walsall I was watching the bus on bustimes (30706; 14:28 journey ex Hayley Green) the bus DID NOT serve the bus station as you will see on the tracking data; the bus came to the roundabout at the bottom of Hagley Road (by Lidl) and turned right back towards Shenstone Island, it wasn't just me waiting. There  was quite a crowd in the bus station and I had to wait a further 30 mins for another Diamond 4H to Walsall to arrive, I did not get the NX 4H for the fact that most of the passengers that were waiting for (30706) ended up getting on that one thus meaning it got full quite quick. Upon further investigation it appears that 30706 returned to depot. I was wondering whether you could look into this as it was quite frustrating having to delay my journey. 

I believe the bus had a suspension issue hence why it returned to depot.

Does anyone know if diamond still accept NX tickets on their WMB services?

They are still accepting NX tickets.

Nearly all bus routes esp main corridors have the issues with anti social behaviour. NX carry a higher volume of passengers so you are bound to encounter more annoying passengers and as their daysavers are easier to get away with using once expired the more chavvy elements are going to be trying their luck on a NX bus thus increasing the chances of being exposed to (for the lack of a better description) more dickheads. You can't blame the drivers or the company really it is just the sad society we currently live in.

30051 branded 226 bus on the 24

@4747 No it wasn't. It was 21008 that was involved in an accident. 30807 was still running at 18:10 when I saw it leave Walsall.

The driver of the bus that was meant to do the last 29 had the RTC(with a car) hence why a 31/2 vehicle and driver covered it.

Do we know why he didn't I think the original was 30807 which I got on this morning

It was involved in an accident

There will be more to this than originally posted. NX don't delete mileage for ticket machine failure either

I wouldn't have thought so to be honest

If a driver reports a fault whilst in service they have to then follow the instruction given by control. Doubt this would have been the driver's decision, however frustrating!

Diamond drivers are instructed to carry pax without charge in the event of TM failure until a replacement machine is sent out to them. It seems unfair to refuse travel for a TMD.

Diamond don't run the 4M...

But they would if it became a combined service as  the 42/3 and 31/32 are going to be.

Their 43 still won't run to the same route as NXWM's, although it's being renumbered to the 43A to avoid any confusion. I'm not sure if NX will run any 43A journeys, or if Diamond will run any 43's.

Diamond will also be running 43's as well according to the bus workings.

Thank you so much 4747 for the info I was told last night a different story it might be withdrawn something to do with the tax and mot not being renewed but I guess only time will tell thank you again for your post greatly appreciated

30826 has returned from paint and is now being prepped for MOT.

Hi everyone as anyone got any info on fleet number 30826 as I have not seen it for a while info would be greatly appreciated thank you

It's going for a repaint I've been told

30509 - 68A/C
Currently parked up in Perry Barr Bus Station.

It's only there as a shuttle. A driver uses it to go to Perry Barr from Tividale so as to cover breaks on 68a/c and then uses the bus on the 50 service.

The 34 is at Tividale as well, not Redditch.
The Optare Solo SR - 20884 is regularly found on the Redditch 30.
Streetlites are not usual on the Redditch 30 as well.

The 34 is run from Redditch. Tividale drivers do the relief trip.

Hmmm, it must be a mistake with the 'main site' then.

Or what's more likely is the ticket machine has been swapped over from another bus and the driver couldn't be arsed to enter the correct fleet number into the machine causing the tracking info to be wrong