FORPOST appears on the UK Sanctions List, the New Zealand Russia Sanctions Register, the EU list of designated vessels and the Canadian autonomous sanctions list under the Russia, Russia Sanctions Act 2022 (New Zealand), and Russia (Reg. 833/2014 Annex XLII) programs. Verify at GOV.UK.
Every vessel on:UK Sanctions ListNew Zealand Russia Sanctions RegisterEU list of designated vesselsCanadian autonomous sanctions list
FORPOST
Oil tanker · Russia · built 2006 · AIS Class A
In short
FORPOST (Oil tanker, Russia flag) was last seen on AIS on , at anchor, in the Baltic Sea. Its crew-entered AIS destination is RU LED (Saint Petersburg (ex Leningrad)); its reported draught is 14.9 m (voyage report via Digitraffic marine AIS, received Nov 16, 2026, 14:28 UTC). It appears on 4 sanctions lists (details below).
Current voyage: from Primorsk (Koivisto) (departed Nov 11, 2026, 17:03 UTC) to RU LED (Saint Petersburg (ex Leningrad))
- Vessel type
- Oil tanker
- Flag
- Russia
- Year built
- 2006
- Gross tonnage
- 81,324
- Size (length × beam)
- 274 m × 48 m
- Registered owner
- —
Last reported position: 60.0338° N, 28.4719° E · Baltic Sea · See on the map
Watch this ship
Get an email when FORPOST reaches Saint Petersburg (ex Leningrad), and when it leaves port, changes destination, name, flag or owner, or is sanctioned, detained or named in an official release.
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 16, 2026, 14:37 UTC.
Free forever. No card. Your first follow also starts a free 14-day Plus trial: alerts for FORPOST 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: Voydar for iPhone
Last reported position
received- Position
- 60.0338° N, 28.4719° E
- Area
- Baltic Sea
- Status
- At anchorWhat do AIS statuses mean?
- Speed
- 0 kn
- Course
- 150°
- Heading
- 189°
- Compass: course over ground 150°, heading 189°
- Arrow: course. Hull: heading. As broadcast on AIS.
Locator map: Natural Earth (public domain)
Last 30 days: 2 port calls (Primorsk (Koivisto)).
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. Follow a ship and Plus is free for 14 days.
Try the live demo, no sign-upIdentity & particulars
Length overall 274.2 mone tick every 50 m
Beam 48 mPlan outline, to scale
- Name
- FORPOST
- IMO numberWhat is an IMO number?
- 9321691
- MMSIWhat is an MMSI?
- 273120040
- Call signWhat is a call sign?
- UAHH5
- Flag
- Russia
- Gross tonnageGross tonnage vs deadweight
- 81,324
- Deadweight (DWT)
- Source: Wikidata, record Q105764453. Added to Voydar on October 24, 2026. Licence: CC0 1.0.158,889 t
- Length overall
- 274.2 m
- Beam
- 48 m
- Year built
- 2006
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.
- 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 Primorsk (Koivisto)AIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at Primorsk (Koivisto)AIS-detected | Voydar port-call detector (AIS geofence) | |
| Left Primorsk (Koivisto)AIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at Primorsk (Koivisto)AIS-detected | Voydar port-call detector (AIS geofence) | |
| Listed on the New Zealand Russia Sanctions Register (MFAT) (Russia Sanctions Act 2022 (New Zealand)) | New Zealand Russia Sanctions Register (ships) | |
| Former name: Lahar | EU designated vessels (Reg. 833/2014 Annex XLII; Reg. 2017/1509 Annex XIV) | |
| Listed on the EU designated vessels (Official Journal) (Russia (Reg. 833/2014 Annex XLII)) | EU designated vessels (Reg. 833/2014 Annex XLII; Reg. 2017/1509 Annex XIV) | |
| Listed on the Canadian autonomous sanctions list (Russia) | Canada Consolidated Autonomous Sanctions List (SEMA/JVCFOA) | |
| Former name: SAI BABA | UK Sanctions List (FCDO) | |
| Listed on the UK Sanctions List (Russia) | UK Sanctions List (FCDO) | |
| Reported departure from Long BeachAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported arrival at Long BeachAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported departure from Corpus ChristiAuthority-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.
Former and other names
Names attested for this ship other than its current name.
| Name | Evidence | Date | Source |
|---|---|---|---|
| Lahar | Former name | May 21, 2025 | EU designated vessels (Reg. 833/2014 Annex XLII; Reg. 2017/1509 Annex XIV) |
| SAI BABA | Former name | Oct 17, 2024 | UK Sanctions List (FCDO) |
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: Council Regulation (EU) No 833/2014, Annex XLII, and Council Regulation (EU) 2017/1509, Annex XIV (Official Journal of the European Union); list compiled by the Danish Maritime Authority. Licence: EU legislation (Official Journal): reuse "for commercial or non-commercial purposes" (Decision 2011/833/EU); facts.
Source: UK Sanctions List (FCDO). Contains public sector information licensed under the Open Government Licence v3.0. Licence: OGL v3.
Sanctions listings
Every listing of this ship on the sanctions lists Voydar tracks, current and past.
| List | Programme | Listed as | Listed | Status |
|---|---|---|---|---|
| New Zealand Russia Sanctions Register (MFAT) | Russia Sanctions Act 2022 (New Zealand) | Barq | Feb 20, 2026 | In force |
| EU designated vessels (Official Journal) | Russia (Reg. 833/2014 Annex XLII) | Lahar | May 21, 2025 | In force |
| Canadian autonomous sanctions list | Russia | Sai Baba | Feb 21, 2025 | In force |
| UK Sanctions List | Russia | SAI BABA | Oct 17, 2024 | In force |
Source: New Zealand Russia Sanctions Register (ships). © Crown copyright, New Zealand Ministry of Foreign Affairs and Trade, CC BY 4.0. Licence: CC-BY-4.0 (Crown copyright).
Source: Council Regulation (EU) No 833/2014, Annex XLII, and Council Regulation (EU) 2017/1509, Annex XIV (Official Journal of the European Union); list compiled by the Danish Maritime Authority. Licence: EU legislation (Official Journal): reuse "for commercial or non-commercial purposes" (Decision 2011/833/EU); facts.
Source: Canada Consolidated Autonomous Sanctions List (SEMA/JVCFOA). Contains information licensed under the Open Government Licence – Canada. Licence: Open Government Licence – Canada.
Source: UK Sanctions List (FCDO). Contains public sector information licensed under the Open Government Licence v3.0. Licence: OGL v3.
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 | 2,327 t | 738 t | 18 days | 508 kg |
| 2019 | 8,033 t | 2,560 t | 58 days | 483 kg |
Technical efficiency: EIV (3.3 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 2019 sits among the ships EU MRV lists as “Oil tanker”. Lower is less CO₂.
- CO₂ per tonne of cargo carried one nautical mile4.04 g per tonne-nautical mile
- Lowest reportedHighest reported
7% of the 1,943 ships in this group reported a lower figure.
Group: lower quartile 6.28 · median 8.86 · upper quartile 14.03
- CO₂ per nautical mile sailed483.4 kg per nautical mile
- Lowest reportedHighest reported
64% of the 1,961 ships in this group reported a lower figure.
Group: lower quartile 335 · median 432.5 · upper quartile 532.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 |
|---|---|---|---|
| Primorsk (Koivisto) RUPRI | Nov 11, 2026, 13:59 UTC | Nov 11, 2026, 17:03 UTC | 3 h 3 min |
| Primorsk (Koivisto) RUPRI | Nov 10, 2026, 08:57 UTC | Nov 10, 2026, 12:28 UTC | 3 h 31 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 |
|---|---|---|---|---|
| Long Beach USLGB | Departure | May 2, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Long Beach USLGB | Arrival | Apr 23, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Corpus Christi USCRP | Departure | Apr 29, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Corpus Christi USCRP | Arrival | Apr 29, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Beaumont USBPT | Departure | Apr 26, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Beaumont USBPT | Arrival | Apr 25, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Departure | Apr 23, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Arrival | Apr 22, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Corpus Christi USCRP | Departure | Jan 5, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Corpus Christi USCRP | Arrival | Jan 5, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Corpus Christi USCRP | Departure | Nov 19, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Corpus Christi USCRP | Arrival | Nov 17, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: March 15, 2007.
Source: US Army Corps of Engineers, Waterborne Commerce Statistics Center (US CBP entrance/clearance records). Licence: US Government work — public domain.
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 |
|---|---|---|
| Nov 12, 2026, 04:21 UTC | Draught change Reported draught went from 9 m to 14.9 m after leaving Primorsk (Koivisto). Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
Source: Fintraffic / digitraffic.fi, license CC 4.0 BY. Licence: CC BY 4.0.
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
- What kind of ship is FORPOST?
- FORPOST is an oil tanker sailing under the flag of Russia, built in 2006 by Samsung Heavy Industries. The vessel is 274.2 m long with a beam of 48 m and has a gross tonnage of 81,324.
- What sanctions and inspection records does Voydar hold for FORPOST?
- FORPOST appears on the UK Sanctions List, the New Zealand Russia Sanctions Register, the EU list of designated vessels and the Canadian autonomous sanctions list under the Russia, Russia Sanctions Act 2022 (New Zealand), and Russia (Reg. 833/2014 Annex XLII) programs. No matched inspection records are displayed for FORPOST. Missing records do not establish whether the ship has been detained.
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 Oil tankers
Other oil tankers with full Voydar profiles. A different set each day. All oil tankers
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/9321691Cite this page
FORPOST. Voydar (voydar.com). https://www.voydar.com/vessel/9321691-forpost. Retrieved November 16, 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 adds internal business use; API plans add building the data into your own products.