Jasmine 201
Bulk carrier · built 1999
In short
Jasmine 201 (Bulk carrier) has no AIS position on record with Seadar.
- Vessel type
- Bulk carrier
- Flag
- —
- Year built
- 1999
- Gross tonnage
- 38,526
- Size (length × beam)
- 225 m × 32 m
- Registered owner
- —
Watch this ship
Get an email when Jasmine 201 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 Jasmine 201.
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
- Jasmine 201
- IMO numberWhat is an IMO number?
- 9207417
- MMSIWhat is an MMSI?
- —
- Call signWhat is a call sign?
- —
- Flag
- —
- Vessel type
- Bulk carrier
- Gross tonnageGross tonnage vs deadweight
- 38,526
- Deadweight (DWT)
- Source: Wikidata, record Q117022743. Added to Seadar on September 23, 2026. Licence: CC0 1.0.73,807 t
- Length overall
- 225 m
- Beam
- 32 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.
- 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 PORT OF SOUTH LOUISIANA (LA)Authority-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 | Sep 18, 2022, 13:46 UTC | PT | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Feb 8, 2022, 20:29 UTC | PT | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| PORT OF SOUTH LOUISIANA (LA) | Departure | Aug 23, 2012(date only) | — | USACE foreign traffic vessel entrances & clearances |
| PORT OF SOUTH LOUISIANA (LA) | Arrival | Aug 19, 2012(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Seattle USSEA | Departure | Dec 9, 2011(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Seattle USSEA | Arrival | Nov 27, 2011(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Seattle USSEA | Departure | Jul 22, 2011(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Seattle USSEA | Arrival | Jul 20, 2011(date only) | — | USACE foreign traffic vessel entrances & clearances |
| PORT OF KALAMA, WA | Departure | Oct 22, 2010(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Longview USLOG | Arrival | Oct 18, 2010(date only) | — | USACE foreign traffic vessel entrances & clearances |
| PORT OF SOUTH LOUISIANA (LA) | Departure | Jan 5, 2009(date only) | — | USACE foreign traffic vessel entrances & clearances |
| PORT OF PLAQUEMINES, LA | Arrival | Jan 3, 2009(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: October 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 Jasmine 201 now?
- Seadar has no displayable AIS position for Jasmine 201 in this profile. A coverage gap does not establish whether the ship is transmitting or where it is now.
- What kind of ship is Jasmine 201?
- Jasmine 201 is a bulk carrier, built in 1999 by Tsuneishi Shipbuilding. The vessel is 225 m long with a beam of 32 m and has a gross tonnage of 38,526.
- What sanctions and inspection records does Seadar hold for Jasmine 201?
- Seadar has no matched sanctions record displayed for Jasmine 201 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 Jasmine 201. 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/9207417Using 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.