(02 Jun 2014, 8:34 am)JakeSavage wrote The timings on the nexus bus stops are based on the quickest scheduled journey. The rather odd timing of the 45 is based on the very first trip (0529 ish?) which doesn't encounter much traffic (cars or passengers). This explains the wide discrepancy to the 46 and 47.

In general terms, if a service has an evening variation, that's the point-to-point timings nexus use. Personally, I think these timings raise customer expectations too much. I'd much prefer they used general daytime timings, as they are generally more robust for connections/ journey planning, etc. and if a bus arrives at destination point earlier than customers expectation, this would certainly excite less comment...

If what you say is correct, and I'm not suggesting it isn't, then this is such an idiotic way to serve as a basis for estimating journey times. Journey times should/need be estimated using the peak timetable on all services. That way, as you point out, customers will have realistic expectations over when the bus will arrive and how long it will take to its destination.

However, while that may explain the disparity between services 45 and 46, it does not explain the disparity between services 45 and 47. Both services have buses leaving the Gill prior to 6am, yet, one bus takes 27 minutes while the other takes 40 minutes. Although, in my view, service 47 takes slightly longer than services 45 & 46 due to its routing through The Teams, the difference does not come anywhere near 30 minutes. Are Nexus trying to suggest that levels of congestion are so much different between 05:30 and 06:00 than they are between 06:00 and 06:30? I accept that traffic levels may be higher in the latter time-window, but I would certainly not put it at peak-time levels which tend to start at 06:45 and 07:15.