Pulpca
Ro-ro ship · Netherlands · built 2008 · AIS Class A
In short
Pulpca (Ro-ro ship, Netherlands flag) was last seen on AIS on , moored, in the port of Sunila. Its crew-entered AIS destination is FIKTK (Kotka), with an ETA of Nov 16, 2026, 05:00 UTC; its reported draught is 7.1 m (voyage report via Digitraffic marine AIS, received Nov 16, 2026, 14:55 UTC). It arrived there on Nov 15, 2026, 20:59 UTC. Registered owner: Rederij Pulpca (source: ILT — Nederlands vlagregister (Netherlands flag register data)).
- Vessel type
- Ro-ro ship
- Flag
- Netherlands
- Year built
- 2008
- Gross tonnage
- 28,289
- Size (length × beam)
- 205 m
- Registered owner
- Rederij Pulpca
Last reported position: 60.484° N, 26.9483° E · Baltic Sea · See on the map
Shipping a car on this vessel?
Follow Pulpca and Voydar's daily email tells you when it has reached Kotka, and when it leaves or changes its destination.
What you would have been told
Following Pulpca over the last 24 hours would have sent 1 message.
- ArrivedSunila
Detected from AIS, as of Nov 16, 2026, 14:58 UTC.
Free forever. No card. Your first follow also starts a free 14-day Plus trial: alerts for Pulpca 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.484° N, 26.9483° E
- Area
- Baltic Sea
- Status
- MooredWhat do AIS statuses mean?
- Speed
- 0 kn
- Course
- 281°
- Heading
- 336°
- Compass: course over ground 281°, heading 336°
- Arrow: course. Hull: heading. As broadcast on AIS.
Locator map: Natural Earth (public domain)
Last 30 days: at least 12 port calls (Sunila, Hango (Hanko), Zeebrugge, Kallo, Holtenau, and Rauma (Raumo)).
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 205 mone tick every 25 m
- Name
- Pulpca
- IMO numberWhat is an IMO number?
- 9345386
- MMSIWhat is an MMSI?
- 245097000
- Call signWhat is a call sign?
- PHMT
- Flag
- Netherlands
- Gross tonnageGross tonnage vs deadweight
- 28,289
- Length overall
- 205 m
- Beam (AIS-reported)
- Broadcast by the ship over AIS, not a register entry. Received via Digitraffic marine AIS on November 16, 2026.26 m
- Year built
- 2008
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.
AIS-reported: the size the ship itself broadcasts over AIS, in whole metres, as entered on board. It is not a register entry. Received via Digitraffic marine AIS on November 16, 2026.
Ownership & management
Each line shows where the fact comes from. Links backed by an identifier point to the company page.
- Registered owner
- Rederij Pulpca(not linked to a company record)Source: ILT — Nederlands vlagregister (Netherlands flag register data) · reported · high confidence · retrieved Nov 12, 2026
- ISM manager
- Source: EU MRV (THETIS-MRV) emissions · reporting years 2024–2025 · reported · high confidence · retrieved Nov 16, 2026
- Builder
- Source: Wikidata · reported · high confidence · retrieved Nov 15, 2026STOCZNIA SZCZECINSKA(not linked to a company record)Source: ILT — Nederlands vlagregister (Netherlands flag register data) · reported · high confidence · retrieved Nov 12, 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 |
|---|---|---|
| Reported arrival at KotkaAuthority-reported | Digitraffic Port Call API | |
| Arrived at SunilaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left Hango (Hanko)AIS-detected | Voydar port-call detector (AIS geofence) | |
| Reported departure from Hango (Hanko)Authority-reported | Digitraffic Port Call API | |
| Reported arrival at Hango (Hanko)Authority-reported | Digitraffic Port Call API | |
| Arrived at Hango (Hanko)AIS-detected | Voydar port-call detector (AIS geofence) | |
| Left ZeebruggeAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at ZeebruggeAIS-detected | Voydar port-call detector (AIS geofence) | |
| Reported departure from Hango (Hanko)Authority-reported | Digitraffic Port Call API | |
| Reported arrival at Hango (Hanko)Authority-reported | Digitraffic Port Call API | |
| Port State Control inspection at Baltimore, Maryland | USCG PSIX / CGMIX inspections | |
| Inspection at Baltimore, Maryland | USCG PSIX / CGMIX inspections | |
| Port State Control inspection at Baltimore, Maryland | USCG PSIX / CGMIX inspections | |
| Inspection at Baltimore, Maryland | USCG PSIX / CGMIX inspections |
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.
Safety & inspections
| Date | Type | Port | Findings |
|---|---|---|---|
| Aug 17, 2023 | Vessel InspectionPSC | Baltimore, Maryland | clean |
| Aug 16, 2023 | Vessel Inspection | Baltimore, Maryland | clean |
| Jun 22, 2023 | Vessel InspectionPSC | Baltimore, Maryland | clean |
| Jun 21, 2023 | Vessel Inspection | Baltimore, Maryland | clean |
Source: U.S. Coast Guard Port State Information Exchange (PSIX) — public domain. Covers inspections recorded in U.S. waters. Free on Voydar; the incumbents charge for this.
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 | 48,086 t | 15,433 t | 227 days | 553 kg |
| 2019 | 49,791 t | 15,977 t | 237 days | 544 kg |
| 2020 | 47,853 t | 15,359 t | 228 days | 534 kg |
| 2021 | 46,687 t | 14,984 t | 226 days | 553 kg |
| 2022 | 47,963 t | 15,394 t | 236 days | 530 kg |
| 2023 | 20,729 t | 6,647 t | 148 days | 433 kg |
| 2024 | 41,415 t | 13,290 t | 222 days | 512 kg |
| 2025 | 46,957 t | 15,066 t | 240 days | 529 kg |
Technical efficiency: EEXI (12.12 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 2025 sits among the ships EU MRV lists as “Container/ro-ro cargo ship”. Lower is less CO₂.
- CO₂ per nautical mile sailed528.8 kg per nautical mile
- Lowest reportedHighest reported
94% of the 60 ships in this group reported a lower figure.
Group: lower quartile 380.1 · median 419.6 · upper quartile 482.8
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 |
|---|---|---|---|
| Sunila FISUL | Nov 15, 2026, 20:59 UTC | in port | — |
| Hango (Hanko) FIHKO | Nov 15, 2026, 08:08 UTC | Nov 15, 2026, 13:27 UTC | 5 h 19 min |
| Zeebrugge BEZEE | Nov 11, 2026, 18:15 UTC | Nov 12, 2026, 11:32 UTC | 17 h 18 min |
| Kallo BEKOU | Nov 10, 2026, 21:26 UTC | Nov 11, 2026, 14:23 UTC | 16 h 58 min |
| Hango (Hanko) FIHKO | Nov 7, 2026, 04:18 UTC | Nov 7, 2026, 13:35 UTC | 9 h 17 min |
| Sunila FISUL | Nov 4, 2026, 17:47 UTC | Nov 6, 2026, 18:06 UTC | 2 d 0 h |
| Hango (Hanko) FIHKO | Nov 4, 2026, 04:15 UTC | Nov 4, 2026, 09:28 UTC | 5 h 14 min |
| Holtenau DEHTU | Nov 2, 2026, 05:26 UTC | Nov 2, 2026, 06:24 UTC | 58 min |
| Kallo BEKOU | Oct 31, 2026, 13:18 UTC | Nov 1, 2026, 00:16 UTC | 10 h 58 min |
| Rauma (Raumo) FIRAU | Oct 28, 2026, 03:50 UTC | Oct 28, 2026, 20:38 UTC | 16 h 48 min |
| Hango (Hanko) FIHKO | Oct 27, 2026, 03:30 UTC | Oct 27, 2026, 16:21 UTC | 12 h 51 min |
| Kallo BEKOU | Oct 23, 2026, 08:36 UTC | Oct 24, 2026, 07:24 UTC | 22 h 49 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 |
|---|---|---|---|---|
| Kotka FIKTK | Arrival | Nov 15, 2026, 21:30 UTC | HIEH5 | Digitraffic Port Call API |
| Hango (Hanko) FIHKO | Arrival | Nov 15, 2026, 08:20 UTC | Roro 1 | Digitraffic Port Call API |
| Hango (Hanko) FIHKO | Arrival | Nov 7, 2026, 04:36 UTC | Roro 1 | Digitraffic Port Call API |
| Kotka FIKTK | Arrival | Nov 4, 2026, 18:20 UTC | HIEH3 | Digitraffic Port Call API |
| Hango (Hanko) FIHKO | Arrival | Nov 4, 2026, 04:30 UTC | Roro 2 | Digitraffic Port Call API |
| Rauma (Raumo) FIRAU | Arrival | Oct 28, 2026, 04:15 UTC | Ro-Ro 4 | Digitraffic Port Call API |
| Hango (Hanko) FIHKO | Arrival | Oct 27, 2026, 03:58 UTC | Roro 1 | Digitraffic Port Call API |
| Hango (Hanko) FIHKO | Arrival | Oct 17, 2026, 04:04 UTC | Roro 1 | Digitraffic Port Call API |
| Kotka FIKTK | Arrival | Oct 14, 2026, 17:25 UTC | HIEH5 | Digitraffic Port Call API |
| Hango (Hanko) FIHKO | Arrival | Oct 14, 2026, 04:10 UTC | Roro 2 | Digitraffic Port Call API |
Records published by the authority named on each row. Earliest record for this ship: October 14, 2026.
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 11, 2026, 12:52 UTC | Draught change Reported draught went from 8.1 m to 7.1 m while in port at Kallo. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Nov 6, 2026, 17:27 UTC | Draught change Reported draught went from 7 m to 7.7 m while in port at Sunila. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Oct 23, 2026, 13:12 UTC | Draught change Reported draught went from 6.9 m to 7.4 m while in port at Kallo. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Oct 20, 2026, 04:09 UTC | Draught change Reported draught went from 8.1 m to 7.3 m while in port at Kallo. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Oct 14, 2026, 17:43 UTC | Draught change Reported draught went from 7.1 m to 7.9 m while in port at Sunila. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Oct 11, 2026, 04:47 UTC | Draught change Reported draught went from 7.5 m to 7 m while in port at Kallo. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Sep 25, 2026, 16:51 UTC | Draught change Reported draught went from 7.1 m to 8.1 m while in port at Sunila. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
Source: AISstream.io global terrestrial AIS. AIS data: AISstream.io. Licence: none published.
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 Pulpca?
- Pulpca is a ro-ro ship sailing under the flag of Netherlands, built in 2008 by Szczecin Shipyard. The vessel is 205 m long and has a gross tonnage of 28,289.
- Who is recorded as the owner or manager of Pulpca?
- Rederij Pulpca is recorded as Registered owner for Pulpca (source: ILT — Nederlands vlagregister (Netherlands flag register data)). This source record does not independently confirm today’s ownership or management.
- What sanctions and inspection records does Voydar hold for Pulpca?
- Voydar has no matched sanctions record displayed for Pulpca 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. Pulpca has 4 recorded Port State Control inspections. Detention and deficiency detail is not recorded for these inspections.
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 Ro-ro ships
Other ro-ro ships with full Voydar profiles. A different set each day. All ro-ro ships
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/9345386Cite this page
Pulpca. Voydar (voydar.com). https://www.voydar.com/vessel/9345386-pulpca. 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.