Prabhu Puni
Bulk carrier · built 2002
In short
Prabhu Puni (Bulk carrier) has no AIS position on record with Seadar.
- Vessel type
- Bulk carrier
- Flag
- —
- Year built
- 2002
- Gross tonnage
- 40,002
- Size (length × beam)
- 225 m × 32 m
- Registered owner
- —
Watch this ship
Get an email when Prabhu Puni 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 Prabhu Puni.
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
No AIS position on record for this vessel. Identity and particulars are 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
- Prabhu Puni
- IMO numberWhat is an IMO number?
- 9224037
- MMSIWhat is an MMSI?
- —
- Call signWhat is a call sign?
- —
- Flag
- —
- Vessel type
- Bulk carrier
- Gross tonnageGross tonnage vs deadweight
- 40,002
- Deadweight (DWT)
- Source: Wikidata, record Q117023016. Added to Seadar on September 23, 2026. Licence: CC0 1.0.76,015 t
- Length overall
- 225 m
- Beam
- 32 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.
- Builder
- Source: Wikidata · reported · confidence 0.8 · retrieved Sep 22, 2026
Timeline
Dated events for this ship from every source Seadar holds, newest first. Each line names its source; derived items say how they were derived.
| Date | Event | Source |
|---|---|---|
| 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) | |
| 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) | |
| Reported departure from SeattleAuthority-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.
Port calls
Two kinds of evidence, kept apart: calls Seadar detected from the ship's AIS positions, and arrivals and departures published by port authorities and customs records.
Reported by authorities Authority-reported
| Port | Record | Date (UTC) | Berth | Source |
|---|---|---|---|---|
| Hong Kong HKHKG | Arrival | Mar 3, 2022, 08:41 UTC | URMA | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | Oct 29, 2018, 10:05 UTC | PT | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Seattle USSEA | Departure | Feb 28, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Seattle USSEA | Arrival | Feb 10, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| PORT OF SOUTH LOUISIANA (LA) | Departure | Nov 2, 2011(date only) | — | USACE foreign traffic vessel entrances & clearances |
| New Orleans USMSY | Arrival | Oct 25, 2011(date only) | — | USACE foreign traffic vessel entrances & clearances |
| PORT OF SOUTH LOUISIANA (LA) | Departure | Mar 20, 2011(date only) | — | USACE foreign traffic vessel entrances & clearances |
| New Orleans USMSY | Arrival | Feb 27, 2011(date only) | — | USACE foreign traffic vessel entrances & clearances |
| PORT OF KALAMA, WA | Departure | Oct 31, 2008(date only) | — | USACE foreign traffic vessel entrances & clearances |
| PORT OF KALAMA, WA | Arrival | Oct 25, 2008(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Tacoma USTIW | Departure | Nov 2, 2006(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Tacoma USTIW | Arrival | Oct 24, 2006(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: November 18, 2002.
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.
Frequently asked questions
- Where is Prabhu Puni now?
- Seadar has no displayable AIS position for Prabhu Puni in this profile. A coverage gap does not establish whether the ship is transmitting or where it is now.
- What kind of ship is Prabhu Puni?
- Prabhu Puni is a bulk carrier, built in 2002 by Tsuneishi Shipbuilding. The vessel is 225 m long with a beam of 32 m and has a gross tonnage of 40,002.
- What sanctions and inspection records does Seadar hold for Prabhu Puni?
- Seadar has no matched sanctions record displayed for Prabhu Puni 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. No matched inspection records are displayed for Prabhu Puni. Missing records do not establish whether the ship has been detained.
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/9224037Using 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.