Lingeborg
General cargo ship · Netherlands · built 2008 · AIS Class A
In short
Lingeborg (General cargo ship, Netherlands flag) was last seen on AIS on , under way at 9.4 kn, in the Baltic Sea. Its crew-entered AIS destination is FIKOK (Karleby (Kokkola)), with an ETA of Nov 18, 2026, 22:00 UTC; its reported draught is 6.5 m (voyage report via Digitraffic marine AIS, received Nov 17, 2026, 16:51 UTC). Registered owner: Scheepvaartonderneming Lingeborg B.V. (source: ILT — Nederlands vlagregister (Netherlands flag register data)). It can carry up to 304 passengers (source: Wikidata).
Current voyage: from Holtenau (departed Nov 15, 2026, 10:08 UTC) to FIKOK (Karleby (Kokkola))
- Vessel type
- General cargo ship
- Flag
- Netherlands
- Year built
- 2008
- Gross tonnage
- 4,695
- Size (length × beam)
- 122 m × 14 m
- Registered owner
- Scheepvaartonderneming Lingeborg B.V.
Last reported position: 60.3982° N, 19.0406° E · Baltic Sea · See on the map
Watch this ship
Get an email when Lingeborg reaches Karleby (Kokkola), 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 17, 2026, 17:11 UTC.
Free forever. No card. Your first follow also starts a free 14-day Plus trial: alerts for Lingeborg 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.3982° N, 19.0406° E
- Area
- Baltic Sea
- Status
- Under way using engineWhat do AIS statuses mean?
- Speed
- 9.4 kn
- Course
- 8°
- Heading
- 4°
- Compass: course over ground 8°, heading 4°
- Arrow: course. Hull: heading. As broadcast on AIS.
Locator map: Natural Earth (public domain)
Last 30 days: 10 port calls (Holtenau, Kiel Canal, Nieuwdorp, IJmuiden/Velsen, Amsterdam, Brunsbuttel, Warnemunde, and Yxpila).
Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls below.
Pro shows Lingeborg's track before the last 30 days. Voydar has recorded its port calls since October 14, 2026.Free forever. No card. Follow a ship and Plus is free for 14 days.
Try the live demo, no sign-upIdentity & particulars
Length overall 122.1 mone tick every 25 m
Beam 14.4 mPlan outline, to scale
- Name
- Lingeborg
- IMO numberWhat is an IMO number?
- 9399399
- MMSIWhat is an MMSI?
- 245046000
- Call signWhat is a call sign?
- PHMK
- Flag
- Netherlands
- Gross tonnageGross tonnage vs deadweight
- 4,695
- Deadweight (DWT)
- Source: Wikidata, record Q85980889. Added to Voydar on October 23, 2026. Licence: CC0 1.0.7,350 t
- Length overall
- 122.1 m
- Beam
- 14.4 m
- Year built
- 2008
- Passengers (maximum)
- Source: Wikidata, record Q85980889. Added to Voydar on October 23, 2026. Licence: CC0 1.0.304
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.
- Registered owner
- Scheepvaartonderneming Lingeborg B.V.(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 year 2025 · reported · high confidence · retrieved Nov 16, 2026
- Builder
- Source: Wikidata · reported · high confidence · retrieved Nov 15, 2026NIESTERN SANDER B.V(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 |
|---|---|---|
| Left HoltenauAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at HoltenauAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left Kiel CanalAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at Kiel CanalAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left NieuwdorpAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at NieuwdorpAIS-detected | Voydar port-call detector (AIS geofence) | |
| Reported departure from Karleby (Kokkola)Authority-reported | Digitraffic Port Call API | |
| Reported arrival at Karleby (Kokkola)Authority-reported | Digitraffic Port Call API | |
| Reported departure from Sibbo (Sipoo)Authority-reported | Digitraffic Port Call API | |
| Reported arrival at Sibbo (Sipoo)Authority-reported | Digitraffic Port Call API | |
| Reported departure from Tolkis (Tolkkinen)Authority-reported | Digitraffic Port Call API | |
| Reported arrival at Tolkis (Tolkkinen)Authority-reported | Digitraffic Port Call API |
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 |
|---|---|---|---|---|
| 2025 | 4,874 t | 1,522 t | 200 days | 117 kg |
Technical efficiency: EEXI (11.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 2025 sits among the ships EU MRV lists as “General cargo ship”. Lower is less CO₂.
- CO₂ per nautical mile sailed116.8 kg per nautical mile
- Lowest reportedHighest reported
53% of the 2,956 ships in this group reported a lower figure.
Group: lower quartile 74.8 · median 110.6 · upper quartile 185.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 |
|---|---|---|---|
| Holtenau DEHTU | Nov 15, 2026, 08:51 UTC | Nov 15, 2026, 10:08 UTC | 1 h 16 min |
| Kiel Canal DECKL | Nov 14, 2026, 22:46 UTC | Nov 15, 2026, 00:34 UTC | 1 h 48 min |
| Nieuwdorp NLNIU | Nov 10, 2026, 18:25 UTC | Nov 13, 2026, 17:13 UTC | 2 d 22 h |
| IJmuiden/Velsen NLIJM | Nov 10, 2026, 07:15 UTC | Nov 10, 2026, 08:08 UTC | 53 min |
| Amsterdam NLAMS | Nov 4, 2026, 13:57 UTC | Nov 10, 2026, 06:18 UTC | 5 d 16 h |
| IJmuiden/Velsen NLIJM | Nov 4, 2026, 12:17 UTC | Nov 4, 2026, 13:32 UTC | 1 h 15 min |
| Brunsbuttel DEBRB | Nov 3, 2026, 05:22 UTC | Nov 3, 2026, 17:58 UTC | 12 h 36 min |
| Holtenau DEHTU | Nov 2, 2026, 20:59 UTC | Nov 2, 2026, 22:04 UTC | 1 h 5 min |
| Warnemunde DEWAR | Nov 1, 2026, 15:18 UTC | Nov 2, 2026, 13:35 UTC | 22 h 17 min |
| Yxpila FIYXP | Oct 23, 2026, 19:16 UTC | Oct 29, 2026, 10:23 UTC | 5 d 15 h |
| Kilpilahti (Skoldvik) FISKV | Oct 17, 2026, 13:48 UTC | Oct 19, 2026, 11:12 UTC | 45 h 24 min |
| Holtenau DEHTU | Oct 14, 2026, 04:32 UTC | Oct 14, 2026, 06:21 UTC | 1 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 |
|---|---|---|---|---|
| Karleby (Kokkola) FIKOK | Arrival | Oct 23, 2026, 19:40 UTC | Syvälaituri 8 | Digitraffic Port Call API |
| Sibbo (Sipoo) FISIP | Arrival | Oct 19, 2026, 13:00 UTC | Ei Tiedossa | Digitraffic Port Call API |
| Tolkis (Tolkkinen) FITOK | Arrival | Oct 17, 2026, 14:15 UTC | Pohjoislaituri | Digitraffic Port Call API |
Records published by the authority named on each row. Earliest record for this ship: October 17, 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, 11:50 UTC | Draught change Reported draught went from 4 m to 6.5 m while in port at Nieuwdorp. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | High (75%) |
| Nov 6, 2026, 15:55 UTC | Draught change Reported draught went from 5 m to 4.2 m while in port at Amsterdam. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Oct 27, 2026, 06:46 UTC | Draught change Reported draught went from 4 m to 5.5 m while in port at Yxpila. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Oct 19, 2026, 10:06 UTC | Draught change Reported draught went from 6.8 m to 6 m while in port at Kilpilahti (Skoldvik). 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.
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 Lingeborg?
- Lingeborg is a general cargo ship sailing under the flag of Netherlands, built in 2008 by Royal Niestern Sander. The vessel is 122.1 m long with a beam of 14.4 m and has a gross tonnage of 4,695.
- Who is recorded as the owner or manager of Lingeborg?
- Scheepvaartonderneming Lingeborg B.V. is recorded as Registered owner for Lingeborg (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 Lingeborg?
- Voydar has no matched sanctions record displayed for Lingeborg 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 Lingeborg. 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
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/9399399Cite this page
Lingeborg. Voydar (voydar.com). https://www.voydar.com/vessel/9399399-lingeborg. Retrieved November 17, 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 includes use in your own product. Growth and Scale add volume, and each includes one Pro membership.