Peak Sauda
General cargo ship · Netherlands · built 1999 · AIS Class A
In short
Peak Sauda (General cargo ship, Netherlands flag) was last seen on AIS on , under way at 10.2 kn, in the English Channel. Its crew-entered AIS destination is DUNKIRK, with an ETA of Oct 2, 2026, 06:00 UTC; its reported draught is 6.6 m (voyage report via AISstream.io global terrestrial AIS, received Oct 2, 2026, 00:29 UTC). Registered owner: Norwegian Fjord B.V. (source: ILT — Nederlands vlagregister (Netherlands flag register data)).
Current voyage: from Herre (departed Sep 29, 2026, 13:25 UTC) to DUNKIRK
- Vessel type
- General cargo ship
- Flag
- Netherlands
- Year built
- 1999
- Gross tonnage
- 2,999
- Size (length × beam)
- 95 m × 13 m
- Registered owner
- Norwegian Fjord B.V.
Watch this ship
Get an email when Peak Sauda arrives or leaves port, changes destination, name, flag or owner, or is sanctioned, detained or named in an official release.
We email you a link and a code. That creates a free account, no password or card, and follows Peak Sauda.
Free account, no card: follow up to 5 ships and ports. Plus follows 50, Pro 500.
By continuing you accept the Terms and the Privacy policy.

Last reported position
received- Position
- 51.1962° N, 1.7525° E
- Area
- English Channel
- StatusWhat do AIS statuses mean?
- Under way using engine
- Speed
- 10.2 kn
- Course
- 221°
- Heading
- 222°
Last 30 days: 4 port calls (Herre, Snekkevik, and Molstrevag).
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)
Try the live demo, no sign-upIdentity & particulars
- Name
- Peak Sauda
- IMO numberWhat is an IMO number?
- 9187136
- MMSIWhat is an MMSI?
- 245871000
- Call signWhat is a call sign?
- PHQA
- Flag
- Netherlands
- AIS ship type
- Cargo
- Gross tonnageGross tonnage vs deadweight
- 2,999
- Deadweight (DWT)
- Source: Wikidata, record Q56191659. Added to Voydar on September 23, 2026. Licence: CC0 1.0.5,049 t
- Length overall
- 95 m
- Beam
- 13.4 m
- Year built
- 1999
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
- Norwegian Fjord B.V.(not linked to a company record)Source: ILT — Nederlands vlagregister (Netherlands flag register data) · reported · confidence 0.9 · retrieved Oct 1, 2026
- Builder
- Source: Wikidata · reported · confidence 0.8 · retrieved Sep 22, 2026DAMEN SHIPYARD YICHANG(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 HerreAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at HerreAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left SnekkevikAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at SnekkevikAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left HerreAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at HerreAIS-detected | Voydar port-call detector (AIS geofence) | |
| Reported departure from ChicagoAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported arrival at ChicagoAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Port State Control inspection at MASSENA, New York | USCG PSIX / CGMIX inspections | |
| Reported departure from PonceAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Inspection at Willowbrook, Illinois | USCG PSIX / CGMIX inspections | |
| Inspection at MASSENA, New York | USCG PSIX / CGMIX inspections | |
| Inspection at MASSENA, New York | 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.
Safety & inspections
| Date | Type | Port | Findings |
|---|---|---|---|
| Oct 30, 2002 | Vessel InspectionPSC | MASSENA, New York | clean |
| Aug 31, 2001 | Vessel Inspection | Willowbrook, Illinois | clean |
| Aug 22, 2001 | Vessel Inspection | MASSENA, New York | clean |
| May 9, 2001 | Vessel Inspection | MASSENA, New York | 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.
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 |
|---|---|---|---|
| Herre NOHRR | Sep 29, 2026, 04:25 UTC | Sep 29, 2026, 13:25 UTC | 9 h 0 min |
| Snekkevik NOSNV | Sep 28, 2026, 16:54 UTC | Sep 29, 2026, 00:01 UTC | 7 h 7 min |
| Herre NOHRR | Sep 23, 2026, 17:45 UTC | Sep 25, 2026, 09:10 UTC | 39 h 25 min |
| Molstrevag NOMOV | Sep 14, 2026, 04:36 UTC | Sep 16, 2026, 17:45 UTC | 2 d 13 h |
| Porsgrunn NOPOR | Aug 31, 2026, 18:04 UTC | Sep 1, 2026, 21:01 UTC | 26 h 57 min |
| Porsgrunn NOPOR | Aug 29, 2026, 15:40 UTC | Aug 30, 2026, 14:48 UTC | 23 h 8 min |
| Herre NOHRR | Aug 29, 2026, 04:48 UTC | Aug 29, 2026, 15:31 UTC | 10 h 42 min |
| Dusavik NODUS | Aug 24, 2026, 22:12 UTC | Aug 24, 2026, 23:49 UTC | 1 h 37 min |
| Porsgrunn NOPOR | Aug 15, 2026, 20:08 UTC | Aug 16, 2026, 19:17 UTC | 23 h 9 min |
| Stadlandet NOSDT | Jul 7, 2026, 19:02 UTC | Jul 7, 2026, 20:16 UTC | 1 h 14 min |
| Molstrevag NOMOV | Jun 24, 2026, 03:38 UTC | Jun 30, 2026, 19:11 UTC | 6 d 15 h |
| Molstrevag NOMOV | Jun 16, 2026, 14:39 UTC | Jun 19, 2026, 02:09 UTC | 2 d 11 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 |
|---|---|---|---|---|
| Chicago USCHI | Departure | Nov 4, 2002(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Chicago USCHI | Arrival | Nov 4, 2002(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Ponce PRPSE | Departure | Aug 22, 2002(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Ponce PRPSE | Arrival | Aug 17, 2002(date only) | — | USACE foreign traffic vessel entrances & clearances |
| ELIZABETH RIVER (SOUTHERN BRANCH) VA | Departure | Aug 2, 2002(date only) | — | USACE foreign traffic vessel entrances & clearances |
| ELIZABETH RIVER (SOUTHERN BRANCH) VA | Arrival | Aug 2, 2002(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: August 2, 2002.
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 |
|---|---|---|
| Sep 29, 2026, 12:53 UTC | Draught change Reported draught went from 5.5 m to 6.6 m while in port at Herre. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Sep 28, 2026, 18:05 UTC | Draught change Reported draught went from 4 m to 5.5 m while in port at Snekkevik. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
Source: BarentsWatch AIS API. Contains data under NLOD made available by BarentsWatch. Licence: NLOD 2.0 (probable).
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 Peak Sauda now?
- Peak Sauda (General cargo ship, Netherlands flag) was last seen on AIS on Oct 2, 2026, 00:41 UTC, under way at 10.2 kn, in the English Channel. The crew-entered destination was DUNKIRK (voyage report via AISstream.io global terrestrial AIS, received Oct 2, 2026, 00:29 UTC). This report does not confirm the ship’s current route.
- What kind of ship is Peak Sauda?
- Peak Sauda is a general cargo ship sailing under the flag of Netherlands, built in 1999 by Damen Yichang Shipyard. The vessel is 95 m long with a beam of 13.4 m and has a gross tonnage of 2,999.
- Who is recorded as the owner or manager of Peak Sauda?
- Norwegian Fjord B.V. is recorded as Registered owner for Peak Sauda (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 Peak Sauda?
- Voydar has no matched sanctions record displayed for Peak Sauda from the OFAC SDN list, the UK Sanctions List, the Canadian autonomous sanctions list, the EU list of designated vessels and the New Zealand Russia Sanctions Register. Coverage may be incomplete; this is not sanctions clearance. Peak Sauda has 4 recorded Port State Control inspections. Detention and deficiency detail is not recorded for these inspections.
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/9187136Using 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.