(30 Jan 2015, 8:27 pm)Andreos1 wrote Without checking, there have been the variations around Eppleton (before and after the X36/37), the re-routing of the 35A to Rainton Bridge and last year, the re-routing of the trip from Rainton via the A690.
There have been a few cancellations/amendments to the timetables too.
At least 4, just off the top of my head.
My last post details the 'major' service changes to service 35 over the last few years - I don't think I missed any of the major ones out?
I'd forgotten about the re-routing of the 35A via the A690, although this was just a minor change designed to improve reliability. Given the intention of this change was not to cut costs and was in fact to improve the reliability of the 35A service, I hardly think it should be cause for complaint?
http://www.simplygo.com/news/changes-from-1-june-2014/
Services X36/X37 were introduced in May 2011, after Veolia service 168 was revised to omit Low Moorsley, and the extension of service 35 to Low Moorsley via Hetton Downs to replace services X36/X37 was from November 2012. Service 35A was revised to operate via Durham Road from this date too, providing a faster journey time. If my memory serves, this allowed more layover time to improve reliability too?
After a bit of digging, I've discovered that Nexus had a delay of up to three weeks when updating bus stop timetables in May 2011. There was quite a large number of changes associated with Durham County Council funding cuts and new operators winning tenders from Nexus, with timetables also being altered. Go North East also altered a number of services from this date, too. I can't believe that this huge delay in posting timetables has been ongoing for years on end...