Singapore Express
Container ship · built 2000
In short
Singapore Express (Container ship) has no AIS position on record with Voydar.
- Vessel type
- Container ship
- Flag
- —
- Year built
- 2000
- Gross tonnage
- 54,401
- Size (length × beam)
- 294 m
- Registered owner
- —
Watch this ship
Singapore Express has not been received for a while. Follow it and we will email you as soon as it is heard again, then when it reaches or leaves port.
Free forever. No card. A free account follows up to 5 ships and ports.
Last reported position
No AIS position on record for this vessel. Identity and particulars are below.
A year of history in the Terminal (Plus) · the full archive since June 1, 2026 (Pro)Free forever. No card. New accounts include 14 days of Pro.
Try the live demo, no sign-upIdentity & particulars
- Name
- Singapore Express
- IMO numberWhat is an IMO number?
- 9200809
- MMSIWhat is an MMSI?
- —
- Call signWhat is a call sign?
- —
- Flag
- —
- Vessel type
- Container ship
- Gross tonnageGross tonnage vs deadweight
- 54,401
- Length overall
- 294 m
- Beam
- —
- Year built
- 2000
A tag next to a value names the register that supplied it (hover or tap it for the record and date). Values without a tag come from the ship's own AIS broadcasts or from Wikidata. Position and identity are derived live from AIS.
Ownership & management
Each line shows where the fact comes from. Links backed by an identifier point to the company page.
- Builder
- Source: Wikidata · reported · confidence 0.8 · retrieved Sep 22, 2026
Timeline
Dated events for this ship from every source Voydar holds, newest first. Each line names its source; derived items say how they were derived.
| Date | Event | Source |
|---|---|---|
| Reported arrival at New OrleansAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported departure from New OrleansAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported departure from HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)Authority-reported | USACE foreign traffic vessel entrances & clearances |
Owner, operator and manager changes found by comparing yearly EU MRV reports are dated to the reporting year ("during 2025"), not to a day. Port calls here are the most recent only; the full lists are further down.
Emissions & fuel consumption
Independently verified annual figures reported under the EU MRV regulation — public environmental data the incumbents don't surface.
| Year | CO₂ emitted | Fuel burned | Time at sea | CO₂ / n mile |
|---|---|---|---|---|
| 2018 | 23,070 t | 7,393 t | 115 days | 619 kg |
| 2019 | 23,360 t | 7,481 t | 126 days | 567 kg |
Technical efficiency: EIV (15.07 gCO₂/t·nm). Source: European Commission / EMSA THETIS-MRV (EU Regulation 2015/757). Covers voyages to, from and within the EU/EEA.
Port calls
Two kinds of evidence, kept apart: calls Voydar detected from the ship's AIS positions, and arrivals and departures published by port authorities and customs records.
Reported by authorities Authority-reported
| Port | Record | Date (UTC) | Berth | Source |
|---|---|---|---|---|
| New Orleans USMSY | Arrival | Dec 12, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| New Orleans USMSY | Departure | Dec 12, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Departure | Dec 10, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Arrival | Dec 10, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Savannah USSAV | Departure | Dec 1, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Savannah USSAV | Arrival | Dec 1, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Charleston USCHS | Arrival | Nov 6, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Charleston USCHS | Departure | Nov 6, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| New Orleans USMSY | Arrival | Nov 2, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| New Orleans USMSY | Departure | Nov 2, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Departure | Oct 30, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Arrival | Oct 30, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: January 18, 2002.
Source: US Army Corps of Engineers, Waterborne Commerce Statistics Center (US CBP entrance/clearance records). Licence: US Government work — public domain.
Frequently asked questions
- Where is Singapore Express now?
- Voydar has no displayable AIS position for Singapore Express in this profile. A coverage gap does not establish whether the ship is transmitting or where it is now.
- What kind of ship is Singapore Express?
- Singapore Express is a container ship, built in 2000 by HD Hyundai Heavy Industries. The vessel is 294 m long and has a gross tonnage of 54,401.
- What sanctions and inspection records does Voydar hold for Singapore Express?
- Voydar has no matched sanctions record displayed for Singapore Express from the OFAC SDN list, the UK Sanctions List, the Canadian autonomous sanctions list, the EU list of designated vessels, the New Zealand Russia Sanctions Register and the French national asset-freeze register. Coverage may be incomplete; this is not sanctions clearance. No matched inspection records are displayed for Singapore Express. Missing records do not establish whether the ship has been detained.
Use this data
This page is also available as JSON, free, with the source and licence of every section. Sections whose sources do not permit redistribution are listed as withheld.
GET /api/v1/vessels/9200809Using this data in code?
Every account gets a personal API allowance: 2,500 credits a month free, 25,000 with Pro. Pro adds internal business use; API plans add building the data into your own products.