Jump to content

Talk:Jurong Port

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

Accident inside Jurong Port

[edit]

It is a fact that Jurong Port had a fatal accident. I would appreciate if the employees from Jurong Port stop deleting this part. Thanks. --Shorty23sin (talk) 02:17, 30 August 2010 (UTC)[reply]

Another issue about the Jurong Port article

[edit]

What I found out from most of the KTMB staff formerly stationed in Singapore that Jurong Port indeed had railway history (Jurong Line). But I don't know if I put it in the article as part of the "History" section will it stay there for long? Or will that part be deleted shortly. Kyrios320 (talk) 13:00, 14 May 2013 (UTC)[reply]

[edit]

Hello fellow Wikipedians,

I have just modified one external link on Jurong Port. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

This message was posted before February 2018. After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using the archive tool instructions below. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template {{source check}} (last update: 5 June 2024).

  • If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
  • If you found an error with any archives or the URLs themselves, you can fix them with this tool.

Cheers.—InternetArchiveBot (Report bug) 05:01, 15 October 2017 (UTC)[reply]