Feed Trondheim
General cargo ship · Norway · built 2002 · AIS Class A
In short
Feed Trondheim (General cargo ship, Norway flag) was last seen on AIS on , under way at 7.4 kn, in the North Sea. Its crew-entered AIS destination is WISMAR, with an ETA of Nov 19, 2026, 13:00 UTC; its reported draught is 5.7 m (voyage report via BarentsWatch AIS API, received Nov 17, 2026, 18:57 UTC). ISM manager: Ulvan Personal AS (source: EU MRV (THETIS-MRV) emissions, reporting year 2025).
Current voyage: from Dale (departed Nov 16, 2026, 05:49 UTC) to WISMAR
- Vessel type
- General cargo ship
- Flag
- Norway
- Year built
- 2002
- Gross tonnage
- 3,925
- Size (length × beam)
- 100 m × 16 m
- ISM manager
- Ulvan Personal AS

Last reported position: 57.9233° N, 7.2535° E · North Sea · See on the map
Watch this ship
Get an email when Feed Trondheim arrives or 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, 19:06 UTC.
Free forever. No card. Your first follow also starts a free 14-day Plus trial: alerts for Feed Trondheim 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
- 57.9233° N, 7.2535° E
- Area
- North Sea
- Status
- Under way using engineWhat do AIS statuses mean?
- Speed
- 7.4 kn
- Course
- 98°
- Heading
- 97°
- Compass: course over ground 98°, heading 97°
- Arrow: course. Hull: heading. As broadcast on AIS.
Locator map: Natural Earth (public domain)
Last 30 days: at least 12 port calls (Dale, Forde, Steinkjer, Trondheim, Vaksdal, Lillo, Delfzijl, Holtenau, Wismar, Eikefjord, and Stavanger).
Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls below.
Data delivered by BarentsWatch
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 99.9 mone tick every 10 m
Beam 16.2 mPlan outline, to scale
- Name
- Feed Trondheim
- IMO numberWhat is an IMO number?
- 9226798
- MMSIWhat is an MMSI?
- 257350220
- Call signWhat is a call sign?
- LADP9
- Flag
- Norway
- Gross tonnageGross tonnage vs deadweight
- 3,925
- Deadweight (DWT)
- Source: Wikidata, record Q84253221. Added to Voydar on October 23, 2026. Licence: CC0 1.0.4,633 t
- Length overall
- 99.9 m
- Beam
- 16.2 m
- Year built
- 2002
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 year 2025 · reported · high confidence · retrieved Nov 16, 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 DaleAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at DaleAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left FordeAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at FordeAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left SteinkjerAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at SteinkjerAIS-detected | Voydar port-call detector (AIS geofence) |
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 | 3,464 t | 1,080 t | 171 days | 94 kg |
Technical efficiency: EEXI (12.47 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 sailed94.2 kg per nautical mile
- Lowest reportedHighest reported
42% 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 |
|---|---|---|---|
| Dale NODSF | Nov 15, 2026, 19:44 UTC | Nov 16, 2026, 05:49 UTC | 10 h 5 min |
| Forde NOFDE | Nov 15, 2026, 07:59 UTC | Nov 15, 2026, 15:09 UTC | 7 h 10 min |
| Steinkjer NOSTE | Nov 11, 2026, 18:44 UTC | Nov 13, 2026, 11:08 UTC | 40 h 24 min |
| Trondheim NOTRD | Nov 11, 2026, 07:30 UTC | Nov 11, 2026, 14:14 UTC | 6 h 44 min |
| Vaksdal NOVAK | Nov 9, 2026, 08:18 UTC | Nov 10, 2026, 00:38 UTC | 16 h 20 min |
| Lillo BELIL | Nov 4, 2026, 20:34 UTC | Nov 6, 2026, 12:43 UTC | 40 h 9 min |
| Delfzijl NLDZL | Nov 2, 2026, 11:33 UTC | Nov 3, 2026, 14:32 UTC | 26 h 59 min |
| Holtenau DEHTU | Nov 1, 2026, 09:12 UTC | Nov 1, 2026, 10:52 UTC | 1 h 40 min |
| Wismar DEWIS | Oct 30, 2026, 14:37 UTC | Nov 1, 2026, 00:06 UTC | 33 h 30 min |
| Dale NODSF | Oct 25, 2026, 20:12 UTC | Oct 26, 2026, 14:54 UTC | 18 h 42 min |
| Eikefjord NOEIK | Oct 25, 2026, 09:25 UTC | Oct 25, 2026, 16:09 UTC | 6 h 43 min |
| Stavanger NOSVG | Oct 21, 2026, 18:15 UTC | Oct 23, 2026, 19:18 UTC | 2 d 1 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.
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 15, 2026, 14:12 UTC | Draught change Reported draught went from 4.4 m to 5.4 m while in port at Forde. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Nov 9, 2026, 22:52 UTC | Draught change Reported draught went from 5.6 m to 5 m while in port at Vaksdal. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Nov 3, 2026, 07:15 UTC | Draught change Reported draught went from 4.4 m to 5.6 m while in port at Delfzijl. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Oct 31, 2026, 23:39 UTC | Draught change Reported draught went from 5.6 m to 4.4 m while in port at Wismar. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Oct 26, 2026, 13:45 UTC | Draught change Reported draught went from 4.8 m to 5.4 m while in port at Dale. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Oct 23, 2026, 06:59 UTC | Draught change Reported draught went from 5.8 m to 4.4 m while in port at Stavanger. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Oct 19, 2026, 20:27 UTC | Draught change Reported draught went from 4.4 m to 5.4 m while in port at Sarpsborg. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Oct 8, 2026, 00:46 UTC | Draught change Reported draught went from 5.1 m to 4.4 m while in port at Wismar. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Oct 7, 2026, 17:04 UTC | Draught change Reported draught went from 5.7 m to 5.1 m while in port at Wismar. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Oct 3, 2026, 03:33 UTC | Draught change Reported draught went from 4.4 m to 5.4 m while in port at Dale. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Sep 30, 2026, 21:39 UTC | Draught change Reported draught went from 5.6 m to 4.4 m after leaving Aalborg. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (55%) |
| Sep 28, 2026, 16:29 UTC | Draught change Reported draught went from 4.4 m to 5.6 m while in port at Rekefjord. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
Source: BarentsWatch AIS API. Data delivered by BarentsWatch (NLOD 2.0; data owner: Kystverket). Licence: NLOD 2.0 (BarentsWatch API terms 2023-11-02; Live/Historic AIS OpenAPI licence NLOD).
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
- What kind of ship is Feed Trondheim?
- Feed Trondheim is a general cargo ship sailing under the flag of Norway, built in 2002. The vessel is 99.9 m long with a beam of 16.2 m and has a gross tonnage of 3,925.
- Who is recorded as the owner or manager of Feed Trondheim?
- Ulvan Personal AS is recorded as ISM manager for Feed Trondheim (source: EU MRV (THETIS-MRV) emissions; reporting year 2025). This source record does not independently confirm today’s ownership or management.
- What sanctions and inspection records does Voydar hold for Feed Trondheim?
- Voydar has no matched sanctions record displayed for Feed Trondheim 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 Feed Trondheim. 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/9226798Cite this page
Feed Trondheim. Voydar (voydar.com). https://www.voydar.com/vessel/9226798-feed-trondheim. 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.