SBI Perseus
Bulk carrier · built 2016
In short
SBI Perseus (Bulk carrier) has no AIS position on record with Voydar.
- Vessel type
- Bulk carrier
- Flag
- —
- Year built
- 2016
- Gross tonnage
- 36,336
- Size (length × beam)
- 200 m × 32 m
- Registered owner
- —
Watch this ship
Get an email when SBI Perseus 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 SBI Perseus.
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
- SBI Perseus
- IMO numberWhat is an IMO number?
- 9712151
- MMSIWhat is an MMSI?
- —
- Call signWhat is a call sign?
- —
- Flag
- —
- Gross tonnageGross tonnage vs deadweight
- 36,336
- Deadweight (DWT)
- Source: Wikidata, record Q84255067. Added to Voydar on September 23, 2026. Licence: CC0 1.0.62,235 t
- Length overall
- 199.9 m
- Beam
- 32.3 m
- Year built
- 2016
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 Voydar holds, newest first. Each line names its source; derived items say how they were derived.
| Date | Event | Source |
|---|---|---|
| Reported departure from ELIZABETH RIVER (SOUTHERN BRANCH) VAAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported arrival at ELIZABETH RIVER (SOUTHERN BRANCH) VAAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported departure from HUDSON RIVER, NY, MOUTH OF SPUYTEN DUYVIL CREEK (HARLEM RIVER) TO WATERFORD, NYAuthority-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.
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 | 3,650 t | 1,166 t | 57 days | 244 kg |
| 2019 | 5,187 t | 1,653 t | 72 days | 285 kg |
| 2022 | 463 t | 147 t | 4 days | 365 kg |
Technical efficiency: EEDI (4.1 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.
Reported by authorities Authority-reported
| Port | Record | Date (UTC) | Berth | Source |
|---|---|---|---|---|
| ELIZABETH RIVER (SOUTHERN BRANCH) VA | Departure | Oct 1, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| ELIZABETH RIVER (SOUTHERN BRANCH) VA | Arrival | Sep 24, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HUDSON RIVER, NY, MOUTH OF SPUYTEN DUYVIL CREEK (HARLEM RIVER) TO WATERFORD, NY | Departure | Sep 18, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HUDSON RIVER, NY, MOUTH OF SPUYTEN DUYVIL CREEK (HARLEM RIVER) TO WATERFORD, NY | Arrival | Sep 13, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Savannah USSAV | Departure | Jul 15, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Savannah USSAV | Arrival | Jul 14, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| DELAWARE RIVER AT CAMDEN, NJ (INCLUDED IN DELAWARE RIVER, PHILADELPHIA, PA TO THE SEA) | Departure | Jul 9, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Philadelphia USPHL | Arrival | Jul 9, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: July 9, 2016.
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 SBI Perseus now?
- Voydar has no displayable AIS position for SBI Perseus in this profile. A coverage gap does not establish whether the ship is transmitting or where it is now.
- What kind of ship is SBI Perseus?
- SBI Perseus is a bulk carrier, built in 2016 by Chengxi Shipyard. The vessel is 199.9 m long with a beam of 32.3 m and has a gross tonnage of 36,336.
- What sanctions and inspection records does Voydar hold for SBI Perseus?
- Voydar has no matched sanctions record displayed for SBI Perseus 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 SBI Perseus. 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/9712151Using 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.