LONDON BAY
Bulk carrier · Palau · built 2004 · AIS Class A
In short
LONDON BAY (Bulk carrier, Palau flag) was last seen on AIS on , under way at 12 kn, near Pulau Sambu, Riau (Strait of Malacca). Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. Its last detected port call was at Port Said: arrived Jul 16, 2026, left Sep 5, 2026. ISM manager: London Tower Shipping SA (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).
- Vessel type
- Bulk carrier
- Flag
- Palau
- Year built
- 2004
- Gross tonnage
- 18,020
- Size (length × beam)
- 170 m × 27 m
- ISM manager
- London Tower Shipping SA
Last reported position: 1.1959° N, 103.884° E · Strait of Malacca · See on the map
Watch this ship
LONDON BAY has not been received for a while. Follow it for an email update when Voydar receives a new position, and for arrival and departure alerts.
Voydar last heard LONDON BAY on September 22, 2026. Our receivers cover coasts and busy waters, so alerts resume when it is next in range.
What you would have been told
Nothing in the last 24 hours: no arrival or departure at a port. You are told the moment that changes.
Detected from AIS, as of Nov 20, 2026, 20:39 UTC.
Free forever. No card. Your first follow also starts a free 14-day Plus trial: alerts for LONDON BAY reach you the moment they happen, arrival-time changes included. When it ends you stay on Free, with a daily email, unless you keep Plus (US$7 a month). Compare plans
Get alerts on your phone: the Voydar app
Last reported position
received- Position
- 1.1959° N, 103.884° E
- Area
- Strait of Malacca
- Status
- Under way using engineWhat do AIS statuses mean?
- Speed
- 12 kn
- Course
- 63°
- Heading
- 61°
- Compass: course over ground 63°, heading 61°
- Arrow: course. Hull: heading. As broadcast on AIS.
Locator map: Natural Earth (public domain)
Voydar detected no port call in the last 30 days.
Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls below.
Pro shows LONDON BAY's track before the last 30 days. Voydar has recorded its port calls since July 16, 2026.Free forever. No card. Follow a ship and Plus is free for 14 days.
Try the live demo, no sign-upIdentity & particulars
Length overall 170 mone tick every 25 m
Beam 27 mPlan outline, to scale
- Name
- LONDON BAY
- IMO numberWhat is an IMO number?
- 9286944
- MMSIWhat is an MMSI?
- 511101245
- Call signWhat is a call sign?
- T8A4529
- Flag
- Palau
- Vessel type
- Detailed type from WikidataBulk carrier
- Gross tonnageGross tonnage vs deadweight
- 18,020
- Deadweight (DWT)
- Source: Wikidata, record Q117024462. Added to Voydar on October 24, 2026. Licence: CC0 1.0.29,727 t
- Length overall
- 170 m
- Beam
- 27 m
- Year built
- 2004
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.
- ISM manager
- Source: EU MRV (THETIS-MRV) emissions · reporting years 2024–2025 · reported · high confidence · retrieved Nov 16, 2026
- Builder
- Source: Wikidata · reported · high confidence · retrieved Nov 15, 2026
Checking ownership or sanctions for your business? Teams screen fleets by IMO, keep watch with alerts and keep a dated record. Voydar for business →
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 |
|---|---|---|
| Left Port SaidAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at Port SaidAIS-detected | Voydar port-call detector (AIS geofence) | |
| Reported departure from Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) | |
| Reported arrival at Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) | |
| Port State Control inspection at Seattle, Washington | USCG PSIX / CGMIX inspections | |
| Reported departure from Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) | |
| Reported arrival at Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) | |
| Inspection at San Pedro, California | USCG PSIX / CGMIX inspections | |
| Inspection at WASHINGTON, District of Columbia | USCG PSIX / CGMIX inspections | |
| Reported departure from TampaAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Inspection at Tampa, Florida | USCG PSIX / CGMIX inspections | |
| Inspection at Tampa, Florida | USCG PSIX / CGMIX inspections | |
| Inspection at Tampa, Florida | USCG PSIX / CGMIX inspections | |
| Inspection at New Orleans, Louisiana | USCG PSIX / CGMIX inspections | |
| Port State Control inspection at PORTLAND, Oregon | USCG PSIX / CGMIX inspections | |
| Inspection at JBER, Alaska | USCG PSIX / CGMIX inspections | |
| Port State Control inspection at Portland, Oregon | USCG PSIX / CGMIX inspections |
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.
Incidents & investigations Authority-reported
Accident and incident reports by national investigation boards, and casualty warnings, that concern this ship. Each links to the original.
- Occurred Apr 19, 2011衝突(単) · 貨物船運輸安全委員会 船舶事故等調査報告書 (JTSB marine accident and incident reports)関門港戸畑航路 福岡県北九州市所在の関門港戸畑航路第1号灯標
貨物船KAITI HILL衝突(灯標)Report published Nov 25, 2011
本船は、船長ほか21人が乗り組み、水先人が乗船し、船首約3.5m、船尾約5.4mの喫水で製鉄戸畑泊地内において、引船の支援を得て出航の態勢として海上保安庁関門海峡海上交通センター(以下「関門マーチス」という。)に連絡したとき、東航船3隻の通過を待って関門航路に入るよう指示されたので、低速のまま戸畑航路に向かった。 水先人は、前方警戒のために引船1隻を関門航路第12号灯浮標付近に向かわせ、平成23年4月19日11時12分ごろ戸畑航路に入って北東進中、本船が風に圧流されていることを認め、左舵を取りながら増速し、船尾を引船に引かせたが、11時16分ごろ、対地針路051.2°(真方位、以下同じ。)及び船首方位008°となったとき、右舷船首部が戸畑航路第1号灯標に衝突した。
Source: 運輸安全委員会 船舶事故等調査報告書 (JTSB marine accident and incident reports). 出典:運輸安全委員会「船舶事故等調査報告書」(https://jtsb.mlit.go.jp/)。Seadar が項目を抽出・加工して作成 (Source: Japan Transport Safety Board marine accident reports; fields extracted and edited by Seadar). Licence: Public Data License 1.0 (公共データ利用規約 第1.0版, PDL1.0; compatible with CC BY 4.0).
Safety & inspections
| Date | Type | Port | Findings |
|---|---|---|---|
| Feb 27, 2023 | Vessel InspectionPSC | Seattle, Washington | clean |
| Oct 4, 2017 | Vessel Inspection | San Pedro, California | clean |
| Feb 20, 2017 | Incident Investigation | WASHINGTON, District of Columbia | clean |
| Oct 10, 2016 | Boarding | Tampa, Florida | clean |
| Oct 10, 2016 | Vessel Inspection | Tampa, Florida | clean |
| Oct 9, 2016 | Vessel Operational Control | Tampa, Florida | clean |
| Oct 5, 2016 | Vessel Operational Control | New Orleans, Louisiana | clean |
| Jun 25, 2016 | Vessel InspectionPSC | PORTLAND, Oregon | clean |
| Nov 17, 2014 | Vessel Inspection | JBER, Alaska | clean |
| May 12, 2014 | Vessel InspectionPSC | Portland, Oregon | clean |
| Jun 12, 2012 | Vessel InspectionPSC | Portland, Oregon | clean |
| May 5, 2011 | Vessel InspectionPSC | JBER, Alaska | clean |
| Jun 10, 2008 | Vessel InspectionPSC | STATEN ISLAND, New York | clean |
| May 2, 2007 | Vessel InspectionPSC | Portland, Oregon | clean |
| Jul 16, 2005 | Vessel InspectionPSC | Brownsville, Texas | clean |
| Jul 5, 2004 | Boarding | San Francisco, California | clean |
| Jun 28, 2004 | Vessel InspectionPSC | San Pedro, California | clean |
| Jun 27, 2004 | Boarding | San Pedro, California | clean |
| Jun 24, 2004 | Boarding | San Pedro, California | clean |
Source: U.S. Coast Guard Port State Information Exchange (PSIX) — public domain. Covers inspections recorded in U.S. waters. Free on Voydar; the incumbents charge for this.
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 |
|---|---|---|---|---|
| 2020 | 4,631 t | 1,483 t | 72 days | 221 kg |
| 2022 | 3,489 t | 1,104 t | 56 days | 231 kg |
| 2024 | 2,125 t | 673 t | 31 days | 219 kg |
| 2025 | 2,013 t | 645 t | 53 days | 197 kg |
Technical efficiency: EEXI (5.66 gCO₂/t·nm). Source: European Commission / EMSA THETIS-MRV (EU Regulation 2015/757). Covers voyages to, from and within the EU/EEA.
Compared with ships of its type
Where this ship’s reported CO₂ intensity for 2025 sits among the ships EU MRV lists as “Bulk carrier”. Lower is less CO₂.
- CO₂ per tonne of cargo carried one nautical mile6.84 g per tonne-nautical mile
- Lowest reportedHighest reported
36% of the 3,661 ships in this group reported a lower figure.
Group: lower quartile 6.06 · median 7.94 · upper quartile 10.76
- CO₂ per nautical mile sailed196.7 kg per nautical mile
- Lowest reportedHighest reported
12% of the 3,811 ships in this group reported a lower figure.
Group: lower quartile 222.1 · median 261.2 · upper quartile 303.2
Calculated by Voydar from the figures ships report under EU MRV. This is not a rating and not the IMO Carbon Intensity Indicator (CII). EU MRV covers ships over 5,000 gross tonnage on voyages to, from and within the EU/EEA, so the group is those ships, not the world fleet. How this is calculated
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.
Detected from AIS AIS-detected
| Port | Arrived | Departed | Time in port |
|---|---|---|---|
| Port Said EGPSD | Jul 16, 2026, 18:03 UTC | Sep 5, 2026, 15:19 UTC | 50 d 21 h |
Detected by Voydar when the ship's AIS positions stayed slow inside a harbour area. Calls shorter than 30 minutes are not shown. Depends on AIS reception; detection started on June 8, 2026.
Reported by authorities Authority-reported
| Port | Record | Date (UTC) | Berth | Source |
|---|---|---|---|---|
| Hong Kong HKHKG | Arrival(matched by call sign) | Apr 5, 2023, 03:55 UTC | PT | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Jul 25, 2019, 18:00 UTC | SELA | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Tampa USTPA | Departure | Oct 13, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Tampa USTPA | Arrival | Oct 10, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Long Beach USLGB | Departure | Jul 1, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Long Beach USLGB | Arrival | Jun 29, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Longview USLOG | Departure | Jun 23, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Longview USLOG | Arrival | Jun 22, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| BARBERS POINT, HI (NET TABLE) | Departure | May 28, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| BARBERS POINT, HI (NET TABLE) | Arrival | May 15, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Longview USLOG | Departure | May 13, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Longview USLOG | Arrival | May 10, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: June 27, 2004.
Source: Marine Department, HKSAR Government — DATA.GOV.HK. Licence: DATA.GOV.HK Terms and Conditions.
Source: US Army Corps of Engineers, Waterborne Commerce Statistics Center (US CBP entrance/clearance records). Licence: US Government work — public domain.
Frequently asked questions
- What kind of ship is LONDON BAY?
- LONDON BAY is a bulk carrier sailing under the flag of Palau, built in 2004 by Shikoku Dockyard. The vessel is 170 m long with a beam of 27 m and has a gross tonnage of 18,020.
- Who is recorded as the owner or manager of LONDON BAY?
- London Tower Shipping SA is recorded as ISM manager for LONDON BAY (source: EU MRV (THETIS-MRV) emissions; reporting years 2024–2025). This source record does not independently confirm today’s ownership or management.
- What sanctions and inspection records does Voydar hold for LONDON BAY?
- Voydar has no matched sanctions record displayed for LONDON BAY 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. LONDON BAY has 19 recorded Port State Control inspections. Detention and deficiency detail is not recorded for these inspections.
Full Vessel Report
A dated PDF with the complete track since June 2026, every port call, ownership and flag changes, inspections, a sanctions and dark-activity screening snapshot, emissions, companies and every source.
Sample: a real report for EVER GIVEN (IMO 9811000), built from public data and marked SAMPLE on every page.
Every fact on this page stays free.
Know this ship?
Help other readers. Member posts are shown as member content, never as sourced data.
- Date, place and an optional note
- Members who know her can answer
- Suggest a correctionChecked against sources before anything changes
More Bulk carriers
Other bulk carriers with full Voydar profiles. A different set each day. All bulk carriers
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/9286944Cite this page
LONDON BAY. Voydar (voydar.com). https://www.voydar.com/vessel/9286944-london-bay. Retrieved November 20, 2026.
Each fact above names its own source and date. Cite that primary source too when you rely on a fact.
Using this data in code?
Every account gets a personal API allowance: 2,500 credits a month free, 25,000 with Pro. Pro includes use in your own product. Growth and Scale add volume, and each includes one Pro membership.