Vohburg
Container ship · Antigua & Barbuda · built 2005 · AIS Class A
In short
Vohburg (Container ship, Antigua & Barbuda flag) was last seen on AIS on , under way at 7.6 kn, in the Baltic Sea. Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. Its crew-entered AIS destination is LTKLJ (Klaipeda), with an ETA of Oct 4, 2026, 22:30 UTC; its reported draught is 7.1 m (voyage report via AISstream.io global terrestrial AIS, received Oct 4, 2026, 23:00 UTC). ISM manager: Jorg Kopping Dritte Bereedereungsgesellschaft mbH & Co. MS. "Vohburg" KG (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).
Current voyage: from Gdynia (departed Oct 4, 2026, 06:46 UTC) to LTKLJ (Klaipeda)
- Vessel type
- Container ship
- Year built
- 2005
- Gross tonnage
- 7,852
- Size (length × beam)
- 141 m × 22 m
Watch this ship
Vohburg 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
received- Position
- 55.6779° N, 21.1383° E
- Area
- Baltic Sea
- StatusWhat do AIS statuses mean?
- Under way using engine
- Speed
- 7.6 kn
- Course
- 169°
- Heading
- 170°
Last 30 days: 9 port calls (Gdynia, Moss, Sjursoja/Oslo, Rotterdam, Hull, Kristiansand, and Salt End).
Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls below.
Pro shows Vohburg's track before the last 30 days. Voydar has recorded its port calls since September 1, 2026.Free forever. No card. New accounts include 14 days of Pro.
Try the live demo, no sign-upIdentity & particulars
- Name
- Vohburg
- IMO numberWhat is an IMO number?
- 9287807
- MMSIWhat is an MMSI?
- 305773000
- Call signWhat is a call sign?
- V2OW7
- Vessel type
- Detailed type from WikidataContainer ship
- AIS ship type
- Cargo
- Gross tonnageGross tonnage vs deadweight
- 7,852
- Deadweight (DWT)
- Source: Wikidata, record Q52354498. Added to Voydar on September 23, 2026. Licence: CC0 1.0.9,296 t
- Length overall
- 140.6 m
- Beam
- 22 m
- Year built
- 2005
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 |
|---|---|---|
| Left GdyniaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Reported arrival at GdyniaAuthority-reported | Urząd Morski w Gdyni: ships in port, expected and departing (Gdynia, Gdańsk) | |
| Arrived at GdyniaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left MossAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at MossAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left Sjursoja/OsloAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at Sjursoja/OsloAIS-detected | Voydar port-call detector (AIS geofence) | |
| Former name: Jsv Yaiza | Wikidata | |
| Former name: Geestdijk | Wikidata |
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.
Former and other names
Names attested for this ship other than its current name.
| Name | Evidence | Date | Source |
|---|---|---|---|
| Jsv Yaiza | Former name | Jan 1, 2009 | Wikidata |
| Geestdijk | Former name | Jan 1, 2005 | Wikidata |
A sanctions list's date is the earliest date the list shows the name, not when the ship took it. A name on a list is shown as a former name only where AIS shows the ship using another name after that date; otherwise it is listed as a name the list uses. AIS name changes are dated when Voydar saw them.
Source: Wikidata. Licence: CC0 1.0.
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 | 21,229 t | 6,734 t | 279 days | 214 kg |
| 2019 | 19,283 t | 6,101 t | 272 days | 211 kg |
| 2020 | 15,870 t | 4,979 t | 227 days | 211 kg |
| 2021 | 16,787 t | 5,236 t | 233 days | 214 kg |
| 2022 | 15,413 t | 4,810 t | 220 days | 220 kg |
| 2023 | 13,548 t | 4,249 t | 207 days | 219 kg |
| 2024 | 13,687 t | 4,389 t | 223 days | 206 kg |
| 2025 | 11,161 t | 3,577 t | 170 days | 203 kg |
Technical efficiency: EIV (36 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 |
|---|---|---|---|
| Gdynia PLGDY | Oct 3, 2026, 15:52 UTC | Oct 4, 2026, 06:46 UTC | 14 h 53 min |
| Moss NOMSS | Oct 1, 2026, 19:26 UTC | Oct 2, 2026, 00:49 UTC | 5 h 23 min |
| Sjursoja/Oslo NOSJU | Oct 1, 2026, 05:46 UTC | Oct 1, 2026, 17:05 UTC | 11 h 18 min |
| Rotterdam NLRTM | Sep 28, 2026, 11:43 UTC | Sep 29, 2026, 14:10 UTC | 26 h 28 min |
| Hull GBHUL | Sep 26, 2026, 14:37 UTC | Sep 27, 2026, 21:09 UTC | 30 h 32 min |
| Kristiansand NOKRS | Sep 24, 2026, 12:23 UTC | Sep 25, 2026, 01:01 UTC | 12 h 39 min |
| Sjursoja/Oslo NOSJU | Sep 23, 2026, 09:41 UTC | Sep 24, 2026, 00:47 UTC | 15 h 6 min |
| Sjursoja/Oslo NOSJU | Sep 17, 2026, 08:16 UTC | Sep 17, 2026, 20:07 UTC | 11 h 51 min |
| Salt End GBSED | Sep 13, 2026, 04:22 UTC | Sep 17, 2026, 08:16 UTC | 4 d 3 h |
| Rotterdam NLRTM | Sep 2, 2026, 01:00 UTC | Sep 5, 2026, 01:08 UTC | 3 d 0 h |
| Pernis NLPER | Sep 1, 2026, 23:03 UTC | Sep 2, 2026, 00:57 UTC | 1 h 54 min |
| Pernis NLPER | Sep 1, 2026, 21:03 UTC | Sep 1, 2026, 23:03 UTC | 2 h 0 min |
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 |
|---|---|---|---|---|
| Gdynia PLGDY | Arrival | Oct 3, 2026, 16:01 UTC | Bu garskie | Urząd Morski w Gdyni: ships in port, expected and departing (Gdynia, Gdańsk) |
Records published by the authority named on each row. Earliest record for this ship: October 3, 2026.
Source: Urząd Morski w Gdyni (www.umgdy.gov.pl); processed by Seadar (times converted to UTC, IMO checksum-validated). The retrieval date is shown with the data. Licence: Polish PSI reuse (ustawa o otwartych danych), conditions: cite source, date, processing.
Behaviour at sea Voydar-derived
Patterns Voydar derived from this ship's AIS broadcasts. They are inferences, not reports: each one shows how it was computed and how confident we are, and none of them says why a ship behaved this way.
| When | What we observed | Confidence |
|---|---|---|
| Sep 29, 2026, 13:05 UTC | Draught change Reported draught went from 6.4 m to 7 m while in port at Rotterdam. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Sep 27, 2026, 13:28 UTC | Draught change Reported draught went from 6.9 m to 6.3 m while in port at Hull. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
Source: AISstream.io global terrestrial AIS. AIS data: AISstream.io. Licence: none published.
Derived from AIS positions of feeds whose terms allow display on Voydar. Coverage is terrestrial: gaps are reported only where our receivers kept hearing other ships. Detections below medium confidence are not shown.
Frequently asked questions
- Where is Vohburg now?
- Vohburg (Container ship, Antigua & Barbuda flag) was last seen on AIS on Oct 4, 2026, 23:14 UTC, under way at 7.6 kn, in the Baltic Sea. Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. The crew-entered destination was LTKLJ (voyage report via AISstream.io global terrestrial AIS, received Oct 4, 2026, 23:00 UTC). This report does not confirm the ship’s current route.
- What kind of ship is Vohburg?
- Vohburg is a container ship sailing under the flag of Antigua & Barbuda, built in 2005 by Damen Shipyards Galați. The vessel is 140.6 m long with a beam of 22 m and has a gross tonnage of 7,852.
- Who is recorded as the owner or manager of Vohburg?
- Jorg Kopping Dritte Bereedereungsgesellschaft mbH & Co. MS. "Vohburg" KG is recorded as ISM manager for Vohburg (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 Vohburg?
- Voydar has no matched sanctions record displayed for Vohburg 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 Vohburg. 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/9287807Using 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.