BROOKLYN BRIDGE
Container ship · built 2010
In short
BROOKLYN BRIDGE (Container ship) has no AIS position on record with Seadar.
- Vessel type
- Container ship
- Flag
- —
- Year built
- 2010
- Gross tonnage
- 44,459
- Size (length × beam)
- 267 m × 35 m
- Registered owner
- —
Watch this ship
Get an email when BROOKLYN BRIDGE arrives or leaves port, changes destination, name, flag or owner, or is sanctioned, detained or named in an official release.
We email you a link and a code. That creates a free account, no password or card, and follows BROOKLYN BRIDGE.
Free account, no card: follow up to 5 ships and ports. Plus follows 50, Pro 500.
By continuing you accept the Terms and the Privacy policy.
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)
Try the live demo, no sign-upIdentity & particulars
- Name
- Source: EU MRV (THETIS-MRV) emissions, record 9458999:2025. Added to Seadar on September 24, 2026. Licence: EC reuse (Decision 2011/833/EU).BROOKLYN BRIDGE
- IMO numberWhat is an IMO number?
- 9458999
- MMSIWhat is an MMSI?
- —
- Call signWhat is a call sign?
- —
- Flag
- —
- Vessel type
- Container ship
- Gross tonnageGross tonnage vs deadweight
- 44,459
- Deadweight (DWT)
- Source: Wikidata, record Q105768182. Added to Seadar on September 23, 2026. Licence: CC0 1.0.52,055 t
- Length overall
- 266.6 m
- Beam
- 35.4 m
- Year built
- 2010
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 year 2025 · reported · confidence 0.9 · retrieved Sep 28, 2026Source: EU MRV (THETIS-MRV) emissions · reporting years 2024–2025 · reported · confidence 0.9 · retrieved Sep 28, 2026
- Builder
- Source: Wikidata · reported · confidence 0.8 · retrieved Sep 22, 2026
Timeline
Dated events for this ship from every source Seadar holds, newest first. Each line names its source; derived items say how they were derived.
| Date | Event | Source |
|---|---|---|
| ISM manager: ONESEA SOLUTIONS PTE LTD (previously "K" LINE SHIP MANAGEMENT (SINGAPORE) PTE LTD) | Seadar relationship-change derivation (derived by Seadar from EU MRV (THETIS-MRV) emissions) | |
| 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) | |
| 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) | |
| 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) |
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 |
|---|---|---|---|---|
| 2022 | 40,449 t | 12,880 t | 220 days | 506 kg |
| 2023 | 34,087 t | 10,885 t | 238 days | 462 kg |
| 2024 | 34,264 t | 10,872 t | 223 days | 480 kg |
| 2025 | 26,854 t | 8,516 t | 176 days | 462 kg |
Technical efficiency: EEXI (13.74 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 Seadar 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 |
|---|---|---|---|---|
| Hong Kong HKHKG | Arrival | Feb 5, 2021, 16:12 UTC | KC7 | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | Nov 25, 2020, 06:08 UTC | PT | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Nov 19, 2020, 14:57 UTC | KC12 | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | Sep 20, 2020, 05:58 UTC | PT | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Oct 20, 2019, 20:00 UTC | KC13 | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Oakland USOAK | Arrival | Dec 13, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Oakland USOAK | Departure | Dec 13, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Long Beach USLGB | Departure | Dec 8, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Long Beach USLGB | Arrival | Dec 8, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Oakland USOAK | Departure | Nov 1, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Oakland USOAK | Arrival | Oct 31, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Long Beach USLGB | Departure | Oct 27, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: June 17, 2010.
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
- Where is BROOKLYN BRIDGE now?
- Seadar has no displayable AIS position for BROOKLYN BRIDGE in this profile. A coverage gap does not establish whether the ship is transmitting or where it is now.
- What kind of ship is BROOKLYN BRIDGE?
- BROOKLYN BRIDGE is a container ship, built in 2010 by HD Hyundai Heavy Industries. The vessel is 266.6 m long with a beam of 35.4 m and has a gross tonnage of 44,459.
- What sanctions and inspection records does Seadar hold for BROOKLYN BRIDGE?
- Seadar has no matched sanctions record displayed for BROOKLYN BRIDGE from the OFAC SDN list, the UK Sanctions List, the Canadian autonomous sanctions list, the EU list of designated vessels and the New Zealand Russia Sanctions Register. Coverage may be incomplete; this is not sanctions clearance. No matched inspection records are displayed for BROOKLYN BRIDGE. Missing records do not establish whether the ship has been detained.
Sister ships
Likely sister ships: built by HD Hyundai Heavy Industries, same type, gross tonnage within 2.5% and length within 1.5% of this ship's.
- Bear Mountain BridgeIMO 9463293Cargo ship · built 2011 · 44,234 GT
- EVERLASTING VIRTUEIMO 9463310Container ship · built 2011 · 44,234 GT
- NYK FUJIIMO 9482938Container ship · built 2011 · 44,854 GT
- NYK FutagoIMO 9487524Container ship · built 2011 · 44,925 GT
- NYK FushimiIMO 9487964Container ship · built 2012 · 44,854 GT
Neighbouring IMO numbers
IMO numbers are issued in sequence. These are the nearest numbers below and above this ship's that have a full Seadar profile.
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/9458999Using 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.