Redeployments (Part 14)
-
SMB240J SMB241G
(WLDEP 969 > WLDEP 187)
TIB727U
(WLDEP 963 > WLDEP 969)
TIB728S
(WLDEP SP > WLDEP 969)
SMB238S
(WLDEP/WRDEP 965 > WLDEP 187)
TIB647S TIB649L TIB660C
(WLDEP 167)
TIB451P TIB452L TIB453J TIB454G TIB455D
(WLDEP 961 > WLDEP TBC) -
Originally posted by TIB433S:
SMB240J SMB241G
(WLDEP 969 > WLDEP 187)
TIB727U
(WLDEP 963 > WLDEP 969)
TIB728S
(WLDEP SP > WLDEP 969)
SMB238S
(WLDEP/WRDEP 965 > WLDEP 187)
TIB647S TIB649L TIB660C
(WLDEP 167)
No former deployments for them...
Haha 727U and 728S r back to 969..I welcome them back.
-
Originally posted by TIB433S:
SMB240J SMB241G
(WLDEP 969 > WLDEP 187)
TIB727U
(WLDEP 963 > WLDEP 969)
TIB728S
(WLDEP SP > WLDEP 969)
SMB238S
(WLDEP/WRDEP 965 > WLDEP 187)
TIB647S TIB649L TIB660C
(WLDEP 167)
TIB451P TIB452L TIB453J TIB454G TIB455D
(WLDEP 961 > WLDEP TBC)Is there any news of the missing scanias, 568L 569J 570D 635B 637X 639R?
Is 2E still a 178 bus? 968R did 2E's block yesterday.
649L a 178 bus? Who edited it? I don't think I saw 649L yesterday.
-
Originally posted by TIB433S:
SMB240J SMB241G
(WLDEP 969 > WLDEP 187)
TIB727U
(WLDEP 963 > WLDEP 969)
TIB728S
(WLDEP SP > WLDEP 969)
SMB238S
(WLDEP/WRDEP 965 > WLDEP 187)
TIB647S TIB649L TIB660C
(WLDEP 167)
TIB451P TIB452L TIB453J TIB454G TIB455D
(WLDEP 961 > WLDEP TBC)i believe that 4 MAN from 960 will perm 187
-
the ELBO not out of 187 / 852?
-
Originally posted by SMB189A:
the ELBO not out of 187 / 852?
844P is on. 846J went over to 852 duty 03.
-
Originally posted by TIB433S:
SMB240J SMB241G
(WLDEP 969 > WLDEP 187)
TIB727U
(WLDEP 963 > WLDEP 969)
TIB728S
(WLDEP SP > WLDEP 969)
SMB238S
(WLDEP/WRDEP 965 > WLDEP 187)
TIB647S TIB649L TIB660C
(WLDEP 167)
TIB451P TIB452L TIB453J TIB454G TIB455D
(WLDEP 961 > WLDEP TBC)I had said before, when the deployments are unconfirmed we put them as spare.
-
Originally posted by Gus.chong:
I had said before, when the deployments are unconfirmed we put them as spare.
TBC =/= SP.
If they are SP, it is SP. If they belong to another svc, It would go that svc instead of SP.
-
Originally posted by TIB783G:
TBC =/= SP.
If they are SP, it is SP. If they belong to another svc, It would go that svc instead of SP.
Then why when buses are registered (the deployments are unconfirmed that time) they were put as spare?
-
Originally posted by Gus.chong:
Then why when buses are registered (the deployments are unconfirmed that time) they were put as spare?
I don't know. If they keep running around, yes they are spare. TBC means that the bus could be spotted on that service alone. If people put spare, then we confirm it to belong to a service, we need to state that the bus was from xx service, to spare, to xx service. Isn't that very tedious and troublesome? And this is within the same depot. if you're talking about cross-depot transfers, yes, it's right to say they are spare. This is the SMRT style. And don't forget, we will have to keep editing SGWiki spare buses. It's very very troublesome to edit the buses back in and out. Hope you understand.. -
Originally posted by Gus.chong:
Then why when buses are registered (the deployments are unconfirmed that time) they were put as spare?
SMB232H and the other 5 MAN are running on various services these 2 weeks. Am I right to say they are spare? -
SMB173U
(WLDEP 859 >> KJDEP SP)
On 67 and 927 today.. -
Originally posted by TIB433S:
SMB232H and the other 5 MAN are running on various services these 2 weeks. Am I right to say they are spare?Yes.
-
Originally posted by TIB433S:
I don't know. If they keep running around, yes they are spare. TBC means that the bus could be spotted on that service alone. If people put spare, then we confirm it to belong to a service, we need to state that the bus was from xx service, to spare, to xx service. Isn't that very tedious and troublesome? And don't forget, we will have to keep editing SGWiki spare buses. It's very very troublesome to edit the buses back in and out. Hope you understand..That's right, but we still have to understand why new buses were spare buses after allocated to their depots.
-
Originally posted by SMB189A:
TIB1181L
(WLDEP SP
WLDEP 901)TIB1178Y
(WLDEP 901
WLDEP SP)This is a long overdue redeployment.
-
TIB658K
(WLDEP 980)
SMB185K
(WLDEP 980 > WLDEP SP) -
Originally posted by TIB433S:
TIB658K
(WLDEP 980)
SMB185K
(WLDEP 980 > WLDEP SP)Finally my wish came true. TIB658K went back to WLDEP 980 for the third time.
-
So any other redeployments regarding depot transfer.I wish for some new bus from other depot too :)
-
Originally posted by TIB 585L:
So any other redeployments regarding depot transfer.I wish for some new bus from other depot too :)
New buses will also be involved in the depot transfers.
-
May I know who's the one who put 815S as Awaiting De-Registration? Today the bus is on 165
-
Originally posted by TIB783G:
Is there any news of the missing scanias, 568L 569J 570D 635B 637X 639R?
Is 2E still a 178 bus? 968R did 2E's block yesterday.
649L a 178 bus? Who edited it? I don't think I saw 649L yesterday.
SMB2E is spotted on Service 178 this afternoon.
-
Originally posted by SBS2615P:
May I know who's the one who put 815S as Awaiting De-Registration? Today the bus is on 165
U can check with user 2656X, he was the one who assumed just because of the fauly door found on SBS815S. Note that when I posted 325's redeployment last week, I indicated the outgoing SBS815S as "either spare or awaiting dereg". For this case I take it to be HGDEP SP.
-
Originally posted by TIB433S:
TIB658K
(WLDEP 980)
SMB185K
(WLDEP 980 > WLDEP SP)Sorry,
SMB185K
(WLDEP 980 KJDEP SP)
On 177 yesterday. Info from SGF user TIB1234T. -
Originally posted by TIB433S:
Sorry,
SMB185K
(WLDEP 980 KJDEP SP)
On 177 yesterday. Info from SGF user TIB1234T.Expected
-
Originally posted by SBS8676Z:
AMDEP also laid up 2 lances - TIB908P and TIB928G
TIB914X
(AMDEP SP
non-user lay up status till 3rd Apr 2013)TIB933R
(AMDEP/SEBP 980
non-user lay up status till 3rd Apr 2013)TIB921A
(AMDEP/SEBP 980
unofficially lay up) now parking inside AMDEP with ezylink reader removed..
**** road tax expired on 3rd April 2012 and did not renew but not reflected as layup as well.