User talk:8549H

Recent Edits

Hi,

I have some doubts with regards to your recent edits

1. The 55x410W crossovers are still seen consistently, including today.
2. Can I ask what services the 63xx citaros have been seen on this week, since you said they are not for 53?
3. While I have seen 6011E and 6095M on 54 multiple times, are they really perm 54 (and likewise 6670, 6671, 6751 for 53)? I still saw 6011 on 53 as well as 6670, 6671 on 54 over the past few weeks. You may want to kiv that further.

(Reply)
Noted your observations, thanks!

BNDEP 7 & 35 swaps

Hi, have noticed your edits on the fleet swaps between Services 7 and 35. However, I noticed last Thursday at 6pm that there was this BNDEP A95 on Service 7 that changed the display from 7 to 35 while it was going to end its trip in Bedok Int. Got a feeling that there are some crossover/interlining duties between both services, do check to see if it is true. Thanks!

Reply

Have observed and there is no interlining duties. The ex sv7 man dds are run full day on sv35. It could be a coincidence since sv35 is almost full fleet man dds. There is no interlining duties on sv7a/b as observed

Opinion

Hi,

I would like to seek your opinion on the following proposed changes:

1. Launch of sgWiki Bus Spotting Page A new page will be created daily and automatically deleted a month later. For example, "Bus Spotting/1 February 2025" would be removed on 1 March 2025. This page is intended to allow editors to document bus registration numbers without the typical edit limitations, enabling infinite edits.

The primary objective is to encourage collaboration among editors and to improve the accuracy of bus deployment data in relation to their permanent services. Many users have noted that the deployment page contains inaccurate and outdated information. By using these pages, we aim to track bus operations more effectively and allocate the correct permanent services, without requiring editors to board the buses to verify duty schedules.

2. Use of Subpages for Bus Model Deployment I have received considerable feedback, mostly criticism, regarding the separation and consolidation of bus advertisements across models. Most complaints focus on advertisement changes rather than deployment accuracy, which contributes to the aforementioned inaccuracies. As such, I propose reorganising the Bus Model deployment using subpages as follows:

Example: Volvo B9TL (WEG Batch 2) will be divided into four subpages:

1. Volvo B9TL (Wright Eclipse Gemini 2) (Batch 2)/Page 1 – (Low Entry, SBS7700T – SBS7729L)
2. Volvo B9TL (Wright Eclipse Gemini 2) (Batch 2)/Page 2 – (Low Floor, SBS3000G – SBS3099Y)
3. Volvo B9TL (Wright Eclipse Gemini 2) (Batch 2)/Page 3 – (Low Floor, SBS3100B – SBS3199S)
4. Volvo B9TL (Wright Eclipse Gemini 2) (Batch 2)/Page 4 – (Low Floor, SBS3200X – SBS3238M & SBS3269Z)

A navigation bar will be added at the top and bottom of each page, linking the respective subpages. Each page will feature a single table listing up to 100 buses, organised in the following format:

Registration No/Livery | Operator/Current Deployment | Advertisement | Former Deployment

This approach seeks to balance different perspectives, and to be more mobile friendly, as I am uncertain why some users are strongly opposed to these changes.

Alternative Table Layouts:

1. Registration No/Livery | Operator/Current Deployment | Former Deployment (Maintain status quo)
2. Batch | Registration No/Livery | Operator/Current Deployment | Former Deployment (Merging of Batches, numerical order, maintain status quo)
3. Batch | Registration No/Livery | Operator/Current Deployment | Advertisement | Former Deployment (Merging of Batches, numerical order)

Please let me know your thoughts on these proposals. Thank you for your time and feedback.

Regards, Supernutorcrazy