Damgracht
General cargo ship · Netherlands · built 2009 · AIS Class A
In short
Damgracht (General cargo ship, Netherlands flag) was last seen on AIS on , under way at 16.3 kn, in the Indian Ocean. Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. Its crew-entered AIS destination is SGSIN (Singapore), with an ETA of Nov 25, 2026, 03:00 UTC; its reported draught is 6.3 m (voyage report via AISstream.io global terrestrial AIS, received Nov 18, 2026, 07:36 UTC). Registered owner: Rederij Damgracht (source: ILT — Nederlands vlagregister (Netherlands flag register data)). It can carry up to 1,040 passengers (source: Wikidata).
Current voyage: from Port Hueneme (departed Oct 8, 2026, 00:53 UTC) to SGSIN (Singapore)
- Vessel type
- General cargo ship
- Flag
- Netherlands
- Year built
- 2009
- Gross tonnage
- 13,558
- Size (length × beam)
- 157 m × 23 m
- Registered owner
- Rederij Damgracht
Last reported position: 32.8575° S, 115.265° E · Indian Ocean · See on the map
Watch this ship
Damgracht has not been received for a while. Follow it for an email update when Voydar receives a new position, and for arrival and departure alerts.
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 20, 2026, 08:48 UTC.
Free forever. No card. Your first follow also starts a free 14-day Plus trial: alerts for Damgracht 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: the Voydar app
Last reported position
received- Position
- 32.8575° S, 115.265° E
- Area
- Indian Ocean
- Status
- Under way using engineWhat do AIS statuses mean?
- Speed
- 16.3 kn
- Course
- 320°
- Heading
- 318°
- Compass: course over ground 320°, heading 318°
- Arrow: course. Hull: heading. As broadcast on AIS.
Locator map: Natural Earth (public domain)
Voydar detected no port call in the last 30 days.
Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls below.
Pro shows Damgracht's track before the last 30 days. Voydar has recorded its port calls since June 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 156.9 mone tick every 25 m
Beam 22.9 mPlan outline, to scale
- Name
- Damgracht
- IMO numberWhat is an IMO number?
- 9420784
- MMSIWhat is an MMSI?
- 245955000
- Call signWhat is a call sign?
- PBOF
- Flag
- Netherlands
- Gross tonnageGross tonnage vs deadweight
- 13,558
- Deadweight (DWT)
- Source: Wikidata, record Q85987086. Added to Voydar on October 25, 2026. Licence: CC0 1.0.18,143 t
- Length overall
- 156.9 m
- Beam
- 22.9 m
- Year built
- 2009
- Passengers (maximum)
- Source: Wikidata, record Q85987086. Added to Voydar on October 25, 2026. Licence: CC0 1.0.1,040
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
- Rederij Damgracht(not linked to a company record)Source: ILT — Nederlands vlagregister (Netherlands flag register data) · reported · high confidence · retrieved Nov 19, 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, 2026JINLING SHIPYARD(not linked to a company record)Source: ILT — Nederlands vlagregister (Netherlands flag register data) · reported · high confidence · retrieved Nov 19, 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 Port HuenemeAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at Port HuenemeAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left HoustonAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at HoustonAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left Corpus ChristiAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at Corpus ChristiAIS-detected | Voydar port-call detector (AIS geofence) | |
| Reported departure from Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) | |
| Reported arrival at Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) | |
| Port State Control inspection at Port Arthur, Texas | USCG PSIX / CGMIX inspections | |
| Reported departure from Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) | |
| Reported arrival at Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) | |
| Inspection at New Orleans, Louisiana | USCG PSIX / CGMIX inspections | |
| Inspection at Port Arthur, Texas | USCG PSIX / CGMIX inspections | |
| Port State Control inspection at Belfast, Maine | USCG PSIX / CGMIX inspections | |
| Reported departure from Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) | |
| Reported arrival at Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) | |
| Inspection at Wilmington, North Carolina | USCG PSIX / CGMIX inspections | |
| Inspection at PORT ARANSAS, Texas | USCG PSIX / CGMIX inspections | |
| Inspection at CORPUS CHRISTI, Texas | USCG PSIX / CGMIX inspections | |
| Inspection at TEXAS CITY, Texas | USCG PSIX / CGMIX inspections | |
| Port State Control inspection at RIVIERA BEACH, Florida | USCG PSIX / CGMIX inspections | |
| Port State Control inspection at PHILADELPHIA, Pennsylvania | 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.
Incidents & investigations Authority-reported
Accident and incident reports by national investigation boards, and casualty warnings, that concern this ship. Each links to the original.
- Occurred Aug 21, 2022ACC · Cargo, Dry BulkNTSB marine investigations (CAROL)Port Arthur, TX, USA
Damgracht / AP Revelin, Port Arthur, TX, USA (NTSB DCA22FM038)Report published Aug 17, 2023
The National Transportation Safety Board determines that the probable cause of the collision between the cargo vessel Damgracht and the cargo vessel AP Revelin was the Damgracht’s loss of propulsion caused by an automatic shutdown of the main engine due to a false alarm, likely triggered by water vapor sensed by the oil mist detector shortly after engine maintenance was completed to replace a fail
Source: NTSB marine investigations (CAROL). Courtesy: National Transportation Safety Board. Licence: US Government work (17 U.S.C. §105), public domain.
Safety & inspections
| Date | Type | Port | Findings |
|---|---|---|---|
| Apr 28, 2025 | Vessel InspectionPSC | Port Arthur, Texas | clean |
| Aug 27, 2022 | Vessel Inspection | New Orleans, Louisiana | clean |
| Aug 21, 2022 | Vessel Inspection | Port Arthur, Texas | clean |
| May 31, 2022 | Vessel InspectionPSC | Belfast, Maine | clean |
| Mar 5, 2021 | Vessel Transfer Monitor | Wilmington, North Carolina | clean |
| Aug 29, 2020 | Boarding | PORT ARANSAS, Texas | clean |
| Aug 26, 2020 | Vessel Operational Control | CORPUS CHRISTI, Texas | clean |
| Jul 7, 2018 | Vessel Inspection | TEXAS CITY, Texas | clean |
| Apr 28, 2018 | Vessel InspectionPSC | RIVIERA BEACH, Florida | clean |
| Jul 17, 2017 | Vessel InspectionPSC | PHILADELPHIA, Pennsylvania | clean |
| May 4, 2016 | Vessel InspectionPSC | RIVIERA BEACH, Florida | clean |
| Sep 2, 2015 | Vessel InspectionPSC | PHILADELPHIA, Pennsylvania | clean |
| Sep 2, 2015 | Incident Investigation | WASHINGTON, District of Columbia | clean |
| Jan 14, 2015 | Vessel InspectionPSC | PHILADELPHIA, Pennsylvania | clean |
| Nov 13, 2012 | Vessel InspectionPSC | RIVIERA BEACH, Florida | clean |
| Aug 12, 2011 | Vessel InspectionPSC | Houston, Texas | clean |
| Jan 10, 2011 | Boarding | Port Arthur, Texas | clean |
| Oct 16, 2010 | Boarding | Savannah, Georgia | clean |
| Jun 5, 2010 | Vessel InspectionPSC | Brownsville, Texas | 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 | 13,766 t | 4,408 t | 156 days | 285 kg |
| 2019 | 3,010 t | 960 t | 35 days | 295 kg |
| 2020 | 6,355 t | 2,039 t | 74 days | 290 kg |
| 2021 | 9,402 t | 3,017 t | 97 days | 279 kg |
| 2022 | 7,005 t | 2,247 t | 80 days | 270 kg |
| 2023 | 3,296 t | 1,056 t | 38 days | 259 kg |
| 2024 | 28 t | 9 t | 1 day | 194 kg |
| 2025 | 10,187 t | 3,263 t | 123 days | 261 kg |
Technical efficiency: EEXI (5.92 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 sailed260.7 kg per nautical mile
- Lowest reportedHighest reported
93% 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 |
|---|---|---|---|
| Port Hueneme USNTD | Oct 5, 2026, 20:45 UTC | Oct 8, 2026, 00:53 UTC | 2 d 4 h |
| Houston USHOU | Sep 9, 2026, 20:40 UTC | Sep 14, 2026, 21:24 UTC | 5 d 0 h |
| Corpus Christi USCRP | Sep 8, 2026, 14:20 UTC | Sep 9, 2026, 01:05 UTC | 10 h 45 min |
| Baltimore USBAL | Aug 30, 2026, 12:59 UTC | Sep 2, 2026, 20:21 UTC | 3 d 7 h |
| Halifax CAHAL | Aug 24, 2026, 23:44 UTC | Aug 30, 2026, 02:32 UTC | 5 d 2 h |
| Koper SIKOP | Jul 25, 2026, 14:10 UTC | Jul 26, 2026, 20:54 UTC | 30 h 44 min |
| Genova ITGOA | Jun 14, 2026, 00:06 UTC | Jun 16, 2026, 21:27 UTC | 2 d 21 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 |
|---|---|---|---|---|
| Hong Kong HKHKG | Arrival | Dec 14, 2025, 09:32 UTC | SELA | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | Feb 27, 2023, 00:04 UTC | WL | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | May 10, 2021, 08:09 UTC | NLA | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| PALM BEACH HARBOR, FL | Arrival | May 10, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| PALM BEACH HARBOR, FL | Departure | May 6, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Wilmington USILG | Departure | Sep 3, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Wilmington USILG | Arrival | Sep 2, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| SEARSPORT HARBOR, ME | Departure | Aug 27, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| SEARSPORT HARBOR, ME | Arrival | Aug 23, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| CHESTER AREA, PA | Departure | Aug 6, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| CHESTER AREA, PA | Arrival | Aug 6, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| PALM BEACH HARBOR, FL | Departure | Aug 1, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: June 4, 2010.
Source: Marine Department, HKSAR Government — DATA.GOV.HK. Licence: DATA.GOV.HK Terms and Conditions.
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 |
|---|---|---|
| Oct 8, 2026, 00:33 UTC | Draught change Reported draught went from 6.3 m to 7.1 m while in port at Port Hueneme. 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.
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 Damgracht?
- Damgracht is a general cargo ship sailing under the flag of Netherlands, built in 2009 by CSC Jinling. The vessel is 156.9 m long with a beam of 22.9 m and has a gross tonnage of 13,558.
- Who is recorded as the owner or manager of Damgracht?
- Rederij Damgracht is recorded as Registered owner for Damgracht (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 Damgracht?
- Voydar has no matched sanctions record displayed for Damgracht 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. Damgracht has 19 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
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/9420784Cite this page
Damgracht. Voydar (voydar.com). https://www.voydar.com/vessel/9420784-damgracht. Retrieved November 20, 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.