Bus Observations (2011)

last SG · 2011-01-05T20:43:22+00:00

Every Saturday, the empty TQ slot for 187 will be done a random rigid. It will reach Block 320 Jurong East Stop at about 7.20am to 7.25am (towards Boon Lay)...

sbst275 SG

I've noticed 1800 - 1930 is not as peak as claimed, I've seen brunching empty ADDs into N9. mmm, maybe ard 1900 yes

Only 1 packed ADD was spotted.

SBS9C SG

SBS9145H made a super loud "WHROONG" sound that frightened almost everyone on the bus stop when it stopped to pick up ppl. SBST should replace the brake pads asap incase of accident due to a worn out brake pad.

chickenlittle2 SG

I've noticed 1800 - 1930 is not as peak as claimed, I've seen brunching empty ADDs into N9. mmm, maybe ard 1900 yes

Only 1 packed ADD was spotted.

As mentioned earlier, empty 241 will occur from BNL to N9 and buses will come together due to the previous bus was late or having high passenger capacity. I had observed this trend where the 179 S or E shift buses start their crossover to 241 are late and caused such problem. Currently, some BC and I also discover an increase in no of ppl leaving N9 during 1800-1915.

sbst275 SG

The problem w/ NP's is that SBS is unable to anymore buses to Clementi.

You can add during AM peak but wat abt PM peak of the bus stop mess os Clementi Mall? The other way is to add on Sv 74 trips instead which incurr buses

sbst275 SG

As for MRT...

I've said over NTU's jioing to LTA to give them a LRT. For NTU's case it's pretty simple, for 1/2 of the year NTU is in recess, what are they going to do w/ e LRT trains? Furthermore an LRT can only carry some 90 pax vs ADD's 120 pax.

As for Clementi Rd, I do not see a point into building an LRT or spur line for now. I think tabulating the cost and benefits does not balance

chickenlittle2 SG

The problem w/ NP's is that SBS is unable to anymore buses to Clementi.

You can add during AM peak but wat abt PM peak of the bus stop mess os Clementi Mall? The other way is to add on Sv 74 trips instead which incurr buses

it is not only SBS issue, 184 and 75 have to play a part too, that also includes the high demand svc like 61.

TIB 781 L SG

I don't know whats with the time keeper at WRI today.

1255H was late, and 584P caught up, and they chose to let 1255H go and 584P wait, where later the same thing at Kranji MRT station happened, 1255H reached Kranji MRT at 2123, 584P caught up at 2128, ended up 1255H doing 2nd last car from BNL, 584P going home last.

Seriously they should have just amended the schedule to meet Sundays one with the fleeting still same.

sbst275 SG

I don't know whats with the time keeper at WRI today.

Seriously they should have just amended the schedule to meet Sundays one with the fleeting still same.

is the bus following schedule?

In such cases nothing wrong w/ timkeeper as long as I do not see the run time allocated.

TIB 781 L SG

is the bus following schedule?

In such cases nothing wrong w/ timkeeper as long as I do not see the run time allocated.

Nope it wasn't following schedule

The fleet order was totally messed up and even after 10 minutes my 584P caught up with 1255H and again at first at WL, later at BNL it happened.

by right 1255H should be starting at 1830 but it didn't, 584P has time and they let 1255H start first instead of extending 584P's break time.

sbst275 SG

Nope it wasn't following schedule

The fleet order was totally messed up and even after 10 minutes my 584P caught up with 1255H and again at first at WL, later at BNL it happened.

by right 1255H should be starting at 1830 but it didn't, 584P has time and they let 1255H start first instead of extending 584P's break time.

if no one bothers to follow the schedule, nothing can be solved.

It contradicts what a schedule is for

If everyone follows the schedule properly and regulate their speed, nothing would happen. You did not even mention how long ppl would have to wait for the next bus aft 584's slot.

sbst275 SG

tat said SMRTB's schedule standard... shakes head

TIB 781 L SG

if no one bothers to follow the schedule, nothing can be solved.

It contradicts what a schedule is for

If everyone follows the schedule properly and regulate their speed, nothing would happen. You did not even mention how long ppl would have to wait for the next bus aft 584's slot.

If I remember correctly at night it was 5 minutes, When I took it late afternoon straight from BNL it was like 10 min+, but 584 somewhat caught up with 1255 at KJ at about 6 and was surprised when I saw 1255H infront, at night 1255 is scheduled to start at 2146, and 584 starting at 2200, and this time also caught up with 1255.

sbst275 SG

the behind bus aft 584

TIB 781 L SG

the behind bus aft 584

I'm not sure. but behind 1255H the freq was about 5 minutes

sbst275 SG

I'm not sure. but behind 1255H the freq was about 5 minutes

178's is always in a mess

Downroutes from Kranji towards BNL, 2 - 3 buses brunching at night. I dunno wat's next

TIB 781 L SG

178's is always in a mess

Downroutes from Kranji towards BNL, 2 - 3 buses brunching at night. I dunno wat's next

The weekday's schedule now follows sunday's schedule indirectly.

If you get my point you will know what I mean. The schedule has been amended atleast 2x, ART(Additional run time) from last year sept-march '11, after march 11 they use Additional with RT, I'm not sure what's next.

sbst275 SG

rescheduling dun matter, it's whether it's done properly or not.

I've better not reveal what I'm planning to do to show e problems w/ 178 in this domain

TIB 781 L SG

For 178's timing they make it longer about more than 15 minutes.

So if 637X comes in at 1715, 638T might follow suit at around 1734, but don't really see a problem with the schedules since all buses came on time, don't have to do downroute on W'days.

SMB66X SG

912 have it's worst fleet yesterday, 9 April 2011, from 1pm to 2pm. First, 3 bendy bunched up(TIB1185B, TIB1143Y, TIB1129P). Due to that, 3-4 normal freq bus, about 20mins, was left, causing a big gap to the next bunch. Around 1:39pm, another 2 bendy bunched up again(TIB1000B & TIB1179U).

sbst275 SG

For 178's timing they make it longer about more than 15 minutes.

So if 637X comes in at 1715, 638T might follow suit at around 1734, but don't really see a problem with the schedules since all buses came on time, don't have to do downroute on W'days.

problem is w/ tat kind of fleet size & 15 mins peak freq, it's very difficult to maintain

I've done a worst case type of scheduling for 178 ever before. It's like 14A/ 14 P, 4 S required. Tat's like 14 - 15 mins PM peak freq.

But I believe headways could be improved further if I go on more into differentating the running time.

« Previous Page Next Page »