User talk:Haram

Recent Edits

Hi refer to the SG6241U, the previous user is saying that SG6241U is sharebus duty with 51 and 161. SBS Transit has introduced a sharebus system.

DDs on 858

Hi just to clarify that that bus 858 DDs are cameo.

Regards,

Alphabetlorefan1

Important

Hi Haram, I know you are editing based on your observations but in fact you missed out the former deployments. It is very important to update these former deployments but you refuse to do that and thats why I had to keep reverting your edit. Please dont make me do it again when you are told to update former deployments. Also why are you giving me unfriendly offensive words when you undo my edit just now? Its not funny so dont do that again. One more unfriendly offensive words to me and I will report you to an admin. Please understand what I am saying.

Thanks, Alphabetlorefan1 (talk) 17 July 2024, 15:29

UPDEP 80 DDs

Hi Haram,

Thanks for reaching out to me last night with your explanations for your edits on UPDEP 80 DD deployments.

Admittedly, I was initially skeptical of your edits due to my observations not tallying up with deployments of buses on the roster, in line with your remarks about how real-life deployments may differ from rostered deployments. Thank you for kindly clearing the air with me on this.

I would like to also mention that I have made some edits to the 80 page partly based on your explanations. If you do not mind, I have removed SG5396M from the duties table below because you have mentioned that it is a standby DD for UPDEP side.

I have also edited the duties table for HGDEP 80 buses based on my observations. For example, I know you previously mentioned SBS3091T to be rostered as a split shift bus, but I have taken it several times consistently on an A/P block, which is why I have edited it as an A/P bus. I do hope my edits are mostly, if not fully, accurate and reflect the deployments happening on 80 currently. Do edit/revert if my edits are false or misguided.

Thank you once again, and I hope to continue being a faithful editor alongside you and other responsible editors on SgWiki.

Regards,
23ispolo

Singapore Bus Fleet

Hi Haram,

I see that you were on the first bus departing Boon Lay Int this morning. As SBS3288T is a Wright Batch 3, it’s considered a debut. Hence, could you help me fill in this page for what service it ran on? No reply needed. Thanks.

Regards, LTA Bus Irrationalisation

BYD buses

What you say is not correct. Ulu Pandan is a package. Thus buses are also assigned to this package /depot. So by right, all the buses under Ulu Pandan should be deployed on Ulu Pandan packages only. So those UPD buses parked in AMDEP/BNDEP should be amended under UPD as well.

Likewise for the BYD buses , these were assign to the serangoon package (I would think you mean HG-Sk packages) as per your advice. So these should be the same situation as those UPD buses.

And with AMDEP closures, AMDEP buses most likely will switch to SWDEP for the time being.

There are two new depots (kim chuan and lorong halus) which should be for HG-SK n serangoon/eunos package. So SWDEP most likely is for AMDEP

Re: Old Page Naming

Hi,

With regards to the purposed renaming for:

• MAN NL323F (Euro VI) → MAN NL323F (Batch 4)
• Scania K230UB (Euro IV) (Batch 1) → Scania K230UB (Batch 1)
• Scania K230UB (Euro IV) (Batch 2) → Scania K230UB (Batch 2)
• Scania K230UB (Euro V) (Batch 1) → Scania K230UB (Batch 3)
• Scania K230UB (Euro V) (Batch 2) → Scania K230UB (Batch 4)
• MAN ND323F (Euro V) (Batch 1) → MAN ND323F (Batch 1)
• MAN ND323F (Euro V) (Batch 2) → MAN ND323F (Batch 2)
• MAN ND323F (Euro V) (Batch 3) → MAN ND323F (Batch 3)
• MAN ND323F (Euro VI) (Batch 1) → MAN ND323F (Batch 4)
• MAN ND323F (Euro VI) (Batch 2) → MAN ND323F (Batch 5)

The old format does not used what you had proposed. It had long be in this title format. I can't remember the old Scania model page uses "(Euro IV Batch 1)" or "(Euro IV) (Batch 1)" for the old format. But even so, it is still minor.

The reason why MAN ND323F renamed to the new format is to "standardised" with Scania K230UB naming convention in 2020/2021.

Regards

Supernutorcrazy (talk) 06:41, 28 July 2025 (+08)

Ban Practice

Hi,

As per discussion, it is aligned with the old sgWiki Buses rule - immediate ban for not syncing. There is no such thing as other editors will do it for you. This is the practice that was practiced since 2008s which majority voted for. The more forgiving ban practice was migrated, with the split of sgWiki Rail to Miraheze.

The first ban was applied for failure to edit Former Deployments of SG5917K from SWDEP to SWDEP 161. You had edited on 17 July 2025 at approx 11.45pm, where the ban was applied only at 18 July 2025 6.35am. There is gap of time for you to update, which 23ispolo did it for you - Hence the indefinite ban was applied. After SMB315C clarify the removal of indefinite ban policy removal (for 2020), no further ban was applied.

The second ban was applied for failure to edit SBS3696Z for former deployment of changes for SBS3128Y and SBS3696Z from SWDEP to SWDEP 25 at 28 July 2025 at 8.35am. The ban was awarded only on 28 July 2025 at 1pm, where there is gap of time for you to update. Hence the 2nd strike applied with the instruction. As there is no indication that it was immediate perm from editing comment it was assumed that SP had to be declared, on otherwise specified.

If you feel this rules are unfair, you are free to head over to sgWiki Miraheze or leave. I was just merely applying the rule of the great old day of sgWiki Buses (which is NOT FORGIVING).

Regards

Supernutorcrazy (talk) 19:26, 12 August 2025 (+08)