Loireborg
General cargo ship · Netherlands · built 2008 · AIS Class A
In short
Loireborg (General cargo ship, Netherlands flag) was last seen on AIS on , under way at 9 kn, in the Baltic Sea. Its crew-entered AIS destination is NLTNZ (Terneuzen), with an ETA of Nov 23, 2026, 08:00 UTC; its reported draught is 6.3 m (voyage report via Digitraffic marine AIS, received Nov 17, 2026, 16:02 UTC). Registered owner: Scheepvaartonderneming Loireborg B.V. (source: ILT — Nederlands vlagregister (Netherlands flag register data)).
Current voyage: from Yxpila (departed Nov 17, 2026, 11:24 UTC) to NLTNZ (Terneuzen)
- Vessel type
- General cargo ship
- Flag
- Netherlands
- Year built
- 2008
- Gross tonnage
- 4,695
- Size (length × beam)
- 122 m × 14 m
- Registered owner
- Scheepvaartonderneming Loireborg B.V.

Last reported position: 63.6888° N, 21.4873° E · Baltic Sea · See on the map
Watch this ship
Get an email when Loireborg reaches Terneuzen, 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
Following Loireborg over the last 24 hours would have sent 1 message.
- LeftYxpila
Detected from AIS, as of Nov 17, 2026, 16:33 UTC.
Free forever. No card. Your first follow also starts a free 14-day Plus trial: alerts for Loireborg 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
- 63.6888° N, 21.4873° E
- Area
- Baltic Sea
- Status
- Under way using engineWhat do AIS statuses mean?
- Speed
- 9 kn
- Course
- 240°
- Heading
- 244°
- Compass: course over ground 240°, heading 244°
- Arrow: course. Hull: heading. As broadcast on AIS.
Locator map: Natural Earth (public domain)
Last 30 days: 6 port calls (Yxpila, Holtenau, Berendrecht, Antwerpen, Lillo, and Schiedam).
Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls below.
Pro shows Loireborg's track before the last 30 days. Voydar has recorded its port calls since September 29, 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.3 mone tick every 25 m
Beam 14.4 mPlan outline, to scale
- Name
- Loireborg
- IMO numberWhat is an IMO number?
- 9399404
- MMSIWhat is an MMSI?
- 245535000
- Call signWhat is a call sign?
- PHPT
- Flag
- Netherlands
- Gross tonnageGross tonnage vs deadweight
- 4,695
- Length overall
- 122.3 m
- Beam
- 14.4 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.
Ownership & management
Each line shows where the fact comes from. Links backed by an identifier point to the company page.
- Registered owner
- Scheepvaartonderneming Loireborg 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 YxpilaAIS-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 | |
| Arrived at YxpilaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left HoltenauAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at HoltenauAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left BerendrechtAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at BerendrechtAIS-detected | Voydar port-call detector (AIS geofence) | |
| Reported departure from DULUTH-SUPERIOR HARBOR, MN AND WIAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported arrival at DULUTH-SUPERIOR HARBOR, MN AND WIAuthority-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 |
|---|---|---|---|---|
| 2025 | 4,144 t | 1,295 t | 168 days | 108 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 sailed107.8 kg per nautical mile
- Lowest reportedHighest reported
49% 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 |
|---|---|---|---|
| Yxpila FIYXP | Nov 11, 2026, 15:31 UTC | Nov 17, 2026, 11:24 UTC | 5 d 19 h |
| Holtenau DEHTU | Nov 7, 2026, 16:48 UTC | Nov 7, 2026, 17:48 UTC | 1 h 0 min |
| Berendrecht BEBRT | Nov 5, 2026, 17:37 UTC | Nov 5, 2026, 19:53 UTC | 2 h 16 min |
| Antwerpen BEANR | Nov 2, 2026, 02:37 UTC | Nov 5, 2026, 17:16 UTC | 3 d 14 h |
| Lillo BELIL | Nov 2, 2026, 01:18 UTC | Nov 2, 2026, 02:29 UTC | 1 h 11 min |
| Schiedam NLSCI | Oct 30, 2026, 08:17 UTC | Nov 1, 2026, 07:13 UTC | 46 h 56 min |
| Antwerpen BEANR | Oct 10, 2026, 16:38 UTC | Oct 13, 2026, 10:27 UTC | 2 d 17 h |
| Lillo BELIL | Oct 10, 2026, 15:15 UTC | Oct 10, 2026, 16:28 UTC | 1 h 12 min |
| Hull GBHUL | Oct 8, 2026, 01:03 UTC | Oct 9, 2026, 22:26 UTC | 45 h 23 min |
| Brunsbuttel DEBRB | Oct 6, 2026, 11:14 UTC | Oct 6, 2026, 12:00 UTC | 46 min |
| Holtenau DEHTU | Oct 6, 2026, 02:06 UTC | Oct 6, 2026, 03:45 UTC | 1 h 39 min |
| Rautaruukki FIRTR | Sep 29, 2026, 19:18 UTC | Oct 2, 2026, 09:41 UTC | 2 d 14 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 |
|---|---|---|---|---|
| Karleby (Kokkola) FIKOK | Arrival | Nov 11, 2026, 15:45 UTC | Hopeakiven laituri 3 | Digitraffic Port Call API |
| DULUTH-SUPERIOR HARBOR, MN AND WI | Departure | Dec 12, 2008(date only) | — | USACE foreign traffic vessel entrances & clearances |
| DULUTH-SUPERIOR HARBOR, MN AND WI | Arrival | Dec 11, 2008(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Chicago USCHI | Departure | Dec 3, 2008(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Chicago USCHI | Arrival | Nov 26, 2008(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: November 26, 2008.
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 5, 2026, 08:28 UTC | Draught change Reported draught went from 4.1 m to 6.6 m while in port at Antwerpen. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | High (75%) |
| Oct 8, 2026, 06:49 UTC | Draught change Reported draught went from 6.7 m to 4.7 m while in port at Hull. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | High (75%) |
| Sep 30, 2026, 05:56 UTC | Draught change Reported draught went from 4.2 m to 6.9 m while in port at Rautaruukki. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | High (75%) |
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 Loireborg?
- Loireborg is a general cargo ship sailing under the flag of Netherlands, built in 2008 by Royal Niestern Sander. The vessel is 122.3 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 Loireborg?
- Scheepvaartonderneming Loireborg B.V. is recorded as Registered owner for Loireborg (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 Loireborg?
- Voydar has no matched sanctions record displayed for Loireborg 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 Loireborg. 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/9399404Cite this page
Loireborg. Voydar (voydar.com). https://www.voydar.com/vessel/9399404-loireborg. 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.