Suomigracht
General cargo ship · Netherlands · built 2004 · AIS Class A
In short
Suomigracht (General cargo ship, Netherlands flag) was last seen on AIS on , moored, in the Baltic Sea. Its crew-entered AIS destination is FIRAU (Rauma (Raumo)); its reported draught is 8.2 m (voyage report via Digitraffic marine AIS, received Oct 5, 2026, 16:52 UTC). Registered owner: Rederij Suomigracht (source: ILT — Nederlands vlagregister (Netherlands flag register data)).
Current voyage: from Husum (departed Oct 2, 2026, 06:15 UTC) to FIRAU (Rauma (Raumo))
- Vessel type
- General cargo ship
- Flag
- Netherlands
- Year built
- 2004
- Gross tonnage
- 18,321
- Size (length × beam)
- 186 m × 26 m
- Registered owner
- Rederij Suomigracht
Watch this ship
Get an email when Suomigracht reaches Rauma (Raumo), and when it leaves port, changes destination, name, flag or owner, or is sanctioned, detained or named in an official release.
Free forever. No card. A free account follows up to 5 ships and ports.
In the news Authority-reported
Reports that name Suomigracht, newest first: the headline, the outlet and a link to the original. Voydar does not copy articles. A report tied to this ship by its IMO number in the text says so; a report that only prints the name is a possible match, because other ships can carry the same name.
Fixed and Moving Safety Zone; Vicinity of the M/V SUOMIGRACHT; Houston Ship Channel and Seabrook, TX
Federal Register documents API (maritime agencies)Jan 8, 2026Possible match · name only · 60% confidenceThe report names “SUOMIGRACHT”; Voydar matched it to this ship by the name alone. It may be about a different ship.
Source: Federal Register (federalregister.gov). Licence: US Government work (17 USC 105).
Headlines belong to their publishers; Voydar shows the headline and links to the original.
Last reported position
received- Position
- 61.1266° N, 21.433° E
- Area
- Baltic Sea
- StatusWhat do AIS statuses mean?
- Moored
- Speed
- 0 kn
- Course
- 86°
- Heading
- 262°
Last 30 days: 4 port calls (Husum, Nowe Warpno, Oskarshamn, and Kiel Canal).
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. New accounts include 14 days of Pro.
Try the live demo, no sign-upIdentity & particulars
- Name
- Suomigracht
- IMO numberWhat is an IMO number?
- 9288057
- MMSIWhat is an MMSI?
- 246100000
- Call signWhat is a call sign?
- PHBT
- Flag
- Netherlands
- Vessel type
- General cargo ship
- AIS ship type
- Cargo
- Gross tonnageGross tonnage vs deadweight
- 18,321
- Deadweight (DWT)
- Source: Wikidata, record Q4816179. Added to Voydar on September 23, 2026. Licence: CC0 1.0.23,660 t
- Length overall
- 186 m
- Beam
- 25.7 m
- Year built
- 2004
NetherlandsA 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 Suomigracht(not linked to a company record)Source: ILT — Nederlands vlagregister (Netherlands flag register data) · reported · confidence 0.9 · retrieved Oct 1, 2026
- ISM manager
- Source: EU MRV (THETIS-MRV) emissions · reporting years 2024–2025 · reported · confidence 0.9 · retrieved Oct 5, 2026
- Builder
- Source: Wikidata · reported · confidence 0.8 · retrieved Sep 22, 2026STOCZNIA SZCZECINSKA NOWA(not linked to a company record)Source: ILT — Nederlands vlagregister (Netherlands flag register data) · reported · confidence 0.9 · retrieved Oct 1, 2026
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 HusumAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at HusumAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left Nowe WarpnoAIS-detected | Voydar port-call detector (AIS geofence) | |
| Reported arrival at GdanskAuthority-reported | Urząd Morski w Gdyni: ships in port, expected and departing (Gdynia, Gdańsk) | |
| Arrived at Nowe WarpnoAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left OskarshamnAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at OskarshamnAIS-detected | Voydar port-call detector (AIS geofence) | |
| Inspection at Jacksonville, Florida | USCG PSIX / CGMIX inspections | |
| Inspection at TEXAS CITY, Texas | USCG PSIX / CGMIX inspections | |
| Inspection at Jacksonville, Florida | USCG PSIX / CGMIX inspections | |
| Port State Control inspection at Baltimore, Maryland | USCG PSIX / CGMIX inspections | |
| Inspection at Baltimore, Maryland | USCG PSIX / CGMIX inspections | |
| Port State Control inspection at Savannah, Georgia | USCG PSIX / CGMIX inspections | |
| Inspection at Houston, Texas | USCG PSIX / CGMIX inspections | |
| Inspection at Portsmouth, Virginia | USCG PSIX / CGMIX inspections | |
| Inspection at Baltimore, Maryland | USCG PSIX / CGMIX inspections | |
| Port State Control inspection at Jacksonville, Florida | USCG PSIX / CGMIX inspections | |
| Reported departure from ELIZABETH RIVER, VAAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported arrival at CHESAPEAKE BAY, MD AND VAAuthority-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.
Safety & inspections
| Date | Type | Port | Findings |
|---|---|---|---|
| Mar 17, 2026 | Vessel Inspection | Jacksonville, Florida | clean |
| Jul 15, 2025 | Vessel Operational Control | TEXAS CITY, Texas | clean |
| May 3, 2025 | Vessel Inspection | Jacksonville, Florida | clean |
| Mar 16, 2025 | Vessel InspectionPSC | Baltimore, Maryland | clean |
| Nov 2, 2024 | Vessel Operational Control | Baltimore, Maryland | clean |
| Feb 17, 2022 | Vessel InspectionPSC | Savannah, Georgia | clean |
| Apr 23, 2020 | Vessel Operational Control | Houston, Texas | clean |
| Mar 12, 2020 | Boarding | Portsmouth, Virginia | clean |
| Mar 5, 2020 | Vessel Inspection | Baltimore, Maryland | clean |
| Feb 19, 2019 | Vessel InspectionPSC | Jacksonville, Florida | clean |
| Jan 24, 2018 | Vessel InspectionPSC | SOUTH PORTLAND, Maine | clean |
| Jun 8, 2017 | Vessel Operational Control | Portsmouth, Virginia | clean |
| Jun 8, 2017 | Vessel Operational Control | Jacksonville, Florida | clean |
| Apr 9, 2017 | Vessel InspectionPSC | Woods Hole, Massachusetts | clean |
| Mar 22, 2016 | Vessel InspectionPSC | Baltimore, Maryland | clean |
| Oct 16, 2015 | Vessel Operational Control | Baltimore, Maryland | clean |
| Oct 14, 2015 | Vessel Inspection | Baltimore, Maryland | clean |
| Feb 28, 2015 | Vessel InspectionPSC | Baltimore, Maryland | clean |
| Jan 9, 2014 | Vessel InspectionPSC | PHILADELPHIA, Pennsylvania | clean |
| Jan 7, 2014 | Vessel Operational Control | PHILADELPHIA, Pennsylvania | 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 | 17,205 t | 5,517 t | 162 days | 296 kg |
| 2019 | 19,759 t | 6,335 t | 201 days | 300 kg |
| 2020 | 21,406 t | 6,863 t | 211 days | 307 kg |
| 2021 | 20,374 t | 6,528 t | 199 days | 318 kg |
| 2022 | 20,092 t | 6,431 t | 168 days | 331 kg |
| 2023 | 20,416 t | 6,539 t | 199 days | 309 kg |
| 2024 | 16,381 t | 5,223 t | 151 days | 314 kg |
| 2025 | 16,066 t | 5,135 t | 158 days | 292 kg |
Technical efficiency: EEXI (5.73 gCO₂/t·nm). Source: European Commission / EMSA THETIS-MRV (EU Regulation 2015/757). Covers voyages to, from and within the EU/EEA.
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 |
|---|---|---|---|
| Husum SEHUS | Oct 1, 2026, 06:44 UTC | Oct 2, 2026, 06:15 UTC | 23 h 31 min |
| Nowe Warpno PLNWA | Sep 27, 2026, 02:18 UTC | Sep 29, 2026, 19:50 UTC | 2 d 17 h |
| Oskarshamn SEOSK | Sep 25, 2026, 04:50 UTC | Sep 26, 2026, 04:50 UTC | 24 h 0 min |
| Kiel Canal DECKL | Sep 23, 2026, 14:24 UTC | Sep 23, 2026, 16:51 UTC | 2 h 27 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 |
|---|---|---|---|---|
| Gdansk PLGDN | Arrival | Sep 27, 2026, 02:35 UTC | Oliwskie | Urząd Morski w Gdyni: ships in port, expected and departing (Gdynia, Gdańsk) |
| ELIZABETH RIVER, VA | Departure | Dec 14, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| CHESAPEAKE BAY, MD AND VA | Arrival | Dec 11, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Philadelphia USPHL | Arrival | Dec 6, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Philadelphia USPHL | Departure | Dec 6, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Savannah USSAV | Departure | Oct 21, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Savannah USSAV | Arrival | Oct 18, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Pensacola USPNS | Departure | Oct 12, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Pensacola USPNS | Arrival | Oct 11, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Port Arthur USPOA | Departure | Oct 7, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Port Arthur USPOA | Arrival | Oct 6, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| PALM BEACH HARBOR, FL | Arrival | Oct 2, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: December 22, 2004.
Source: Urząd Morski w Gdyni (www.umgdy.gov.pl); processed by Seadar (times converted to UTC, IMO checksum-validated). The retrieval date is shown with the data. Licence: Polish PSI reuse (ustawa o otwartych danych), conditions: cite source, date, processing.
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 2, 2026, 04:05 UTC | Draught change Reported draught went from 7.6 m to 8.2 m while in port at Husum. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Sep 29, 2026, 18:41 UTC | Draught change Reported draught went from 7.1 m to 7.6 m while in port at Nowe Warpno. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
Source: Fintraffic / digitraffic.fi, license CC 4.0 BY. Licence: CC BY 4.0.
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
- Where is Suomigracht now?
- Suomigracht (General cargo ship, Netherlands flag) was last seen on AIS on Oct 5, 2026, 16:51 UTC, moored, in the Baltic Sea. The crew-entered destination was FIRAU (voyage report via Digitraffic marine AIS, received Oct 5, 2026, 16:52 UTC). This report does not confirm the ship’s current route.
- What kind of ship is Suomigracht?
- Suomigracht is a general cargo ship sailing under the flag of Netherlands, built in 2004 by Szczecin Shipyard. The vessel is 186 m long with a beam of 25.7 m and has a gross tonnage of 18,321.
- Who is recorded as the owner or manager of Suomigracht?
- Rederij Suomigracht is recorded as Registered owner for Suomigracht (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 Suomigracht?
- Voydar has no matched sanctions record displayed for Suomigracht 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. Suomigracht has 38 recorded Port State Control inspections. Detention and deficiency detail is not recorded for these inspections.
Sister ships
Likely sister ships: built by Szczecin Shipyard, same type, gross tonnage within 2.5% and length within 1.5% of this ship's.
Neighbouring IMO numbers
IMO numbers are issued in sequence. These are the nearest numbers below and above this ship's that have a full Voydar profile.
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/9288057Using 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.