GCL LAZARO
Bulk carrier · Singapore · AIS Class A
In short
GCL LAZARO (Bulk carrier, Singapore flag) was last seen on AIS on , moored, in the port of Norfolk. Its crew-entered AIS destination is US NNS (Newport News); its reported draught is 7.8 m (voyage report via AISstream.io global terrestrial AIS, received Oct 6, 2026, 10:42 UTC). It arrived there on Oct 4, 2026, 17:44 UTC. ISM manager: Dalian Dongrong Ship Management Co.,Ltd. (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).
- Vessel type
- Bulk carrier
- Flag
- Singapore
- Year built
- —
- Gross tonnage
- —
- Size (length × beam)
- —
- ISM manager
- Dalian Dongrong Ship Management Co.,Ltd.
Watch this ship
Get an email when GCL LAZARO reaches Newport News, and when it leaves port, changes destination, name, flag or owner, or is sanctioned, detained or named in an official release.
Free forever. No card. A free account follows up to 5 ships and ports.
Last reported position
received- Position
- 36.8793° N, 76.3314° W
- Area
- North Atlantic Ocean
- StatusWhat do AIS statuses mean?
- Moored
- Speed
- 0 kn
- Course
- 93°
- Heading
- 95°
Last 30 days: 3 port calls (Norfolk, Hampton Roads Pt, and Newport News).
Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls 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
- GCL LAZARO
- IMO numberWhat is an IMO number?
- 9957476
- MMSIWhat is an MMSI?
- 563182300
- Call signWhat is a call sign?
- 9V7706
- Flag
- Singapore
- AIS ship type
- Cargo
- Gross tonnageGross tonnage vs deadweight
- —
- Length overall
- —
- Beam
- —
- Year built
- —
SingaporeA 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 · confidence 0.9 · retrieved Oct 5, 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 |
|---|---|---|
| Arrived at NorfolkAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left Hampton Roads PtAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at Hampton Roads PtAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left Newport NewsAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at Newport NewsAIS-detected | Voydar port-call detector (AIS geofence) |
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 |
|---|---|---|---|---|
| 2023 | 7,091 t | 2,265 t | 103 days | 266 kg |
| 2024 | 12,025 t | 3,837 t | 187 days | 272 kg |
| 2025 | 4,610 t | 1,478 t | 64 days | 265 kg |
Technical efficiency: EEXI (3.03 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.
Detected from AIS AIS-detected
| Port | Arrived | Departed | Time in port |
|---|---|---|---|
| Norfolk USORF | Oct 4, 2026, 17:44 UTC | in port | — |
| Hampton Roads Pt USHR3 | Oct 2, 2026, 22:27 UTC | Oct 4, 2026, 17:31 UTC | 43 h 4 min |
| Newport News USNNS | Sep 30, 2026, 21:51 UTC | Oct 2, 2026, 22:15 UTC | 2 d 0 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.
Frequently asked questions
- Where is GCL LAZARO now?
- GCL LAZARO (Bulk carrier, Singapore flag) was last seen on AIS on Oct 6, 2026, 10:50 UTC, moored, in the port of Norfolk. The crew-entered destination was US NNS (voyage report via AISstream.io global terrestrial AIS, received Oct 6, 2026, 10:42 UTC). This report does not confirm the ship’s current route.
- What kind of ship is GCL LAZARO?
- GCL LAZARO is a bulk carrier sailing under the flag of Singapore.
- Who is recorded as the owner or manager of GCL LAZARO?
- Dalian Dongrong Ship Management Co.,Ltd. is recorded as ISM manager for GCL LAZARO (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 GCL LAZARO?
- Voydar has no matched sanctions record displayed for GCL LAZARO 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 GCL LAZARO. Missing records do not establish whether the ship has been detained.
Neighbouring IMO numbers
IMO numbers are issued in sequence. These are the nearest numbers below and above this ship's that have a full Voydar 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/9957476Using 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.