Difference between revisions of "User talk:SG5064X"
Wekelwrady (talk | contribs) m (→Kranji B1s) |
Shinjuku184 (talk | contribs) (→Re CCK deployments: new section) |
||
(5 intermediate revisions by 3 users not shown) | |||
Line 39: | Line 39: | ||
Wekelwrady | Wekelwrady | ||
== Perm on 975 == | |||
Hi, | |||
SMB104U more or less act as a spare for this time being because it runs around for the month of December . As it is common for 190 and 985 OCs perm to run around on this service with duration of consecutive weeks, it will be well appreciated if more checking is done before edit. For instance, SMB42P previously also spawn 975 for weeks to last month. As for SMB107L, don’t think is really 975 perm too because it only run around for 2 weeks. After that, ur cameo other route such as 307/T and 976 before it went back to 190. So this bus does not serve as a direct swap for SMB104U or SMB108J. | |||
Cheers and thanks. | |||
===Counter-point=== | |||
From what I witness and remember, SMB107L had in fact been doing 975 for at least the entire of September 2022 and still saw it some time into October. SMB108J was SMB107L's direct swap. At the time when SMB108J started perming 190A in early September, SMB107L was entirely nowhere to be seen on 190 even during peak hours, not even showing up for 190A duty. SMB108J was directly doing the same duty that SMB107L previously did. As for SMB104U, it was still sticking to its original perm slot and was never involved in swapping (in fact it was the front bus of SMB108J). And to add on, I would agree with user SG5064X's explanation that this GoMo ad has a perm service to stick to for its ad contract. | |||
Thank you user SG5064X for keeping a lookout. | |||
== Bus deployment for KJDEP == | |||
Dear user, | |||
I would like to bring up the point that 5454D has been a 190 perm since early this year and 5587D & 5601X are direct swap for 5596C and 5597A for 176 & 190. I believe you can see it for yourself if you are not aware of it. Cheers. Thanks. | |||
== Counterpoint == | |||
190 and 176 DDs are involved in cameos quite often these days, even buses like 5497 to 5499 and 3614U are doing 190 often and are also seen on 176 as well as far as I remember. Nevertheless, thanks for your inputs | |||
Cheers. | |||
== Re CCK deployments == | |||
Hi as a matter of fact, none of my edits were based on 'one-off appearances'. 5026D had been running on 184 for over a week before I made that edit. I also saw it on 184 last Fri, on Tue and on Wed. I take 190 daily and I have never seen it on 190 since it got the ad. | |||
For 5037Y, it was also on 190 for a while and also ran on 190 last Fri. But it also runs on 67 at times so it could still be a 67 perm. | |||
Same for 3613Y. Running on 190 regularly full day including last week and yesterday. Long-time perms are not immune to redeployment. Just look at SMB5Y | |||
For 302, 5930X is definitely not a 'very recent' addition. As stated previously it already came in in late-Oct/early-Nov and runs on 5825S' slot and subsequently replaced by 6110P. In fact it seems that 5930X's time in 302 has already come to an end. |
Latest revision as of 18:47, 21 November 2024
TIB1206A[edit]
Hi,
I am user SG5119Y.I am a SG forum user but my SG forum name is not SG5119Y.Regarding on your edit,I can understand how both u and other user feels.TIB1206A is now perm.I also text that user already.Cheers.Thanks.
RE: Suspected Multiple accounts hold by TIB1152X 190[edit]
Hi SG5064X,
Thank you for whistle blowing the two accounts for suspected multiple account holders. I had been observing the two accounts that you had provided over the days. As the editing patterns are different from one another, there is no concrete link to be hold by the same users.
Regarding on the clause on editing false information/disruptive editing, I would sincerely apologies as my main duty in-charge (as admin) is under the RAIL sector and not buses. You may wished to inform another admin @ Apex-LW'21 or any of the long-time editors to backed your claim before I could do any preventive measures.
Thanks & Regards
--Supernutorcrazy (talk, administrator) 27 June 2017 16:49 SGT
OC deployment[edit]
Hi,
I believe that 107L should be more sticky to 975 now that it has the nursing advert. Meanwhile for 104U, it keeps jumping around, or operates during peak hours only hence it's not seen.. hope this will help --TIB965Z (talk) 18:44, 19 June 2018 (+08)
Perm status[edit]
Dear user,
It has come to my attention whenever I edit something as a service perm u would always remove without hesitating. I does fact check to make sure I do not miss or get any facts wrong as much as possible. For instance,SG5172S has been always a 190 perm just that it spawn abt other services for a few weeks. Recently it have come back on 190 performing on their usual duties. I sincerely hope you can check for yourself before jumping to conclusion. Thank you.
Kranji B1s[edit]
Hi, just a quick check from your perspective, how often do these batch 1s spawn on 979 in your point of view?
Based on my checks in Bukit Panjang last month for weekdays, I have seen them going on 180, 190/A, 922, 972/M, 991 during morning peak and 3-6pm.
I have never seen them for every morning peak hour along 979 route, and occasionally only one Batch 1 will appear on 979 during evening peak at least once per week. In their place there will usually be a Euro 6 A95 and a random split shift slot for single/double decker.
Would appreciate if more checking is done, I will try relay the info from my part the best I can! Thanks and regards.
Edit: Other than the Batch 1 Euro Vs, have confirmed that all the current E500s, 5494, 5887 are still in 979 fleet on a daily basis.
Wekelwrady
Perm on 975[edit]
Hi,
SMB104U more or less act as a spare for this time being because it runs around for the month of December . As it is common for 190 and 985 OCs perm to run around on this service with duration of consecutive weeks, it will be well appreciated if more checking is done before edit. For instance, SMB42P previously also spawn 975 for weeks to last month. As for SMB107L, don’t think is really 975 perm too because it only run around for 2 weeks. After that, ur cameo other route such as 307/T and 976 before it went back to 190. So this bus does not serve as a direct swap for SMB104U or SMB108J.
Cheers and thanks.
Counter-point[edit]
From what I witness and remember, SMB107L had in fact been doing 975 for at least the entire of September 2022 and still saw it some time into October. SMB108J was SMB107L's direct swap. At the time when SMB108J started perming 190A in early September, SMB107L was entirely nowhere to be seen on 190 even during peak hours, not even showing up for 190A duty. SMB108J was directly doing the same duty that SMB107L previously did. As for SMB104U, it was still sticking to its original perm slot and was never involved in swapping (in fact it was the front bus of SMB108J). And to add on, I would agree with user SG5064X's explanation that this GoMo ad has a perm service to stick to for its ad contract.
Thank you user SG5064X for keeping a lookout.
Bus deployment for KJDEP[edit]
Dear user,
I would like to bring up the point that 5454D has been a 190 perm since early this year and 5587D & 5601X are direct swap for 5596C and 5597A for 176 & 190. I believe you can see it for yourself if you are not aware of it. Cheers. Thanks.
Counterpoint[edit]
190 and 176 DDs are involved in cameos quite often these days, even buses like 5497 to 5499 and 3614U are doing 190 often and are also seen on 176 as well as far as I remember. Nevertheless, thanks for your inputs
Cheers.
Re CCK deployments[edit]
Hi as a matter of fact, none of my edits were based on 'one-off appearances'. 5026D had been running on 184 for over a week before I made that edit. I also saw it on 184 last Fri, on Tue and on Wed. I take 190 daily and I have never seen it on 190 since it got the ad. For 5037Y, it was also on 190 for a while and also ran on 190 last Fri. But it also runs on 67 at times so it could still be a 67 perm. Same for 3613Y. Running on 190 regularly full day including last week and yesterday. Long-time perms are not immune to redeployment. Just look at SMB5Y
For 302, 5930X is definitely not a 'very recent' addition. As stated previously it already came in in late-Oct/early-Nov and runs on 5825S' slot and subsequently replaced by 6110P. In fact it seems that 5930X's time in 302 has already come to an end.