ZIM Virginia
Container ship · Israel · built 2002 · AIS Class A
In short
ZIM Virginia (Container ship, Israel flag) was last seen on AIS on , moored, in the port of Norfolk. Its crew-entered AIS destination is NORFOLK, with an ETA of Oct 6, 2026, 11:00 UTC; its reported draught is 11.6 m (voyage report via AISstream.io global terrestrial AIS, received Oct 6, 2026, 16:25 UTC). It arrived there on Oct 6, 2026, 14:15 UTC. ISM manager: ZIM Integrated Shipping Services (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).
- Vessel type
- Container ship
- Flag
- Israel
- Year built
- 2002
- Gross tonnage
- 53,453
- Size (length × beam)
- 293 m
- ISM manager
- ZIM Integrated Shipping Services
Watch this ship
Get an email when ZIM Virginia arrives or 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.9059° N, 76.3266° W
- Area
- North Atlantic Ocean
- StatusWhat do AIS statuses mean?
- Moored
- Speed
- 0 kn
- Course
- 161°
- Heading
- 351°
Last 30 days: 2 port calls (Norfolk and Port Richmond).
Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls below.
Pro shows ZIM Virginia's track before the last 30 days. Voydar has recorded its port calls since June 21, 2026.Free forever. No card. New accounts include 14 days of Pro.
Try the live demo, no sign-upIdentity & particulars
- Name
- ZIM Virginia
- IMO numberWhat is an IMO number?
- 9231808
- MMSIWhat is an MMSI?
- 428002000
- Call signWhat is a call sign?
- 4XFV
- Flag
- Israel
- Vessel type
- Container ship
- AIS ship type
- Cargo
- Gross tonnageGross tonnage vs deadweight
- 53,453
- Length overall
- 293 m
- Beam
- —
- Year built
- 2002
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 · confidence 0.9 · retrieved Oct 5, 2026
- 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 |
|---|---|---|
| Arrived at NorfolkAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left Port RichmondAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at Port RichmondAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left BarcelonaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at BarcelonaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Reported arrival at New YorkAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported departure from New YorkAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported departure from SavannahAuthority-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 |
|---|---|---|---|---|
| 2023 | 20,600 t | 6,596 t | 121 days | 497 kg |
| 2024 | 32,744 t | 10,489 t | 154 days | 599 kg |
| 2025 | 30,187 t | 9,600 t | 150 days | 629 kg |
Technical efficiency: EEXI (13 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 6, 2026, 14:15 UTC | in port | — |
| Port Richmond USRI4 | Oct 4, 2026, 14:43 UTC | Oct 5, 2026, 08:41 UTC | 17 h 58 min |
| Barcelona ESBCN | Jun 21, 2026, 15:40 UTC | Jul 5, 2026, 08:55 UTC | 13 d 17 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 |
|---|---|---|---|---|
| New York USNYC | Arrival | Dec 26, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| New York USNYC | Departure | Dec 26, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Savannah USSAV | Departure | Dec 22, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Savannah USSAV | Arrival | Dec 22, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| New York USNYC | Arrival | Oct 15, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| New York USNYC | Departure | Oct 15, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| ELIZABETH RIVER, VA | Departure | Oct 15, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| ELIZABETH RIVER, VA | Arrival | Oct 14, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Savannah USSAV | Departure | Oct 12, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Savannah USSAV | Arrival | Oct 12, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| San Juan PRSJU | Departure | Jul 25, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| San Juan PRSJU | Arrival | Jul 25, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: September 24, 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 ZIM Virginia now?
- ZIM Virginia (Container ship, Israel flag) was last seen on AIS on Oct 6, 2026, 16:52 UTC, moored, in the port of Norfolk. The crew-entered destination was NORFOLK (voyage report via AISstream.io global terrestrial AIS, received Oct 6, 2026, 16:25 UTC). This report does not confirm the ship’s current route.
- What kind of ship is ZIM Virginia?
- ZIM Virginia is a container ship sailing under the flag of Israel, built in 2002 by HD Hyundai Heavy Industries. The vessel is 293 m long and has a gross tonnage of 53,453.
- Who is recorded as the owner or manager of ZIM Virginia?
- ZIM Integrated Shipping Services is recorded as ISM manager for ZIM Virginia (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 ZIM Virginia?
- Voydar has no matched sanctions record displayed for ZIM Virginia 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 ZIM Virginia. 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/9231808Using 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.